From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
x86@kernel.org, kvm@vger.kernel.org,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
Paul Durrant <pdurrant@amazon.com>
Cc: Borislav Petkov <bp@alien8.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Woodhouse <dwmw2@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Juergen Gross <jgross@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v7 0/2] KVM: x86/xen: update Xen CPUID Leaf 4
Date: Thu, 19 Jan 2023 20:48:54 +0000 [thread overview]
Message-ID: <167409095498.2375862.15711695818147385057.b4-ty@google.com> (raw)
In-Reply-To: <20230106103600.528-1-pdurrant@amazon.com>
On Fri, 06 Jan 2023 10:35:58 +0000, Paul Durrant wrote:
> Patch #2 was the original patch. It has been expended to a series in v6.
>
> Paul Durrant (2):
> KVM: x86/cpuid: generalize kvm_update_kvm_cpuid_base() and also
> capture limit
> KVM: x86/xen: update Xen CPUID Leaf 4 (tsc info) sub-leaves, if
> present
>
> [...]
Applied to kvm-x86 misc, thanks!
[1/2] KVM: x86/cpuid: generalize kvm_update_kvm_cpuid_base() and also capture limit
https://github.com/kvm-x86/linux/commit/e3ac476711ca
[2/2] KVM: x86/xen: update Xen CPUID Leaf 4 (tsc info) sub-leaves, if present
https://github.com/kvm-x86/linux/commit/509d19565173
--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes
prev parent reply other threads:[~2023-01-19 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 10:35 [PATCH v7 0/2] KVM: x86/xen: update Xen CPUID Leaf 4 Paul Durrant
2023-01-06 10:35 ` [PATCH v7 1/2] KVM: x86/cpuid: generalize kvm_update_kvm_cpuid_base() and also capture limit Paul Durrant
2023-01-11 10:00 ` David Woodhouse
2023-01-06 10:36 ` [PATCH v7 2/2] KVM: x86/xen: update Xen CPUID Leaf 4 (tsc info) sub-leaves, if present Paul Durrant
2023-01-11 10:00 ` David Woodhouse
2023-01-19 20:48 ` Sean Christopherson [this message]
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=167409095498.2375862.15711695818147385057.b4-ty@google.com \
--to=seanjc@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pdurrant@amazon.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.