From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: [Qemu-devel] Re: [PATCH] Split machine creation from the main loop
Date: Mon, 28 Feb 2011 06:08:11 -0600 [thread overview]
Message-ID: <4D6B902B.7040601@codemonkey.ws> (raw)
In-Reply-To: <4D6B6746.6060605@redhat.com>
On 02/28/2011 03:13 AM, Avi Kivity wrote:
> On 02/28/2011 10:57 AM, Paolo Bonzini wrote:
>> On 02/28/2011 09:20 AM, Avi Kivity wrote:
>>>>
>>>> We should have another abstraction for connection based backend. I'll
>>>> take a go at this when I'm ready to try to get those patches in.
>>>
>>> Shouldn't each new connection return a chardev?
>>
>> You would need a kind of "factory" interface that knows how to create
>> a new {monitor,serial port,you name it} for each new connection.
>> Actually it doesn't make much sense except for monitors.
>
> Monitors and vnc.
VNC also does it's own buffering when reading and writing to a file
descriptor. The chardev layer doesn't really have a concept of flow
control.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-02-28 12:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 21:38 [Qemu-devel] [PATCH] Split machine creation from the main loop Anthony Liguori
2011-02-23 23:00 ` [Qemu-devel] " Juan Quintela
2011-02-23 23:12 ` Anthony Liguori
2011-02-23 23:38 ` Juan Quintela
2011-02-24 0:36 ` Anthony Liguori
2011-02-24 10:19 ` Stefan Hajnoczi
2011-02-24 14:47 ` Anthony Liguori
2011-02-24 16:01 ` Avi Kivity
2011-02-24 17:25 ` Anthony Liguori
2011-02-27 11:33 ` Avi Kivity
2011-02-28 4:01 ` Anthony Liguori
2011-02-28 8:20 ` Avi Kivity
2011-02-28 8:57 ` Paolo Bonzini
2011-02-28 9:13 ` Avi Kivity
2011-02-28 10:08 ` Paolo Bonzini
2011-02-28 12:08 ` Anthony Liguori [this message]
2011-02-25 17:02 ` [Qemu-devel] " Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6B902B.7040601@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.