From: Santosh Shukla <sshukla@mvista.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v7 0/4] Add virtio support for arm/arm64
Date: Sun, 7 Feb 2016 19:21:04 +0530 [thread overview]
Message-ID: <1454853068-14621-1-git-send-email-sshukla@mvista.com> (raw)
Hi,
Patch series to allow access to virtio using vfio interface.
Tested for vfio-noiommu mode for x86_64/arm64{thunderX} platform.
patch series builds successfully for armv7/v8/x86_64/i686.
Note: Rebased on David(s) recent patch series titled "rework virtio for ioport".
Step to enable vfio-noiommu mode:
- modprobe vfio-pci
echo 1 > /sys/module/vfio/parameters/enable_unsafe_*
- then bind
./tools/dpdk_nic_bind.py -b vfio-pci 0000:00:03.0
- Testpmd application to try out for:
./app/testpmd -c 0x3 -n 4 -- -i --portmask=0x0 --nb-cores=1 --port-topology=chained
On host side ping to tapX interface and observe pkt_cnt on guest side.
v6-->v7:
- added support for vfio map/umap/rd/wr method for linuxapp.
- Tested for x86 / arm64{thunderX} vfio mode both.
v5-->v6:
- Removed KDRV_NOIOMMU mode
- patchseries aligned in topic-wise ordered way
- Introduced virtio_io.h; has in/out api, and header file sys/io.h
- Renamed virtio_vfio_rw.h to virtio_vfio_io.h, renamed ioport_in/out{b,w,l} to
vfio_in/out{b,w,l}
v4 --> v5:
- Introducing RTE_KDRV_VFIO_NOIOMMU driver mode
- Incorporated v4 review comments, Pl. refer each patchset for review change.
For older version(v4.. v1) patch history, refer [2].
Thanks.
[1] https://github.com/sshukla82/dpdk.git branch virtio-vfio-v6-review
[2] http://comments.gmane.org/gmane.comp.networking.dpdk.devel/31402
Santosh Shukla (4):
eal/linux: never check iopl for arm
virtio: Introduce config RTE_VIRTIO_INC_VECTOR
eal/linux: vfio: ignore mapping for ioport region
eal/linux: vfio: add pci ioport support
config/common_linuxapp | 1 +
config/defconfig_arm-armv7a-linuxapp-gcc | 4 +-
config/defconfig_arm64-armv8a-linuxapp-gcc | 4 +-
config/defconfig_i686-native-linuxapp-gcc | 1 +
config/defconfig_i686-native-linuxapp-icc | 1 +
drivers/net/virtio/Makefile | 2 +-
drivers/net/virtio/virtio_rxtx.c | 16 ++++++-
drivers/net/virtio/virtio_rxtx.h | 2 +
lib/librte_eal/linuxapp/eal/eal.c | 2 +
lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 68 ++++++++++++++++++++++------
10 files changed, 83 insertions(+), 18 deletions(-)
--
1.7.9.5
next reply other threads:[~2016-02-07 13:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 13:51 Santosh Shukla [this message]
2016-02-07 13:51 ` [dpdk-dev] [PATCH v7 1/4] eal/linux: never check iopl for arm Santosh Shukla
2016-02-18 5:26 ` Santosh Shukla
2016-02-07 13:51 ` [dpdk-dev] [PATCH v7 2/4] virtio: Introduce config RTE_VIRTIO_INC_VECTOR Santosh Shukla
2016-02-07 21:25 ` Thomas Monjalon
2016-02-08 5:45 ` Santosh Shukla
[not found] ` <CAAyOgsZO+6+kFZZZM203fPR3AmVYB0v7j3-f+DawZOCuR-AVvQ@mail.gmail.com>
[not found] ` <20160215105743.GB21426@yliu-dev.sh.intel.com>
[not found] ` <CAAyOgsaT5TcsPfum8x6yzAJAz=5N+c5QebEn7KCyJn7oK=VMsw@mail.gmail.com>
2016-02-16 3:05 ` Yuanhan Liu
2016-02-19 4:46 ` Santosh Shukla
2016-02-19 6:42 ` Yuanhan Liu
2016-02-22 2:03 ` Xie, Huawei
2016-02-22 4:14 ` Santosh Shukla
2016-02-22 10:22 ` Thomas Monjalon
2016-02-07 13:51 ` [dpdk-dev] [PATCH v7 3/4] eal/linux: vfio: ignore mapping for ioport region Santosh Shukla
2016-02-08 9:15 ` Burakov, Anatoly
2016-02-18 5:26 ` Santosh Shukla
2016-02-07 13:51 ` [dpdk-dev] [PATCH v7 4/4] eal/linux: vfio: add pci ioport support Santosh Shukla
2016-02-08 8:51 ` David Marchand
2016-02-08 9:40 ` Santosh Shukla
2016-02-21 14:17 ` [dpdk-dev] [PATCH v9 0/3] Add virtio support for arm/arm64 Santosh Shukla
2016-02-21 14:17 ` [dpdk-dev] [PATCH v9 1/3] eal/linux: never check iopl for arm Santosh Shukla
2016-02-21 14:18 ` [dpdk-dev] [PATCH v9 2/3] eal/linux: vfio: ignore mapping for ioport region Santosh Shukla
2016-02-21 14:18 ` [dpdk-dev] [PATCH v9 3/3] eal/linux: vfio: add pci ioport support Santosh Shukla
2016-02-22 5:41 ` [dpdk-dev] [PATCH v9 0/3] Add virtio support for arm/arm64 Yuanhan Liu
2016-02-23 6:11 ` Santosh Shukla
2016-02-24 10:45 ` 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=1454853068-14621-1-git-send-email-sshukla@mvista.com \
--to=sshukla@mvista.com \
--cc=dev@dpdk.org \
/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).