[Intel-gfx] [PATCH] tools/intel_guc_logger: Utility for capturing GuC firmware logs in a file
Chris Wilson
chris at chris-wilson.co.uk
Wed Sep 7 09:55:21 UTC 2016
On Wed, Sep 07, 2016 at 10:37:07AM +0100, Tvrtko Ursulin wrote:
>
> On 07/09/16 09:44, Chris Wilson wrote:
> >And fixing the blocking read() is about 10 lines in the kernel...
>
> Haven't checked but if that is the case, since we are already fixing
> relayfs issues, it would be good to do that one as well since it
> would simplify the logger. Because if we do it straight away then we
> know logger can use it, and if we leave it for later then it gets
> uglier for the logger.
>
> But if we cannot make the fix go in the same kernel version (or
> earlier) than the GuC logging then I think we don't need to block on
> that.
Totally agree. I think the poll() example is more useful anyway, since
that is more likely to fit into the event loop of a real client.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
More information about the Intel-gfx
mailing list