| Date | Thu, 15 Feb 2007 23:20:46 -0800 | From | Jeremy Fitzhardinge <> | Subject | Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface |
| |
Andrew Morton wrote: > On Thu, 15 Feb 2007 18:24:49 -0800 Jeremy Fitzhardinge <jeremy@goop.org> 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 - 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/
|