qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/2] trap signals for "-serial mon:stdio"
Date: Tue, 09 Jul 2013 13:21:44 +0200	[thread overview]
Message-ID: <51DBF248.4050102@suse.de> (raw)
In-Reply-To: <CAMo8BfLiESYYZdU2Q3HJo3VQ5K9PWayNTyTOtNeDnX=KNUzcqQ@mail.gmail.com>

Hi Max,

Am 09.07.2013 13:00, schrieb Max Filippov:
> On Tue, Jul 9, 2013 at 12:42 PM, Andreas Färber <afaerber@suse.de> wrote:
>> Am 09.07.2013 09:39, schrieb Michael Tokarev:
>>> Ping?
>>
>> Have you tested -semihosting? The xtensa test image on the Wiki uses
>> -nographic, but semihosting content always seems to go to stdout without
>> going through a chardev IIUC...
> 
> xtensa semihosting allows guest privileged code to work with host's file
> descriptors doing open/read/write/lseek/close. Linux sim machine uses it
> to implement console (with standard 0/1 file descriptors), simulated disks
> and networking. Do you think it's worth tying these descriptors with a
> chardev? If so, I'm probably the right person to do it (:

Paolo's/Michael's patches are relying on -serial stdio,signal=on as a
replacement implementation for -nographic, so I raised the question of
whether that would work as expected for -semihosting in general. I do
not have test images for arm or m68k semihosting, so I cannot tell
whether xtensa should be doing something differently.

Peter and me seemed to agree that unicore32 instructions shouldn't mess
with the host's ncurses directly, but Blue apparently didn't agree and
applied it (and I guess neither of us has access to a test image to see
it in action).

stdio seems less intrusive compared to that, but I did have issues with
input at the xtensa login prompt going to the monitor instead (I use
-qmp for all my test machines to inspect the QOM tree, so I needed to
specify -monitor mon:stdio manually); -display none -monitor none -qmp
unix:... worked better for me.

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-07-09 11:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 16:29 [Qemu-devel] [PATCH v3 1/2] trap signals for "-serial mon:stdio" Michael Tokarev
2013-07-03 16:29 ` [Qemu-devel] [PATCH v3 2/2] display: stop using DT_NOGRAPHIC, use DT_NONE Michael Tokarev
2013-07-09 14:07   ` Peter Maydell
2013-07-09  7:39 ` [Qemu-devel] [PATCH v3 1/2] trap signals for "-serial mon:stdio" Michael Tokarev
2013-07-09  8:42   ` Andreas Färber
2013-07-09  8:57     ` Michael Tokarev
2013-07-09 11:00     ` Max Filippov
2013-07-09 11:21       ` Andreas Färber [this message]
2013-07-09 12:02     ` Michael Tokarev
2013-07-09 12:37       ` Peter Maydell
2013-07-09 12:40         ` Andreas Färber
2013-07-09 12:45           ` Peter Maydell
2013-07-09 13:13           ` Michael Tokarev
2013-07-09 14:04 ` Peter Maydell
2013-07-09 14:24   ` Michael Tokarev
2013-07-10 19:33 ` Anthony Liguori

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=51DBF248.4050102@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).