From: Laszlo Ersek <lersek@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: pkg-qemu-devel@lists.alioth.debian.org, ard.biesheuvel@linaro.org
Subject: Re: [Qemu-devel] [PATCH] hw/block: report when pflash backing file isn't aligned
Date: Thu, 14 Feb 2019 20:54:07 +0100 [thread overview]
Message-ID: <bbefd980-c740-cb8f-a648-a6f51772d63d@redhat.com> (raw)
In-Reply-To: <20190214155714.8779-1-alex.bennee@linaro.org>
On 02/14/19 16:57, Alex Bennée wrote:
> It looks like there was going to be code to check we had some sort of
> alignment so lets replace it with an actual check. This is a bit more
> useful than the enigmatic "failed to read the initial flash content"
> when we attempt to read the number of bytes the device should have.
>
> This is a potential confusing stumbling block when you move from using
> -bios to using -drive if=pflash,file=blob,format=raw,readonly for
> loading your firmware code.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> hw/block/pflash_cfi01.c | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/hw/block/pflash_cfi01.c b/hw/block/pflash_cfi01.c
> index bffb4c40e7..f3251b236c 100644
> --- a/hw/block/pflash_cfi01.c
> +++ b/hw/block/pflash_cfi01.c
> @@ -722,12 +722,19 @@ static void pflash_cfi01_realize(DeviceState *dev, Error **errp)
> }
> device_len = sector_len_per_device * blocks_per_device;
>
> - /* XXX: to be fixed */
> -#if 0
> - if (total_len != (8 * 1024 * 1024) && total_len != (16 * 1024 * 1024) &&
> - total_len != (32 * 1024 * 1024) && total_len != (64 * 1024 * 1024))
> - return NULL;
> -#endif
> + /*
> + * Validate the backing store is the right size for pflash
> + * devices. It has to be padded to a multiple of the flash block
> + * size.
> + */
> + if (pfl->blk) {
> + uint64_t backing_len = blk_getlength(pfl->blk);
> + if (device_len != backing_len) {
> + error_setg(errp, "backing file wrong size "
> + "(%" PRId64 " != %" PRId64")", backing_len, device_len);
> + return;
> + }
> + }
>
> memory_region_init_rom_device(
> &pfl->mem, OBJECT(dev),
>
I have two suggestions:
- backing_len and device_len are both uint64_t; we should print them
with PRIu64
- from a user POV, I find it more useful if the error message also shows
which quantity is which, not just two inequal numbers.
I don't feel too strongly about this, so up to you.
Thanks,
Laszlo
next prev parent reply other threads:[~2019-02-14 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 15:57 [Qemu-devel] [PATCH] hw/block: report when pflash backing file isn't aligned Alex Bennée
2019-02-14 19:54 ` Laszlo Ersek [this message]
2019-02-14 22:38 ` Alex Bennée
2019-02-15 6:23 ` Geert Stappers
2019-02-15 9:12 ` Markus Armbruster
2019-02-15 13:57 ` Laszlo Ersek
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=bbefd980-c740-cb8f-a648-a6f51772d63d@redhat.com \
--to=lersek@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=pkg-qemu-devel@lists.alioth.debian.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).