From: David Marchand <david.marchand@redhat.com>
To: "Pei, Andy" <andy.pei@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Volodymyr Fialko <vfialko@marvell.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>
Subject: Re: enable ASAN issue when run on a Virtio PCI device
Date: Thu, 9 Mar 2023 15:43:42 +0100 [thread overview]
Message-ID: <CAJFAV8xFVZb9bzh4w8c6c1xvfzLRMTYz5KsaZqAw1Y6dh7DoBw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8x+K9NXz+9hr2P+Wo-2OKBzu_V_Xm2onrtbTRS9nAuCGg@mail.gmail.com>
On Thu, Mar 9, 2023 at 2:44 PM David Marchand <david.marchand@redhat.com> wrote:
> On Thu, Mar 9, 2023 at 2:05 PM Pei, Andy <andy.pei@intel.com> wrote:
> > I am running testpmd on a virtio PCI device, and encounter this issue when enable ASAN.
> >
> > I got this ERROR,
> >
> > check_vq_phys_addr_ok(): vring address shouldn't be above 16TB!
> > virtio_init_queue(): setup_queue failed
> > eth_virtio_pci_init(): Failed to init virtio device
> > EAL: Releasing PCI mapped resource for 0000:18:00.0
> > EAL: Calling pci_unmap_resource for 0000:18:00.0 at 0x7fc9c0000000
> > EAL: Calling pci_unmap_resource for 0000:18:00.0 at 0x7fc197a75000
> > EAL: Requested device 0000:18:00.0 cannot be used
> > EAL: Bus (pci) probe failed.
> > TELEMETRY: No legacy callbacks, legacy socket not created
> > testpmd: No probed ethernet devices
> >
> >
> > How to fix this issue when ASAN is enabled, huge pages are all mapped to very high address, adding “--base-virtaddr” args does not works.
>
> I am not able to reproduce your issue.
> You'll have to share more details about your setup.
Actually, relooking at the code, I think we can do something on virtio
side, for modern devices and Maxime seemed to agree.
Can you have a try with:
https://patchwork.dpdk.org/project/dpdk/patch/20230309143604.2354288-1-david.marchand@redhat.com/
Thanks.
--
David Marchand
next prev parent reply other threads:[~2023-03-09 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 13:04 Pei, Andy
2023-03-09 13:44 ` David Marchand
2023-03-09 14:43 ` David Marchand [this message]
2023-03-10 6:05 ` Pei, Andy
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=CAJFAV8xFVZb9bzh4w8c6c1xvfzLRMTYz5KsaZqAw1Y6dh7DoBw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=andy.pei@intel.com \
--cc=chenbo.xia@intel.com \
--cc=drc@linux.vnet.ibm.com \
--cc=maxime.coquelin@redhat.com \
--cc=users@dpdk.org \
--cc=vfialko@marvell.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).