OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [virtio-dev] Re: [PATCH v3 0/3] transport-pci: Introduce legacy registers access using AQ



> From: Jason Wang <jasowang@redhat.com>
> Sent: Tuesday, June 6, 2023 10:27 PM
> 
> I can't say I like this. I prefer to do meditation on top of a modern device with
> some lightweight features like _F_LEAGCY_HEADER. I don't see any advantages
> of a new legacy ABI over _F_LEGACY_HEADER. I don't want to repeat but I don't
> get any response here
> 
It is net only and not generic. Not a big blocker.
It doesnt stop at _F_LEAGCY_HEADER.

> Anything that prevents you from adding things like VIRTIO_NET_F_LEGACY_HEADER?
It requires hypervisor to mediate 1.x config region and intercept feature negotiation including q config and more.

Additionally, 1.x device says the mac address is read only, while legacy is RW.
And that requires yet another feature bit negotiation.

The main design goal is to not mediate 1.x specific region and not modify 1.x region definitions.
Which is why we step forward with the AQ.

> https://lore.kernel.org/virtio-
> dev/CACGkMEuixsBibSq_pEQvcKOH0WBQWnta4Q2c28SV8qTS8gaVcA@mail.g
> mail.com/#t


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]