From: Alex Williamson <alex.williamson@redhat.com>
To: kvm@vger.kernel.org
Cc: alex.williamson@redhat.com, ddutile@redhat.com,
chrisw@redhat.com, bernhard.kohl@nsn.com
Subject: [PATCH v2] device-assignment: Reset device on system reset
Date: Thu, 17 Mar 2011 15:24:31 -0600 [thread overview]
Message-ID: <20110317212413.14852.67041.stgit@s20.home> (raw)
In-Reply-To: <20110317192923.24889.79288.stgit@s20.home>
On system reset, we currently try to quiesce DMA by clearing the
command register. This assumes that nothing re-enables bus master
support without first de-programming the device. Use a bigger
hammer to help the guest not shoot itself by issuing a function
reset via sysfs on each system reset.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
v2: Fix segment support
hw/device-assignment.c | 24 ++++++++++++++++++++++--
1 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/hw/device-assignment.c b/hw/device-assignment.c
index db82e73..4997b6e 100644
--- a/hw/device-assignment.c
+++ b/hw/device-assignment.c
@@ -1693,13 +1693,33 @@ static const VMStateDescription vmstate_assigned_device = {
static void reset_assigned_device(DeviceState *dev)
{
- PCIDevice *d = DO_UPCAST(PCIDevice, qdev, dev);
+ PCIDevice *pci_dev = DO_UPCAST(PCIDevice, qdev, dev);
+ AssignedDevice *adev = DO_UPCAST(AssignedDevice, dev, pci_dev);
+ char reset_file[64];
+ const char reset[] = "1";
+ int fd, ret;
+
+ snprintf(reset_file, sizeof(reset_file),
+ "/sys/bus/pci/devices/%04x:%02x:%02x.%01x/reset",
+ adev->host.seg, adev->host.bus, adev->host.dev, adev->host.func);
+
+ /*
+ * Issue a device reset via pci-sysfs. Note that we use write(2) here
+ * and ignore the return value because some kernels have a bug that
+ * returns 0 rather than bytes written on success, sending us into an
+ * infinite retry loop using other write mechanisms.
+ */
+ fd = open(reset_file, O_WRONLY);
+ if (fd != -1) {
+ ret = write(fd, reset, strlen(reset));
+ close(fd);
+ }
/*
* When a 0 is written to the command register, the device is logically
* disconnected from the PCI bus. This avoids further DMA transfers.
*/
- assigned_dev_pci_write_config(d, PCI_COMMAND, 0, 2);
+ assigned_dev_pci_write_config(pci_dev, PCI_COMMAND, 0, 2);
}
static int assigned_initfn(struct PCIDevice *pci_dev)
next prev parent reply other threads:[~2011-03-17 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 19:29 [PATCH] device-assignment: Reset device on system reset Alex Williamson
2011-03-17 21:12 ` Chris Wright
2011-03-17 21:17 ` Alex Williamson
2011-03-17 21:59 ` Chris Wright
2011-03-17 21:24 ` Alex Williamson [this message]
2011-03-17 21:55 ` [PATCH v2] " Chris Wright
2011-04-01 21:57 ` Marcelo Tosatti
2011-04-03 0:20 ` Marcelo Tosatti
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=20110317212413.14852.67041.stgit@s20.home \
--to=alex.williamson@redhat.com \
--cc=bernhard.kohl@nsn.com \
--cc=chrisw@redhat.com \
--cc=ddutile@redhat.com \
--cc=kvm@vger.kernel.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