linux-kernel - Re: [PATCH V3 16/19] virtio-pci: introduce modern device module

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <24cb3ebe-1248-3e31-0716-cf498cf1d728@redhat.com>
Date:   Mon, 8 Feb 2021 13:42:27 +0800
From:   Jason Wang <jasowang@...hat.com>
To:     "Michael S. Tsirkin" <mst@...hat.com>
Cc:     virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org, shahafs@...lanox.com,
        lulu@...hat.com, sgarzare@...hat.com, rdunlap@...radead.org
Subject: Re: [PATCH V3 16/19] virtio-pci: introduce modern device module


On 2021/2/5 下午11:34, Michael S. Tsirkin wrote:
> On Mon, Jan 04, 2021 at 02:55:00PM +0800, Jason Wang wrote:
>> Signed-off-by: Jason Wang<jasowang@...hat.com>
> I don't exactly get why we need to split the modern driver out,
> and it can confuse people who are used to be seeing virtio-pci.


The virtio-pci module still there. No user visible changes. Just some 
codes that could be shared with other driver were split out.


>
> The vdpa thing so far looks like a development tool, why do
> we care that it depends on a bit of extra code?


If I'm not misunderstanding, trying to share codes is proposed by you here:

https://lkml.org/lkml/2020/6/10/232

We also had the plan to convert IFCVF to use this library.

Thanks

>