From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Serial port hacking -- BUG?
Date: Tue, 17 Aug 2004 18:26:19 +1200 [thread overview]
Message-ID: <1092723978.2596.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1092615186.5801.2.camel@unixadmindazfc2.chh.co.nz>
[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]
Hi All,
I've been working on the latest snapshot's serial code and it
appears that there is some sort of bug that is preventing data sent by a
guest from making out to the host. For example, if one connects the
builtin serial port (com1 or /dev/ttyS0) to stdio with '-serial stdio'
then if you connect something like minicom or hyperterm to the
appropriate port in the guest, you can see anything you type into the
console (STDIN) of the host appearing correctly in the guest. However,
if you send some data down the line from inside the guest, nothing
'comes out' at the host end (on STDOUT, in this example). I have also
connected the host end of the pipe to a psuedo-terminal slave and the
same behaviour is present; anything cat-ed (or whatever) to the pty on
the Host appears on the serial port of the guest, but the reverse is not
true...
I have verified that the data sent from the guest is indeed being
read and it appears inside the serial_ioport_read() function
successfully, but tracing it onwards from there appears to take me deep
into the guts of qemu's machine emulation model and I'm not really
enough of an uber-hacker to follow it from there without spending
serious amounts of time...
Can anyone shed some light on this apparent bug, or perhaps point me
in the right direction to trace it further than serial_ioport_read() and
its entry into the ioport_table ?
Cheers,
D
On Mon, 2004-08-16 at 12:13, Darryl Dixon wrote:
> Hi,
>
> Whereabouts would I start looking to find the 'glue' code that
> connects the emulation of the guest's serial port with the 'real'
> world? I've looked briefly at serial.c but it only seemed to deal
> with the guts of the emulation, rather that directing its output...
> (maybe I'm just being thick and missing the obvious?) Any pointers
> and help to send me in the right direction appreciated.
>
> Cheers,
> --
> Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
>
> ______________________________________________________________________
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
[-- Attachment #2: Type: text/html, Size: 3087 bytes --]
next prev parent reply other threads:[~2004-08-17 6:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 0:13 [Qemu-devel] Serial port hacking Darryl Dixon
2004-08-15 19:37 ` Nile Geisinger
2004-08-17 6:26 ` Darryl Dixon [this message]
2004-08-17 0:23 ` [Qemu-devel] Serial port -- OPPOSITE BUG == COMPLETE SOLUTION? Nile Geisinger
2004-08-17 14:00 ` Darryl Dixon
2004-08-19 20:47 ` [Qemu-devel] Serial port hacking -- BUG? Hampa Hug
2004-08-19 17:15 ` [Qemu-devel] Serial port hacking -- Fix verified on Linux Nile Geisinger
2004-08-20 3:07 ` [Qemu-devel] Serial port hacking -- Fix verified for Windows Guest (kindof ;) Darryl Dixon
2004-08-23 19:00 ` Fabrice Bellard
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=1092723978.2596.8.camel@localhost.localdomain \
--to=esrever_otua@pythonhacker.is-a-geek.net \
--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).