From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D6isl-0002HE-4g for qemu-devel@nongnu.org; Thu, 03 Mar 2005 00:28:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D6isk-0002Gn-Ff for qemu-devel@nongnu.org; Thu, 03 Mar 2005 00:28:18 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6isk-0002Gk-9z for qemu-devel@nongnu.org; Thu, 03 Mar 2005 00:28:18 -0500 Received: from [128.8.10.164] (helo=po2.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D6iaC-0005rr-JU for qemu-devel@nongnu.org; Thu, 03 Mar 2005 00:09:08 -0500 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po2.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j23596eh003440 for ; Thu, 3 Mar 2005 00:09:07 -0500 (EST) Date: Thu, 3 Mar 2005 00:09:06 -0500 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Qemu Guest Tools Message-ID: <20050303050906.GA14446@jbrown.mylinuxbox.org> References: <4912.1109718464@www32.gmx.net> <20050302013220.GA28323@jbrown.mylinuxbox.org> <4225B533.2030801@gmx.de> <20050302143856.GA4688@jbrown.mylinuxbox.org> <4226916C.8050706@wasp.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4226916C.8050706@wasp.net.au> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Thu, Mar 03, 2005 at 08:24:12AM +0400, Brad Campbell wrote: > Jim C. Brown wrote: > > > >I am against mouse grabbing myself. I just use the no-sdl-grab patch and > >deal > >with a desyncing guest mouse pointer (sometimes I can work around it by > >turning mouse acceleration off in the guest). > > I was thinking about a little guest app to keep them in sync. This is how > win4lin does it and it works very well. It is dead easy to do under windows > as mouse manipulation from userspace is a doddle, don't know about linux > though. > Does it move the guest pointer back to the spot where the host pointer is (in which case disabling mouse accerleration would be better) or does it let win4lin know where the guest pointer is so the host pointer can be moved to that position? The latter would be ideal, but short of guest-to-host communication there is no way to be completely sure where the mouse pointer is (tho you can be pretty sure most of the time). > > > >>I've decided against some special i/o port or such because I don't know > >>anything about these things :) and because it would require a driver on > >>the guest side (is that correct?). > > > > > >Unfortuantly, yes. However, the magic instruction set would not. (You would > >probably need to reimplement a new one for each arch qemu supports/will be > >ported to though.) > > > > This was my thought. Networking is not always available. A couple of IO > ports would always be there. Actually, I think that magic instructions might be better. It doesn't require a special guest driver and thus it would be easier to develop the tools. IO ports would be easier to standardize however. Detecting whether or not they're running in qemu is also a cinch: if they aren't they get an "illegal instruction" error. > > Regards, > Brad > -- > "Human beings, who are almost unique in having the ability > to learn from the experience of others, are also remarkable > for their apparent disinclination to do so." -- Douglas Adams > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.