From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XYYqu-0001Wo-Rg for qemu-devel@nongnu.org; Mon, 29 Sep 2014 07:10:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XYYqk-0007Wo-T1 for qemu-devel@nongnu.org; Mon, 29 Sep 2014 07:10:48 -0400 Received: from mail-we0-x235.google.com ([2a00:1450:400c:c03::235]:54250) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XYYqk-0007WR-DO for qemu-devel@nongnu.org; Mon, 29 Sep 2014 07:10:38 -0400 Received: by mail-we0-f181.google.com with SMTP id u57so1221288wes.26 for ; Mon, 29 Sep 2014 04:10:32 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <54293E24.3080205@redhat.com> Date: Mon, 29 Sep 2014 13:10:28 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1411757235-29128-1-git-send-email-dslutz@verizon.com> <1411757235-29128-2-git-send-email-dslutz@verizon.com> <54291463.1080205@suse.de> In-Reply-To: <54291463.1080205@suse.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/1] xen-hvm.c: Add support for Xen access to vmport List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf , Don Slutz , qemu-devel@nongnu.org Cc: xen-devel@lists.xensource.com, Marcel Apfelbaum , "Michael S. Tsirkin" , Markus Armbruster , Anthony Liguori , =?windows-1252?Q?Andreas_F=E4rber?= , Stefano Stabellini Il 29/09/2014 10:12, Alexander Graf ha scritto: > Could you instead plug into the existing cpu_synchronize_registers() > framework and just implement register synchronization for the Xen side, > just like it's been done for KVM? :) No, because here it's Xen that sends out the register contents. With KVM, it's QEMU that requests the register contents. Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 1/1] xen-hvm.c: Add support for Xen access to vmport Date: Mon, 29 Sep 2014 13:10:28 +0200 Message-ID: <54293E24.3080205@redhat.com> References: <1411757235-29128-1-git-send-email-dslutz@verizon.com> <1411757235-29128-2-git-send-email-dslutz@verizon.com> <54291463.1080205@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54291463.1080205@suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Alexander Graf , Don Slutz , qemu-devel@nongnu.org Cc: xen-devel@lists.xensource.com, Marcel Apfelbaum , "Michael S. Tsirkin" , Markus Armbruster , Anthony Liguori , =?windows-1252?Q?Andreas_F=E4rber?= , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org Il 29/09/2014 10:12, Alexander Graf ha scritto: > Could you instead plug into the existing cpu_synchronize_registers() > framework and just implement register synchronization for the Xen side, > just like it's been done for KVM? :) No, because here it's Xen that sends out the register contents. With KVM, it's QEMU that requests the register contents. Paolo