Re: [PATCH] KVM: SEV: drop FOLL_LONGTERM for encrypted region registration

[Gupta, Pankaj]

> > 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