From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH 1/1] xen-hvm.c: Add support for Xen access
	to vmport
Date: Mon, 29 Sep 2014 14:57:12 +0200
Message-ID: <54295728.5080203@suse.de>
References: <1411757235-29128-1-git-send-email-dslutz@verizon.com>	<1411757235-29128-2-git-send-email-dslutz@verizon.com>
	<54291463.1080205@suse.de> <54293E24.3080205@redhat.com>
	<54294832.9060001@suse.de> <54294ECF.1040705@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
In-Reply-To: <54294ECF.1040705@redhat.com>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=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: Paolo Bonzini <pbonzini@redhat.com>, Don Slutz <dslutz@verizon.com>, qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, Marcel Apfelbaum <marcel.a@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, Markus Armbruster <armbru@redhat.com>, Anthony Liguori <aliguori@amazon.com>, =?windows-1252?Q?Andreas_F=E4rber?= <afaerber@suse.de>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org



On 29.09.14 14:21, Paolo Bonzini wrote:
> Il 29/09/2014 13:53, Alexander Graf ha scritto:
>>
>>   cpu_handle_ioreq()
>>   {
>>     ...
>>
>>     if (req->type == IOPORT_REGISTERS_SYNCHRONIZED) {
>>         cpu->xen_vcpu_dirty = true;
>>         synchronize_xen_to_env(xenptr, cpu);
>>     }
>>
>>     handle_ioreq();
>>
>>     if (req->type == IOPORT_REGISTERS_SYNCHRONIZED) {
>>         cpu->xen_vcpu_dirty = false;
>>         synchronize_env_to_xen(xenptr, cpu);
>>     }
>>
>>     ...
>>   }
>>
>>   void xen_cpu_synchronize_state(CPUState *cpu)
>>   {
>>     assert(cpu->xen_vcpu_dirty);
>>   }
>>
>> Then no changes to the vmport code would be necessary and this problems
>> where some code path wants to do direct access to registers
>> automatically tells us that things are broken.
> 
> Yeah, that would be possible.  You do not even need synchronize_state,
> it seems to me that it introduces more complication for little gain.

Well, it makes all accels behave the same and keep information always at
a single entity (the env struct). I don't think the vmport code should
have knowledge of a xen env struct.


Alex