From: Bandan Das <bsd@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com
Subject: [Qemu-devel] [PATCH v2 1/2] vfio: warn if host device rom can't be read
Date: Wed, 15 Jan 2014 15:38:05 +0530 [thread overview]
Message-ID: <1389780486-10826-2-git-send-email-bsd@redhat.com> (raw)
In-Reply-To: <1389780486-10826-1-git-send-email-bsd@redhat.com>
If the device rom can't be read, report an error to the
user. This alerts the user that the device has a bad
state that is causing rom read failure or option rom
loading has been disabled from the device boot menu
(among other reasons).
Signed-off-by: Bandan Das <bsd@redhat.com>
---
v2: Removed the macros to print only once. We want to print
the warning message for each assigned device for which rom
read fails
hw/misc/vfio.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/hw/misc/vfio.c b/hw/misc/vfio.c
index 9aecaa8..d2e68e2 100644
--- a/hw/misc/vfio.c
+++ b/hw/misc/vfio.c
@@ -1125,6 +1125,13 @@ static void vfio_pci_load_rom(VFIODevice *vdev)
vdev->rom_offset = reg_info.offset;
if (!vdev->rom_size) {
+ error_report("vfio-pci: Cannot read device rom at "
+ "%04x:%02x:%02x.%x\n",
+ vdev->host.domain, vdev->host.bus, vdev->host.slot,
+ vdev->host.function);
+ error_printf("Device option ROM contents are probably invalid "
+ "(check dmesg).\nSkip option ROM probe with rombar=0, "
+ "or load from file with romfile=\n");
return;
}
--
1.8.3.1
next prev parent reply other threads:[~2014-01-15 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 10:08 [Qemu-devel] [PATCH v2 0/2] vfio: Warn on failure to read device rom Bandan Das
2014-01-15 10:08 ` Bandan Das [this message]
2014-01-15 10:08 ` [Qemu-devel] [PATCH v2 2/2] vfio: Do not reattempt a failed rom read Bandan Das
2014-01-15 19:47 ` [Qemu-devel] [PATCH v2 0/2] vfio: Warn on failure to read device rom Alex Williamson
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=1389780486-10826-2-git-send-email-bsd@redhat.com \
--to=bsd@redhat.com \
--cc=alex.williamson@redhat.com \
--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).