|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] vram_dirty vs. shadow paging dirty tracking
When thinking about multithreading the device model, it occurred to me
that it's a little odd that we're doing a memcmp to determine which
portions of the VRAM has changed. Couldn't we just use dirty page
tracking in the shadow paging code? That should significantly lower the
overhead of this plus I believe the infrastructure is already mostly
there in the shadow2 code.
Is this a sane idea?
Regards,
Anthony Liguori
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] vram_dirty vs. shadow paging dirty tracking,
Anthony Liguori <=
|
|
|
|
|