From: David Marchand <david.marchand@6wind.com>
To: Santosh Shukla <sshukla@mvista.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v8 4/4] eal/linux: vfio: add pci ioport support
Date: Tue, 9 Feb 2016 10:04:22 +0100 [thread overview]
Message-ID: <CALwxeUvspVAbb+wu9MM_VGRG3W769FJWU3jd0rei6HnSBUZWWw@mail.gmail.com> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E45123697820C6E32@IRSMSX109.ger.corp.intel.com>
On Mon, Feb 8, 2016 at 3:13 PM, Burakov, Anatoly
<anatoly.burakov@intel.com> wrote:
>> Include vfio map/rd/wr support for pci ioport.
>>
>> Signed-off-by: Santosh Shukla <sshukla@mvista.com>
>> ---
>> v7->v8:
>> - Remove rte_pci_ioport malloc and rte_free()/unmap() func from v7.
>> - removed umap from git header.
>>
>> lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 36 ++++++++++++++++++-------
>> ---
>> 1 file changed, 24 insertions(+), 12 deletions(-)
>>
>> diff --git a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
>> b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
>> index 4832313..9571ed8 100644
>> --- a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
>> +++ b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
>> @@ -74,6 +74,7 @@ EAL_REGISTER_TAILQ(rte_vfio_tailq)
>> #define VFIO_GROUP_FMT "/dev/vfio/%u"
>> #define VFIO_NOIOMMU_GROUP_FMT "/dev/vfio/noiommu-%u"
>> #define VFIO_GET_REGION_ADDR(x) ((uint64_t) x << 40ULL)
>> +#define VFIO_GET_REGION_IDX(x) (x >> 40)
>>
>> /* per-process VFIO config */
>> static struct vfio_config vfio_cfg;
>> @@ -999,30 +1000,41 @@ int
>> pci_vfio_ioport_map(struct rte_pci_device *dev, int bar,
>> struct rte_pci_ioport *p)
>> {
>> - RTE_SET_USED(dev);
>> - RTE_SET_USED(bar);
>> - RTE_SET_USED(p);
>> - return -1;
>> + if (bar < VFIO_PCI_BAR0_REGION_INDEX ||
>> + bar > VFIO_PCI_BAR5_REGION_INDEX) {
>> + RTE_LOG(ERR, EAL, "invalid bar (%d)!\n", bar);
>> + return -1;
>> + }
>> +
>> + p->dev = dev;
>> + p->offset = VFIO_GET_REGION_ADDR(bar);
>> + return 0;
>> }
>>
I still think we don't need this p->dev = dev.
But that's not important.
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Acked-by: David Marchand <david.marchand@6wind.com>
--
David Marchand
next prev parent reply other threads:[~2016-02-09 9:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000-cover-letter.patch>
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 1/8] eal: pci: add api to rd/wr pci bar region Santosh Shukla
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 2/8] linuxapp/vfio: ignore mapping for ioport region Santosh Shukla
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 3/8] eal/linux: never check iopl for arm Santosh Shukla
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 4/8] virtio: Introduce config RTE_VIRTIO_INC_VECTOR Santosh Shukla
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 5/8] virtio: move io header and api from virtio_pci.h Santosh Shukla
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 6/8] virtio: add vfio api to rd/wr ioport space Santosh Shukla
2016-02-01 12:48 ` Yuanhan Liu
2016-02-02 4:30 ` Santosh Shukla
2016-02-02 5:19 ` Yuanhan Liu
2016-02-02 6:02 ` Santosh Shukla
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 7/8] virtio: extend pci rw api for vfio Santosh Shukla
2016-01-29 18:21 ` [dpdk-dev] [PATCH v6 8/8] virtio: do not parse if interface is vfio Santosh Shukla
2016-02-01 13:48 ` [dpdk-dev] [PATCH v6 1/8] eal: pci: add api to rd/wr pci bar region Yuanhan Liu
2016-02-02 4:14 ` Santosh Shukla
2016-02-02 5:43 ` Yuanhan Liu
2016-02-02 5:50 ` David Marchand
2016-02-02 8:49 ` Yuanhan Liu
2016-02-02 15:51 ` Santosh Shukla
2016-02-02 16:18 ` Santosh Shukla
2016-02-03 9:50 ` Santosh Shukla
2016-02-03 11:50 ` Yuanhan Liu
2016-02-05 17:56 ` David Marchand
2016-02-03 11:43 ` Yuanhan Liu
2016-02-02 7:00 ` Santosh Shukla
2016-02-02 7:01 ` Santosh Shukla
2016-02-08 10:03 ` [dpdk-dev] [PATCH v8 3/4] eal/linux: vfio: ignore mapping for ioport region Santosh Shukla
2016-02-08 10:03 ` [dpdk-dev] [PATCH v8 4/4] eal/linux: vfio: add pci ioport support Santosh Shukla
2016-02-08 14:13 ` Burakov, Anatoly
2016-02-09 9:04 ` David Marchand [this message]
2016-02-18 5:25 ` Santosh Shukla
2016-02-18 14:00 ` Thomas Monjalon
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=CALwxeUvspVAbb+wu9MM_VGRG3W769FJWU3jd0rei6HnSBUZWWw@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--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).