[Crash-utility] [PATCH 0/2] extensions/trace: Sync up with v5.8 struct renaming

[HAGIO KAZUHITO(萩尾 一仁)]

Bhupesh, Lianbo,

I have certainly cc'd Xu Huan (not seen in the email sent by the list for
some reason though), but no response for two weeks.  so let's review this.

Valentin, please wait for a while.

Thanks,
Kazu

-----Original Message-----
> Hi Valentin,
> 
> Thanks for the patchset.
> I've cc'd this to the maintainer of the trace extension.
> 
> Xu Huan, could you please review the patchset?
> 
> (Apparently, Xu could not respond in March 2019, though.. [1]
> Does anyone in Fujitsu know who can maintain this?)
> 
> [1] https://www.redhat.com/archives/crash-utility/2019-March/msg00030.html
> 
> Thanks,
> Kazu
> 
> -----Original Message-----
> > Hi,
> >
> > Trying to use the trace extension on a mainline kernel doesn't work, and it
> > stems from some struct renaming that has happened upstream.
> >
> > These two patches update the internal naming to match the upstream one, and
> > includes some backwards-compatibility checks to figure out which naming version
> > to use depending on what symbols are available.
> >
> > This was briefly tested on on both v5.4 and 5.9-rc1 kernels using QEMU's
> > dump-guest-memory. The kernel starts tracing some sched & initicall stuff from
> > boot, and "trace show" behaves just fine on both of these.
> >
> > Cheers,
> > Valentin
> >
> > Valentin Schneider (2):
> >   extensions/trace: Rename trace_buffer to array_buffer
> >   extensions/trace: Rename ring_buffer to trace_buffer
> >
> >  extensions/trace.c | 101 ++++++++++++++++++++++++++++-----------------
> >  1 file changed, 63 insertions(+), 38 deletions(-)
> >
> > --
> > 2.27.0
> >
> >
> > --
> > Crash-utility mailing list
> > Crash-utility at redhat.com
> > https://www.redhat.com/mailman/listinfo/crash-utility
> 
> 
> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility