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
| ||
|
Date: Wed, 21 Feb 2007 12:02:58 -0800 From: Jeremy Fitzhardinge <jeremy@...p.org> To: Christoph Lameter <clameter@....com> CC: Andi Kleen <ak@....de>, Zachary Amsden <zach@...are.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com, Chris Wright <chrisw@...s-sol.org>, Rusty Russell <rusty@...tcorp.com.au> Subject: Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface Christoph Lameter wrote: > And it seems that the hooks are not generic but bound to a particular > hypervisor. Should the Xen specific stuff not be in the binary blob? Xen has no "binary blob". It needs guests to cooperate with it by making hypercalls; all that code is in the Xen implementation of the paravirt_ops interface, which is just ordinary code which lives in the kernel sources. J - 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