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: <1205248016.27299.110.camel@perihelion>
Date:	Tue, 11 Mar 2008 11:06:56 -0400
From:	Jon Masters <jonathan@...masters.org>
To:	Rik van Riel <riel@...hat.com>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, lwoodman@...hat.com
Subject: Re: [PATCH] sysrq show-all-cpus


On Tue, 2008-03-11 at 10:07 -0400, Rik van Riel wrote:
> On Tue, 11 Mar 2008 03:18:24 -0400
> Jon Masters <jonathan@...masters.org> wrote:
> 
> > On Mon, 2008-03-10 at 14:03 -0400, Rik van Riel wrote:
> > > SysRQ-P is not always useful on SMP systems, since it usually ends up showing the
> > > backtrace of a CPU that is doing just fine, instead of the backtrace of the CPU
> > > that is having problems.
> > > 
> > > This patch adds SysRQ show-all-cpus(L), which shows the backtrace of every active
> > > CPU in the system.  It skips idle CPUs because some SMP systems are just too large
> > > and we already know what the backtrace of the idle task looks like.
> > >  
> > > Signed-off-by: Rik van Riel <riel@...hat.com>
> > 
> > Why not have it just print the local CPU on non-SMP anyway?
> 
> Sysrq p already does exactly that.

That's my point. I understand why there's a new command, because it is
different from 'p', but probably worth doing something on non-SMP too.

Jon.


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