From: Alex Williamson <alex.williamson@redhat.com>
To: Bernhard Kohl <bernhard.kohl@nsn.com>
Cc: kvm@vger.kernel.org, kwolf@redhat.com,
Thomas Ostler <thomas.ostler@nsn.com>
Subject: Re: [PATCH] device-assignment: register a reset function
Date: Fri, 17 Sep 2010 10:16:21 -0600 [thread overview]
Message-ID: <1284740181.14301.15.camel@x201> (raw)
In-Reply-To: <1284737271-21457-1-git-send-email-bernhard.kohl@nsn.com>
On Fri, 2010-09-17 at 17:27 +0200, Bernhard Kohl wrote:
> This is necessary because during reboot of a VM the assigned devices
> continue DMA transfers which causes memory corruption.
>
> Signed-off-by: Thomas Ostler <thomas.ostler@nsn.com>
> Signed-off-by: Bernhard Kohl <bernhard.kohl@nsn.com>
> ---
> hw/device-assignment.c | 14 ++++++++++++++
> 1 files changed, 14 insertions(+), 0 deletions(-)
>
> diff --git a/hw/device-assignment.c b/hw/device-assignment.c
> index 87f7418..fb47813 100644
> --- a/hw/device-assignment.c
> +++ b/hw/device-assignment.c
> @@ -1450,6 +1450,17 @@ static void assigned_dev_unregister_msix_mmio(AssignedDevice *dev)
> dev->msix_table_page = NULL;
> }
>
> +static void reset_assigned_device(void *opaque)
> +{
> + PCIDevice *d = (PCIDevice *)opaque;
> + uint32_t conf;
> +
> + /* reset the bus master bit to avoid further DMA transfers */
> + conf = assigned_dev_pci_read_config(d, PCI_COMMAND, 2);
> + conf &= ~PCI_COMMAND_MASTER;
> + assigned_dev_pci_write_config(d, PCI_COMMAND, conf, 2);
> +}
> +
> static int assigned_initfn(struct PCIDevice *pci_dev)
> {
> AssignedDevice *dev = DO_UPCAST(AssignedDevice, dev, pci_dev);
> @@ -1499,6 +1510,9 @@ static int assigned_initfn(struct PCIDevice *pci_dev)
> if (r < 0)
> goto assigned_out;
>
> + /* register reset function for the device */
> + qemu_register_reset(reset_assigned_device, pci_dev);
> +
> /* intercept MSI-X entry page in the MMIO */
> if (dev->cap.available & ASSIGNED_DEVICE_CAP_MSIX)
> if (assigned_dev_register_msix_mmio(dev))
Hmm, at a minimum, we need a qemu_unregister_reset() in the exitfn, but
upon further inspection, we should probably just do it the qdev way.
That would mean simply setting qdev.reset to reset_assigned_device() in
assign_info, then we can leave the registration/de-registration to qdev.
Does that work? Sorry I missed that the first time. Thanks,
Alex
next prev parent reply other threads:[~2010-09-17 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 15:04 [PATCH] device-assignment: register a reset function Bernhard Kohl
2010-09-16 15:48 ` Alex Williamson
2010-09-17 14:14 ` Bernhard Kohl
2010-09-17 15:27 ` Bernhard Kohl
2010-09-17 16:16 ` Alex Williamson [this message]
2010-09-21 14:01 ` Bernhard Kohl
[not found] ` <1289820837-24254-1-git-send-email-bernhard.kohl@nsn.com>
2010-11-15 12:08 ` Jan Kiszka
2010-11-15 20:38 ` Alex Williamson
2010-11-15 21:58 ` Jan Kiszka
2010-11-16 11:39 ` Bernhard Kohl
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=1284740181.14301.15.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=bernhard.kohl@nsn.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=thomas.ostler@nsn.com \
/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