From: Muli Ben-Yehuda Subject: Re: [PATCH] allow connecting to xenconsole from remote hosts Date: Wed, 13 Sep 2006 16:59:04 +0300 Message-ID: <20060913135904.GG5723@rhun.haifa.ibm.com> References: <20060907072859.GA24294@rhun.haifa.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Jimi Xenidis , xen-devel , Anthony Liguori , Orran Y Krieger List-Id: xen-devel@lists.xenproject.org On Wed, Sep 13, 2006 at 02:37:31PM +0100, Keir Fraser wrote: > On 7/9/06 08:28, "Muli Ben-Yehuda" wrote: > > > The attached patch makes xenconsole send and receive console messages > > over a remote connection, instead of via stdin/stdout - if given the > > --remote switch. It is useful for proxy'ing real console message or > > other protocol messages (such as gdb) between dom0 and a remote > > host. We're currently using it for proxying gdb between gdbstub in a > > partition that talks gdb over the console page to a remote host > > running gdb. > > You still have that message/queue struct stuff. Is it needed, especially now > that noecho is gone? I need someplace to keep what we read from a source fd until the destination fd becomes writable. The original code just assumed everything is writable and wrote it immediately; this assumption may not be correct when the destination fd is a socket. Cheers, Muli