qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH RFC v4 00/16] qemu: towards virtio-1 host suppor


From: Cornelia Huck
Subject: Re: [Qemu-devel] [PATCH RFC v4 00/16] qemu: towards virtio-1 host support
Date: Thu, 27 Nov 2014 17:28:42 +0100

On Thu, 27 Nov 2014 18:18:25 +0200
"Michael S. Tsirkin" <address@hidden> wrote:

> On Thu, Nov 27, 2014 at 05:06:51PM +0100, Cornelia Huck wrote:

> > So we should have a per-device callback into the transport layer, say
> > check_legacy()?
> 
> I would just have 2 masks: legacy_features and features.

But these belong to the device type and the transport just needs to
trigger usage of the right one, right?

> 
> > For ccw, this would check for the negotiated revision; for mmio, it
> > could check a device property configured with the device; and for pci,
> > whatever the mechanism is there :)
> > 
> > A transport not implementing this callback is simply considered
> > legacy-only.
> 
> I dislike callbacks. Let's just give all info to core,
> and have it DTRT.
> 
Have a is_legacy flag in the vdev that is initialized to 1, and
transports can unset it when the revision is negotiated or during init?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]