* MEM_SHARING_DEBUG
@ 2016-06-12 10:07 sepanta s
2016-06-13 8:29 ` MEM_SHARING_DEBUG Wei Liu
0 siblings, 1 reply; 6+ messages in thread
From: sepanta s @ 2016-06-12 10:07 UTC (permalink / raw)
To: xen-devel
[-- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MEM_SHARING_DEBUG
2016-06-12 10:07 MEM_SHARING_DEBUG sepanta s
@ 2016-06-13 8:29 ` Wei Liu
2016-06-14 6:21 ` MEM_SHARING_DEBUG sepanta s
0 siblings, 1 reply; 6+ messages in thread
From: Wei Liu @ 2016-06-13 8:29 UTC (permalink / raw)
To: sepanta s; +Cc: Wei Liu, xen-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MEM_SHARING_DEBUG
2016-06-13 8:29 ` MEM_SHARING_DEBUG Wei Liu
@ 2016-06-14 6:21 ` sepanta s
2016-06-14 8:34 ` MEM_SHARING_DEBUG Wei Liu
0 siblings, 1 reply; 6+ messages in thread
From: sepanta s @ 2016-06-14 6:21 UTC (permalink / raw)
To: Wei Liu; +Cc: xen-devel
[-- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MEM_SHARING_DEBUG
2016-06-14 6:21 ` MEM_SHARING_DEBUG sepanta s
@ 2016-06-14 8:34 ` Wei Liu
2016-06-14 9:16 ` MEM_SHARING_DEBUG sepanta s
0 siblings, 1 reply; 6+ messages in thread
From: Wei Liu @ 2016-06-14 8:34 UTC (permalink / raw)
To: sepanta s; +Cc: Wei Liu, xen-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MEM_SHARING_DEBUG
2016-06-14 8:34 ` MEM_SHARING_DEBUG Wei Liu
@ 2016-06-14 9:16 ` sepanta s
2016-06-14 9:34 ` MEM_SHARING_DEBUG Wei Liu
0 siblings, 1 reply; 6+ messages in thread
From: sepanta s @ 2016-06-14 9:16 UTC (permalink / raw)
To: Wei Liu; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 2168 bytes --]
On Tue, Jun 14, 2016 at 1:04 PM, Wei Liu <wei.liu2@citrix.com> wrote:
> 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.
>
> how can I configure it ?
> 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.
>
> no it is not related to MEM_SHARING_DEBUG,
I think it is because of compiling xen in debug mode.
> 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
>
>
[-- Attachment #1.2: Type: text/html, Size: 4036 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MEM_SHARING_DEBUG
2016-06-14 9:16 ` MEM_SHARING_DEBUG sepanta s
@ 2016-06-14 9:34 ` Wei Liu
0 siblings, 0 replies; 6+ messages in thread
From: Wei Liu @ 2016-06-14 9:34 UTC (permalink / raw)
To: sepanta s; +Cc: Wei Liu, xen-devel
On Tue, Jun 14, 2016 at 01:46:45PM +0430, sepanta s wrote:
> On Tue, Jun 14, 2016 at 1:04 PM, Wei Liu <wei.liu2@citrix.com> wrote:
>
> > 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.
> >
> > how can I configure it ?
Use "xl debug-keys h" and then "xl dmesg" to see all debug keys.
Try "xl debug-keys T" and then "xl dmesg"? I think you should be able to
see "debugtrace_printk now writing to $THING" where $THING would be
either buffer or console.
Note, you do need to enable DEBUG_TRACE_DUMP (a compile time option) in
your hypervisor to have debugtrace support.
>
>
> > 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.
> >
> > no it is not related to MEM_SHARING_DEBUG,
> I think it is because of compiling xen in debug mode.
>
The only way to find out is to obtain relevant logs and see what goes
wrong.
http://wiki.xenproject.org/wiki/Xen_Serial_Console
Wei.
> > 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-06-14 9:34 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 ` 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
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.