From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: stappers@stappers.nl, lersek@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] hw/block: better reporting on pflash backing file mismatch
Date: Thu, 21 Feb 2019 21:42:32 +0100 [thread overview]
Message-ID: <3ba41c9b-05a0-acfe-e621-10f43048c874@redhat.com> (raw)
In-Reply-To: <20190221184857.22434-1-alex.bennee@linaro.org>
Hi Alex,
On 2/21/19 7:48 PM, 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. To mitigate that we automatically pad in
> the read-only case.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> ---
> v3
> - tweak commit title/commentary
> - use total_len instead of device_len for checks
> - if the device is read-only do the padding for them
> - accept baking_len > total_len (how to warn_report with NULL *errp?)
> ---
> hw/block/pflash_cfi01.c | 28 +++++++++++++++++++++-------
> 1 file changed, 21 insertions(+), 7 deletions(-)
>
> diff --git a/hw/block/pflash_cfi01.c b/hw/block/pflash_cfi01.c
> index 00c2efd0d7..37d7513c45 100644
> --- a/hw/block/pflash_cfi01.c
> +++ b/hw/block/pflash_cfi01.c
> @@ -714,13 +714,6 @@ 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
> -
> memory_region_init_rom_device(
> &pfl->mem, OBJECT(dev),
> &pflash_cfi01_ops,
> @@ -747,6 +740,27 @@ static void pflash_cfi01_realize(DeviceState *dev, Error **errp)
> }
>
> if (pfl->blk) {
> + /*
> + * Validate the backing store is the right size for pflash
> + * devices. It should be padded to a multiple of the flash
> + * block size. If the device is read-only we can elide the
> + * check and just null pad the region first. If the user
> + * supplies a larger file we silently accept it.
> + */
> + uint64_t backing_len = blk_getlength(pfl->blk);
> +
> + if (backing_len < total_len) {
> + if (pfl->ro) {
> + memset(pfl->storage, 0, total_len);
When you erasing a NOR flash sector, all bits are set to 1.
Then you can program a word by setting its bits to 0.
It is not possible to set bits from 0 to 1 on a word boundary,
it is only possible to set bits to 1 by erasing a whole sector (sector
boundary).
The pflash QEMU models are of NOR type (is different for other flash
technologies).
If we want to set the padded area to the fabric blank state, we should
use the NOR flash erased value of 0xff.
> + total_len = backing_len;
> + } else {
> + error_setg(errp, "device(s) needs %" PRIu64 " bytes, "
> + "backing file provides only %" PRIu64 " bytes",
> + total_len, backing_len);
> + return;
> + }
> + }
> +
> /* read the initial flash content */
> ret = blk_pread(pfl->blk, 0, pfl->storage, total_len);
>
>
next prev parent reply other threads:[~2019-02-21 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 18:48 [Qemu-devel] [PATCH v3] hw/block: better reporting on pflash backing file mismatch Alex Bennée
2019-02-21 19:16 ` Laszlo Ersek
2019-02-21 20:07 ` Alex Bennée
2019-02-22 8:09 ` Laszlo Ersek
2019-02-22 8:56 ` Philippe Mathieu-Daudé
2019-02-21 20:42 ` Philippe Mathieu-Daudé [this message]
2019-02-22 8:06 ` Laszlo Ersek
2019-02-22 9:02 ` Markus Armbruster
2019-02-22 9:27 ` Alex Bennée
2019-02-22 12:29 ` Markus Armbruster
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=3ba41c9b-05a0-acfe-e621-10f43048c874@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stappers@stappers.nl \
/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).