Hi Jerrin, I think what was agreed wasn't to remove Legacy Virtio support, but instead remove support for probing legacy Virtio devices when they are not bound to any Kernel drivers.
It should still be possible to use these legacy Virtio devices when bound to VFIO or UIO. Regards, Maximle On 5/25/20 7:46 AM, jer...@marvell.com wrote: > From: Jerin Jacob <jer...@marvell.com> > > The legacy virtio feature is not architecture agnostics. > It relies on x86 IO port scheme support for its working. > > The legacy virtio is only the consumer of RTE_KDRV_NONE in DPDK PCI > subsystem. Legacy virtio removal will also optimize DPDK PCI enumeration > management as it does not need to probe RTE_KDRV_NONE based > devices anymore. > > Legacy virtio feature removal is planned in the v20.11 release. > > More details at http://patches.dpdk.org/patch/69351/ > > Cc: maxime.coque...@redhat.com > Cc: david.march...@redhat.com > Signed-off-by: Jerin Jacob <jer...@marvell.com> > --- > doc/guides/rel_notes/deprecation.rst | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/doc/guides/rel_notes/deprecation.rst > b/doc/guides/rel_notes/deprecation.rst > index cf8b1eb7b..79a03432c 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -107,3 +107,11 @@ Deprecation Notices > Python 2 support will be completely removed in 20.11. > In 20.08, explicit deprecation warnings will be displayed when running > scripts with Python 2. > + > +* virtio: The legacy virtio feature is not architecture agnostics. > + It relies on x86 IO port scheme support for its working. > + The legacy virtio is only the consumer of RTE_KDRV_NONE in DPDK PCI > subsystem. > + Legacy virtio removal will also optimize DPDK PCI enumeration management as > + it does not need to probe RTE_KDRV_NONE based devices anymore. > + Legacy virtio feature removal is planned in the v20.11 release. > + More details at http://patches.dpdk.org/patch/69351/ >
