From: "Pei, Andy" <andy.pei@intel.com>
To: David Marchand <david.marchand@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Xia, Chenbo" <chenbo.xia@intel.com>
Subject: RE: [PATCH] net/virtio: remove address width limit for modern devices
Date: Fri, 10 Mar 2023 06:11:20 +0000 [thread overview]
Message-ID: <DM5PR11MB1739EB29BB184F7587E777528FBA9@DM5PR11MB1739.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zESX438wNqayxfVv2OEFvzt+cLu2mDPTz9LBA_fTLVfw@mail.gmail.com>
Hi David,
The case is just want to enable ASAN to scan customer developed code.
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, March 9, 2023 11:08 PM
> To: Maxime Coquelin <maxime.coquelin@redhat.com>
> Cc: dev@dpdk.org; Pei, Andy <andy.pei@intel.com>; Xia, Chenbo
> <Chenbo.Xia@intel.com>
> Subject: Re: [PATCH] net/virtio: remove address width limit for modern
> devices
>
> On Thu, Mar 9, 2023 at 3:59 PM Maxime Coquelin
> <maxime.coquelin@redhat.com> wrote:
> >
> > Hi David,
> >
> > On 3/9/23 15:36, David Marchand wrote:
> > > Modern devices don't have the same limitation as legacy devices,
> > > because vring addresses are not configured using a 32-bit register.
> > >
> >
> > Do we want to backport it? This is a bug in my opinion.
>
> I wonder, this is the first time we see some report about this issue.
> I'd like to first get more details from Andy who reported this issue, like in
> which setup / condition this problem was caught.
>
>
> --
> David Marchand
next prev parent reply other threads:[~2023-03-10 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 14:36 David Marchand
2023-03-09 14:59 ` Maxime Coquelin
2023-03-09 15:08 ` David Marchand
2023-03-10 6:11 ` Pei, Andy [this message]
2023-03-10 6:10 ` Pei, Andy
2023-03-10 8:07 ` Xia, Chenbo
2023-03-14 8:53 ` [PATCH v2] " David Marchand
2023-03-16 14:46 ` Maxime Coquelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM5PR11MB1739EB29BB184F7587E777528FBA9@DM5PR11MB1739.namprd11.prod.outlook.com \
--to=andy.pei@intel.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).