From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
To: Vishal Annapurve <vannapurve@google.com>
Cc: David Rientjes <rientjes@google.com>,
Sean Christopherson <seanjc@google.com>,
Elliot Berman <quic_eberman@quicinc.com>,
Fuad Tabba <tabba@google.com>,
David Hildenbrand <david@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
maz@kernel.org, kvm@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>,
linux-kselftest@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH RFC 0/5] mm/gup: Introduce exclusive GUP pinning
Date: Wed, 26 Jun 2024 07:20:58 +0200 [thread overview]
Message-ID: <CAM9Jb+j8egUkkvXns9AF7+LPQ-4innp4NPHbsoPLn03h9ekWAg@mail.gmail.com> (raw)
In-Reply-To: <CAGtprH8VT6B6efy0dC=6cQEf6mpz3dfh2q4gGp2S-m+wNJn5ew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4602 bytes --]
I am also interested and would like to join the discussion.
Best regards,
Pankaj Gupta
On Wed, 26 Jun, 2024, 5:19 am Vishal Annapurve, <vannapurve@google.com>
wrote:
> On Mon, Jun 24, 2024 at 2:50 PM David Rientjes <rientjes@google.com>
> wrote:
> >
> > On Mon, 24 Jun 2024, Sean Christopherson wrote:
> >
> > > On Fri, Jun 21, 2024, Elliot Berman wrote:
> > > > On Fri, Jun 21, 2024 at 11:16:31AM +0100, Fuad Tabba wrote:
> > > > > On Fri, Jun 21, 2024 at 10:10 AM David Hildenbrand <
> david@redhat.com> wrote:
> > > > > > On 21.06.24 10:54, Fuad Tabba wrote:
> > > > > > > On Fri, Jun 21, 2024 at 9:44 AM David Hildenbrand <
> david@redhat.com> wrote:
> > > > > > >>
> > > > > > >>>> Again from that thread, one of most important aspects
> guest_memfd is that VMAs
> > > > > > >>>> are not required. Stating the obvious, lack of VMAs makes
> it really hard to drive
> > > > > > >>>> swap, reclaim, migration, etc. from code that fundamentally
> operates on VMAs.
> > > > > > >>>>
> > > > > > >>>> : More broadly, no VMAs are required. The lack of
> stage-1 page tables are nice to
> > > > > > >>>> : have; the lack of VMAs means that guest_memfd isn't
> playing second fiddle, e.g.
> > > > > > >>>> : it's not subject to VMA protections, isn't restricted
> to host mapping size, etc.
> > > > > > >>>>
> > > > > > >>>> [1] https://lore.kernel.org/all/Zfmpby6i3PfBEcCV@google.com
> > > > > > >>>> [2] https://lore.kernel.org/all/Zg3xF7dTtx6hbmZj@google.com
> > > > > > >>>
> > > > > > >>> I wonder if it might be more productive to also discuss this
> in one of
> > > > > > >>> the PUCKs, ahead of LPC, in addition to trying to go over
> this in LPC.
> > > > > > >>
> > > > > > >> I don't know in which context you usually discuss that, but
> I could
> > > > > > >> propose that as a topic in the bi-weekly MM meeting.
> > > > > > >>
> > > > > > >> This would, of course, be focused on the bigger MM picture:
> how to mmap,
> > > > > > >> how how to support huge pages, interaction with page pinning,
> ... So
> > > > > > >> obviously more MM focused once we are in agreement that we
> want to
> > > > > > >> support shared memory in guest_memfd and how to make that
> work with core-mm.
> > > > > > >>
> > > > > > >> Discussing if we want shared memory in guest_memfd might be
> betetr
> > > > > > >> suited for a different, more CC/KVM specific meeting (likely
> the "PUCKs"
> > > > > > >> mentioned here?).
> > > > > > >
> > > > > > > Sorry, I should have given more context on what a PUCK* is :)
> It's a
> > > > > > > periodic (almost weekly) upstream call for KVM.
> > > > > > >
> > > > > > > [*]
> https://lore.kernel.org/all/20230512231026.799267-1-seanjc@google.com/
> > > > > > >
> > > > > > > But yes, having a discussion in one of the mm meetings ahead
> of LPC
> > > > > > > would also be great. When do these meetings usually take
> place, to try
> > > > > > > to coordinate across timezones.
> > >
> > > Let's do the MM meeting. As evidenced by the responses, it'll be
> easier to get
> > > KVM folks to join the MM meeting as opposed to other way around.
> > >
> > > > > > It's Wednesday, 9:00 - 10:00am PDT (GMT-7) every second week.
> > > > > >
> > > > > > If we're in agreement, we could (assuming there are no other
> planned
> > > > > > topics) either use the slot next week (June 26) or the following
> one
> > > > > > (July 10).
> > > > > >
> > > > > > Selfish as I am, I would prefer July 10, because I'll be on
> vacation
> > > > > > next week and there would be little time to prepare.
> > > > > >
> > > > > > @David R., heads up that this might become a topic ("shared and
> private
> > > > > > memory in guest_memfd: mmap, pinning and huge pages"), if people
> here
> > > > > > agree that this is a direction worth heading.
> > > > >
> > > > > Thanks for the invite! Tentatively July 10th works for me, but I'd
> > > > > like to talk to the others who might be interested (pKVM, Gunyah,
> and
> > > > > others) to see if that works for them. I'll get back to you
> shortly.
> > > > >
> > > >
> > > > I'd like to join too, July 10th at that time works for me.
> > >
> > > July 10th works for me too.
> > >
> >
> > Thanks all, and David H for the topic suggestion. Let's tentatively
> > pencil this in for the Wednesday, July 10th instance at 9am PDT and I'll
> > follow-up offlist with those will be needed to lead the discussion to
> make
> > sure we're on track.
>
> I would like to join the call too.
>
> Regards,
> Vishal
>
>
[-- Attachment #2: Type: text/html, Size: 6838 bytes --]
next prev parent reply other threads:[~2024-06-26 5:21 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 0:05 Elliot Berman
2024-06-19 0:05 ` [PATCH RFC 1/5] mm/gup: Move GUP_PIN_COUNTING_BIAS to page_ref.h Elliot Berman
2024-06-19 0:05 ` [PATCH RFC 2/5] mm/gup: Add an option for obtaining an exclusive pin Elliot Berman
2024-06-19 0:05 ` [PATCH RFC 3/5] mm/gup: Add support for re-pinning a normal pinned page as exclusive Elliot Berman
2024-06-19 0:05 ` [PATCH RFC 4/5] mm/gup-test: Verify exclusive pinned Elliot Berman
2024-06-19 0:05 ` [PATCH RFC 5/5] mm/gup_test: Verify GUP grabs same pages twice Elliot Berman
2024-06-19 0:11 ` [PATCH RFC 0/5] mm/gup: Introduce exclusive GUP pinning Elliot Berman
2024-06-19 2:44 ` John Hubbard
2024-06-19 7:37 ` David Hildenbrand
2024-06-19 9:11 ` Fuad Tabba
2024-06-19 11:51 ` Jason Gunthorpe
2024-06-19 12:01 ` Fuad Tabba
2024-06-19 12:42 ` Jason Gunthorpe
2024-06-20 15:37 ` Sean Christopherson
2024-06-21 8:23 ` Fuad Tabba
2024-06-21 8:43 ` David Hildenbrand
2024-06-21 8:54 ` Fuad Tabba
2024-06-21 9:10 ` David Hildenbrand
2024-06-21 10:16 ` Fuad Tabba
2024-06-21 16:54 ` Elliot Berman
2024-06-24 19:03 ` Sean Christopherson
2024-06-24 21:50 ` David Rientjes
2024-06-26 3:19 ` Vishal Annapurve
2024-06-26 5:20 ` Pankaj Gupta [this message]
2024-06-19 12:17 ` David Hildenbrand
2024-06-20 4:11 ` Christoph Hellwig
2024-06-20 8:32 ` Fuad Tabba
2024-06-20 13:55 ` Jason Gunthorpe
2024-06-20 14:01 ` David Hildenbrand
2024-06-20 14:29 ` Jason Gunthorpe
2024-06-20 14:45 ` David Hildenbrand
2024-06-20 16:04 ` Sean Christopherson
2024-06-20 18:56 ` David Hildenbrand
2024-06-20 16:36 ` Jason Gunthorpe
2024-06-20 18:53 ` David Hildenbrand
2024-06-20 20:30 ` Sean Christopherson
2024-06-20 20:47 ` David Hildenbrand
2024-06-20 22:32 ` Sean Christopherson
2024-06-20 23:00 ` Jason Gunthorpe
2024-06-20 23:11 ` Jason Gunthorpe
2024-06-20 23:54 ` Sean Christopherson
2024-06-21 7:43 ` David Hildenbrand
2024-06-21 12:39 ` Jason Gunthorpe
2024-06-20 23:08 ` Jason Gunthorpe
2024-06-20 22:47 ` Elliot Berman
2024-06-20 23:18 ` Jason Gunthorpe
2024-06-21 7:32 ` Quentin Perret
2024-06-21 8:02 ` David Hildenbrand
2024-06-21 9:25 ` Quentin Perret
2024-06-21 9:37 ` David Hildenbrand
2024-06-21 16:48 ` Elliot Berman
2024-06-21 12:26 ` Jason Gunthorpe
2024-06-19 12:16 ` David Hildenbrand
2024-06-20 8:47 ` Fuad Tabba
2024-06-20 9:00 ` David Hildenbrand
2024-06-20 14:01 ` Jason Gunthorpe
2024-06-20 13:08 ` Mostafa Saleh
2024-06-20 14:14 ` David Hildenbrand
2024-06-20 14:34 ` Jason Gunthorpe
2024-08-02 8:26 ` Tian, Kevin
2024-08-02 11:22 ` Jason Gunthorpe
2024-08-05 2:24 ` Tian, Kevin
2024-08-05 23:22 ` Jason Gunthorpe
2024-08-06 0:50 ` Tian, Kevin
2024-06-20 16:33 ` Mostafa Saleh
2024-07-12 23:29 ` Ackerley Tng
2024-07-16 16:03 ` Sean Christopherson
2024-07-16 16:08 ` Jason Gunthorpe
2024-07-16 17:34 ` Sean Christopherson
2024-07-16 20:11 ` Jason Gunthorpe
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=CAM9Jb+j8egUkkvXns9AF7+LPQ-4innp4NPHbsoPLn03h9ekWAg@mail.gmail.com \
--to=pankaj.gupta.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=quic_eberman@quicinc.com \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tabba@google.com \
--cc=vannapurve@google.com \
--cc=willy@infradead.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