[Top][All Lists]

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

[Qemu-devel] Insane virtio-serial semantics (was: [PATCH v2 4/5] backdoo

From: Markus Armbruster
Subject: [Qemu-devel] Insane virtio-serial semantics (was: [PATCH v2 4/5] backdoor: [softmmu] Add QEMU-side proxy to "libbackdoor.a")
Date: Wed, 07 Dec 2011 09:21:01 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Anthony Liguori <address@hidden> writes:

> On 12/06/2011 04:30 PM, Lluís Vilanova wrote:
>> Anthony Liguori writes:
>>> I really worry about us introducing so many of these one-off paravirtual 
>>> devices.
>>> I would much prefer that you look at doing this as an extension to the 
>>> ivshmem
>>> device as it already has this sort of scope.  You should be able to do this 
>>> by
>>> just extending the size of bar 1 and using a well known guest id.
>> I did in fact look at ivshmem some time ago, and it's true that both use the
>> same mechanisms; but each device has a completely different purpose. To me it
>> just seems that extending the control BAR in ivshmem to call the 
>> user-provided
>> backdoor callbacks is just conflating two completely separate devices into a
>> single one. Besides, I think that the qemu-side of the backdoor is simple 
>> enough
>> to avoid being a maintenance burden.
> They have the same purpose (which are both vague TBH).  The only
> reason I'm sympathetic to this device is that virtio-serial has such
> insane semantics.

Could you summarize what's wrong?  Is it fixable?


reply via email to

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