linux-kernel - Re: [PATCH 07/15] ARM: etm: Return the entire trace buffer if it is empty after reset

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]

Date:	Thu, 28 Jun 2012 17:57:50 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Arve Hjønnevåg <arve@...roid.com>,
	Russell King <linux@....linux.org.uk>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Subject: Re: [PATCH 07/15] ARM: etm: Return the entire trace buffer if it is
 empty after reset

On Thu, Jun 21, 2012 at 12:47 AM, John Stultz <john.stultz@...aro.org> wrote:

> From: Arve Hjønnevåg <arve@...roid.com>
>
> On some SOCs the read and write pointer are reset when the chip
> resets, but the trace buffer content is preserved. If the status
> bits indicates that the buffer is empty and we have never started
> tracing, assume the buffer is full instead. This can be useful
> if the system rebooted from a watchdog reset.
>
> CC: Russell King <linux@....linux.org.uk>
> CC: Paul Gortmaker <paul.gortmaker@...driver.com>
> CC: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
> Acked-by: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
> Signed-off-by: Arve Hjønnevåg <arve@...roid.com>
> Signed-off-by: John Stultz <john.stultz@...aro.org>

This looks *very* useful.
Acked-by: Linus Walleij <linus.walleij@...aro.org>

Yours,
Linus Walleij
--
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/