From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tomasz Figa <tfiga@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: [PULL] topic/iomem-mmap-vs-gup
Date: Mon, 10 May 2021 20:13:31 +0200 [thread overview]
Message-ID: <dcdc8bea-ebe8-bbcb-b581-309d9acf1657@redhat.com> (raw)
In-Reply-To: <YJlz+p787mK8tAh+@google.com>
On 10/05/21 19:57, Sean Christopherson wrote:
> +Paolo
>
> On Mon, May 10, 2021, Jason Gunthorpe wrote:
>> On Mon, May 10, 2021 at 04:55:39PM +0200, Daniel Vetter wrote:
>>
>>> yeah vfio is still broken for the case I care about. I think there's
>>> also some questions open still about whether kvm really uses
>>> mmu_notifier in all cases correctly,
>>
>> IIRC kvm doesn't either.
>
> Yep, KVM on x86 has a non-trivial number of flows that don't properly hook into
> the mmu_notifier. Paolo is working on fixing the problem, but I believe the
> rework won't be ready until 5.14.
Yeah, I like the way it's coming, but I'm at 20-ish patches and counting.
Paolo
prev parent reply other threads:[~2021-05-10 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 19:15 [PULL] topic/iomem-mmap-vs-gup Daniel Vetter
2021-05-06 22:30 ` Linus Torvalds
2021-05-07 15:53 ` Daniel Vetter
2021-05-08 16:46 ` Linus Torvalds
2021-05-10 7:16 ` Daniel Vetter
2021-05-10 7:29 ` Christoph Hellwig
2021-05-17 15:29 ` Daniel Vetter
2021-05-17 22:04 ` Stephen Rothwell
2021-05-10 13:50 ` Jason Gunthorpe
2021-05-10 14:55 ` Daniel Vetter
2021-05-10 15:34 ` Jason Gunthorpe
2021-05-10 17:57 ` Sean Christopherson
2021-05-10 18:13 ` Paolo Bonzini [this message]
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=dcdc8bea-ebe8-bbcb-b581-309d9acf1657@redhat.com \
--to=pbonzini@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=seanjc@google.com \
--cc=tfiga@chromium.org \
--cc=torvalds@linux-foundation.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).