From: Tao Su <tao1.su@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kvm@vger.kernel.org, x86@kernel.org, seanjc@google.com,
pbonzini@redhat.com, dave.hansen@linux.intel.com,
chao.gao@intel.com, xiaoyao.li@intel.com, jiaan.lu@intel.com,
xuelian.guo@intel.com
Subject: Re: [PATCH 0/4] Advertise CPUID for new instructions in Clearwater Forest
Date: Mon, 4 Nov 2024 21:21:02 +0800 [thread overview]
Message-ID: <ZyjKPkrFXrMnqbdS@linux.bj.intel.com> (raw)
In-Reply-To: <20241104095834.GBZyiaytJCvXylJgc2@fat_crate.local>
On Mon, Nov 04, 2024 at 10:58:34AM +0100, Borislav Petkov wrote:
> On Mon, Nov 04, 2024 at 03:04:41PM +0800, Tao Su wrote:
> > Would it be better if I attach rev, chapter and section?
>
> Put enough information from the document so that one can find it doing a web
> search. So that even if the vendor URL changes, a search engine will index it
> shortly after again.
>
Sure, I agree with you.
> > I mainly referred to the previous patch set [*] which is very similar to
> > this one.
>
> That patch set is doing more than just adding bits although I still would've
> merged patches 3-8 as they're simply adding feature bits and are obvious.
>
Got it.
> > If you think a patch is better, I can send a v2 with only one
> > patch.
>
> Yes please.
Will do, thanks!
prev parent reply other threads:[~2024-11-04 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 6:35 [PATCH 0/4] Advertise CPUID for new instructions in Clearwater Forest Tao Su
2024-11-04 6:35 ` [PATCH 1/4] x86: KVM: Advertise SHA512 CPUID to userspace Tao Su
2024-11-04 6:35 ` [PATCH 2/4] x86: KVM: Advertise SM3 " Tao Su
2024-11-04 16:40 ` Dave Hansen
2024-11-05 0:58 ` Tao Su
2024-11-04 6:35 ` [PATCH 3/4] x86: KVM: Advertise SM4 " Tao Su
2024-11-04 6:35 ` [PATCH 4/4] KVM: x86: Advertise AVX-VNNI-INT16 " Tao Su
2024-11-04 6:51 ` [PATCH 0/4] Advertise CPUID for new instructions in Clearwater Forest Borislav Petkov
2024-11-04 7:04 ` Tao Su
2024-11-04 9:58 ` Borislav Petkov
2024-11-04 13:21 ` Tao Su [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=ZyjKPkrFXrMnqbdS@linux.bj.intel.com \
--to=tao1.su@linux.intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jiaan.lu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=xuelian.guo@intel.com \
/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.