| 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
| ||
|
Date: Mon, 9 Jan 2023 18:13:00 +0000
From: Sean Christopherson <seanjc@...gle.com>
To: Vishal Annapurve <vannapurve@...gle.com>
Cc: x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, pbonzini@...hat.com,
shuah@...nel.org, bgardon@...gle.com, oupton@...gle.com,
peterx@...hat.com, vkuznets@...hat.com, dmatlack@...gle.com
Subject: Re: [V4 PATCH 2/4] KVM: selftests: x86: Add variables to store cpu
type
In shortlogs and changelogs, try to provide a synopsis of the change, not a
literal description of the change. As suggested in the previous patch, this:
KVM: selftests: Cache host CPU vendor (AMD vs. Intel)
is more precise (vendor instead of "cpu type") and hints at the intent (caching
the information), whereas this doesn't capture the vendor part, nor does it provide
any hint whatsoever as to (a) how the variables will be used or (b) why we want to
add variables to store
KVM: selftests: x86: Add variables to store cpu type
On Wed, Dec 28, 2022, Vishal Annapurve wrote:
> Add variables to hold the cpu vendor type that are initialized early
> during the selftest setup and later synced to guest vm post VM creation.
>
> These variables will be used in later patches to avoid querying CPU
> type multiple times.
Performance is a happy bonus, it is not the main reason for caching. The main
reason for caching is so that the guest can select the native hypercall instruction
without having to make assumptions about guest vs. host CPUID information.
Powered by blists - more mailing lists