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:	Fri, 21 Mar 2014 14:41:47 -0700
From:	"H. Peter Anvin" <>
To:	Andi Kleen <>
CC:	Peter Wu <>,
	Peter Zijlstra <>,
	Ingo Molnar <>,
Subject: Re: GPF in intel_pmu_lbr_reset() with qemu -cpu host

On 03/21/2014 02:37 PM, Andi Kleen wrote:
> On Fri, Mar 21, 2014 at 01:46:04PM -0700, H. Peter Anvin wrote:
>> Not really.  That is equally braindamaged.  The problem is that KVM is telling the host that our is something it simply cannot be.
> Well it has to pick something. It's unlikely it will ever implement 100% of that particular CPU.
> 0 is the best you can get in many cases.
> Also I thought Xen did return 0.

That's why at least to some extent The Right Thing is not to try to
pretend to be a CPU you don't even know how to emulate.

But again, that has its own issues, too, mostly with userspace
optimization, and making the Linux code more resilient wouldn't hurt.
In that sense #GP(0) is *much* better than 0: it unambiguously gives an
error to work with.

However, labeling it a bug in Linux is silly.


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