Re: [Xen-devel] [PATCH v4 3/6] tools/dm_restrict: Ask QEMU to chroot

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Anthony PERARD [mailto:anthony.perard@xxxxxxxxxx]
> Sent: 06 November 2018 11:11
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> Cc: George Dunlap <George.Dunlap@xxxxxxxxxx>; xen-
> devel@xxxxxxxxxxxxxxxxxxxx; Ian Jackson <Ian.Jackson@xxxxxxxxxx>; Wei Liu
> <wei.liu2@xxxxxxxxxx>
> Subject: Re: [Xen-devel] [PATCH v4 3/6] tools/dm_restrict: Ask QEMU to
> chroot
> 
> On Tue, Nov 06, 2018 at 10:53:48AM +0000, Paul Durrant wrote:
> > Ok. The trace backend is set at build time in tools/Makefile:
> >
> >         if $$source/scripts/tracetool.py --check-backend --backend log ;
> then \
> >                 enable_trace_backend='--enable-trace-backend=log';
> >         elif $$source/scripts/tracetool.py --check-backend --backend
> stderr ; then \
> >                 enable_trace_backend='--enable-trace-backend=stderr'; \
> >         else \
> >                 enable_trace_backend='' ; \
> >         fi ; \
> >
> > and log appears to favoured. Is this still going to work with the
> > chroot? We rely on the tracing in xen_platform to get log messages out
> > of PV drivers.
> 
> log vs stderr are just different names for the same thing. "stderr"
> doesn't exist anymore in recent version of QEMU and as been renamed
> "log".

Oh yes, I'd forgotten... That's fine then :-)

  Paul

> 
> --
> Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel