* [Qemu-devel] Multiple monitor terminals
@ 2009-01-20 10:32 Jan Kiszka
2009-01-20 13:00 ` [Qemu-devel] " Jan Kiszka
0 siblings, 1 reply; 2+ messages in thread
From: Jan Kiszka @ 2009-01-20 10:32 UTC (permalink / raw)
To: qemu-devel@nongnu.org
Hi,
trying to re-animate Jason Wessel's nice monitor-pass-through patches
for the gdbstub that we carry in our tree, I'm currently a bit lost in
the monitor mux design. Why do we need multiple monitor terminal devices
at the moment? And why are they all receiving the same output? What
would be a scenario for more than one monitor_hd != NULL?
Jason once suggested to define a focus when issuing a new command and
send all related replies only back to this focused terminal. I think
this would fit quite well for most use cases, specifically when adding
another monitor channel via remote gdb. Just migration raises some
concerns ATM. But as I may oversee more issues while trying to apply
this focus concept also on the existing monitor terminals, I'd like to
get some feedback on this approach first.
Thanks in advance,
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Qemu-devel] Re: Multiple monitor terminals
2009-01-20 10:32 [Qemu-devel] Multiple monitor terminals Jan Kiszka
@ 2009-01-20 13:00 ` Jan Kiszka
0 siblings, 0 replies; 2+ messages in thread
From: Jan Kiszka @ 2009-01-20 13:00 UTC (permalink / raw)
To: qemu-devel
Jan Kiszka wrote:
> Hi,
>
> trying to re-animate Jason Wessel's nice monitor-pass-through patches
> for the gdbstub that we carry in our tree, I'm currently a bit lost in
> the monitor mux design. Why do we need multiple monitor terminal devices
> at the moment? And why are they all receiving the same output? What
> would be a scenario for more than one monitor_hd != NULL?
To answer myself: The idea seems to be allowing to mux the monitor on
other character devices, be it one or more, be there also a dedicated
monitor terminal at the same time. But I still wonder if it is a
desirable behavior to have this broadcasting of typed commands and their
replies. Thinking more about this now.
>
> Jason once suggested to define a focus when issuing a new command and
> send all related replies only back to this focused terminal. I think
> this would fit quite well for most use cases, specifically when adding
> another monitor channel via remote gdb. Just migration raises some
> concerns ATM. But as I may oversee more issues while trying to apply
> this focus concept also on the existing monitor terminals, I'd like to
> get some feedback on this approach first.
>
> Thanks in advance,
> Jan
>
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-01-20 13:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-20 10:32 [Qemu-devel] Multiple monitor terminals Jan Kiszka
2009-01-20 13:00 ` [Qemu-devel] " Jan Kiszka
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).