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>] [day] [month] [year] [list]
Message-ID: <8763pt8dmz.fsf@mid.deneb.enyo.de>
Date:	Fri, 22 Aug 2008 13:58:44 +0200
From:	Florian Weimer <fw@...eb.enyo.de>
To:	linux-kernel@...r.kernel.org
Subject: Disabling hypervisor capability at boot

For various reasons, it might be desirable to disable hypervisor
capability during the system boot-up process.

It has been suggested to do this in user space.  While I think it's fine
to trigger it from user space (in the sense that an additional boot
parameter makes no difference), I'm not convinced that the actual code
to disable the hypervisor capability should reside in user space.  What
about architectures where this step can only performed from kernel mode?
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ