From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Jon Cargille <jcargill@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Eric Northup <digitaleric@gmail.com>,
Eric Northup <digitaleric@google.com>
Subject: Re: [PATCH 1/1] KVM: pass through CPUID(0x80000006)
Date: Tue, 14 Apr 2020 19:51:05 -0700 [thread overview]
Message-ID: <20200415025105.GE12547@linux.intel.com> (raw)
In-Reply-To: <20200415023726.GD12547@linux.intel.com>
On Tue, Apr 14, 2020 at 07:37:26PM -0700, Sean Christopherson wrote:
> On Tue, Apr 14, 2020 at 06:23:20PM -0700, Jon Cargille wrote:
> > From: Eric Northup <digitaleric@gmail.com>
> >
> > Return L2 cache and TLB information to guests.
> > They could have been set before, but the defaults that KVM returns will be
> > necessary for usermode that doesn't supply their own CPUID tables.
>
> I don't follow the changelog. The code makes sense, but I don't understand
> the justification. This only affects KVM_GET_SUPPORTED_CPUID, i.e. what's
> advertised to userspace, it doesn't directly change CPUID emulation in any
> way. The "They could have been set before" blurb is especially confusing.
>
> I assume you want to say something like:
>
> Return the host's L2 cache and TLB information for CPUID.0x80000006
> instead of zeroing out the entry as part of KVM_GET_SUPPORTED_CPUID.
> This allows a userspace VMM to feed KVM_GET_SUPPORTED_CPUID's output
> directly into KVM_SET_CPUID2 (without breaking the guest).
>
> > Signed-off-by: Eric Northup <digitaleric@google.com>
> > Signed-off-by: Eric Northup <digitaleric@gmail.com>
> > Signed-off-by: Jon Cargille <jcargill@google.com>
> > Signed-off-by: Jim Mattson <jmattson@google.com>
>
> Jim's tag is unnecessary, unless he was a middleman between Eric and Jon,
> in which case Jim's tag should also come between Eric's and Jon's.
>
> Only one of Eric's signoffs is needed (the one that matches the From: tag,
> i.e. is the official author). I'm guessing Google would prefer the author
> to be the @google.com address.
Ah, Eric's @google.com mail bounced. Maybe do:
Signed-off-by: Eric Northup (Google) <digitaleric@gmail.com>
to clarify the work was done for Google without having a double signoff
and/or a dead email.
next prev parent reply other threads:[~2020-04-15 2:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 1:23 [PATCH 1/1] KVM: pass through CPUID(0x80000006) Jon Cargille
2020-04-15 2:37 ` Sean Christopherson
2020-04-15 2:51 ` Sean Christopherson [this message]
2020-04-15 5:27 ` Eric Northup
2020-04-15 14:52 ` Paolo Bonzini
2020-04-15 17:27 ` Jon Cargille
[not found] ` <CANxmayh4P5hhbJPxAnA2nvbzZC9EwFPeVCxDrkHzu8h6Y7JPPQ@mail.gmail.com>
2020-04-15 17:32 ` Sean Christopherson
2023-07-07 11:41 ` Takahiro Itazuri
2023-07-12 15:58 ` Sean Christopherson
2023-07-12 17:02 ` Takahiro Itazuri
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=20200415025105.GE12547@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bp@alien8.de \
--cc=digitaleric@gmail.com \
--cc=digitaleric@google.com \
--cc=hpa@zytor.com \
--cc=jcargill@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).