linux-kernel - Re: [RFC Patch 0/9] Hardware Breakpoint interfaces

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:	Tue, 07 Oct 2008 14:29:05 +0200
From:	Avi Kivity <avi@...hat.com>
To:	prasad@...ux.vnet.ibm.com
CC:	linux-kernel@...r.kernel.org,
	Alan Stern <stern@...land.harvard.edu>,
	Roland McGrath <roland@...hat.com>, akpm@...ux-foundation.org,
	mingo@...e.hu, jason.wessel@...driver.com,
	richardj_moore@...ibm.com
Subject: Re: [RFC Patch 0/9] Hardware Breakpoint interfaces

K.Prasad wrote:
> - Enable KGDB and KVM to use the register_kernel_hw_breakpoint()
>   interface for their HW Breakpoint usage, in the absence of which
>   they will be broken during simultaneous use.
>   

KVM conceptually isn't a kernel use of the debug registers.  KVM 
modifies the debug registers while the guest is running, and restores 
them after the guest returns.

Right now, as an optimization, KVM defers restoring the debug registers 
until after the next context switch out of the kvm task, or until the 
next exit to userspace (whichever comes earlier); we should change this 
to avoid the deferral if kernel breakpoints are in effect.  This will 
allow simultaneous use of KVM breakpoints and kernel breakpoints.

-- 
error compiling committee.c: too many arguments to function

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