From: "Gupta, Pankaj" <pankaj.gupta@amd.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>
Cc: seanjc@google.com, pbonzini@redhat.com, tglx@kernel.org,
mingo@redhat.com, dave.hansen@linux.intel.com, bp@alien8.de,
x86@kernel.org, thomas.lendacky@amd.com, hpa@zytor.com,
yangge1116@126.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] KVM: SEV: drop FOLL_LONGTERM for encrypted region registration
Date: Fri, 10 Jul 2026 15:06:54 +0200 [thread overview]
Message-ID: <5b9b8ef2-1481-418a-951c-c48a75921f85@amd.com> (raw)
In-Reply-To: <adf66571-4ef4-4f8a-824f-fdd5ab5099ab@kernel.org>
>> hmm but we have FOLL_LONGTERM as an adjunct to FOLL_PIN (doesn't make sense
>> without - any checks that exist for that btw should be extended to this noew
>> flag).
>>
>> Also don't we want to encode the legacy aspect here?
>>
>> Maybe FOLL_LONGTERM_LEGACY_READONLY? Naming is hard :)
> I'm confused about the _READONLY, well. and the FOLL_PIN_NO_GUP_WRITE.
>
> We want to longterm write-pin.
>
> @Pankaj, how come you would call this "FOLL_PIN_NO_GUP_WRITE" -- why "no GUP
> write" ?
Honestly, I did not finalize it then, just tossed the name for some
suggestion :-)
> I agree that someting like FOLL_LONGTERM_LEGACY_* is the right thing to do, but
> I don't see where this is "no write" or "readonly" ?
Maybe FOLL_LONGTERM_LEGACY_, still pondering what that name could be ...
Thanks,
Pankaj
prev parent reply other threads:[~2026-07-10 13:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 14:45 Pankaj Gupta
2026-07-01 16:25 ` David Hildenbrand (Arm)
2026-07-01 16:30 ` Sean Christopherson
2026-07-01 16:39 ` David Hildenbrand (Arm)
2026-07-01 16:56 ` Sean Christopherson
2026-07-06 12:03 ` Gupta, Pankaj
2026-07-07 10:04 ` David Hildenbrand (Arm)
2026-07-07 13:45 ` Gupta, Pankaj
2026-07-07 13:59 ` Sean Christopherson
2026-07-07 14:58 ` David Hildenbrand (Arm)
2026-07-08 16:35 ` Gupta, Pankaj
2026-07-09 14:28 ` Lorenzo Stoakes
2026-07-09 15:19 ` Gupta, Pankaj
2026-07-09 15:44 ` Lorenzo Stoakes
2026-07-10 12:57 ` David Hildenbrand (Arm)
2026-07-10 13:05 ` Lorenzo Stoakes
2026-07-10 15:37 ` David Hildenbrand (Arm)
2026-07-10 15:47 ` Sean Christopherson
2026-07-10 16:13 ` Lorenzo Stoakes
2026-07-10 16:24 ` Sean Christopherson
2026-07-10 16:38 ` David Hildenbrand (Arm)
2026-07-10 16:58 ` Lorenzo Stoakes
2026-07-15 6:38 ` Gupta, Pankaj
2026-07-10 13:06 ` Gupta, Pankaj [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=5b9b8ef2-1481-418a-951c-c48a75921f85@amd.com \
--to=pankaj.gupta@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--cc=yangge1116@126.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
all inboxes | Powered by JetHome®