Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422930AbXBUUDJ (ORCPT ); Wed, 21 Feb 2007 15:03:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423014AbXBUUDJ (ORCPT ); Wed, 21 Feb 2007 15:03:09 -0500 Received: from gw.goop.org ([64.81.55.164]:49602 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422930AbXBUUDE (ORCPT ); Wed, 21 Feb 2007 15:03:04 -0500 Message-ID: <45DCA572.9090704@goop.org> Date: Wed, 21 Feb 2007 12:02:58 -0800 From: Jeremy Fitzhardinge User-Agent: Thunderbird 1.5.0.9 (X11/20070212) MIME-Version: 1.0 To: Christoph Lameter CC: Andi Kleen , Zachary Amsden , Andrew Morton , linux-kernel@vger.kernel.org, virtualization@lists.osdl.org, xen-devel@lists.xensource.com, Chris Wright , Rusty Russell Subject: Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface References: <20070216022449.739760547@goop.org> <45D61C74.2000601@vmware.com> <45D626BB.20007@vmware.com> <20070217135112.GA15102@muc.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 645 Lines: 16 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/