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-devel

Re: [Xen-devel] Re: [Patch] the interface of invalidating qemumapcache

To: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>, "Li, Xin B" <xin.b.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Patch] the interface of invalidating qemumapcache
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 27 Jan 2007 16:43:08 +0000
Delivery-date: Sat, 27 Jan 2007 08:42:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8FFF7E42E93CC646B632AB40643802A801E8C33C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: AcbhNpSgnLlsyleeR3aZurd/xO5mYAAmjw1QAHpYsZANUy+bAAbmp7kgAzBSt0AAA6R4dgADlbrAAByKhhoAAgYC0AABZeHTAAhnpzAAAPIroAADTPPi
Thread-topic: [Xen-devel] Re: [Patch] the interface of invalidating qemumapcache
User-agent: Microsoft-Entourage/11.3.3.061214


On 27/1/07 3:27 pm, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx> wrote:

>> Why are we triggering this with an ioport access rather than just
>> adding a new message type between xen and qemu-dm? The latter seems
>> rather cleaner.
>> 
>> Ian
> 
> Since qemu-dm is reponsible for I/O events, I think it's natural (i.e.
> kind of chipset featrue) to construct and send an I/O event to qemu-dm
> to trigger mapcache invalidation. It does not mean the guest needs to
> use an I/O instruction, but our plan is that Xen sends a mapcache
> invalidation message and it's implemented as an I/O event for HVM
> guests.

If Xen is going to trigger the mapcache zap then the additions to the
pv-on-hvm driver package itself doesn't make much sense.

 -- Keir



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