From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>
Subject: Re: [PATCH] pc-bios/s390-ccw: Use memory barriers in virtio code
Date: Wed, 17 Feb 2021 07:11:37 -0800 [thread overview]
Message-ID: <52bc865c-9e4d-ebfa-e7c0-15747f194532@linaro.org> (raw)
In-Reply-To: <CAFEAcA-sgkxazKcR8tbLdj_B3F5bwg2c4TqkNd7gCSCQ5BYQEQ@mail.gmail.com>
On 2/17/21 3:15 AM, Peter Maydell wrote:
> This isn't aarch64-host-specific, though, is it? It's going to be
> the situation for any host with a relaxed memory model.
Yes. I intend to make the code-generation changes generic.
> Do we really
> want to make all loads and stores lower-performance by adding in
> the ldacq/strel (or worse, barriers everywhere on host archs without
> ldacq/strel)?
Well, yes. But then we get to enable mttcg too.
> I feel like there ought to be an alternate approach
> involving using some kind of exclusion to ensure that we don't run
> the iothreads in parallel with the vCPU thread if we're using the
> non-MTTCG setup where all the vCPUs are on a single thread, and that
> that's probably less of a perf hit.
I don't know where to put such a block, do you?
The memory barriers are a perf hit with -smp 1, but I would think that all that
and more are recoverable by not having to run -smp 2 serially.
r~
prev parent reply other threads:[~2021-02-17 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 11:00 [PATCH] pc-bios/s390-ccw: Use memory barriers in virtio code Thomas Huth
2021-02-16 11:43 ` Peter Maydell
2021-02-16 11:47 ` Thomas Huth
2021-02-16 11:47 ` Cornelia Huck
2021-02-16 14:21 ` Thomas Huth
2021-02-16 14:30 ` Cornelia Huck
2021-02-16 14:32 ` Peter Maydell
2021-02-16 14:35 ` Thomas Huth
2021-02-16 14:37 ` Peter Maydell
2021-02-16 14:49 ` Cornelia Huck
2021-02-16 14:40 ` Halil Pasic
2021-02-16 15:17 ` Cornelia Huck
2021-02-16 16:15 ` Thomas Huth
2021-02-16 16:44 ` Peter Maydell
2021-02-16 17:11 ` Halil Pasic
2021-02-17 4:31 ` Richard Henderson
2021-02-17 11:15 ` Peter Maydell
2021-02-17 15:11 ` Richard Henderson [this message]
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=52bc865c-9e4d-ebfa-e7c0-15747f194532@linaro.org \
--to=richard.henderson@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).