qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Anthony Liguori" <aliguori@us.ibm.com>,
	"Todd T. Fries" <todd@fries.net>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] display: stop using DT_NOGRAPHIC, use DT_NONE
Date: Fri, 28 Jun 2013 14:06:51 +0200	[thread overview]
Message-ID: <51CD7C5B.10509@redhat.com> (raw)
In-Reply-To: <51CD7C16.3040208@msgid.tls.msk.ru>

Il 28/06/2013 14:05, Michael Tokarev ha scritto:
> That's exactly why I don't think looking at -nographic here in
> serial code is wrong.  It should do the same regardless of
> -nographic - if, say, serial is redirected to stdio, it should
> always pass Ctrl+C to guest instead of killing it.  So I'm
> not really sure we should test for -display none here, either.

See the patch I just sent.

>> > It would be nice to be able to say "-nographic is equivalent to
>> > '-display none -serial stdio -disable-ctrl-c -other-things'"
>> > but I'm not sure exactly what the -other-things are or even
>> > if we can set them all on the command line specifically.
> We have some code in sun4 which also enabled serial ports
> differently with and without -nographic, maybe because of
> the same thing (which is what this all is about!).
> 
> And there's also another place, passing this NOGRAPHIC thing
> to bios.
> 
> So far that's all.  With chardev you can explicitly control
> Ctrl+C behavour using signal={on|off} attribute.

Unfortunately, you cannot use -chardev for the vast majority of boards
(all those that have no ISA/PCI/virtio).

Paolo

  reply	other threads:[~2013-06-28 12:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 12:34 [Qemu-devel] [PATCH] display: stop using DT_NOGRAPHIC, use DT_NONE Michael Tokarev
2013-06-28 10:38 ` Michael Tokarev
2013-06-28 11:24 ` Peter Maydell
2013-06-28 11:29   ` Michael Tokarev
2013-06-28 11:34     ` Peter Maydell
2013-06-28 11:43       ` Michael Tokarev
2013-06-28 11:50         ` Peter Maydell
2013-06-28 12:05         ` Paolo Bonzini
2013-06-28 11:45     ` Andreas Färber
2013-06-28 11:50       ` Michael Tokarev
2013-06-28 11:55         ` Peter Maydell
2013-06-28 12:05           ` Michael Tokarev
2013-06-28 12:06             ` Paolo Bonzini [this message]
2013-06-28 12:09             ` Peter Maydell
2013-06-28 11:56         ` Andreas Färber
2013-06-28 12:05         ` Andreas Färber
2013-06-28 12:11           ` Paolo Bonzini
2013-07-09 18:37 ` Anthony Liguori
2013-07-09 19:00   ` Michael Tokarev
2013-07-09 20:45     ` Anthony Liguori
2013-07-09 21:18       ` Peter Maydell
2013-07-09 21:24         ` Anthony Liguori
2013-07-09 21:36           ` Peter Maydell
2013-07-09 22:03             ` Anthony Liguori
2013-07-16 11:10               ` Michael Tokarev
2013-07-10  4:45           ` Michael Tokarev
2013-07-10  5:08             ` Michael Tokarev
2013-07-16 11:35               ` Peter Maydell
2013-07-10  4:18       ` Michael Tokarev

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=51CD7C5B.10509@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=todd@fries.net \
    /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).