Hi,
On 03/22/2013 06:11 PM, Anthony Liguori wrote:
Hans de Goede hdego...@redhat.com writes:
snip
If the qemu-char.c code did:
int qemu_chr_fe_write(...) {
if (!s-fe_open) {
qemu_chr_fe_open(s);
}
...
}
That would be one thing. It's a hack, but a more reasonable
Hi,
On 03/21/2013 07:18 PM, Anthony Liguori wrote:
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of CharDriverState.
Sorry, I don't get it.
There isn't a notion of connected for the
Hi,
There isn't a notion of connected for the front-ends in the char
layer. The closest thing is whether add_handlers() have been called or
not.
It isn't new. There are qemu_chr_fe_open + qemu_chr_fe_close doing
exactly that signaling (whenever someone has opened the virtio-serial
port,
Hi,
On 03/22/2013 09:25 AM, Gerd Hoffmann wrote:
Hi,
There isn't a notion of connected for the front-ends in the char
layer. The closest thing is whether add_handlers() have been called or
not.
It isn't new. There are qemu_chr_fe_open + qemu_chr_fe_close doing
exactly that signaling
Gerd Hoffmann kra...@redhat.com writes:
Hi,
There isn't a notion of connected for the front-ends in the char
layer. The closest thing is whether add_handlers() have been called or
not.
It isn't new. There are qemu_chr_fe_open + qemu_chr_fe_close doing
exactly that signaling (whenever
Hans de Goede hdego...@redhat.com writes:
Hi,
On 03/21/2013 07:18 PM, Anthony Liguori wrote:
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of CharDriverState.
Sorry, I don't get it.
Hi,
Okay, let's use your example here with a standard UART. In the
following sequence, I should receive:
1) Starts guest
2) When guest initializes the UART, qemu_chr_fe_open()
3) Reboot guest
4) Receive qemu_chr_fe_close()
5) Boot new guest without a UART driver
6) Nothing is
Hi,
On 03/22/2013 02:50 PM, Anthony Liguori wrote:
Hans de Goede hdego...@redhat.com writes:
Hi,
On 03/21/2013 07:18 PM, Anthony Liguori wrote:
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other
Hans de Goede hdego...@redhat.com writes:
Hi,
On 03/22/2013 02:50 PM, Anthony Liguori wrote:
Hans de Goede hdego...@redhat.com writes:
We should have never allowed that in the first place and
I object strongly to extending the concept without making it make sense
for everything else.
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of CharDriverState.
Signed-off-by: Alon Levy al...@redhat.com
---
hw/virtio-console.c | 9 +
include/char/char.h | 11 +++
qemu-char.c | 9 +
3
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of CharDriverState.
Sorry, I don't get it.
There isn't a notion of connected for the front-ends in the char
layer. The closest thing is whether
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of
CharDriverState.
Sorry, I don't get it.
There isn't a notion of connected for the front-ends in the char
layer. The closest thing
Alon Levy al...@redhat.com writes:
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of
CharDriverState.
Sorry, I don't get it.
There isn't a notion of connected for the front-ends in
Alon Levy al...@redhat.com writes:
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of
CharDriverState.
Sorry, I don't get it.
There isn't a notion of connected for the
Alon Levy al...@redhat.com writes:
Alon Levy al...@redhat.com writes:
Note that the handler is called chr_is_guest_connected and not
chr_is_fe_connected, consistent with other members of
CharDriverState.
Sorry, I don't get it.
There isn't a notion of connected
15 matches
Mail list logo
