From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface Date: Thu, 15 Feb 2007 23:20:46 -0800 Message-ID: <45D55B4E.4000008@goop.org> References: <20070216022449.739760547@goop.org> <20070215225932.11a1b43e.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070215225932.11a1b43e.akpm@linux-foundation.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andrew Morton Cc: Zachary Amsden , xen-devel@lists.xensource.com, virtualization@lists.osdl.org, linux-kernel@vger.kernel.org, Chris Wright , Andi Kleen List-Id: virtualization@lists.linuxfoundation.org Andrew Morton wrote: > On Thu, 15 Feb 2007 18:24:49 -0800 Jeremy Fitzhardinge wrote: > > >> This patch series implements the Linux Xen guest in terms of the >> paravirt-ops interface. >> > > The whole patchset exports 67 symbols to modules. How come? > > Are they all needed? Yep, pretty much. They're all generally to do with Xen's virtual device model, and are needed by modular frontend/backed drivers. This series only includes the basic block and network frontend devices, but there are more waiting in the wings. The breakdown, roughly, is: * event channel management * pseudophysical <-> machine addresses * grant-table management * xenbus, which includes o which has a filesystem-like namespace o the means to monitor changes in objects in the namespace o shared resource management o suspend/resume J