From: Eric Auger <eric.auger@linaro.org>
To: Bharat Bhushan <Bharat.Bhushan@freescale.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
alex.williamson@redhat.com
Cc: marc.zyngier@arm.com, will.deacon@arm.com
Subject: Re: [RFC PATCH 0/6] vfio: Add interface to map MSI pages
Date: Tue, 12 Jan 2016 09:55:50 +0100 [thread overview]
Message-ID: <5694BF96.3060606@linaro.org> (raw)
In-Reply-To: <1443625060-24396-1-git-send-email-Bharat.Bhushan@freescale.com>
Hi Bharat, all,
I now have access to HW that allows to bring out that task on ARM and I
would be happy to try contributing on this thread on both kernel and
QEMU side. Bharat, do you intend to respin shortly or can I try to
pursue your efforts while keeping credit to you (and also take into
account Pranav and Pavel contributions too if relevant)?
Thanks in advance
Best Regards
Eric
/2015 04:57 PM, Bharat Bhushan wrote:
> This patch series add the interface to map MSI pages in iommu
> for msi-capable device pass-through using vfio.
>
> First patch adds a generic interface to set reserved iova regions.
> These reserved regions can be used for mapping physical address.
> Follow-up patches uses these reserved iova for mapping msi-pages.
>
> This patch series does not provide interface to let user-space know
> how many minimum reserved iova regions are required on a given platform.
> This interface can be added once this patches series get reviewed and will
> be in acceptable state.
>
> Bharat Bhushan (6):
> vfio: Add interface for add/del reserved iova region
> iommu: Add interface to get msi-pages mapping attributes
> vfio: Extend iommu-info to return MSIs automap state
> vfio: Add interface to iommu-map/unmap MSI pages
> vfio-pci: Create iommu mapping for msi interrupt
> arm-smmu: Allow to set iommu mapping for MSI
>
> drivers/iommu/arm-smmu.c | 8 +
> drivers/iommu/fsl_pamu_domain.c | 3 +
> drivers/iommu/iommu.c | 14 ++
> drivers/vfio/pci/vfio_pci_intrs.c | 36 +++-
> drivers/vfio/vfio.c | 52 ++++++
> drivers/vfio/vfio_iommu_type1.c | 344 +++++++++++++++++++++++++++++++++++++-
> include/linux/iommu.h | 9 +-
> include/linux/vfio.h | 9 +-
> include/uapi/linux/vfio.h | 46 +++++
> 9 files changed, 516 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2016-01-12 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 14:57 [RFC PATCH 0/6] vfio: Add interface to map MSI pages Bharat Bhushan
2015-09-30 14:57 ` Bharat Bhushan
2016-01-12 8:55 ` Eric Auger [this message]
2016-01-12 9:00 ` Bharat Bhushan
2016-01-12 9:00 ` Bharat Bhushan
2016-01-12 9:30 ` Eric Auger
2016-01-12 9:49 ` Pavel Fedin
2016-01-12 10:34 ` Eric Auger
2016-01-19 4:11 ` Pranav Sawargaonkar
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=5694BF96.3060606@linaro.org \
--to=eric.auger@linaro.org \
--cc=Bharat.Bhushan@freescale.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=will.deacon@arm.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.