All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: David Woodhouse <dwmw2@infradead.org>,
	Brendan Jackman <jackmanb@google.com>,
	Takahiro Itazuri <itazur@amazon.com>,
	kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Fuad Tabba <tabba@google.com>, Paul Durrant <pdurrant@amazon.com>,
	Nikita Kalyazin <kalyazin@amazon.com>,
	Patrick Roy <patrick.roy@campus.lmu.de>,
	Takahiro Itazuri <zulinx86@gmail.com>
Subject: Re: [RFC PATCH 0/2] KVM: pfncache: Support guest_memfd without direct map
Date: Fri, 5 Dec 2025 08:15:51 +0100	[thread overview]
Message-ID: <d07652fb-dece-4e9a-b307-ba018277bf8e@kernel.org> (raw)
In-Reply-To: <cfdf2bfcacc8e0de20d97d126de4917eea720c5c.camel@infradead.org>

On 12/4/25 23:31, David Woodhouse wrote:
> On Wed, 2025-12-03 at 17:06 +0000, Brendan Jackman wrote:
>> Makes sense. I didn't properly explore if there are any challenges with
>> making vmalloc aware of it, but assuming there are no issues there I
>> don't think setting up an mm-local region is very challinging [1]. I
>> have the impression the main reason there isn't already an mm-local
>> region is just that the right usecase hasn't come along yet?
> 
> I'm fairly sure we have a *usecase* for mm-local.

Haha, I just skimmed over this patch and wondered "is mm-local a new mm 
branch we want to have" :)

> 
> And since researchers dusted off our XSA-289 advisory from 2019,
> rediscovered it and called it 'L1TF reloaded' and then expressed
> surprise that environments which have been using mm-local ever since
> those days don't actually leak secrets from one guest to another... I'd
> kind of hope that everyone else has come round to our way of thinking
> that we have a usecase for mm-local too? :)

Yeah, I would assume that we have such use cases indeed.

-- 
Cheers

David

      reply	other threads:[~2025-12-05  7:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 14:41 [RFC PATCH 0/2] KVM: pfncache: Support guest_memfd without direct map Takahiro Itazuri
2025-12-03 14:41 ` [RFC PATCH 1/2] KVM: pfncache: Use kvm_gmem_get_pfn() for guest_memfd-backed memslots Takahiro Itazuri
2026-01-19 12:34   ` David Hildenbrand (Red Hat)
2025-12-03 14:41 ` [RFC PATCH 2/2] KVM: pfncache: Use vmap() for guest_memfd pages without direct map Takahiro Itazuri
2025-12-05  9:55   ` kernel test robot
2025-12-05 10:06   ` kernel test robot
2025-12-05 17:24   ` kernel test robot
2025-12-03 16:01 ` [RFC PATCH 0/2] KVM: pfncache: Support guest_memfd " Brendan Jackman
2025-12-03 16:35   ` David Woodhouse
2025-12-03 17:06     ` Brendan Jackman
2025-12-04 22:31       ` David Woodhouse
2025-12-05  7:15         ` David Hildenbrand (Red Hat) [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=d07652fb-dece-4e9a-b307-ba018277bf8e@kernel.org \
    --to=david@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=itazur@amazon.com \
    --cc=jackmanb@google.com \
    --cc=kalyazin@amazon.com \
    --cc=kvm@vger.kernel.org \
    --cc=patrick.roy@campus.lmu.de \
    --cc=pbonzini@redhat.com \
    --cc=pdurrant@amazon.com \
    --cc=seanjc@google.com \
    --cc=tabba@google.com \
    --cc=vkuznets@redhat.com \
    --cc=zulinx86@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.