[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.