From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: [PATCH 0/5] Reinstate ability to use Qemu on pre-SSE4.1 x86 hosts
Date: Wed, 12 Jun 2024 15:39:28 +0200 [thread overview]
Message-ID: <CABgObfbPu10_jEuT2sEHJmF91Vov9M7bTmLR9dQXRR5gicNF5Q@mail.gmail.com> (raw)
In-Reply-To: <b5fac5cc-40af-2437-44c4-4e0d5747691d@ispras.ru>
On Wed, Jun 12, 2024 at 3:34 PM Alexander Monakov <amonakov@ispras.ru> wrote:
> On Wed, 12 Jun 2024, Paolo Bonzini wrote:
> > > I found out from the mailing list. My Core2-based desktop would be affected.
> >
> > Do you run QEMU on it? With KVM or TCG?
>
> Excuse me? Are you going to ask for SSH access to ensure my computer really
> exists and is in working order?
Come on. The thing is, I'm not debating the existence of computers
that don't have x86_64-v2, but I *am* debating the usefulness of
making QEMU run on them and any extra information can be interesting.
> Can you tell me why you never commented on buffer_is_zero improvements, where
> v1 was sent in October? Just trying to understand how you care for 2% of L1D
> use but could be ok with those kinds of speedups be dropped on the floor.
I'm not sure if there is any overlap in the scenarios where
buffer_is_zero performance matters, and x86 emulation. People can care
about thing A but not thing B. If there's anything that you think I
can help reviewing, feel free to let me know offlist.
Paolo
next prev parent reply other threads:[~2024-06-12 13:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 10:55 [PATCH 0/5] Reinstate ability to use Qemu on pre-SSE4.1 x86 hosts Alexander Monakov
2024-06-12 10:55 ` [PATCH 1/5] Revert "host/i386: assume presence of POPCNT" Alexander Monakov
2024-06-12 10:55 ` [PATCH 2/5] Revert "host/i386: assume presence of SSSE3" Alexander Monakov
2024-06-12 10:55 ` [PATCH 3/5] Revert "host/i386: assume presence of SSE2" Alexander Monakov
2024-06-12 10:55 ` [PATCH 4/5] Revert "host/i386: assume presence of CMOV" Alexander Monakov
2024-06-12 10:55 ` [PATCH 5/5] Revert "meson: assume x86-64-v2 baseline ISA" Alexander Monakov
2024-06-12 11:04 ` [PATCH 0/5] Reinstate ability to use Qemu on pre-SSE4.1 x86 hosts Daniel P. Berrangé
2024-06-12 11:12 ` Paolo Bonzini
2024-06-12 11:19 ` Alexander Monakov
2024-06-12 11:29 ` Paolo Bonzini
2024-06-12 11:46 ` Alexander Monakov
2024-06-12 11:58 ` Paolo Bonzini
2024-06-12 12:10 ` Alexander Monakov
2024-06-12 12:13 ` Paolo Bonzini
2024-06-12 13:34 ` Alexander Monakov
2024-06-12 13:39 ` Paolo Bonzini [this message]
2024-06-12 14:27 ` Alexander Monakov
2024-06-12 11:38 ` Daniel P. Berrangé
2024-06-12 11:51 ` Paolo Bonzini
2024-06-12 12:21 ` Daniel P. Berrangé
2024-06-12 15:09 ` Daniel P. Berrangé
2024-06-12 15:29 ` Paolo Bonzini
2024-06-12 15:40 ` Alexander Monakov
2024-06-12 16:24 ` Daniel P. Berrangé
2024-06-12 17:06 ` Daniel P. Berrangé
2024-06-12 17:00 ` Daniel P. Berrangé
2024-06-12 17:08 ` Paolo Bonzini
2024-06-23 21:27 ` Alexander Monakov
2024-06-23 22:14 ` Richard Henderson
2024-06-12 11:14 ` Alexander Monakov
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=CABgObfbPu10_jEuT2sEHJmF91Vov9M7bTmLR9dQXRR5gicNF5Q@mail.gmail.com \
--to=pbonzini@redhat.com \
--cc=amonakov@ispras.ru \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).