linux-kernel - Re: [PATCH -mm] extend sysrq-p functionality to cover all CPUs

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: <20080310130341.74eac553@bree.surriel.com>
Date:	Mon, 10 Mar 2008 13:03:41 -0400
From:	Rik van Riel <riel@...riel.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, lwoodman@...hat.com
Subject: Re: [PATCH -mm] extend sysrq-p functionality to cover all CPUs

On Mon, 10 Mar 2008 09:24:13 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> > however just
> > sysrq-p seems like a waste to have because it will probably not
> > print anything useful on a large CPU system...
> 
> Yeah, sometimes it helps to keep hitting it until you get the right CPU,
> but that rather depends on interrupt distribution.
> 
> It would be neat to suppress the trace for idle CPUs.  I don't _think_
> there's a need to display the trace for idle CPUs in sysrq-P?
> 
> > If you still want it to be a separate letter, just let me know
> > which one of the last four I should take.
> 
> l :)

OK, I'll do that.  I will also change the show_lock to spinlock_irq_save
just in case sysrq-p gets invoked from multiple cpus simultaneously.

I'll send you the updated patch in a separate email, so the changelog
and commit logs do not have this discussion.

--
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/