From: Laurent Vivier <laurent@vivier.eu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-m68k@lists.linux-m68k.org, qemu-devel@nongnu.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH qemu v2 2/2] m68k: align bootinfo strings and data to 4 bytes
Date: Mon, 26 Sep 2022 15:00:42 +0200 [thread overview]
Message-ID: <2a8cee1f-2d80-68fc-0ea9-be370a941ede@vivier.eu> (raw)
In-Reply-To: <20220926113900.1256630-2-Jason@zx2c4.com>
Le 26/09/2022 à 13:39, Jason A. Donenfeld a écrit :
> Various tools, such as kexec-tools and m68k-bootinfo, expect each
> bootinfo entry to be aligned to 4 bytes, not 2 bytes. So adjust the
> padding to fill this out as such.
Agree, I found the same problem using petitboot as a ROM for the virt machine [1].
(I didn't update BOOTINFOSTR() but I think I should).
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
[1] https://github.com/vivier/qemu-m68k/commits/m68k-virt
>
> Also, break apart the padding additions from the other field length
> additions, so that it's more clear why these magic numbers are being
> added, and comment them too.
>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Laurent Vivier <laurent@vivier.eu>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> hw/m68k/bootinfo.h | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/hw/m68k/bootinfo.h b/hw/m68k/bootinfo.h
> index bd8b212fd3..897162b818 100644
> --- a/hw/m68k/bootinfo.h
> +++ b/hw/m68k/bootinfo.h
> @@ -48,13 +48,14 @@
> stw_phys(as, base, id); \
> base += 2; \
> stw_phys(as, base, \
> - (sizeof(struct bi_record) + strlen(string) + 2) & ~1); \
> + (sizeof(struct bi_record) + strlen(string) + \
> + 1 /* null termination */ + 3 /* padding */) & ~3); \
> base += 2; \
> for (i = 0; string[i]; i++) { \
> stb_phys(as, base++, string[i]); \
> } \
> stb_phys(as, base++, 0); \
> - base = (base + 1) & ~1; \
> + base = (base + 3) & ~3; \
> } while (0)
>
> #define BOOTINFODATA(as, base, id, data, len) \
> @@ -63,13 +64,14 @@
> stw_phys(as, base, id); \
> base += 2; \
> stw_phys(as, base, \
> - (sizeof(struct bi_record) + len + 3) & ~1); \
> + (sizeof(struct bi_record) + len + \
> + 2 /* length field */ + 3 /* padding */) & ~3); \
> base += 2; \
> stw_phys(as, base, len); \
> base += 2; \
> for (i = 0; i < len; ++i) { \
> stb_phys(as, base++, data[i]); \
> } \
> - base = (base + 1) & ~1; \
> + base = (base + 3) & ~3; \
> } while (0)
> #endif
next prev parent reply other threads:[~2022-09-26 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 11:38 [PATCH qemu v2 1/2] m68k: rework BI_VIRT_RNG_SEED as BI_RNG_SEED Jason A. Donenfeld
2022-09-26 11:39 ` [PATCH qemu v2 2/2] m68k: align bootinfo strings and data to 4 bytes Jason A. Donenfeld
2022-09-26 13:00 ` Laurent Vivier [this message]
2022-09-26 21:37 ` Laurent Vivier
2022-09-26 21:40 ` Jason A. Donenfeld
2022-09-26 21:42 ` Laurent Vivier
2022-09-26 21:42 ` Jason A. Donenfeld
2022-09-28 23:13 ` Jason A. Donenfeld
2022-09-29 6:37 ` [PATCH qemu v2 1/2] m68k: rework BI_VIRT_RNG_SEED as BI_RNG_SEED Laurent Vivier
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=2a8cee1f-2d80-68fc-0ea9-be370a941ede@vivier.eu \
--to=laurent@vivier.eu \
--cc=Jason@zx2c4.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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).