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

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

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

Yeah, but I can see how its useful hack to have for testability, which
is a good thing -- I'd leave it in place even when we get xen triggering
the flush.

In fact, I'd recommend we try getting the linux PV mem driver running on
HVM (using the magic io port write) before starting on the xen side of
things.

Ian



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