linux-kernel - Re: [PATCH] usb: dwc3: Log dwc3 instance name in traces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250919210150.lpawo24fq26pqls4@synopsys.com>
Date: Fri, 19 Sep 2025 21:01:54 +0000
From: Thinh Nguyen <Thinh.Nguyen@...opsys.com>
To: Prashanth K <prashanth.k@....qualcomm.com>,
        Steven Rostedt
	<rostedt@...dmis.org>
CC: Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Log dwc3 instance name in traces

++Steven

On Fri, Sep 19, 2025, Prashanth K wrote:
> 
> I think we need to go ahead with approach 1 (Passing dwc3 structure to
> dwc3_readl/writel), because we were wrong about the usage of
> container_of(), it wouldn't work since it's a __iomem pointer.
> 
> I'm planning to break this into a 3 patch series
> 1. Removal of dep->regs and use dwc->regs everywhere
> 2. Use dwc pointer in all dwc3_readl/writel()
> 3. Adding the base addr in traces.
> 

Ok.

Hi Steven,

I have a question about trace event configuration. Is there a mechanism
to associate tracepoints with specific device instances when defining
trace events?

This would be useful when we want to avoid extensive driver rewrites,
for both dwc3 and xHCI devices (and potentially others).

Thanks,
Thinh