Re: [PATCH v2 0/4] io_uring: text representation of opcode in trace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2022-04-25 at 16:47 -0600, Jens Axboe wrote:
> On 4/25/22 9:07 AM, Dylan Yudaken wrote:
> > 
> > This series adds the text representation of opcodes into the trace.
> > This
> > makes it much quicker to understand traces without having to
> > translate
> > opcodes in your head.
> > 
> > Patch 1 adds a type to io_uring opcodes
> > Patch 2 is the translation function.
> > Patch 3 is a small cleanup
> > Patch 4 uses the translator in the trace logic
> 
> Sorry forgot, one last request - can you make this against the
> for-5.19/io_uring-socket branch? That'll include the opcodes added
> for
> 5.19, otherwise we'll most likely end up in a situation where it'll
> merge cleanly but trigger a warning at build time. Also avoids having
> to
> fix those up after the fact in any case.
> 

Sure - that's easy enough




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux