From: sepanta s <sapanta992@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: MEM_SHARING_DEBUG
Date: Tue, 14 Jun 2016 10:51:33 +0430 [thread overview]
Message-ID: <CABaiLQ8irSarVfV=YQqRtAONZwZsYSqdkMpsK6uyc8k3WdUmvw@mail.gmail.com> (raw)
In-Reply-To: <20160613082937.GB25425@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1363 bytes --]
On Mon, Jun 13, 2016 at 12:59 PM, Wei Liu <wei.liu2@citrix.com> wrote:
> 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.
>
> Should I change the mem_debug_share to printk you mean?
dmesg buffer is limited and I miss some debugging info.
> 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.
>
> I have enabled debugging in xen as I changed debug:= y in Config.mk.
But after compilation and reboot, when I select booting from xen hypervisor
in the grub menu, my ubuntu goes beyond the initialzing ram and then it
reboots.
Am I missing something?
Wei.
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 2415 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 prev parent reply other threads:[~2016-06-14 6:21 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 ` MEM_SHARING_DEBUG Wei Liu
2016-06-14 6:21 ` sepanta s [this message]
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='CABaiLQ8irSarVfV=YQqRtAONZwZsYSqdkMpsK6uyc8k3WdUmvw@mail.gmail.com' \
--to=sapanta992@gmail.com \
--cc=wei.liu2@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.