linux-kernel - Re: Implement Functions in boot.c

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>] [day] [month] [year] [list]

Date:	Wed, 07 Jan 2015 12:31:59 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	nick <xerofoify@...il.com>
Cc:	x86@...nel.org, ak@...ux.intel.com, JBeulich@...e.com,
	lguest@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: Implement Functions in boot.c

nick <xerofoify@...il.com> writes:
> Greetings Rusty,
> I am wondering why we haven't implementing the below functions:
>  /* Let's just say, I wouldn't do debugging under a Guest. */
>  static unsigned long lguest_get_debugreg(int regno)
> {
>          /* FIXME: Implement */
>          return 0;
> }
>
>  static void lguest_set_debugreg(int regno, unsigned long value)
> {
>          /* FIXME: Implement */
> }
> Seems to me that this are needed for various areas in the lguest subsystem and should
> be implemented for debugging ease of use in the lguest subsystem.

Well, normal use of gdb works.  It can't use hardware watchpoints,
though.

To fix this, hypercalls would have to be added to manipulate the debug
registers, and these registers would have to be saved and restored in
the world switcher code.

Patches welcome!
Rusty.
--
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/