From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>, <gowrishankar.m@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH] vfio: fix compile on older kernels
Date: Wed, 22 Mar 2017 10:16:17 +0530 [thread overview]
Message-ID: <467aba33-3bcb-0d1f-c762-4281b2f5a870@nxp.com> (raw)
In-Reply-To: <1490112483-5603-1-git-send-email-anatoly.burakov@intel.com>
Super trivial comment inline:
On Tuesday 21 March 2017 09:38 PM, Anatoly Burakov wrote:
> From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
>
> Fixing compile failures for kernels without sPAPR IOMMU support.
>
> Fixes: 0fe9830b5345 ("eal/ppc: support sPAPR IOMMU for vfio-pci")
> Signed-off-by: Burakov, Anatoly <anatoly.burakov@intel.com>
> ---
> lib/librte_eal/linuxapp/eal/eal_vfio.h | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_vfio.h b/lib/librte_eal/linuxapp/eal/eal_vfio.h
> index ac31a4f..58b7976 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_vfio.h
> +++ b/lib/librte_eal/linuxapp/eal/eal_vfio.h
> @@ -59,6 +59,7 @@
> #define VFIO_IOMMU_SPAPR_REGISTER_MEMORY _IO(VFIO_TYPE, VFIO_BASE + 17)
> #define VFIO_IOMMU_SPAPR_TCE_CREATE _IO(VFIO_TYPE, VFIO_BASE + 19)
> #define VFIO_IOMMU_SPAPR_TCE_REMOVE _IO(VFIO_TYPE, VFIO_BASE + 20)
> +#define VFIO_IOMMU_SPAPR_TCE_GET_INFO _IO(VFIO_TYPE, VFIO_BASE + 12)
I guess a new line should be added here and ...
> struct vfio_iommu_spapr_register_memory {
> uint32_t argsz;
> uint32_t flags;
> @@ -75,6 +76,18 @@ struct vfio_iommu_spapr_tce_remove {
> uint32_t argsz;
> uint64_t start_addr;
> };
and here...
> +struct vfio_iommu_spapr_tce_ddw_info {
> + uint64_t pgsizes;
> + uint32_t max_dynamic_windows_supported;
> + uint32_t levels;
> +};
and here.
> +struct vfio_iommu_spapr_tce_info {
> + uint32_t argsz;
> + uint32_t flags;
> + uint32_t dma32_window_start;
> + uint32_t dma32_window_size;
> + struct vfio_iommu_spapr_tce_ddw_info ddw;
> +};
> #else
> #define RTE_VFIO_SPAPR VFIO_SPAPR_TCE_v2_IOMMU
> #endif
>
next prev parent reply other threads:[~2017-03-22 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:08 Anatoly Burakov
2017-03-22 4:46 ` Shreyansh Jain [this message]
2017-03-22 9:57 ` Burakov, Anatoly
2017-03-23 12:56 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2017-03-27 13:17 ` Thomas Monjalon
2017-03-28 15:53 ` [dpdk-dev] [PATCH v3] " Anatoly Burakov
2017-03-30 14:53 ` 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=467aba33-3bcb-0d1f-c762-4281b2f5a870@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.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).