From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-arm@nongnu.org
Subject: Re: [PATCH 2/2] hw/intc/arm_gicv3: Replace mis-used MEMTX_* constants by booleans
Date: Tue, 31 Aug 2021 09:56:45 -0700 [thread overview]
Message-ID: <e764f9f5-5f7e-5a70-e5c7-135e62784959@linaro.org> (raw)
In-Reply-To: <20210826180704.2131949-3-philmd@redhat.com>
On 8/26/21 11:07 AM, Philippe Mathieu-Daudé wrote:
> Quoting Peter Maydell:
>
> These MEMTX_* aren't from the memory transaction API functions;
> they're just being used by gicd_readl() and friends as a way to
> indicate a success/failure so that the actual MemoryRegionOps
> read/write fns like gicv3_dist_read() can log a guest error.
> Arguably this is a bit of a misuse of the MEMTX_* constants and
> perhaps we should have gicd_readl etc return a bool instead.
>
> Follow his suggestion and replace the MEMTX_* constants by
> boolean values, simplifying a bit the gicv3_dist_read() /
> gicv3_dist_write() handlers.
>
> Suggested-by: Peter Maydell<peter.maydell@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé<philmd@redhat.com>
> ---
> hw/intc/arm_gicv3_dist.c | 201 +++++++++++++++++++++------------------
> 1 file changed, 106 insertions(+), 95 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2021-08-31 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 18:07 [PATCH 0/2] hw/intc/arm_gicv3: Replace mis-used MEMTX_* constants by booleans Philippe Mathieu-Daudé
2021-08-26 18:07 ` [PATCH 1/2] hw/intc/arm_gicv3_dist: Rename 64-bit accessors with 'q' suffix Philippe Mathieu-Daudé
2021-08-31 16:53 ` Richard Henderson
2021-08-26 18:07 ` [PATCH 2/2] hw/intc/arm_gicv3: Replace mis-used MEMTX_* constants by booleans Philippe Mathieu-Daudé
2021-08-31 16:56 ` Richard Henderson [this message]
2021-08-31 20:30 ` [PATCH 0/2] " Peter Maydell
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=e764f9f5-5f7e-5a70-e5c7-135e62784959@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).