| 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: <53BD311B.2050404@citrix.com> Date: Wed, 9 Jul 2014 13:10:03 +0100 From: David Vrabel <david.vrabel@...rix.com> To: <konrad@...nel.org>, <xen-devel@...ts.xenproject.org>, <david.vrabel@...rix.com>, <boris.ostrovsky@...cle.com>, <linux-kernel@...r.kernel.org> Subject: Re: [Xen-devel] [PATCH v2] xen: Introduce 'xen_nopv' to disable PV extensions for HVM guests. On 08/07/14 21:52, konrad@...nel.org wrote: > From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> > > By default when CONFIG_XEN and CONFIG_XEN_PVHVM kernels are > run, they will enable the PV extensions (drivers, interrupts, timers, > etc) - which is perfect. If it's "perfect" what's this option for? ;) I think you mean to say "which is the best option for the majority of use cases". > However, in some cases (kexec not fully wokring, benchmarking) > we want to disable Xen PV extensions. As such introduce the > 'xen_nopv' parameter that will do it. "working" I'm unconvinced about the utility of this option. The resulting kernel will go like molasses and I'm not sure what the use of being any to benchmark a configuration no one will use in practice. But it's a small patch so Reviewed-by: David Vrabel <david.vrabel@...rix.com> David -- 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