From: Richard Henderson <richard.henderson@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: lei4.wang@intel.com, robert.hu@linux.intel.com,
xiaoyao.li@intel.com, chenyi.qiang@intel.com
Subject: Re: [PATCH v4 2/4] target/i386: add FZRM, FSRS, FSRC
Date: Mon, 27 Feb 2023 09:31:12 -1000 [thread overview]
Message-ID: <c45b9a95-7951-6dab-3ef3-5d7189ca7b09@linaro.org> (raw)
In-Reply-To: <20230227101332.636203-3-pbonzini@redhat.com>
On 2/27/23 00:13, Paolo Bonzini wrote:
> These are three more markers for string operation optimizations.
> They can all be added to TCG, whose string operations are more or
> less as fast as they can be for short lengths.
>
> Signed-off-by: Paolo Bonzini<pbonzini@redhat.com>
> ---
> target/i386/cpu.c | 7 ++++---
> target/i386/cpu.h | 7 +++++++
> 2 files changed, 11 insertions(+), 3 deletions(-)
They could in fact be faster, but good enough. :-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2023-02-27 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:13 [PATCH v4 0/4] target/i386: Add new CPU model SapphireRapids and new fast string op leaves Paolo Bonzini
2023-02-27 10:13 ` [PATCH v4 1/4] target/i386: add FSRM to TCG Paolo Bonzini
2023-02-27 19:29 ` Richard Henderson
2023-02-27 10:13 ` [PATCH v4 2/4] target/i386: add FZRM, FSRS, FSRC Paolo Bonzini
2023-02-27 13:39 ` Xiaoyao Li
2023-02-27 19:31 ` Richard Henderson [this message]
2023-02-27 10:13 ` [PATCH v4 3/4] target/i386: KVM: allow fast string operations if host supports them Paolo Bonzini
2023-02-27 13:35 ` Xiaoyao Li
2023-02-27 19:32 ` Richard Henderson
[not found] ` <20230227101332.636203-5-pbonzini@redhat.com>
2023-02-27 13:45 ` [PATCH v4 4/4] target/i386: Add new CPU model SapphireRapids Xiaoyao Li
2023-02-28 8:46 ` [PATCH v4 0/4] target/i386: Add new CPU model SapphireRapids and new fast string op leaves Xiaoyao Li
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=c45b9a95-7951-6dab-3ef3-5d7189ca7b09@linaro.org \
--to=richard.henderson@linaro.org \
--cc=chenyi.qiang@intel.com \
--cc=lei4.wang@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@linux.intel.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 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).