| 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
| ||
|
Message-ID: <1291819684.28378.70.camel@laptop> Date: Wed, 08 Dec 2010 15:48:04 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Vivek Goyal <vgoyal@...hat.com> Cc: Don Zickus <dzickus@...hat.com>, "Eric W. Biederman" <ebiederm@...ssion.com>, Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>, Jason Wessel <jason.wessel@...driver.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Haren Myneni <hbabu@...ibm.com> Subject: Re: perf hw in kexeced kernel broken in tip On Wed, 2010-12-08 at 09:42 -0500, Vivek Goyal wrote: > > Either driver itself can detect that device is in inconsistent state and > reset it otherwise we also pass a command line parameter "reset_devices" to > second kernel to explicitly tell kernel that devices might be in bad state, > reset these during initialization. If we want to use these perf counters in > kdump kernel, we shall have to do something similar. Right, so I'm perfectly fine with leaving the kdump kernel broken for now and if people really do need hardware events we can try and reset the hardware when we find that reset_devices command line parameter. Not sure how that interacts with these broken BIOSes, but its kdump so its mostly broken by design anyway ;-) -- 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/
Powered by blists - more mailing lists