From: Matthew Wilcox <willy@infradead.org>
To: Xie Yongji <xieyongji@bytedance.com>
Cc: linux-mm@kvack.org, virtualization@lists.linux-foundation.org,
akpm@linux-foundation.org, mst@redhat.com
Subject: Re: [RFC 1/4] mm: export zap_page_range() for driver use
Date: Mon, 19 Oct 2020 16:14:18 +0100 [thread overview]
Message-ID: <20201019151418.GT20115@casper.infradead.org> (raw)
In-Reply-To: <20201019145623.671-2-xieyongji@bytedance.com>
On Mon, Oct 19, 2020 at 10:56:20PM +0800, Xie Yongji wrote:
> Export zap_page_range() for use in VDUSE.
I think you're missing a lot of MMU notifier work by calling this
directly. It probably works in every scenario you've tested, but won't
work for others. I see you're using VM_MIXEDMAP -- would it make sense
to use VM_PFNMAP instead and use zap_vma_ptes()? Or would it make sense
to change zap_vma_ptes() to handle VM_MIXEDMAP as well as VM_PFNMAP?
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2020-10-19 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201019145623.671-1-xieyongji@bytedance.com>
[not found] ` <20201019145623.671-4-xieyongji@bytedance.com>
2020-10-19 15:05 ` [RFC 3/4] vduse: grab the module's references until there is no vduse device Michael S. Tsirkin
[not found] ` <CACycT3sQ-rw+weEktyK5jQTfMNWYR6qSaD1vAUEyCP6x7C9rRQ@mail.gmail.com>
2020-10-19 15:47 ` [External] " Michael S. Tsirkin
[not found] ` <CACycT3vG+ZEhn3SYy=7c5rkMz4XRbQZL21NdpPozPnH_x6Srhg@mail.gmail.com>
2020-10-19 16:41 ` Michael S. Tsirkin
[not found] ` <20201019145623.671-3-xieyongji@bytedance.com>
2020-10-19 15:08 ` [RFC 2/4] vduse: Introduce VDUSE - vDPA Device in Userspace Michael S. Tsirkin
2020-10-19 15:24 ` Randy Dunlap
[not found] ` <20201019145623.671-2-xieyongji@bytedance.com>
2020-10-19 15:14 ` Matthew Wilcox [this message]
2020-10-19 17:16 ` [RFC 0/4] " Michael S. Tsirkin
[not found] ` <CACycT3vzpm_+v-DbqeVRMg8BRny_GoL2JxpbzYC3JYTMKGn_vg@mail.gmail.com>
2020-10-20 2:20 ` [External] " Jason Wang
2020-10-20 3:20 ` Jason Wang
[not found] ` <CACycT3srzADF63rotgHwfsqn5GJOCbXx+19Dcnw8HLyTGY_7Eg@mail.gmail.com>
2020-10-20 8:01 ` [External] " Jason Wang
[not found] ` <CACycT3ssE-iMquAmrrHGQyBCv7XkQ2WrinFMMPTTubxuuOQ92g@mail.gmail.com>
2020-10-20 9:12 ` Jason Wang
[not found] ` <CACycT3s2GZ3yKP+Xn2V83_-=tXg342J4n91ZAb0c-+UD_+sFnA@mail.gmail.com>
2020-10-23 8:44 ` Jason Wang
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=20201019151418.GT20115@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.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 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).