linux-kernel - RE: [PATCH] virtio_pci: Wait for legacy device to be reset

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <TY2PR06MB3424F04CDC1D891BABCBE5DA859A9@TY2PR06MB3424.apcprd06.prod.outlook.com>
Date:   Tue, 11 Apr 2023 12:10:53 +0000
From:   Angus Chen <angus.chen@...uarmicro.com>
To:     "Michael S. Tsirkin" <mst@...hat.com>
CC:     Jason Wang <jasowang@...hat.com>,
        "virtualization@...ts.linux-foundation.org" 
        <virtualization@...ts.linux-foundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] virtio_pci: Wait for legacy device to be reset



> -----Original Message-----
> From: Michael S. Tsirkin <mst@...hat.com>
> Sent: Tuesday, April 11, 2023 7:14 PM
> To: Angus Chen <angus.chen@...uarmicro.com>
> Cc: Jason Wang <jasowang@...hat.com>;
> virtualization@...ts.linux-foundation.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH] virtio_pci: Wait for legacy device to be reset
> 
> On Tue, Apr 11, 2023 at 10:57:51AM +0000, Angus Chen wrote:
> > > > > Yes, not very clear still. What are the device and vendor ID of the
> > > > > card? Does it have the virtio capabilities?
> > > > > Thanks
> > > > It's have the virtio capabilities.
> > > > When it is used in bare metal ，
> > > >    it just use PCI_VENDOR_ID_REDHAT_QUMRANET.
> > > > When it use in vm,
> > > >  It is just like :
> > > > { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET,
> > > >              VIRTIO_TRANS_ID_NET,
> > > >              PCI_VENDOR_ID_JAGUARMICRO,
> > > >              VIRTIO_ID_NET) },
> > > >     { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET,
> > > >              VIRTIO_TRANS_ID_BLOCK,
> > > >              PCI_VENDOR_ID_JAGUARMICRO,
> > > >              VIRTIO_ID_BLOCK) },
> > > >
> > >
> > > Okay. So it's a transitional device. The question, then,
> > > is how come you end up with drivers/virtio/virtio_pci_legacy.c
> > > with a modern linux at all?
> > > Did you by chance set force_legacy = true ?
> > Yes,I can provide more information about it.
> > We can test it use force_legacy ,or we use a server with multi os but it use only
> one card.
> > Thanks.
> 
> Okay, so I don't yet see lots of value of merging this patch upstream.
> The problematic code does not run by default as the modern driver is
> used, and applying the patch upstream does nothing to fix the multi-os
> case.
> 
En, I thought the same way you did,so I just fixed it out of tree one year ago.
But the legacy virtio model is used more than we thought in real cloud computing.

Btw,I will show the mail to my boss that Although it is merged failed, I tried,haha.

> What did I miss?
> 
> 
> --
> MST