From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Santosh Shukla <sshukla@mvista.com>, david.marchand@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 1/8] eal: pci: add api to rd/wr pci bar region
Date: Mon, 1 Feb 2016 21:48:54 +0800 [thread overview]
Message-ID: <20160201134854.GE4257@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1454091717-32251-1-git-send-email-sshukla@mvista.com>
On Fri, Jan 29, 2016 at 11:51:50PM +0530, Santosh Shukla wrote:
> Introducing below api for pci bar region rd/wr.
> Api's are:
> - rte_eal_pci_read_bar
> - rte_eal_pci_write_bar
>
> Signed-off-by: Santosh Shukla <sshukla@mvista.com>
> ---
> v5-->v6:
> - update api infor in rte_eal_version.map file
> suggested by david manchand.
>
> lib/librte_eal/bsdapp/eal/eal_pci.c | 19 ++++++++++++
> lib/librte_eal/bsdapp/eal/rte_eal_version.map | 3 ++
> lib/librte_eal/common/include/rte_pci.h | 38 +++++++++++++++++++++++
> lib/librte_eal/linuxapp/eal/eal_pci.c | 34 ++++++++++++++++++++
> lib/librte_eal/linuxapp/eal/eal_pci_init.h | 6 ++++
> lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 28 +++++++++++++++++
> lib/librte_eal/linuxapp/eal/rte_eal_version.map | 3 ++
> 7 files changed, 131 insertions(+)
>
> diff --git a/lib/librte_eal/bsdapp/eal/eal_pci.c b/lib/librte_eal/bsdapp/eal/eal_pci.c
> index 95c32c1..2e535ea 100644
> --- a/lib/librte_eal/bsdapp/eal/eal_pci.c
> +++ b/lib/librte_eal/bsdapp/eal/eal_pci.c
...
> +int rte_eal_pci_read_bar(const struct rte_pci_device *device,
> + void *buf, size_t len, off_t offset,
> + int bar_idx)
> +
> +{
> + const struct rte_intr_handle *intr_handle = &device->intr_handle;
I'd suggest to reference this var inside pci_vfio_read/write_bar(), and
pass device as the parmater instead.
> +
> + switch (device->kdrv) {
> + case RTE_KDRV_VFIO:
> + return pci_vfio_read_bar(intr_handle, buf, len,
> + offset, bar_idx);
> + default:
> + RTE_LOG(ERR, EAL, "write bar not supported by driver\n");
^^^^^
typo.
BTW, I have a question about this API. Obviously, reading/writing bar
space is supported with UIO (when memory resource is mmapped). And I
know why you introduced such 2 APIs, for reading IO bar.
So, here is the question: what are the 2 APIs for, for being gerneric
APIs to read/write bar spaces, or just to read IO bar spaces? If it's
former, the message is wrong; if it's later, you may better rename it
to rte_eal_pci_read/write_io_bar()?
David, what do you think of that?
> + return -1;
> + }
> +}
> +
...
> +int
> +pci_vfio_read_bar(const struct rte_intr_handle *intr_handle,
> + void *buf, size_t len, off_t offs, int bar_idx)
> +{
> + if (bar_idx < VFIO_PCI_BAR0_REGION_INDEX
> + || bar_idx > VFIO_PCI_BAR5_REGION_INDEX) {
A minor nit: it's more nature to put the '||' at the end of expression,
instead of at the front:
if (bar_idx < VFIO_PCI_BAR0_REGION_INDEX ||
bar_idx > VFIO_PCI_BAR5_REGION_INDEX) {
--yliu
next prev parent reply other threads:[~2016-02-01 13:47 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 ` 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 ` Yuanhan Liu [this message]
2016-02-02 4:14 ` [dpdk-dev] [PATCH v6 1/8] eal: pci: add api to rd/wr pci bar region 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
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=20160201134854.GE4257@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=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).