xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: sepanta s <sapanta992@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Date: Mon, 13 Jun 2016 09:29:37 +0100	[thread overview]
Message-ID: <20160613082937.GB25425@citrix.com> (raw)
In-Reply-To: <CABaiLQ--HMqWWja3yhuPKf6yarnAX1c-HmNUvVkO5KRenAYT=Q@mail.gmail.com>

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.


> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Xen-devel mailing list

  reply	other threads:[~2016-06-13  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-12 10:07 MEM_SHARING_DEBUG sepanta s
2016-06-13  8:29 ` Wei Liu [this message]
2016-06-14  6:21   ` MEM_SHARING_DEBUG sepanta s
2016-06-14  8:34     ` MEM_SHARING_DEBUG Wei Liu
2016-06-14  9:16       ` MEM_SHARING_DEBUG sepanta s
2016-06-14  9:34         ` MEM_SHARING_DEBUG Wei Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160613082937.GB25425@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=sapanta992@gmail.com \
    --cc=xen-devel@lists.xen.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).