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

[Xen-devel] is there any way to avoid lazy updates to page attribute bits?

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Kip Macy" <kip.macy@xxxxxxxxx>
  • Date: Tue, 19 Feb 2008 18:34:58 -0800
  • Delivery-date: Tue, 19 Feb 2008 18:35:26 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=bfr59L0OnWwOGGKxddsU7tTErgzK6wE6t9wwHe7PGwS1tC+447XX5eOweladekMfRqzqeuAR7aKzpxbIZ+j8D3uC/DzZM6BzEcUlsxwyOSCXnnRFTFRQL+deKm2AnOxHruhGf+CwBAfWn6/UvlVBGVSLY5ASRj7ndGtfI9OeOIs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm finding that regardless of which update method I use - writeable
page tables, HYPERVISOR_update_va_mapping, or HYPERVISOR_mmu_update
that xen will frequently only update the address bits in the page
table at the time of the hypercall - presumably setting the attribute
bits some time later when the mapping is accessed. This is fairly
problematic for me in that freebsd relies on the page attribute bits
in the page table accurately reflecting the attributes that were set
for a mapping. Is it now necessary for PV guests to maintain page
attribute data outside of the page tables?


Xen-devel mailing list



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