| 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: <1634884154.20090603004438@eikelenboom.it> Date: Wed, 3 Jun 2009 00:44:38 +0200 From: Sander Eikelenboom <linux@...elenboom.it> To: linux-kernel@...r.kernel.org Subject: Re: Xen is a feature So the conclusion would be that for inclusion in mainline: -The xen dom0 interface should be clean, and the code self contained -Backwards compatibility of the hypervisor is no argument to include anything in mainline (and if desired, should be realised in the hypervisor by (temporarily) supporting the old abi for the current xen specific kernels and one for the mainline kernel, and thus placing the maintenance burden of that desire on Xen and not the Kernel) -- Sander -- 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