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

[Xen-devel] Tracking DomU memory

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Security Initiative Team <passrete@xxxxxxxxx>
  • Date: Sat, 7 Oct 2006 17:53:27 -0700 (PDT)
  • Delivery-date: Mon, 09 Oct 2006 03:25:16 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=KmHQ2e2EVW4uf9GOZeZJRe3tRzWKOFMxgaLdaJsF2sN6fpPjGp7F1oLj1dx6UEDg1e+SiSifoWUvbX5K8+z0ep/0+S9+bPXF1p3N4Irth0azrmw6U0bFhums2MpNbCljYyHQnyri6Fx9zFx2NOPU4+7PMdwi/KqU06x/d0vSsa4= ;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


To track the memory being used by an application running in DomU,
is it better to make tweaks in Dom0 or the hypervisor layer?

Is it possible to just put some hooks in the do_mmu_update hypercall?

Also, how does one enable log-dirty shadow mode?
Does this actually createa log file somewhere?


Get your email and more, right on the new Yahoo.com
Xen-devel mailing list



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