From: Scott Wood <scottwood@freescale.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"agraf@suse.de" <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Yoder Stuart-B08248 <B08248@freescale.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
Bhushan Bharat-R65777 <R65777@freescale.com>
Subject: Re: [Qemu-devel] RFC: vfio API changes needed for powerpc (v3)
Date: Thu, 11 Apr 2013 14:53:24 -0500 [thread overview]
Message-ID: <1365710004.3640.8@snotra> (raw)
In-Reply-To: <20130411125659.GL6858@8bytes.org> (from joro@8bytes.org on Thu Apr 11 07:56:59 2013)
On 04/11/2013 07:56:59 AM, Joerg Roedel wrote:
> On Tue, Apr 09, 2013 at 01:22:15AM +0000, Yoder Stuart-B08248 wrote:
> > > What happens if a normal unmap call is done on the MSI iova? Do
> we
> > > need a separate unmap?
> >
> > I was thinking a normal unmap on an MSI windows would be an
> error...but
> > I'm not set on that. I put the msi unmap there to make things
> symmetric,
> > a normal unmap would work as well...and then we could drop the msi
> unmap.
>
> Hmm, this API semantic isn't very clean. When you explicitly map the
> MSI
> banks a clean API would also allow to unmap them. But that is not
> possible in your design because the kernel is responsible for mapping
> MSIs and you can't unmap a MSI bank that is in use by the kernel.
Why is it not possible to unmap them? Once they've been mapped,
they're just like any other IOMMU mapping. If the user breaks MSI for
their own devices by unmapping the MSI page, that's their problem.
> So since the kernel owns the MSI setup anyways it should also take
> care
> of mapping the MSI banks. What is the reason to not let the kernel
> allocate the MSI banks top-down from the end of the DMA window space?
It's less flexible, and possibly more complicated.
-Scott
next prev parent reply other threads:[~2013-04-11 19:53 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
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 [this message]
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=1365710004.3640.8@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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).