From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"agraf@suse.de" <agraf@suse.de>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alex Williamson <alex.williamson@redhat.com>,
Bhushan Bharat-R65777 <R65777@freescale.com>,
Sethi Varun-B16395 <B16395@freescale.com>
Subject: Re: [Qemu-devel] RFC: vfio API changes needed for powerpc (v3)
Date: Fri, 5 Apr 2013 17:17:25 -0500 [thread overview]
Message-ID: <1365200245.17535.13@snotra> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E15035A29FB@039-SN1MPN1-003.039d.mgd.msft.net> (from B08248@freescale.com on Thu Apr 4 17:10:27 2013)
On 04/04/2013 05:10:27 PM, Yoder Stuart-B08248 wrote:
> /*
> * VFIO_IOMMU_PAMU_UNMAP_MSI_BANK
> *
> * Unmaps the MSI bank at the specified iova.
> * Caller provides struct vfio_pamu_msi_bank_unmap with all fields
> set.
> * Operates on VFIO file descriptor (/dev/vfio/vfio).
> * Return: 0 on success, -errno on failure
> */
>
> struct vfio_pamu_msi_bank_unmap {
> __u32 argsz;
> __u32 flags; /* no flags currently */
> __u64 iova; /* the iova to be unmapped to */
> };
> #define VFIO_IOMMU_PAMU_UNMAP_MSI_BANK _IO(VFIO_TYPE, VFIO_BASE + x,
> struct vfio_pamu_msi_bank_unmap )
What happens if a normal unmap call is done on the MSI iova? Do we
need a separate unmap?
-Scott
next prev parent reply other threads:[~2013-04-05 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 22:10 [Qemu-devel] RFC: vfio API changes needed for powerpc (v3) Yoder Stuart-B08248
2013-04-05 22:17 ` Scott Wood [this message]
2013-04-09 1:22 ` Yoder Stuart-B08248
2013-04-11 12:56 ` Joerg Roedel
2013-04-11 16:15 ` Yoder Stuart-B08248
2013-04-11 19:53 ` Scott Wood
2013-04-09 17:47 ` Bhushan Bharat-R65777
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=1365200245.17535.13@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=B16395@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).