From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, qemu-ppc@nongnu.org, qemu-arm@nongnu.org,
qemu-block@nongnu.org, BALATON Zoltan <balaton@eik.bme.hu>
Subject: Re: [PATCH v2 3/4] bulk: Replace TARGET_FMT_plx -> HWADDR_PRIx
Date: Wed, 11 Jan 2023 09:50:25 -1000 [thread overview]
Message-ID: <782e40cf-532b-8148-1512-1b56668977e1@linaro.org> (raw)
In-Reply-To: <20230111083909.42624-4-philmd@linaro.org>
On 1/11/23 00:39, Philippe Mathieu-Daudé wrote:
> The 'hwaddr' type is defined in "exec/hwaddr.h" as:
>
> hwaddr is the type of a physical address
> (its size can be different from 'target_ulong').
>
> All definitions use the 'HWADDR_' prefix, except TARGET_FMT_plx:
>
> $ fgrep define include/exec/hwaddr.h
> #define HWADDR_H
> #define HWADDR_BITS 64
> #define HWADDR_MAX UINT64_MAX
> #define TARGET_FMT_plx "%016" PRIx64
> ^^^^^^
> #define HWADDR_PRId PRId64
> #define HWADDR_PRIi PRIi64
> #define HWADDR_PRIo PRIo64
> #define HWADDR_PRIu PRIu64
> #define HWADDR_PRIx PRIx64
> #define HWADDR_PRIX PRIX64
>
> Since hwaddr's size can be*different* from target_ulong, it is
> very confusing to read one of its format using the 'TARGET_FMT_'
> prefix, normally used for the target_long / target_ulong types:
>
> $ fgrep TARGET_FMT_ include/exec/cpu-defs.h
> #define TARGET_FMT_lx "%08x"
> #define TARGET_FMT_ld "%d"
> #define TARGET_FMT_lu "%u"
> #define TARGET_FMT_lx "%016" PRIx64
> #define TARGET_FMT_ld "%" PRId64
> #define TARGET_FMT_lu "%" PRIu64
>
> Apparently this format was missed during commit a8170e5e97
> ("Rename target_phys_addr_t to hwaddr"), so complete it by
> doing a bulk-replacement to '"%016" HWADDR_PRIx' using:
>
> $ sed -i -E \
> -e 's/" ?TARGET_FMT_plx ?"/%016" HWADDR_PRIx "/g' \
> -e 's/" ?TARGET_FMT_plx/%016" HWADDR_PRIx/g' \
> -e 's/TARGET_FMT_plx ?"/"%016" HWADDR_PRIx "/g' \
> $(git grep -l TARGET_FMT_plx)
>
> and removing the definition from "exec/hwaddr.h".
>
> Suggested-by: BALATON Zoltan<balaton@eik.bme.hu>
> Signed-off-by: Philippe Mathieu-Daudé<philmd@linaro.org>
> ---
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2023-01-12 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 8:39 [PATCH v2 0/4] bulk: Replace TARGET_FMT_plx by HWADDR_PRIx Philippe Mathieu-Daudé
2023-01-11 8:39 ` [PATCH v2 1/4] hw: Remove hardcoded tabs (code style) Philippe Mathieu-Daudé
2023-01-11 19:48 ` Richard Henderson
2023-01-11 8:39 ` [PATCH v2 2/4] bulk: Coding style fixes Philippe Mathieu-Daudé
2023-01-11 19:48 ` Richard Henderson
2023-01-18 16:09 ` Thomas Huth
2023-01-18 17:04 ` Philippe Mathieu-Daudé
2023-01-11 8:39 ` [PATCH v2 3/4] bulk: Replace TARGET_FMT_plx -> HWADDR_PRIx Philippe Mathieu-Daudé
2023-01-11 19:50 ` Richard Henderson [this message]
2023-01-11 8:39 ` [RFC PATCH v2 4/4] bulk: Prefix '0x' to hex values displayed with HWADDR_PRIx format Philippe Mathieu-Daudé
2023-01-20 7:24 ` [PATCH v2 0/4] bulk: Replace TARGET_FMT_plx by HWADDR_PRIx Thomas Huth
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=782e40cf-532b-8148-1512-1b56668977e1@linaro.org \
--to=richard.henderson@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-riscv@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).