qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Multiple monitor terminals
Date: Tue, 20 Jan 2009 11:32:51 +0100	[thread overview]
Message-ID: <4975A853.5080603@siemens.com> (raw)

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

             reply	other threads:[~2009-01-20 10:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 10:32 Jan Kiszka [this message]
2009-01-20 13:00 ` [Qemu-devel] Re: Multiple monitor terminals Jan Kiszka

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=4975A853.5080603@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    /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 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).