From: Bandan Das <bsd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2 v4] vfio: blacklist loading of unstable roms
Date: Tue, 25 Feb 2014 18:47:39 -0500 [thread overview]
Message-ID: <1393372061-12493-1-git-send-email-bsd@redhat.com> (raw)
v4:
1. Short Description of the issue in comments, pointer
to qemu bug tracker in 2/2
2. Remove unnecessary check on rom_bar in vfio_pci_size_rom 2/2
3. No changes to 1/2 - Andreas, I have retained your "Reviewed-by"
since the code hasn't changed.
v3:
1. Change the "force" logic to depend on whether the user specified rombar,
eliminate dependence on multiple values of rom_bar
2. Avoid printing the informational message if there's no rom
3. Minor changes to commit messages
v2:
1. Break up into two patches separating the infrastructural changes
2. Change vendor_id and device_id type to uint16_t
3. Rename struct for blacklisted devid and vendorid to more meaningful names
4. Remove unnecessary rom_quirk variable and just call vfio_blacklist_opt_rom()
in vfio_pci_size_rom()
Bandan Das (2):
qdev-monitor: set DeviceState opts before calling realize
vfio: blacklist loading of unstable roms
hw/misc/vfio.c | 73 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
qdev-monitor.c | 4 +++-
2 files changed, 76 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2014-02-25 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 23:47 Bandan Das [this message]
2014-02-25 23:47 ` [Qemu-devel] [PATCH 1/2 v4] qdev-monitor: set DeviceState opts before calling realize Bandan Das
2014-02-25 23:47 ` [Qemu-devel] [PATCH 2/2 v4] vfio: blacklist loading of unstable roms Bandan Das
2014-02-26 18:11 ` [Qemu-devel] [PATCH 0/2 " 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=1393372061-12493-1-git-send-email-bsd@redhat.com \
--to=bsd@redhat.com \
--cc=afaerber@suse.de \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=mst@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).