[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1235786365-17744-1-git-send-email-jeremy@goop.org>
Date: Fri, 27 Feb 2009 17:59:06 -0800
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Xen-devel <xen-devel@...ts.xensource.com>
Subject: [PATCH] xen: core dom0 support
Hi,
This series implements the core parts of Xen dom0 support; that is, just
enough to get the kernel started when booted by Xen as a dom0 kernel.
The Xen dom0 kernel runs as a normal paravirtualized Xen kernel, but
it also has the additional responsibilty for managing all the machine's
hardware, as Xen itself has almost no internal driver support (it barely
even knows about PCI).
This series includes:
- setting up a Xen hvc console
- initializing Xenbus
- enabling IO permissions for the kernel
- MTRR setup hooks
- Use _PAGE_IOMAP to allow direct hardware mappings
- add a paravirt-ops for page_is_ram, to allow Xen to exclude granted pages
- enable the use of a vga console
Not included in this series is the hooks into apic setup; that's next.
This may be pulled from:
The following changes since commit cc2f3b455c8efa01c66b8e66df8aad1da9310901:
Ingo Molnar (1):
Merge branch 'sched/urgent'
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git push/xen/dom0/core
Ian Campbell (4):
xen: disable PAT
xen/dom0: Use host E820 map
xen: implement XENMEM_machphys_mapping
xen: clear reserved bits in l3 entries given in the initial pagetables
Jeremy Fitzhardinge (6):
xen dom0: Make hvc_xen console work for dom0.
xen-dom0: only selectively disable cpu features
xen/dom0: use _PAGE_IOMAP in ioremap to do machine mappings
paravirt/xen: add pvop for page_is_ram
xen/dom0: add XEN_DOM0 config option
xen: allow enable use of VGA console on dom0
Juan Quintela (2):
xen dom0: Initialize xenbus for dom0.
xen dom0: Set up basic IO permissions for dom0.
Mark McLoughlin (5):
xen mtrr: Use specific cpu_has_foo macros instead of generic cpu_has()
xen mtrr: Kill some unneccessary includes
xen mtrr: Use generic_validate_add_page()
xen mtrr: Implement xen_get_free_region()
xen mtrr: Add xen_{get,set}_mtrr() implementations
Stephen Tweedie (2):
xen dom0: Add support for the platform_ops hypercall
xen mtrr: Add mtrr_ops support for Xen mtrr
arch/x86/include/asm/page.h | 9 +-
arch/x86/include/asm/paravirt.h | 7 +
arch/x86/include/asm/pat.h | 5 +
arch/x86/include/asm/xen/hypercall.h | 8 +
arch/x86/include/asm/xen/interface.h | 6 +-
arch/x86/include/asm/xen/interface_32.h | 5 +
arch/x86/include/asm/xen/interface_64.h | 13 +--
arch/x86/include/asm/xen/page.h | 15 +--
arch/x86/kernel/cpu/mtrr/Makefile | 1 +
arch/x86/kernel/cpu/mtrr/amd.c | 1 +
arch/x86/kernel/cpu/mtrr/centaur.c | 1 +
arch/x86/kernel/cpu/mtrr/cyrix.c | 1 +
arch/x86/kernel/cpu/mtrr/generic.c | 1 +
arch/x86/kernel/cpu/mtrr/main.c | 11 +-
arch/x86/kernel/cpu/mtrr/mtrr.h | 7 +
arch/x86/kernel/cpu/mtrr/xen.c | 120 ++++++++++++++++
arch/x86/kernel/paravirt.c | 1 +
arch/x86/mm/ioremap.c | 2 +-
arch/x86/mm/pat.c | 5 -
arch/x86/xen/Kconfig | 26 ++++
arch/x86/xen/Makefile | 3 +-
arch/x86/xen/enlighten.c | 58 ++++++--
arch/x86/xen/mmu.c | 135 ++++++++++++++++++-
arch/x86/xen/setup.c | 51 ++++++-
arch/x86/xen/vga.c | 65 +++++++++
arch/x86/xen/xen-ops.h | 12 ++
drivers/char/hvc_xen.c | 101 +++++++++-----
drivers/xen/events.c | 2 +-
drivers/xen/xenbus/xenbus_probe.c | 30 ++++-
include/xen/events.h | 2 +
include/xen/interface/memory.h | 42 ++++++
include/xen/interface/platform.h | 232 +++++++++++++++++++++++++++++++
include/xen/interface/xen.h | 41 ++++++
33 files changed, 931 insertions(+), 88 deletions(-)
create mode 100644 arch/x86/kernel/cpu/mtrr/xen.c
create mode 100644 arch/x86/xen/vga.c
create mode 100644 include/xen/interface/platform.h
Thanks,
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