From: "Zhang, Cathy" <cathy.zhang@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Cc: "Christopherson, Sean J" <sean.j.christopherson@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Park, Kyung Min" <kyung.min.park@intel.com>,
"ricardo.neri-calderon@linux.intel.com"
<ricardo.neri-calderon@linux.intel.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"jmattson@google.com" <jmattson@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>,
"jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>
Subject: Re: [PATCH v3 2/2] x86/kvm: Expose new features for supported cpuid
Date: Tue, 11 Aug 2020 08:18:32 +0800 [thread overview]
Message-ID: <8f5d3b35-2478-c030-e51d-3183dbcaf4a6@intel.com> (raw)
In-Reply-To: <e92df7bb267c478f8dfa28a31fc59d95@intel.com>
On 8/11/2020 7:59 AM, Luck, Tony wrote:
>> As you suggest, I will split the kvm patch into two parts, SERIALIZE and
>> TSXLDTRK, and this series will include three patches then, 2 kvm patches
>> and 1 kernel patch. SERIALIZE could get merged into 5.9, but TSXLDTRK
>> should wait for the next release. I just want to double confirm with
>> you, please help correct me if I'm wrong.
> Paolo is saying that he has applied the SERIALIZE part to his KVM tree.
>
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=queue&id=43bd9ef42b3b862c97f1f4e86bf3ace890bef924
>
> Next step for you is a two part series.
>
> Part 1: Add TSXLDTRK to cpufeatures.h
> Part 2: Add TSXLDTRK to arch/x86/kvm/cpuid.c (on top of the version that Paolo committed with SERIALIZE)
>
> Paolo: The 5.9 merge window is still open this week. Will you send the KVM serialize patch to Linus
> before this merge window closes? Or do you have it queued for v5.10?
>
> -Tony
Got it! Thanks for the explanation, Tony!
next prev parent reply other threads:[~2020-08-11 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 7:47 [PATCH v3 0/2] Expose new features for Intel processor Cathy Zhang
2020-08-09 7:47 ` [PATCH v3 1/2] x86/cpufeatures: Enumerate TSX suspend load address tracking instructions Cathy Zhang
2020-08-09 7:47 ` [PATCH v3 2/2] x86/kvm: Expose new features for supported cpuid Cathy Zhang
2020-08-09 17:14 ` Paolo Bonzini
2020-08-10 23:50 ` Zhang, Cathy
2020-08-10 23:59 ` Luck, Tony
2020-08-11 0:18 ` Zhang, Cathy [this message]
2020-08-11 8:32 ` Paolo Bonzini
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=8f5d3b35-2478-c030-e51d-3183dbcaf4a6@intel.com \
--to=cathy.zhang@intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=jpoimboe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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