WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

[Xen-devel] Re: [PATCH 0/3][IA64] Accelerate IDE PIO on HVM/IA64

To: Kouya SHIMURA <kouya@xxxxxxxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxx>
Subject: [Xen-devel] Re: [PATCH 0/3][IA64] Accelerate IDE PIO on HVM/IA64
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 27 Feb 2007 10:56:16 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 27 Feb 2007 02:55:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200702270850.l1R8oeK3019985@xxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdaXecoJf2U98ZREdupjAAX8io7RQ==
Thread-topic: [PATCH 0/3][IA64] Accelerate IDE PIO on HVM/IA64
User-agent: Microsoft-Entourage/11.2.5.060620


On 27/2/07 09:34, "Kouya SHIMURA" <kouya@xxxxxxxxxxxxxx> wrote:

> The basic idea is to add a buffering mechanism in a hypervisor.
> I know this approach is not sophisticated. But there is no other
> good way in IA64 which has no string instructions like x86's.
> 
> This patchset is indispensable to support windows/ia64 on HVM
> since installing windows and crash dumping is terribly slow.

Can you explain how this new code works? As I understand it the problem is
that each PIO instruction decoded by Xen and propagated to qemu only
transfers a single word of data. How does this new buffering mechanism work
around this?

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel