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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANsc=4Vb-2br+K51NWsyQV25R3eJo_=YfpnXsh1G1ecRVDYc3w@mail.gmail.com>
Date:	Thu, 5 Dec 2013 18:54:49 -0500
From:	Adrien Vergé <adrienverge@...il.com>
To:	Christopher Covington <cov@...eaurora.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Russell King <linux@....linux.org.uk>,
	Randy Dunlap <rdunlap@...radead.org>,
	Will Deacon <will.deacon@....com>,
	linux-kernel@...r.kernel.org,
	Ben Dooks <ben.dooks@...ethink.co.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dietmar Eggemann <dietmar.eggemann@....com>,
	linux-arm-kernel@...ts.infradead.org,
	"zhangwei(Jovi)" <jovi.zhangwei@...wei.com>
Subject: Re: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control

Hi Greg and Christopher,

Thank you for your feedback.

2013/12/4 Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> What is it's purpose then?  At first glance, this seems to be exactly
> what 'perf' provides already.  Doesn't perf work on ARM today?

On ARM, perf is unable to trace every instruction, and certainly not
recording the number of cycles taken by every of them. Also, ETM is
not just tracing the execution flow. It can trace data, trigger
tracing on events such as address matching, data matching, context ID
change, monitor CPRT... It would be sad not to use these capabilities.

If we want perf to use ETM's full functionality, its framework clearly
needs to be extended. Future Intel processors will embed Processor
Trace [1], which seems to have similar capabilities as ETM on ARM. At
that point, it will be easier to decide what should be in the kernel
or in perf.

I the meantime, while ETM is not supported elsewhere than in sysfs, it
should at least be configurable. The current implementation is almost
not usable.

> Well, these patches were incorrect, so that's not really a valid
> question :)

Should I correct the pid size and send them again?

Thanks,

Adrien

[1]: http://software.intel.com/en-us/blogs/2013/09/18/processor-tracing
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ