All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bandan Das <bsd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2 v3] vfio: blacklist loading of unstable roms
Date: Mon, 24 Feb 2014 23:34:22 -0500	[thread overview]
Message-ID: <1393302864-11348-1-git-send-email-bsd@redhat.com> (raw)

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 | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 qdev-monitor.c |  4 +++-
 2 files changed, 63 insertions(+), 1 deletion(-)

-- 
1.8.3.1

             reply	other threads:[~2014-02-25  4:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25  4:34 Bandan Das [this message]
2014-02-25  4:34 ` [Qemu-devel] [PATCH 1/2 v3] qdev-monitor: set DeviceState opts before calling realize Bandan Das
2014-02-25  7:39   ` Andreas Färber
2014-02-25  4:34 ` [Qemu-devel] [PATCH 2/2 v3] vfio: blacklist loading of unstable roms Bandan Das
2014-02-25 15:41   ` Alex Williamson
2014-02-25 16:51     ` Bandan Das

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=1393302864-11348-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.