From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ewan Hai-oc <ewanhai-oc@zhaoxin.com>,
pbonzini@redhat.com, tglx@kernel.org, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
binbin.wu@linux.intel.com, cobechen@zhaoxin.com,
tonywwang@zhaoxin.com
Subject: Re: [PATCH v3 0/5] KVM: x86: Expose Zhaoxin CPUID 0xC0000001 EDX cryptographic features
Date: Mon, 6 Jul 2026 07:38:48 -0700 [thread overview]
Message-ID: <aku9-O5K4a7vTDXS@google.com> (raw)
In-Reply-To: <20260702014926.GHakXDpsIK5srVj0Mk@fat_crate.local>
On Wed, Jul 01, 2026, Borislav Petkov wrote:
> Btw, Sashiko rightfully mentions:
Please no, let the perf folks deal with synchronizing the headers. I explicitly
instruct people *not* to copy kernel header changes to tools/ when sumbmitting
KVM patches, because it creates the false impression that KVM selftests actually
consume those headers.
> https://lore.kernel.org/r/20260610024350.F13471F00893@smtp.kernel.org
next prev parent reply other threads:[~2026-07-06 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 2:35 [PATCH v3 0/5] KVM: x86: Expose Zhaoxin CPUID 0xC0000001 EDX cryptographic features Ewan Hai-oc
2026-06-10 2:35 ` [PATCH v3 1/5] KVM: x86: Expose Zhaoxin SM2 CPUID feature Ewan Hai-oc
2026-06-10 2:35 ` [PATCH v3 2/5] KVM: x86: Expose Zhaoxin CCS (SM3 + SM4) " Ewan Hai-oc
2026-06-10 2:35 ` [PATCH v3 3/5] KVM: x86: Expose Zhaoxin RNG2 " Ewan Hai-oc
2026-06-10 2:35 ` [PATCH v3 4/5] KVM: x86: Expose Zhaoxin PHE2 " Ewan Hai-oc
2026-06-10 2:35 ` [PATCH v3 5/5] KVM: x86: Expose Zhaoxin RSA " Ewan Hai-oc
2026-07-01 2:45 ` [PATCH v3 0/5] KVM: x86: Expose Zhaoxin CPUID 0xC0000001 EDX cryptographic features Ewan Hai-oc
2026-07-01 14:09 ` Sean Christopherson
2026-07-02 1:49 ` Borislav Petkov
2026-07-02 3:27 ` Ewan Hai-oc
2026-07-06 14:38 ` Sean Christopherson [this message]
2026-07-06 17:00 ` Borislav Petkov
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=aku9-O5K4a7vTDXS@google.com \
--to=seanjc@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=cobechen@zhaoxin.com \
--cc=dave.hansen@linux.intel.com \
--cc=ewanhai-oc@zhaoxin.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@kernel.org \
--cc=tonywwang@zhaoxin.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