Linux USB
 help / color / mirror / Atom feed
From: Linyu Yuan <quic_linyyuan@quicinc.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>, Bin Liu <b-liu@ti.com>,
	Peter Chen <peter.chen@kernel.org>,
	Pawel Laszczak <pawell@cadence.com>,
	Roger Quadros <rogerq@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-usb@vger.kernel.org>, <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/8] usb: gadget: add anonymous definition in some struct for trace purpose
Date: Fri, 15 Sep 2023 09:56:08 +0800	[thread overview]
Message-ID: <e7120ef7-683d-7a92-1f8f-e125b7ccdf6a@quicinc.com> (raw)
In-Reply-To: <eae2be47-f489-4f1b-91c7-f2f81304bfdb@rowland.harvard.edu>


On 9/15/2023 9:51 AM, Alan Stern wrote:
> On Fri, Sep 15, 2023 at 09:02:48AM +0800, Linyu Yuan wrote:
>> On 9/14/2023 10:54 PM, Alan Stern wrote:
>>> You didn't include the version number in the Subject: line.  Undoubtedly
>>> Greg's automatic error checker will warn you about this.  Unless the
>>> version number is clearly marked for each patch, it's difficult for his
>>> programs to tell which email message contains the most recent version.
>>>
>>> On Thu, Sep 14, 2023 at 06:02:56PM +0800, Linyu Yuan wrote:
>>>> Some UDC trace event will save usb udc information, but it use one int
>>>> size buffer to save one bit information of usb udc, it is wast trace
>>>> buffer.
>>>>
>>>> Add anonymous union which have one u32 member can be used by trace event
>>>> during fast assign stage to save more entries with same trace ring buffer
>>>> size.
>>>>
>>>> Signed-off-by: Linyu Yuan <quic_linyyuan@quicinc.com>
>>>> ---
>>> And you didn't include the version change information here, below the
>>> "---" line.
>>>
>>> Apart from that, this is a _lot_ better than before!  I don't know if
>>> Greg will think this change is worth merging, but at least now it's
>>> possible to read the code and understand what's going on.
>>
>> according Steven's comment, maybe will always save data in little endian at
>> trace event
>>
>> fast assign stage.
>>
>> it will add definition of bit field back.
> Yes, that would be even better because you wouldn't have to change the
> definition of struct usb_gadget or struct usb_endpoint at all.  The fast
> assign stage can simply do:
>
> 	__entry->dw1 = (g->sg_supported << 0) |
> 			(g->is_otg << 1) |
> 			...
>
> and then you can easily access the individual bits in __entry.  It
> wouldn't be as fast but it would still save a lot of space.


how about __entry->dw1 = cpu_to_le32(g->dw1) ?




>
> Alan Stern

  reply	other threads:[~2023-09-15  1:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 10:02 [PATCH 0/8] usb: gadget: reduce usb gadget trace event buffer usage Linyu Yuan
2023-09-14 10:02 ` [PATCH 1/8] trace: add new DECLARE_EVENT_CLASS_PRINT_INIT class type Linyu Yuan
2023-09-14 14:29   ` kernel test robot
2023-09-14 10:02 ` [PATCH 2/8] usb: gadget: add anonymous definition in some struct for trace purpose Linyu Yuan
2023-09-14 14:54   ` Alan Stern
2023-09-15  1:02     ` Linyu Yuan
2023-09-15  1:51       ` Alan Stern
2023-09-15  1:56         ` Linyu Yuan [this message]
2023-09-14 10:02 ` [PATCH 3/8] usb: udc: trace: reduce buffer usage of trace event Linyu Yuan
2023-09-14 16:54   ` Steven Rostedt
2023-09-15  1:11     ` Linyu Yuan
2023-09-15  2:16       ` Steven Rostedt
2023-09-15  2:25         ` Linyu Yuan
2023-09-14 10:02 ` [PATCH 4/8] usb: cdns3: " Linyu Yuan
2023-09-14 10:02 ` [PATCH 5/8] usb: dwc3: " Linyu Yuan
2023-09-14 10:03 ` [PATCH 6/8] usb: cdns2: " Linyu Yuan
2023-09-14 10:03 ` [PATCH 7/8] usb: mtu3: " Linyu Yuan
2023-09-14 10:03 ` [PATCH 8/8] usb: musb: " Linyu Yuan
2023-09-14 16:42 ` [PATCH 0/8] usb: gadget: reduce usb gadget trace event buffer usage Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e7120ef7-683d-7a92-1f8f-e125b7ccdf6a@quicinc.com \
    --to=quic_linyyuan@quicinc.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=b-liu@ti.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=pawell@cadence.com \
    --cc=peter.chen@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox