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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 19 Mar 2015 16:23:07 +0200
From:	Alexander Shishkin <>
To:	Mathieu Poirier <>
Cc:	Greg Kroah-Hartman <>,
	"linux-kernel\" <>,
	Pratik Patel <>,,,,,,
Subject: Re: [PATCH v0 01/11] stm class: Introduce an abstraction for System Trace Module devices

Mathieu Poirier <> writes:

> I forgot to mention in my previous email...  I think the hierarchy of
> our respective tracing module along with the generic-stm probably
> needs a review.
> Currently we have drivers/coresight, drivers/intel_th and drivers/stm.
> To me it doesn't scale - what happens when other architectures come
> out with their own hw tracing technologies?
> I suggest we move everything under drivers/hwtracing and as such have:
> drivers/hwtracing
> drivers/hwtracing/intel_ht
> drivers/hwtracing/coresight
> drivers/hwtracing/stm
> That way other architectures can add drivers for their own hw tracing
> technology without further polluting the drivers/ directory and
> concentrating everything in the same area.  What's your view on that?

I wanted to suggest something similar, actually, if you don't mind
moving drivers/coresight, then let's do it.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists