Re: [Xen-devel] [PATCH v5 14/28] x86, xsplice: Print payload's symbol name and payload name in backtraces

2016-04-06 Thread Jan Beulich
>>> Konrad Rzeszutek Wilk 04/06/16 4:39 AM >>> >On Fri, Apr 01, 2016 at 09:23:15AM -0600, Jan Beulich wrote: >> >>> On 24.03.16 at 21:00, wrote: >> > @@ -331,16 +332,17 @@ static char *pointer(char *str, char *end, const >> > char **fmt_ptr, >> > { >> > unsigned long sym_size, sym_

Re: [Xen-devel] [PATCH v5 14/28] x86, xsplice: Print payload's symbol name and payload name in backtraces

2016-04-05 Thread Konrad Rzeszutek Wilk
On Fri, Apr 01, 2016 at 09:23:15AM -0600, Jan Beulich wrote: > >>> On 24.03.16 at 21:00, wrote: > > @@ -331,16 +332,17 @@ static char *pointer(char *str, char *end, const char > > **fmt_ptr, > > { > > unsigned long sym_size, sym_offset; > > char namebuf[KSYM_NAME_LEN+1]; >

Re: [Xen-devel] [PATCH v5 14/28] x86, xsplice: Print payload's symbol name and payload name in backtraces

2016-04-01 Thread Jan Beulich
>>> On 24.03.16 at 21:00, wrote: > @@ -331,16 +332,17 @@ static char *pointer(char *str, char *end, const char > **fmt_ptr, > { > unsigned long sym_size, sym_offset; > char namebuf[KSYM_NAME_LEN+1]; > +bool_t payload = 0; > > /* Advance parents fmt string

[Xen-devel] [PATCH v5 14/28] x86, xsplice: Print payload's symbol name and payload name in backtraces

2016-03-24 Thread Konrad Rzeszutek Wilk
Naturally the backtrace is presented when an instruction hits an bug_frame or %p is used. The payloads do not support bug_frames yet - however the functions the payloads call could hit an BUG() or WARN(). The traps.c has logic to scan for it this - and eventually it will find the correct bug_fram