linux-kernel - Re: [PATCH] KVM: nVMX: Rename prepare_vmcs02_*_full to prepare_vmcs02_*

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <525f4ee1-c111-aaa0-2dcd-6c5ce26e3088@redhat.com>
Date:   Fri, 7 Jun 2019 18:24:22 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Sean Christopherson <sean.j.christopherson@...el.com>
Cc:     linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH] KVM: nVMX: Rename prepare_vmcs02_*_full to
 prepare_vmcs02_*_extra

On 07/06/19 18:04, Sean Christopherson wrote:
>> That's what came to mind first, but then "extended" had the same issue
>> as "full" (i.e. encompassing the "basic" set as well) so I decided you
>> knew better!
> Ah, I was thinking of "basic" and "extended" as separate states, but your
> interpretation is correct.
> 
> I probably have a slight preference for 'uncommon' over 'extra'?  I feel
> like they have equal odds of being misinterpreted, so pick your poison :-)

Among your proposals, in fact, I also thought of "uncommon" and "rare".
 Uncommon is a bit long so I'll go with "rare", knowing that the meat
reference will give me a chuckle every now and then.

Paolo