On Sun, Jun 12, 2016 at 02:37:29PM +0430, sepanta s wrote: > Hi, > > how to does MEM_SHARING_DEBUG works in xen ? > This function is located at and its internal structure is > xen/arch/x86/mm/mem_sharing.c > <https://github.com/mirage/xen/blob/a6f2cdb633bf519244a16674031b8034b581ba7f/xen/arch/x86/mm/mem_sharing.c> > debugtrace_printk("*mem_sharing_debug*: %s(): " _f, __func__, ##_a) > , so where the logs are being saved?
From reading the code it can be configured to go to the hypervisor console. You then can use xl dmesg to view it. Note that you need to have a debug hypervisor to have debugtrace support. Then you can use xl debug-keys T to toggle whether the output goes to console directly or goes to internal buffer. Wei. > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
