From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfVqL-0001Wi-3x for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:28:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfVqE-0001U6-Ad for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:27:59 -0400 Received: from [199.232.76.173] (port=40127 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfVqD-0001Tw-Sq for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:27:53 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:50377) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MfVqD-0007S7-JM for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:27:53 -0400 Received: by fxm7 with SMTP id 7so1519811fxm.34 for ; Mon, 24 Aug 2009 02:27:52 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20090824092214.GA22972@shareable.org> References: <20090823124410.GA30789@shareable.org> <53e878390908231020s32575288jf2dd1450bae241c9@mail.gmail.com> <20090823215558.GA9093@shareable.org> <53e878390908231554o39fb1700n8b495e6c1089fc6@mail.gmail.com> <53e878390908240144v4c99fb89i7ac204356128d38f@mail.gmail.com> <20090824092214.GA22972@shareable.org> Date: Mon, 24 Aug 2009 11:27:52 +0200 Message-ID: <53e878390908240227ta9aa3a6qd71d64cbec41a78d@mail.gmail.com> Subject: Re: [Qemu-devel] [PATCH 0 of 1] Fix for DOS keyboard problems From: Stefan Ring Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: qemu-devel@nongnu.org On Mon, Aug 24, 2009 at 11:22 AM, Jamie Lokier wrote: > Btw, a timer won't necessarily fix the problem seen with Borland, if > QEMU/KVM are preempted at the wrong moment - unless there's a virtual > CPU timer available which is not affected by host scheduling. That's what I thought. Bochs uses a virtual CPU timer but that's easy to do in Bochs because everything is emulated. I suppose the same could be done with QEMU for 16 bit mode because everything is emulated as well, AFAIK. The more native 32 bit modes would be much more difficult or almost impossible, though. And it would not be good to have port 60h behave differently in 16 bit mode vs. 32 bit mode. Just some random thoughts...