From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KvBxp-0006MY-FD for qemu-devel@nongnu.org; Wed, 29 Oct 2008 10:24:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KvBxn-0006Lg-Lt for qemu-devel@nongnu.org; Wed, 29 Oct 2008 10:24:00 -0400 Received: from [199.232.76.173] (port=45032 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KvBxn-0006LX-AP for qemu-devel@nongnu.org; Wed, 29 Oct 2008 10:23:59 -0400 Received: from mail-gx0-f28.google.com ([209.85.217.28]:52022) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KvBxn-00082t-2w for qemu-devel@nongnu.org; Wed, 29 Oct 2008 10:23:59 -0400 Received: by gxk9 with SMTP id 9so108080gxk.10 for ; Wed, 29 Oct 2008 07:23:58 -0700 (PDT) Message-ID: <490871F9.3010801@codemonkey.ws> Date: Wed, 29 Oct 2008 09:23:53 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 3/3] Add KVM support to QEMU References: <1225224814-9875-1-git-send-email-aliguori@us.ibm.com> <1225224814-9875-2-git-send-email-aliguori@us.ibm.com> <1225224814-9875-3-git-send-email-aliguori@us.ibm.com> <49078707.5000109@redhat.com> <49078955.2090109@codemonkey.ws> <5d6222a80810281604g39708040kf710725dce6413dd@mail.gmail.com> <4907A1FA.2060106@codemonkey.ws> <49086E96.80809@redhat.com> <49087029.9020100@bellard.org> In-Reply-To: <49087029.9020100@bellard.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Cc: Glauber Costa , hollis@alumni.cmu.edu, Gerd Hoffmann , kvm-devel Fabrice Bellard wrote: > Avi Kivity wrote: > >> Hollis Blanchard wrote: >> >>> >>> Out of curiosity, where are those places? >>> >>> >> local apic -- needs to access interrupt disable flag >> acpi sleep -- halts the current processor, so tied to cpustate >> vmport -- bad ABI requires access to registers >> > > These accesses are the exception and should be done with specific CPU > methods. IMHO, direct access to the CPU state should otherwise never be > done from devices. > Yes, this is what I'm working on now. There are also non-devices that access CPUState but they are also special cases (gdbstub, monitor, save/restore). Regards, Anthony Liguori > Regards, > > Fabrice. > > > >