From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH 0/4] ppc: improve some memory ordering issues
Date: Mon, 23 May 2022 16:24:22 -0300 [thread overview]
Message-ID: <a7632f4e-156c-3efd-949a-4e56408ddb7e@gmail.com> (raw)
In-Reply-To: <20220519135908.21282-1-npiggin@gmail.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 5/19/22 10:59, Nicholas Piggin wrote:
> Since RFC[*], this fixes a compile issue noticed by Richard,
> and has survived some basic stressing with mttcg.
>
> Thanks,
> Nick
>
> [*] https://lists.nongnu.org/archive/html/qemu-ppc/2022-05/msg00046.html
>
> Nicholas Piggin (4):
> target/ppc: Fix eieio memory ordering semantics
> tcg/ppc: ST_ST memory ordering is not provided with eieio
> tcg/ppc: Optimize memory ordering generation with lwsync
> target/ppc: Implement lwsync with weaker memory ordering
>
> target/ppc/cpu.h | 4 +++-
> target/ppc/cpu_init.c | 13 +++++++------
> target/ppc/machine.c | 3 ++-
> target/ppc/translate.c | 35 +++++++++++++++++++++++++++++++++--
> tcg/ppc/tcg-target.c.inc | 11 ++++++-----
> 5 files changed, 51 insertions(+), 15 deletions(-)
>
prev parent reply other threads:[~2022-05-23 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 13:59 [PATCH 0/4] ppc: improve some memory ordering issues Nicholas Piggin
2022-05-19 13:59 ` [PATCH 1/4] target/ppc: Fix eieio memory ordering semantics Nicholas Piggin
2022-05-19 15:30 ` Richard Henderson
2022-05-19 13:59 ` [PATCH 2/4] tcg/ppc: ST_ST memory ordering is not provided with eieio Nicholas Piggin
2022-05-19 13:59 ` [PATCH 3/4] tcg/ppc: Optimize memory ordering generation with lwsync Nicholas Piggin
2022-05-19 15:30 ` Richard Henderson
2022-05-19 13:59 ` [PATCH 4/4] target/ppc: Implement lwsync with weaker memory ordering Nicholas Piggin
2022-05-19 15:34 ` Richard Henderson
2022-05-23 19:24 ` Daniel Henrique Barboza [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=a7632f4e-156c-3efd-949a-4e56408ddb7e@gmail.com \
--to=danielhb413@gmail.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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.