From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BwxUt-0002mx-5j for qemu-devel@nongnu.org; Tue, 17 Aug 2004 02:31:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BwxUn-0002lj-DI for qemu-devel@nongnu.org; Tue, 17 Aug 2004 02:31:02 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BwxUn-0002lZ-B5 for qemu-devel@nongnu.org; Tue, 17 Aug 2004 02:30:57 -0400 Received: from [203.9.177.36] (helo=mailhost.chh.co.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BwxQZ-0001BL-3I for qemu-devel@nongnu.org; Tue, 17 Aug 2004 02:26:35 -0400 Subject: Re: [Qemu-devel] Serial port hacking -- BUG? From: Darryl Dixon In-Reply-To: <1092615186.5801.2.camel@unixadmindazfc2.chh.co.nz> References: <1092615186.5801.2.camel@unixadmindazfc2.chh.co.nz> Content-Type: multipart/alternative; boundary="=-GYXvw9YiXfaB0nDNeZMh" Message-Id: <1092723978.2596.8.camel@localhost.localdomain> Mime-Version: 1.0 Date: Tue, 17 Aug 2004 18:26:19 +1200 Reply-To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org --=-GYXvw9YiXfaB0nDNeZMh Content-Type: text/plain Content-Transfer-Encoding: 7bit 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 > > ______________________________________________________________________ > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Darryl Dixon --=-GYXvw9YiXfaB0nDNeZMh Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit 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>
--=-GYXvw9YiXfaB0nDNeZMh--