From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: lersek@redhat.com, armbru@redhat.com, stappers@stappers.nl,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH v4] hw/block: better reporting on pflash backing file mismatch
Date: Fri, 22 Feb 2019 15:44:54 +0000 [thread overview]
Message-ID: <20190222154454.30289-1-alex.bennee@linaro.org> (raw)
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 and warn the user when we have performed magic to
enable things to Just Work (tm).
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?)
v4
- error check blk_getlength
- optimise memset and use NOR erase pattern
- restore singular device (overly confusing)
- add warn_report for when we do magic
---
hw/block/pflash_cfi01.c | 40 +++++++++++++++++++++++++++++++++-------
1 file changed, 33 insertions(+), 7 deletions(-)
diff --git a/hw/block/pflash_cfi01.c b/hw/block/pflash_cfi01.c
index 00c2efd0d7..c69ecc20a0 100644
--- a/hw/block/pflash_cfi01.c
+++ b/hw/block/pflash_cfi01.c
@@ -45,6 +45,7 @@
#include "qemu/bitops.h"
#include "qemu/host-utils.h"
#include "qemu/log.h"
+#include "qemu/error-report.h"
#include "hw/sysbus.h"
#include "sysemu/sysemu.h"
#include "trace.h"
@@ -714,13 +715,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 +741,38 @@ 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 ignore the tail.
+ */
+ int64_t backing_len = blk_getlength(pfl->blk);
+ if (backing_len < 0) {
+ error_setg(errp, "unable to check size of backing file");
+ return;
+ }
+
+ if (backing_len < total_len) {
+ if (pfl->ro) {
+ size_t pad_bytes = total_len - backing_len;
+ /* pad with NOR erase pattern */
+ memset((uint8_t*)pfl->storage + backing_len, 0xff, pad_bytes);
+ warn_report("device needs %" PRIu64
+ " bytes, padded with %zd 0xff bytes",
+ total_len, pad_bytes);
+ total_len = backing_len;
+ } else {
+ error_setg(errp, "device needs %" PRIu64 " bytes, "
+ "backing file provides only %" PRIu64 " bytes",
+ total_len, backing_len);
+ return;
+ }
+ } else if (backing_len > total_len) {
+ warn_report("device needs %" PRIu64 " bytes, rest ignored", total_len);
+ }
+
/* read the initial flash content */
ret = blk_pread(pfl->blk, 0, pfl->storage, total_len);
--
2.20.1
next reply other threads:[~2019-02-22 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 15:44 Alex Bennée [this message]
2019-02-22 18:44 ` [Qemu-devel] [PATCH v4] hw/block: better reporting on pflash backing file mismatch Laszlo Ersek
2019-02-27 17:59 ` no-reply
2019-02-27 18:02 ` no-reply
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=20190222154454.30289-1-alex.bennee@linaro.org \
--to=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).