From: sepanta s <sapanta992@gmail.com>
To: xen-devel@lists.xen.org
Subject: MEM_SHARING_DEBUG
Date: Sun, 12 Jun 2016 14:37:29 +0430 [thread overview]
Message-ID: <CABaiLQ--HMqWWja3yhuPKf6yarnAX1c-HmNUvVkO5KRenAYT=Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 351 bytes --]
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?
[-- Attachment #1.2: Type: text/html, Size: 537 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-06-12 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 10:07 sepanta s [this message]
2016-06-13 8:29 ` MEM_SHARING_DEBUG Wei Liu
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABaiLQ--HMqWWja3yhuPKf6yarnAX1c-HmNUvVkO5KRenAYT=Q@mail.gmail.com' \
--to=sapanta992@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).