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
Subject: Re: MEM_SHARING_DEBUG
Date: Tue, 14 Jun 2016 09:34:09 +0100 [thread overview]
Message-ID: <20160614083409.GA26606@citrix.com> (raw)
In-Reply-To: <CABaiLQ8irSarVfV=YQqRtAONZwZsYSqdkMpsK6uyc8k3WdUmvw@mail.gmail.com>
On Tue, Jun 14, 2016 at 10:51:33AM +0430, sepanta s wrote:
> 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?
No. I think the output can go to console if you configure it properly.
You can change that to printk if you want to, but I don't think that's
absolutely necessary.
> 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?
>
I don't think it is related to MEM_SHARING_DEBUG.
Wei.
> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-14 8:34 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 ` MEM_SHARING_DEBUG sepanta s
2016-06-14 8:34 ` Wei Liu [this message]
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=20160614083409.GA26606@citrix.com \
--to=wei.liu2@citrix.com \
--cc=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).