From: Alex Williamson <alex.williamson@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: kvm@vger.kernel.org, Alexey Kardashevskiy <aik@ozlabs.ru>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] vfio powerpc: enabled on powernv platform
Date: Wed, 12 Dec 2012 20:22:36 -0700 [thread overview]
Message-ID: <1355368956.3224.357.camel@bling.home> (raw)
In-Reply-To: <1355367458.19932.84.camel@pasglop>
On Thu, 2012-12-13 at 13:57 +1100, Benjamin Herrenschmidt wrote:
> On Wed, 2012-12-12 at 16:30 -0700, Alex Williamson wrote:
> > Locked page accounting in this version is very, very broken. How do
> > powerpc folks feel about seemingly generic kernel iommu interfaces
> > messing with the current task mm? Besides that, more problems
> > below...
>
> After a second look & thought...
>
> This whole accounting business is fucked. First, we simply can't just
> randomly return errors from H_PUT_TCE because the process reached some
> rlimit. This is not a proper failure mode. That means that the guest
> will probably panic() ... possibly right in the middle of some disk
> writeback or god knows what. Not good.
>
> Also the overhead of doing all that crap on every TCE map/unmap is
> ridiculous.
>
> Finally, it's just not going to work for real mode which we really want,
> since we can't take the mmap-sem in real mode anyway, so unless we
> convert that counter to an atomic, we can't do it.
>
> I'd suggest just not bothering, or if you want to bother, check once
> when creating a TCE table that the rlimit is enough to bolt as many
> pages as can be populated in that table and fail to create *that*. The
> failure mode is much better, ie, qemu failing to create a PCI bus due to
> insufficient rlimits.
I agree, we don't seem to be headed in the right direction. x86 needs
to track rlimits or else a user can exploit the interface to pin all the
memory in the system. On power, only the iova window can be pinned, so
it's a fixed amount. I could see it as granting access to a group
implicitly grants access to pinning the iova window. We can still make
it more explicit by handling the rlimit accounting upfront. Thanks,
Alex
next prev parent reply other threads:[~2012-12-13 3:22 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121113033832.GW4696@truffula.fritz.box>
2012-11-20 0:48 ` [PATCH] vfio powerpc: enabled and supported on powernv platform Alexey Kardashevskiy
2012-11-20 18:19 ` Alex Williamson
2012-11-22 11:56 ` Sethi Varun-B16395
2012-11-23 2:02 ` Alexey Kardashevskiy
2012-11-26 15:18 ` Alex Williamson
2012-11-26 18:04 ` Alex Williamson
2012-11-27 0:21 ` Benjamin Herrenschmidt
2012-11-27 3:28 ` Alexey Kardashevskiy
2012-11-27 4:23 ` Alex Williamson
2012-11-26 15:08 ` Alex Williamson
2012-11-23 9:03 ` [PATCH 0/2] vfio powerpc: implemented and enabled Alexey Kardashevskiy
2012-11-23 9:03 ` [PATCH 1/2] vfio powerpc: implemented IOMMU driver for VFIO Alexey Kardashevskiy
2012-11-26 18:20 ` Alex Williamson
2012-11-27 4:06 ` Alexey Kardashevskiy
2012-11-27 4:29 ` Alex Williamson
2012-11-27 4:58 ` Alexey Kardashevskiy
2012-11-27 5:06 ` David Gibson
2012-11-27 5:07 ` Alex Williamson
2012-11-28 7:21 ` [PATCH] " Alexey Kardashevskiy
2012-11-28 21:01 ` Alex Williamson
2012-11-29 3:51 ` Alexey Kardashevskiy
2012-11-23 9:03 ` [PATCH 2/2] vfio powerpc: enabled on powernv platform Alexey Kardashevskiy
2012-11-27 4:41 ` Alex Williamson
2012-11-28 7:18 ` [PATCH] " Alexey Kardashevskiy
2012-11-28 21:30 ` Alex Williamson
2012-11-29 3:53 ` Alexey Kardashevskiy
2012-11-29 4:20 ` Alex Williamson
2012-11-30 6:14 ` Alexey Kardashevskiy
2012-11-30 16:48 ` Alex Williamson
2012-12-01 0:14 ` Alexey Kardashevskiy
2012-11-30 6:16 ` Alexey Kardashevskiy
2012-12-03 2:52 ` [PATCH 0/2] vfio on power: yet another try Alexey Kardashevskiy
2012-12-03 2:52 ` [PATCH 1/2] vfio powerpc: enabled on powernv platform Alexey Kardashevskiy
2012-12-03 17:35 ` Alex Williamson
2012-12-04 8:12 ` Alexey Kardashevskiy
2012-12-04 15:51 ` Alex Williamson
2012-12-07 7:35 ` [PATCH] " Alexey Kardashevskiy
2012-12-07 17:38 ` Alex Williamson
2012-12-12 6:14 ` Alexey Kardashevskiy
2012-12-12 14:34 ` Alex Williamson
2012-12-13 2:29 ` Benjamin Herrenschmidt
2012-12-13 6:27 ` Alexey Kardashevskiy
2012-12-12 12:34 ` Alexey Kardashevskiy
2012-12-12 12:38 ` Alexey Kardashevskiy
2012-12-12 23:30 ` Alex Williamson
2012-12-13 2:24 ` Alexey Kardashevskiy
2012-12-13 2:39 ` Benjamin Herrenschmidt
2012-12-13 2:57 ` Benjamin Herrenschmidt
2012-12-13 3:22 ` Alex Williamson [this message]
2012-12-03 2:52 ` [PATCH 2/2] vfio powerpc: implemented IOMMU driver for VFIO Alexey Kardashevskiy
2012-12-03 17:53 ` Alex Williamson
2012-12-07 7:34 ` [PATCH] " Alexey Kardashevskiy
2012-12-07 17:01 ` Alex Williamson
2012-12-12 6:59 ` Alexey Kardashevskiy
2012-12-12 14:36 ` Alex Williamson
2012-12-12 12:35 ` Alexey Kardashevskiy
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=1355368956.3224.357.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).