public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Bernhard Kohl <bernhard.kohl@nsn.com>,
	kvm@vger.kernel.org, Thomas Ostler <thomas.ostler@nsn.com>
Subject: Re: [PATCH v2] device-assignment: register a reset function
Date: Tue, 16 Nov 2010 15:49:42 +0100	[thread overview]
Message-ID: <4CE29A06.5050509@siemens.com> (raw)
In-Reply-To: <1289918267.2805.248.camel@x201>

Am 16.11.2010 15:37, Alex Williamson wrote:
> On Tue, 2010-11-16 at 15:05 +0100, 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>
>> ---
>> Changes v1 -> v2:
>> - use defined macros, e.g. PCI_COMMAND
>> - write all zero to the command register to disconnect the device logically
>> ---
>>  hw/device-assignment.c |   12 ++++++++++++
>>  1 files changed, 12 insertions(+), 0 deletions(-)
> 
> Looks good to me.
> 
> Acked-by: Alex Williamson <alex.williamson@redhat.com>

Acked-by: Jan Kiszka <jan.kiszka@siemens.com>

> 
>> diff --git a/hw/device-assignment.c b/hw/device-assignment.c
>> index 5f5bde1..8d5a609 100644
>> --- a/hw/device-assignment.c
>> +++ b/hw/device-assignment.c
>> @@ -1434,6 +1434,17 @@ static void assigned_dev_unregister_msix_mmio(AssignedDevice *dev)
>>      dev->msix_table_page = NULL;
>>  }
>>  
>> +static void reset_assigned_device(DeviceState *dev)
>> +{
>> +    PCIDevice *d = DO_UPCAST(PCIDevice, qdev, dev);
>> +
>> +    /*
>> +     * 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);
>> +}
>> +
>>  static int assigned_initfn(struct PCIDevice *pci_dev)
>>  {
>>      AssignedDevice *dev = DO_UPCAST(AssignedDevice, dev, pci_dev);
>> @@ -1544,6 +1555,7 @@ static PCIDeviceInfo assign_info = {
>>      .qdev.name    = "pci-assign",
>>      .qdev.desc    = "pass through host pci devices to the guest",
>>      .qdev.size    = sizeof(AssignedDevice),
>> +    .qdev.reset   = reset_assigned_device,
>>      .init         = assigned_initfn,
>>      .exit         = assigned_exitfn,
>>      .config_read  = assigned_dev_pci_read_config,

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-11-16 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 14:05 [PATCH v2] device-assignment: register a reset function Bernhard Kohl
2010-11-16 14:37 ` Alex Williamson
2010-11-16 14:49   ` Jan Kiszka [this message]
2010-11-17 14:09 ` 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=4CE29A06.5050509@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=alex.williamson@redhat.com \
    --cc=bernhard.kohl@nsn.com \
    --cc=kvm@vger.kernel.org \
    --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