From: Zhao Liu <zhao1.liu@intel.com>
To: Ewan Hai <ewanhai-oc@zhaoxin.com>
Cc: pbonzini@redhat.com, xiaoyao.li@intel.com, qemu-devel@nongnu.org,
ewanhai@zhaoxin.com, cobechen@zhaoxin.com, rockcui@zhaoxin.com,
louisqi@zhaoxin.com, liamni@zhaoxin.com, frankzhu@zhaoxin.com
Subject: Re: [PATCH v2 4/4] target/i386: Update CMPLegacy handling for Zhaoxin CPUs
Date: Fri, 9 Aug 2024 11:47:21 +0800 [thread overview]
Message-ID: <ZrWRSXIPYwEkpXK/@intel.com> (raw)
In-Reply-To: <d37a0bb1-23c3-4226-87c9-da73f4b59d72@zhaoxin.com>
On Thu, Aug 08, 2024 at 11:25:45PM -0400, Ewan Hai wrote:
[snip]
> Thank you for your suggestion; the changes will indeed make it clearer.
> I have a question: since you’ve already added your reviewed-by tag to
> the first three patches, if I want to modify these descriptions, should
> I submit a v3 patchset containing all four patches, or should I only send a
> new patch titled "target/i386: Mask CMPLegacy bit in CPUID[0x80000001].ecx
> for Zhaoxin/Centaur CPUs"?
The v3 should contain all 4 patches, and you can add my R/b tag in the
first three patches.
next prev parent reply other threads:[~2024-08-09 3:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 11:25 [PATCH v2 0/4] Add support for Zhaoxin Yongfeng CPU model and other improvements EwanHai
2024-07-04 11:25 ` [PATCH v2 1/4] target/i386: Add support for Zhaoxin CPU vendor identification EwanHai
2024-08-08 10:31 ` Zhao Liu
2024-07-04 11:25 ` [PATCH v2 2/4] target/i386: Add CPUID leaf 0xC000_0001 EDX definitions EwanHai
2024-08-08 10:35 ` Zhao Liu
2024-07-04 11:25 ` [PATCH v2 3/4] target/i386: Introduce Zhaoxin Yongfeng CPU model EwanHai
2024-08-08 10:55 ` Zhao Liu
2024-07-04 11:25 ` [PATCH v2 4/4] target/i386: Update CMPLegacy handling for Zhaoxin CPUs EwanHai
2024-08-08 10:30 ` Zhao Liu
2024-08-09 1:44 ` Ewan Hai
2024-08-09 3:22 ` Zhao Liu
2024-08-09 3:25 ` Ewan Hai
2024-08-09 3:47 ` Zhao Liu [this message]
2024-08-09 3:37 ` Ewan Hai
2024-08-08 9:23 ` [PATCH v2 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=ZrWRSXIPYwEkpXK/@intel.com \
--to=zhao1.liu@intel.com \
--cc=cobechen@zhaoxin.com \
--cc=ewanhai-oc@zhaoxin.com \
--cc=ewanhai@zhaoxin.com \
--cc=frankzhu@zhaoxin.com \
--cc=liamni@zhaoxin.com \
--cc=louisqi@zhaoxin.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rockcui@zhaoxin.com \
--cc=xiaoyao.li@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.