qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Fontana <cfontana@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: "Marcel Apfelbaum" <marcel@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] virtio-pci: don't touch pci on virtio reset
Date: Wed, 27 Jul 2022 19:32:29 +0200	[thread overview]
Message-ID: <c111d840-a10d-6374-6ee4-85d7b23b4967@suse.de> (raw)
In-Reply-To: <c458e6cd-a18e-88e9-dcdf-5e294713ad87@suse.de>

Hmm, no that's not it,
still segfault in ovs, but I'll try to see if I can merge that and the workaround I am currently using...


On 7/27/22 19:14, Claudio Fontana wrote:
> testing it now...
> 
> Thanks!
> 
> C
> 
> 
> On 7/27/22 18:14, Michael S. Tsirkin wrote:
>> virtio level reset should not affect pci express
>> registers such as PM, error or link.
>>
>> Fixes: 27ce0f3afc ("hw/virtio: fix Power Management Control Register for PCI Express virtio devices")
>> Fixes: d584f1b9ca ("hw/virtio: fix Link Control Register for PCI Express virtio devices")
>> Fixes: c2cabb3422 ("hw/virtio: fix error enabling flags in Device Control register")
>> Cc: "Marcel Apfelbaum" <marcel@redhat.com>
>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>> ---
>>  hw/virtio/virtio-pci.c | 9 ++++++++-
>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
>> index 45327f0b31..3189ec014d 100644
>> --- a/hw/virtio/virtio-pci.c
>> +++ b/hw/virtio/virtio-pci.c
>> @@ -1955,6 +1955,13 @@ static void virtio_pci_reset(DeviceState *qdev)
>>          proxy->vqs[i].avail[0] = proxy->vqs[i].avail[1] = 0;
>>          proxy->vqs[i].used[0] = proxy->vqs[i].used[1] = 0;
>>      }
>> +}
>> +
>> +static void virtio_pci_bus_reset(DeviceState *qdev)
>> +{
>> +    PCIDevice *dev = PCI_DEVICE(qdev);
>> +
>> +    virtio_pci_reset(qdev);
>>  
>>      if (pci_is_express(dev)) {
>>          pcie_cap_deverr_reset(dev);
>> @@ -2022,7 +2029,7 @@ static void virtio_pci_class_init(ObjectClass *klass, void *data)
>>      k->class_id = PCI_CLASS_OTHERS;
>>      device_class_set_parent_realize(dc, virtio_pci_dc_realize,
>>                                      &vpciklass->parent_dc_realize);
>> -    dc->reset = virtio_pci_reset;
>> +    dc->reset = virtio_pci_bus_reset;
>>  }
>>  
>>  static const TypeInfo virtio_pci_info = {
> 
> 



      reply	other threads:[~2022-07-27 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 16:14 [PATCH] virtio-pci: don't touch pci on virtio reset Michael S. Tsirkin
2022-07-27 17:14 ` Claudio Fontana
2022-07-27 17:32   ` Claudio Fontana [this message]

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=c111d840-a10d-6374-6ee4-85d7b23b4967@suse.de \
    --to=cfontana@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=marcel@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).