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  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:	Mon, 5 Jan 2015 10:35:04 +0000
From:	David Vrabel <>
To:	Jan Beulich <>,
	Boris Ostrovsky <>,
	Konrad Rzeszutek Wilk <>
CC:	xen-devel <>,
Subject: Re: xen/x86: properly retrieve NMI reason

On 19/12/14 16:16, Jan Beulich wrote:
> Using the native code here can't work properly, as the hypervisor would
> normally have cleared the two reason bits by the time Dom0 gets to see
> the NMI (if passed to it at all). There's a shared info field for this,
> and there's an existing hook to use - just fit the two together. Note
> that the hook can (and should) be used irrespective of whether being in
> Dom0, as accessing port 0x61 in a DomU would be even worse, while the
> shared info field would just hold zero all the time.
> Signed-off-by: Jan Beulich <>

This doesn't build.

In file included from
/local/davidvr/work/ warning:
data definition has no type or storage class [enabled by default]
/local/davidvr/work/ error:
type defaults to ‘int’ in declaration of ‘DEFINE_XEN_GUEST_HANDLE’
cc1: some warnings being treated as errors

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists