linux-kernel - Re: [PATCH 04/15] x86,kgdb: Individual register get/set for x86

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: <4C53605A.8050603@zytor.com>
Date:	Fri, 30 Jul 2010 16:29:30 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jason Wessel <jason.wessel@...driver.com>
CC:	linux-kernel@...r.kernel.org, kgdb-bugreport@...ts.sourceforge.net,
	mingo@...e.hu, Ingo Molnar <mingo@...hat.com>, x86@...nel.org
Subject: Re: [PATCH 04/15] x86,kgdb: Individual register get/set for x86

On 07/30/2010 12:17 PM, Jason Wessel wrote:
> Implement the ability to individually get and set registers for kdb
> and kgdb for x86.
> 
> Signed-off-by: Jason Wessel <jason.wessel@...driver.com>
> CC: Ingo Molnar <mingo@...hat.com>
> CC: H. Peter Anvin <hpa@...or.com>
> CC: x86@...nel.org

Looks reasonable to me (GDB_PS drove me nuts at first, thinking it was a
typo for SP; I gather that like GDB_PC it's a gratuitous renaming of x86
registers to match some other CPU convention, but that's presumably a
GDB issue and not a kernel one.)

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