From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Luca Boccassi <bluca@debian.org>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 16.11 1/2] vfio: fix build on old kernel
Date: Fri, 23 Nov 2018 09:26:34 +0000 [thread overview]
Message-ID: <42e415ca-4e97-7a07-4e9e-57ded7f95019@intel.com> (raw)
In-Reply-To: <20181121164802.8186-1-bluca@debian.org>
On 21-Nov-18 4:48 PM, Luca Boccassi wrote:
> From: Anatoly Burakov <anatoly.burakov@intel.com>
>
> [ backported from upstream commit 468f42cc264580c078b892fe6886810fe996a75f ]
>
> Fixing compile failures for kernels without sPAPR IOMMU support.
>
> Fixes: 0fe9830b5345 ("eal/ppc: support sPAPR IOMMU for vfio-pci")
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> lib/librte_eal/linuxapp/eal/eal_vfio.h | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_vfio.h b/lib/librte_eal/linuxapp/eal/eal_vfio.h
> index ac31a4fc1..0bf85bb59 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_vfio.h
> +++ b/lib/librte_eal/linuxapp/eal/eal_vfio.h
> @@ -59,22 +59,44 @@
> #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)
> +
> +/* SPAPR_v2 is not present, but SPAPR might be */
> +#ifndef VFIO_SPAPR_TCE_IOMMU
> +#define VFIO_IOMMU_SPAPR_TCE_GET_INFO _IO(VFIO_TYPE, VFIO_BASE + 12)
> +
> +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;
> +};
> +#endif
> +
> struct vfio_iommu_spapr_register_memory {
> uint32_t argsz;
> uint32_t flags;
> uint64_t vaddr;
> uint64_t size;
> };
> +
> struct vfio_iommu_spapr_tce_create {
> uint32_t argsz;
> uint32_t page_shift;
> uint64_t window_size;
> uint32_t levels;
> };
> +
> struct vfio_iommu_spapr_tce_remove {
> uint32_t argsz;
> uint64_t start_addr;
> };
> +
> +struct vfio_iommu_spapr_tce_ddw_info {
> + uint64_t pgsizes;
> + uint32_t max_dynamic_windows_supported;
> + uint32_t levels;
> +};
> #else
> #define RTE_VFIO_SPAPR VFIO_SPAPR_TCE_v2_IOMMU
> #endif
>
Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
prev parent reply other threads:[~2018-11-23 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 16:48 Luca Boccassi
2018-11-21 16:48 ` [dpdk-stable] [PATCH 16.11 2/2] vfio: fix build Luca Boccassi
2018-11-23 9:29 ` Burakov, Anatoly
2018-11-23 9:26 ` Burakov, Anatoly [this message]
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=42e415ca-4e97-7a07-4e9e-57ded7f95019@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bluca@debian.org \
--cc=stable@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).