From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Santosh Shukla <sshukla@mvista.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
dev@dpdk.org, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v6 08/11] eal: pci: introduce RTE_KDRV_VFIO_NOIOMMUi driver mode
Date: Wed, 27 Jan 2016 16:39:23 +0100 [thread overview]
Message-ID: <25509182.RtDY3IvNbk@xps13> (raw)
In-Reply-To: <CAAyOgsakEwkgUdNMFqbJgSTv0QKgVW_G9p90WA3F4bGEy2iHxg@mail.gmail.com>
2016-01-27 21:02, Santosh Shukla:
> 1. virtio currently works for vfio+noiommu and likely will work for
> vfio+iommu in near future.
> 2. So remove __noiommu suffix and always use default.
> 3. Introduce vfio resource parsing global function, That function
> suppose to do parsing for default vfio case and for vfio-noiommu case.
> This function will be used by pmd drivers for resource parsing purpose
> example virtio.
>
> Yuan won't be happy with 3) I guess, because he wanted to get rid of
> interface parsing from pmd driver.
>
> Thomas, if 1/2/3/ addresses your concern then I'll spin the series,
I agree with 1/ and 2/.
Please, could you explain why 3/ is needed?
next prev parent reply other threads:[~2016-01-27 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 18:57 Santosh Shukla
2016-01-21 10:32 ` David Marchand
2016-01-21 11:13 ` Santosh Shukla
2016-01-21 11:28 ` Thomas Monjalon
2016-01-21 12:04 ` Santosh Shukla
2016-01-21 14:46 ` Thomas Monjalon
2016-01-21 17:17 ` Santosh Shukla
2016-01-25 15:29 ` Thomas Monjalon
2016-01-26 10:26 ` Santosh Shukla
2016-01-26 13:00 ` Thomas Monjalon
2016-01-26 14:05 ` Santosh Shukla
2016-01-26 14:28 ` Thomas Monjalon
2016-01-26 16:21 ` Santosh Shukla
2016-01-27 10:41 ` Santosh Shukla
2016-01-27 15:32 ` Santosh Shukla
2016-01-27 15:39 ` Thomas Monjalon [this message]
2016-01-27 15:56 ` Santosh Shukla
2016-01-27 17:18 ` Santosh Shukla
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=25509182.RtDY3IvNbk@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alex.williamson@redhat.com \
--cc=dev@dpdk.org \
--cc=mst@redhat.com \
--cc=sshukla@mvista.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).