From: Sohil Mehta <sohil.mehta@intel.com>
To: Kishen Maloor <kishen.maloor@intel.com>, <qemu-devel@nongnu.org>
Cc: <pbonzini@redhat.com>, <zhao1.liu@intel.com>,
<kvm@vger.kernel.org>, <xiaoyao.li@intel.com>,
<binbin.wu@linux.intel.com>, <farrah.chen@intel.com>
Subject: Re: [PATCH 0/5] target/i386: Add support for LASS
Date: Tue, 1 Sep 2026 09:08:16 -0700 [thread overview]
Message-ID: <291cee47-c9a7-41ed-9be4-fbdc1a950078@intel.com> (raw)
In-Reply-To: <20260826035734.114685-1-kishen.maloor@intel.com>
On 8/25/2026 8:57 PM, Kishen Maloor wrote:
> Isaku Yamahata (2):
> target/i386: Add support for LASS in CPUID enumeration
> target/i386: Add LASS support in CR4
>
> Kishen Maloor (3):
> target/i386: Introduce DiamondRapids-v3 to enable LASS
> target/i386: Introduce SierraForest-v7 to enable LASS
> target/i386: Introduce ClearwaterForest-v5 to enable LASS
>
Acked-by: Sohil Mehta <sohil.mehta@intel.com>
> target/i386/cpu.c | 26 +++++++++++++++++++++++++-
> target/i386/cpu.h | 7 ++++++-
> target/i386/helper.c | 4 ++++
> 3 files changed, 35 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2026-09-01 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 3:57 [PATCH 0/5] target/i386: Add support for LASS Kishen Maloor
2026-08-26 3:57 ` [PATCH 1/5] target/i386: Add support for LASS in CPUID enumeration Kishen Maloor
2026-09-02 10:14 ` Zhao Liu
2026-08-26 3:57 ` [PATCH 2/5] target/i386: Add LASS support in CR4 Kishen Maloor
2026-09-02 10:16 ` Zhao Liu
2026-08-26 3:57 ` [PATCH 3/5] target/i386: Introduce DiamondRapids-v3 to enable LASS Kishen Maloor
2026-09-02 10:16 ` Zhao Liu
2026-08-26 3:57 ` [PATCH 4/5] target/i386: Introduce SierraForest-v7 " Kishen Maloor
2026-09-02 10:17 ` Zhao Liu
2026-08-26 3:57 ` [PATCH 5/5] target/i386: Introduce ClearwaterForest-v5 " Kishen Maloor
2026-09-02 10:17 ` Zhao Liu
2026-08-27 3:07 ` [PATCH 0/5] target/i386: Add support for LASS Chen, Farrah
2026-09-01 16:08 ` Sohil Mehta [this message]
2026-09-02 2:40 ` Binbin Wu
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=291cee47-c9a7-41ed-9be4-fbdc1a950078@intel.com \
--to=sohil.mehta@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=farrah.chen@intel.com \
--cc=kishen.maloor@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoyao.li@intel.com \
--cc=zhao1.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox