From: Zhao Liu <zhao1.liu@intel.com>
To: EwanHai <ewanhai-oc@zhaoxin.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, ewanhai@zhaoxin.com,
cobechen@zhaoxin.com, rockcui@zhaoxin.com, louisqi@zhaoxin.com
Subject: Re: [PATCH 0/4] Add support for Zhaoxin Yongfeng CPU model and other improvements
Date: Tue, 25 Jun 2024 22:31:19 +0800 [thread overview]
Message-ID: <ZnrUt0/5CZ2Ww45e@intel.com> (raw)
In-Reply-To: <20240625091905.1325205-1-ewanhai-oc@zhaoxin.com>
Hi EwanHai,
On Tue, Jun 25, 2024 at 05:19:01AM -0400, EwanHai wrote:
> Date: Tue, 25 Jun 2024 05:19:01 -0400
> From: EwanHai <ewanhai-oc@zhaoxin.com>
> Subject: [PATCH 0/4] Add support for Zhaoxin Yongfeng CPU model and other
> improvements
> X-Mailer: git-send-email 2.34.1
>
> This patch series introduces support for the Zhaoxin Yongfeng CPU model and includes
> some improvements and updates related to Zhaoxin and VIA CPUs. The changes ensure that
> QEMU can correctly identify and emulate Zhaoxin CPUs, providing accurate functionality
> and performance characteristics.
>
>
> ### Summary of Changes
>
> EwanHai (4):
> target/i386: Add support for Zhaoxin/VIA CPU vendor identification
> target/i386: Add CPUID leaf 0xC000_0001 EDX definitions
> target/i386: Introduce Zhaoxin Yongfeng CPU model
> target/i386: Update CMPLegacy handling for Zhaoxin and VIA CPUs
>
> target/i386/cpu.c | 130 ++++++++++++++++++++++++++++++++++++++++++++--
> target/i386/cpu.h | 38 ++++++++++++++
> 2 files changed, 165 insertions(+), 3 deletions(-)
>
> ### Known Bugs
>
> 1. Issue with VMX Preemption Timer Rate on Yongfeng CPU:
> - Description: On Yongfeng CPUs, the VMX preemption timer rate is 128, meaning that
> bits 4:0 of MSR_IA32_VMX_MISC_CTLS should be set to 7. However, due to Intel's rate
> being 5, the Linux kernel has hardcoded this value as 5:
> `#define VMX_MISC_EMULATED_PREEMPTION_TIMER_RATE 5`
> - Impact: This discrepancy can cause incorrect behavior in the VMX preemption timer on
> Yongfeng CPUs.
> - Workaround: A patch to correct this issue in the Linux kernel is currently being
> prepared and will be submitted soon.
>
Thanks for your patch. Is there some spec/datasheet link that people can
refer to?
Regards,
Zhao
next prev parent reply other threads:[~2024-06-25 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 9:19 [PATCH 0/4] Add support for Zhaoxin Yongfeng CPU model and other improvements EwanHai
2024-06-25 9:19 ` [PATCH 1/4] target/i386: Add support for Zhaoxin/VIA CPU vendor identification EwanHai
2024-06-25 9:19 ` [PATCH 2/4] target/i386: Add CPUID leaf 0xC000_0001 EDX definitions EwanHai
2024-06-25 9:19 ` [PATCH 3/4] target/i386: Introduce Zhaoxin Yongfeng CPU model EwanHai
2024-06-25 9:19 ` [PATCH 4/4] target/i386: Update CMPLegacy handling for Zhaoxin and VIA CPUs EwanHai
2024-07-03 14:49 ` Xiaoyao Li
2024-07-04 3:14 ` Ewan Hai
2024-07-04 3:19 ` Xiaoyao Li
2024-07-04 6:32 ` Ewan Hai
2024-06-25 14:31 ` Zhao Liu [this message]
2024-06-26 2:47 ` [PATCH 0/4] Add support for Zhaoxin Yongfeng CPU model and other improvements Ewan Hai
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=ZnrUt0/5CZ2Ww45e@intel.com \
--to=zhao1.liu@intel.com \
--cc=cobechen@zhaoxin.com \
--cc=ewanhai-oc@zhaoxin.com \
--cc=ewanhai@zhaoxin.com \
--cc=louisqi@zhaoxin.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rockcui@zhaoxin.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;
as well as URLs for NNTP newsgroup(s).