qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tao Su <tao1.su@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, richard.henderson@linaro.org,
	yang.zhong@intel.com, jing2.liu@intel.com, vkuznets@redhat.com,
	philmd@linaro.org
Subject: [PATCH v2 6/6] target/i386: Add support for PREFETCHIT0/1 in CPUID enumeration
Date: Fri,  3 Mar 2023 14:59:13 +0800	[thread overview]
Message-ID: <20230303065913.1246327-7-tao1.su@linux.intel.com> (raw)
In-Reply-To: <20230303065913.1246327-1-tao1.su@linux.intel.com>

From: Jiaxi Chen <jiaxi.chen@linux.intel.com>

Latest Intel platform Granite Rapids has introduced a new instruction -
PREFETCHIT0/1, which moves code to memory (cache) closer to the
processor depending on specific hints.

The bit definition:
CPUID.(EAX=7,ECX=1):EDX[bit 14]

Add CPUID definition for PREFETCHIT0/1.

Signed-off-by: Jiaxi Chen <jiaxi.chen@linux.intel.com>
Signed-off-by: Tao Su <tao1.su@linux.intel.com>
---
 target/i386/cpu.c | 2 +-
 target/i386/cpu.h | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index eee1e5c25f..719e6a2636 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -894,7 +894,7 @@ FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
             NULL, NULL, NULL, NULL,
             "avx-vnni-int8", "avx-ne-convert", NULL, NULL,
             NULL, NULL, NULL, NULL,
-            NULL, NULL, NULL, NULL,
+            NULL, NULL, "prefetchiti", NULL,
             NULL, NULL, NULL, NULL,
             NULL, NULL, NULL, NULL,
             NULL, NULL, NULL, NULL,
diff --git a/target/i386/cpu.h b/target/i386/cpu.h
index 14876938c1..febb1837d0 100644
--- a/target/i386/cpu.h
+++ b/target/i386/cpu.h
@@ -922,6 +922,8 @@ uint64_t x86_cpu_get_supported_feature_word(FeatureWord w,
 #define CPUID_7_1_EDX_AVX_VNNI_INT8     (1U << 4)
 /* AVX NE CONVERT Instructions */
 #define CPUID_7_1_EDX_AVX_NE_CONVERT    (1U << 5)
+/* PREFETCHIT0/1 Instructions */
+#define CPUID_7_1_EDX_PREFETCHITI       (1U << 14)
 
 /* XFD Extend Feature Disabled */
 #define CPUID_D_1_EAX_XFD               (1U << 4)
-- 
2.34.1



  parent reply	other threads:[~2023-03-03  7:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03  6:59 [PATCH v2 0/6] target/i386: Support new Intel platform Instructions in CPUID enumeration Tao Su
2023-03-03  6:59 ` [PATCH v2 1/6] target/i386: Add support for CMPCCXADD " Tao Su
2023-03-03  6:59 ` [PATCH v2 2/6] target/i386: Add support for AMX-FP16 " Tao Su
2023-03-03  6:59 ` [PATCH v2 3/6] target/i386: Add support for AVX-IFMA " Tao Su
2023-03-03  6:59 ` [PATCH v2 4/6] target/i386: Add support for AVX-VNNI-INT8 " Tao Su
2023-03-03  6:59 ` [PATCH v2 5/6] target/i386: Add support for AVX-NE-CONVERT " Tao Su
2023-03-03  6:59 ` Tao Su [this message]
2023-03-04  4:04 ` [PATCH v2 0/6] target/i386: Support new Intel platform Instructions " Xiaoyao Li
2023-04-26 12:24 ` Paolo Bonzini
2023-04-27  1:39   ` Tao Su

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=20230303065913.1246327-7-tao1.su@linux.intel.com \
    --to=tao1.su@linux.intel.com \
    --cc=jing2.liu@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=vkuznets@redhat.com \
    --cc=yang.zhong@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;
as well as URLs for NNTP newsgroup(s).