From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Northup <digitaleric@gmail.com>,
Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Jon Cargille <jcargill@google.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@google.com>
Subject: Re: [PATCH 1/1] KVM: pass through CPUID(0x80000006)
Date: Wed, 15 Apr 2020 16:52:35 +0200 [thread overview]
Message-ID: <c351cec8-fb35-c34f-edbf-2117fa147082@redhat.com> (raw)
In-Reply-To: <CAPC9edWgcrC+mc1pQSYmJjPs17VZ-Af1LJ+s6PaeY=9fPA89NQ@mail.gmail.com>
On 15/04/20 07:27, Eric Northup wrote:
>>> 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).
> This is a much better commit message, thanks.
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2020-04-15 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 1:23 Jon Cargille
2020-04-15 2:37 ` Sean Christopherson
2020-04-15 2:51 ` Sean Christopherson
2020-04-15 5:27 ` Eric Northup
2020-04-15 14:52 ` Paolo Bonzini [this message]
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=c351cec8-fb35-c34f-edbf-2117fa147082@redhat.com \
--to=pbonzini@redhat.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=sean.j.christopherson@intel.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
all inboxes | Powered by JetHome®