From: Stephen Hemminger <stephen@networkplumber.org>
To: Pawel Wodkowski <pawelx.wodkowski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [RFC][PATCH] vfio: allow to map other memory regions
Date: Wed, 17 May 2017 10:20:23 -0700 [thread overview]
Message-ID: <20170517102023.3c78590e@xeon-e3> (raw)
In-Reply-To: <1495032287-216322-1-git-send-email-pawelx.wodkowski@intel.com>
On Wed, 17 May 2017 16:44:46 +0200
Pawel Wodkowski <pawelx.wodkowski@intel.com> wrote:
> /* IOMMU types we support */
> static const struct vfio_iommu_type iommu_types[] = {
> /* x86 IOMMU, otherwise known as type 1 */
> - { RTE_VFIO_TYPE1, "Type 1", &vfio_type1_dma_map},
> + { RTE_VFIO_TYPE1, "Type 1", &vfio_type1_dma_map, &vfio_type1_dma_mem_map},
> /* ppc64 IOMMU, otherwise known as spapr */
> - { RTE_VFIO_SPAPR, "sPAPR", &vfio_spapr_dma_map},
> + { RTE_VFIO_SPAPR, "sPAPR", &vfio_spapr_dma_map, NULL},
> /* IOMMU-less mode */
> - { RTE_VFIO_NOIOMMU, "No-IOMMU", &vfio_noiommu_dma_map},
> + { RTE_VFIO_NOIOMMU, "No-IOMMU", &vfio_noiommu_dma_map, &vfio_noiommu_dma_mem_map},
> };
For complex tables like this why not use C99 style initializer.
next prev parent reply other threads:[~2017-05-17 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 14:44 [RFC][PATCH] vfio: allow to map other memory regions Pawel Wodkowski
2017-05-17 17:20 ` Stephen Hemminger [this message]
2017-05-18 9:06 ` Wodkowski, PawelX
2017-05-18 11:23 ` Burakov, Anatoly
2017-05-23 13:53 ` [PATCH v2] " Pawel Wodkowski
2017-05-23 13:59 ` [PATCH v3] " Pawel Wodkowski
2017-05-24 11:17 ` [PATCH] " Pawel Wodkowski
[not found] ` <1496663643-65002-1-git-send-email-pawelx.wodkowski@intel.com>
2017-06-05 8:16 ` Wodkowski, PawelX
2017-06-13 9:02 ` Burakov, Anatoly
2017-06-19 21:04 ` Thomas Monjalon
2017-06-28 9:54 ` Wodkowski, PawelX
2017-06-28 11:50 ` 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=20170517102023.3c78590e@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=pawelx.wodkowski@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.