From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>,
"Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 1/3] hw/mips/jazz: Remove the big_endian variable
Date: Mon, 28 Aug 2023 14:41:53 +0200 [thread overview]
Message-ID: <0b618261-b056-ff46-061c-7a0845e58ea9@redhat.com> (raw)
In-Reply-To: <94cb7c35-39f7-0108-d623-78435a5e7fee@linaro.org>
On 28/08/2023 14.19, Philippe Mathieu-Daudé wrote:
> Hi Thomas,
>
> On 25/8/23 19:51, Thomas Huth wrote:
>> There is an easier way to get a value that can be used to decide
>> whether the target is big endian or not: Simply use the
>> target_words_bigendian() function instead.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> hw/mips/jazz.c | 10 ++--------
>> 1 file changed, 2 insertions(+), 8 deletions(-)
>
>
>> @@ -157,12 +157,6 @@ static void mips_jazz_init(MachineState *machine,
>> [JAZZ_PICA61] = {33333333, 4},
>> };
>> -#if TARGET_BIG_ENDIAN
>> - big_endian = 1;
>> -#else
>> - big_endian = 0;
>> -#endif
>> -
>> if (machine->ram_size > 256 * MiB) {
>> error_report("RAM size more than 256Mb is not supported");
>> exit(EXIT_FAILURE);
>> @@ -301,7 +295,7 @@ static void mips_jazz_init(MachineState *machine,
>> dev = qdev_new("dp8393x");
>> qdev_set_nic_properties(dev, nd);
>> qdev_prop_set_uint8(dev, "it_shift", 2);
>> - qdev_prop_set_bit(dev, "big_endian", big_endian > 0);
>> + qdev_prop_set_bit(dev, "big_endian", target_words_bigendian());
>
> IIRC last time I tried that Peter pointed me at the documentation:
>
> /**
> * target_words_bigendian:
> * Returns true if the (default) endianness of the target is big endian,
> * false otherwise. Note that in target-specific code, you can use
> * TARGET_BIG_ENDIAN directly instead. On the other hand, common
> * code should normally never need to know about the endianness of the
> * target, so please do *not* use this function unless you know very
> * well what you are doing!
> */
>
> (Commit c95ac10340 "cpu: Provide a proper prototype for
> target_words_bigendian() in a header")
>
> Should we update the comment?
What would you change? My motivation here was mainly to decrease the size of
the code - I think it's way more complicated via the #if + extra variable
compared to simply calling target_words_bigendian(), isn't it? I think the
diffstat says it all...
Thomas
next prev parent reply other threads:[~2023-08-28 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 17:51 [PATCH 0/3] hw/mips/jazz: Rework the NIC init code Thomas Huth
2023-08-25 17:51 ` [PATCH 1/3] hw/mips/jazz: Remove the big_endian variable Thomas Huth
2023-08-25 21:37 ` Richard Henderson
2023-08-28 12:19 ` Philippe Mathieu-Daudé
2023-08-28 12:41 ` Thomas Huth [this message]
2023-08-28 15:48 ` Philippe Mathieu-Daudé
2023-08-28 17:00 ` Thomas Huth
2023-08-29 10:04 ` Peter Maydell
2023-08-25 17:51 ` [PATCH 2/3] hw/mips/jazz: Move the NIC init code into a separate function Thomas Huth
2023-08-25 17:51 ` [PATCH 3/3] hw/mips/jazz: Simplify the NIC setup code Thomas Huth
2023-09-01 10:15 ` [PATCH 0/3] hw/mips/jazz: Rework the NIC init code Michael Tokarev
2023-09-07 11:37 ` 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=0b618261-b056-ff46-061c-7a0845e58ea9@redhat.com \
--to=thuth@redhat.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=hpoussin@reactos.org \
--cc=jiaxun.yang@flygoat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).