linux-kernel - Re: [PATCH 4/8] ARM: etm: Allow range selection

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: <AANLkTim776VyU_LioTL2-pOjskVDeU4BpFuw6CxGUXRT@mail.gmail.com>
Date:	Tue, 15 Feb 2011 15:04:31 -0800
From:	Arve Hjønnevåg <arve@...roid.com>
To:	Arve Hjønnevåg <arve@...roid.com>,
	linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org,
	Russell King <linux@....linux.org.uk>,
	Jason Wessel <jason.wessel@...driver.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/8] ARM: etm: Allow range selection

On Tue, Feb 15, 2011 at 5:50 AM, Alexander Shishkin <virtuoso@...nd.org> wrote:
> On Mon, Feb 14, 2011 at 10:11:12PM -0800, Arve Hjønnevåg wrote:
>> Trace kernel text segment by default as before, allow tracing of other
>> ranges by writing a range to /sys/devices/etm/trace_range, or to trace
>> everything by writing 0 0.
>
> Since you're adding this, I think it might make sense to add a 3rd optional
> ctx id field, so that userspace tracing is also possible, especially when
> on-chip ETB sizes increase to something more sensible than what they are
> these days.
>

That might be useful, but I think it can be added later. My main
motivation for adding this is so we can turn off the filtering. We
want to use tracing in combination with a hardware watchdog to debug
hard lockups and we don't want any filtering in this case.

-- 
Arve Hjønnevåg
--
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/