From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pl1-f170.google.com (mail-pl1-f170.google.com [209.85.214.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id ED286131732 for ; Mon, 24 Jun 2024 21:50:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.214.170 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719265823; cv=none; b=RgvxlGfSoqbA8HAm3ptut0nZ9Sv/jDV8dbCQzyks4/GUcSOP7dr4GAd495ZmuUL3ixQUw05m7floFSeJ49wFNaqN3IjmB+hqz6fGSqz2CXxuT1wtMx5eOOvT3crMUqd9ggyGuqtNeIw8AXeK4SDmT5HLuZ9AzBNytKaaUuyJMJM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719265823; c=relaxed/simple; bh=FoiUdQ7swPpEh3VgIWO/eUW1hfzGK5LLI1M3/9Im2U0=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=iPsVM/FyGKljO3qoDlgc3PAUj1jzn67JSfkDToEoK0RPhp9lM3KyC+KZ5iErkmZ11KmdHdy8w7pExlwp3aku3JY6ZCxq1DGNQ905N6Km7M+24tnLWcPshup6cuU5we0fh0W71EMhlOeEV1luvgj9rDOTagCIEFilPkowrk6BPBA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=bP6Yshgl; arc=none smtp.client-ip=209.85.214.170 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="bP6Yshgl" Received: by mail-pl1-f170.google.com with SMTP id d9443c01a7336-1fa4b332645so21865ad.1 for ; Mon, 24 Jun 2024 14:50:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1719265821; x=1719870621; darn=vger.kernel.org; h=mime-version:references:message-id:in-reply-to:subject:cc:to:from :date:from:to:cc:subject:date:message-id:reply-to; bh=2lDDpbzZjbYoW0ZccZa58xFekph1Nf38bp9Ut4WlNiM=; b=bP6YshglPnfMT1TYeGsO8YPNaNPRGJOUu9HQKh7VA7ZFNRGl0Spty3bgoLnY3UzACa 7529QdJhEtwHQcQFKGWi4LtgsiRKFo9uJKCO5uCd+36+VM1zA0NwbtmiERRadBf4kHDy ra/tj857m6PZPheO9lDZ7MkzKIRji9olg5nfPC3B3mmaq6ye0b6JhGIS/hXIirbbx+8e aULE2s309uq3oH+MRjIdECUEq0nLUGXMYo7ttPjxEFHb4Qwj0OADZTL0CpVd5Pt+VG7T thntXvEzlGe7ueZqRCgcOZ8xl2CPT4AAKSwlH5eQstcpwY8SBaPwTbZERSoy3LiLGejh MZDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719265821; x=1719870621; h=mime-version:references:message-id:in-reply-to:subject:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2lDDpbzZjbYoW0ZccZa58xFekph1Nf38bp9Ut4WlNiM=; b=f3SvjmeR9CFNP/1fJ0tns/N2SBXERzEs4rp0kJqmWzo/GZDeAvon6HHZVAZYJ6sHmY ncC6QgGjK5dzKMUvCMoG1nNCqGUUhdrQq2eqatPIH3rpJlwz9guz2xpO24h6wr9+5ZiR jk/4r3azPPFbi/WgdqIxV78wl9mHUGZTt/c465wxFMp3BISDiISLlsY4+9a5mKxsQyZW g4uKEclYIu6y9kt/7zVJ7nMZm1h1dgyfkBG57iPpsewj+/lpVpkRR69ioyn1FkG/SDG5 g9mSWO/vjNyYhv0aumrdzZ32JHSoRQv3zmf5mTZSrkvtTNYHRiIZf3aKEpfoU5wRgmTL PeNQ== X-Forwarded-Encrypted: i=1; AJvYcCVWVgQoLcrYxJvX2Zm7ERCilS58S4jvsnHG7L/CilDG1W4gXrhnGvn/v3Wl5V///1r9HhyMEXaDErcA6GNIlW4LGTAq9oXnmZRq8jBtGQ== X-Gm-Message-State: AOJu0YzQdlOh0jsu/+4n/keupnRCC9iuiDEFelYZfcuwcFELAEYeRn7h SaFz6ZYHlZT2e4EfshLuc94QS3HIPI/o5DXeu0GOyU/Jsek7d53xMeJfX04lWw== X-Google-Smtp-Source: AGHT+IFeFR7zMjbNB9DCvgCjRBXeGOiI4lkJ8SgQ6QWD0Q5nCQ7py7AEvLDgXuqqLYyDF5Y75QDGNA== X-Received: by 2002:a17:902:bd46:b0:1fa:2c8c:7e8 with SMTP id d9443c01a7336-1fa68fe3318mr1035325ad.4.1719265820845; Mon, 24 Jun 2024 14:50:20 -0700 (PDT) Received: from [2620:0:1008:15:5ad8:4b69:7e4b:92e2] ([2620:0:1008:15:5ad8:4b69:7e4b:92e2]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-1f9eb3c5ef4sm67546215ad.163.2024.06.24.14.50.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Jun 2024 14:50:20 -0700 (PDT) Date: Mon, 24 Jun 2024 14:50:19 -0700 (PDT) From: David Rientjes To: Sean Christopherson cc: Elliot Berman , Fuad Tabba , David Hildenbrand , Jason Gunthorpe , John Hubbard , Andrew Morton , Shuah Khan , Matthew Wilcox , maz@kernel.org, kvm@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, pbonzini@redhat.com Subject: Re: [PATCH RFC 0/5] mm/gup: Introduce exclusive GUP pinning In-Reply-To: Message-ID: <5e14ebf6-2a7f-3828-c3f6-5155026d59ae@google.com> References: <20240619115135.GE2494510@nvidia.com> <4c8b81a0-3a76-4802-875f-f26ff1844955@redhat.com> <8e9436f2-6ebb-4ce1-a44f-2a941d354e2a@redhat.com> <20240621095319587-0700.eberman@hu-eberman-lv.qualcomm.com> Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2003064516-1965583562-1719265820=:2019105" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2003064516-1965583562-1719265820=:2019105 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT 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 wrote: > > > > On 21.06.24 10:54, Fuad Tabba wrote: > > > > > On Fri, Jun 21, 2024 at 9:44 AM David Hildenbrand 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. --2003064516-1965583562-1719265820=:2019105--