similar to: [PATCH 2/5] Add subarch mmu queue flush hook

MMU code movement. Unfortunately, this one is a little bit more complicated than the rest. We have to override the default accessors that directly write to page table entries. Because of the 2/3-level PAE split in Linux, this turned out to be really ugly at first, but by allowing the sub-arch layer to override the definitions and keeping the native definitions in place, the code becomes much

MMU code movement. Unfortunately, this one is a little bit more complicated than the rest. We have to override the default accessors that directly write to page table entries. Because of the 2/3-level PAE split in Linux, this turned out to be really ugly at first, but by allowing the sub-arch layer to override the definitions and keeping the native definitions in place, the code becomes much

i386 Transparent paravirtualization subarch patch #5 This change encapsulates descriptor and task register management. Diffs against: 2.6.13-rc4-mm1 Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/include/asm-i386/desc.h =================================================================== --- linux-2.6.13.orig/include/asm-i386/desc.h 2005-08-08 17:31:59.000000000 -0700

i386 Transparent paravirtualization subarch patch #5 This change encapsulates descriptor and task register management. Diffs against: 2.6.13-rc4-mm1 Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/include/asm-i386/desc.h =================================================================== --- linux-2.6.13.orig/include/asm-i386/desc.h 2005-08-08 17:31:59.000000000 -0700

Implement lazy MMU update hooks which are SMP safe for both direct and shadow page tables. The idea is that PTE updates and page invalidations while in lazy mode can be batched into a single hypercall. We use this in VMI for shadow page table synchronization, and it is a win. It also can be used by PPC and for direct page tables on Xen. For SMP, the enter / leave must happen under protection

Ok, the use of "1 + " and subtraction of one for PAE PDPEs has confused many people now. Make it explicit what is going on and why anding with PAGE_MASK is a better idea to strip these bits. Signed-off-by: Zachary Amsden <zach@vmware.com> Depends-on: add-pgtable-allocation-notifiers Index: linux-2.6.13/arch/i386/mm/pgtable.c

Ok, the use of "1 + " and subtraction of one for PAE PDPEs has confused many people now. Make it explicit what is going on and why anding with PAGE_MASK is a better idea to strip these bits. Signed-off-by: Zachary Amsden <zach@vmware.com> Depends-on: add-pgtable-allocation-notifiers Index: linux-2.6.13/arch/i386/mm/pgtable.c

Looks like the subarch tree has been checked in. Does this mean 3.0.1 has been pushed out to include more? Or do we release 3.0.1 once the new tree is fully tested? Jun --- Intel Open Source Technology Center ---- From: xen-changelog-bounces@lists.xensource.com [mailto:xen-changelog-bounces@lists.xensource.com] On Behalf Of Xen patchbot -unstable Sent: Monday, January 30, 2006 4:08 PM To:

Add a helper function to convert an arbitrary mapped virtual address to a physical frame number. Adapted from code by Chris Wright, added support for large pages. Because of the placement, this needs to be a macro; pgd_offset_k requires init_mm to be defined, and getting the include files right seemed more complicated than a macroized implementation. A more proper location would be in

Add a helper function to convert an arbitrary mapped virtual address to a physical frame number. Adapted from code by Chris Wright, added support for large pages. Because of the placement, this needs to be a macro; pgd_offset_k requires init_mm to be defined, and getting the include files right seemed more complicated than a macroized implementation. A more proper location would be in

> On Tue, 2006-07-18 at 00:00 -0700, Chris Wright wrote: > > plain text document attachment (i386-setup) > > Implement the start-of-day subarchitecture setup hooks for booting on > > Xen. Add subarch macros for determining loader type and initrd > > location. > > > diff -r a5848bce3730 arch/i386/kernel/setup.c > > --- a/arch/i386/kernel/setup.c Thu Jun 22

A brave attempt to be rid of an unnecessary subarch hook and clean things up a bit. First, all subarches use IRQ-2 as a cascade IRQ. So do that in the common code. Second, there is no need for a pre_intr_init_hook. We can set up the interrupt gates at any time, as this doesn't touch any real hardware, just the processor gates. Now the subarch code still needs to setup the appropriate irq

A brave attempt to be rid of an unnecessary subarch hook and clean things up a bit. First, all subarches use IRQ-2 as a cascade IRQ. So do that in the common code. Second, there is no need for a pre_intr_init_hook. We can set up the interrupt gates at any time, as this doesn't touch any real hardware, just the processor gates. Now the subarch code still needs to setup the appropriate irq

I''m sure everyone has seen the drop of VMI patches for Linux at this point, but just in case, the link is included below. I''ve read this version of the VMI spec and have made my way through most of the patches. While I wasn''t really that impressed with the first spec wrt Xen, the second version seems to be much more palatable. Specifically, the code inlining and

Add Xen accessors for LDT updates. Todo: Bring back return values from write_ldt_entry. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/arch/i386/kernel/ldt.c =================================================================== --- linux-2.6.13.orig/arch/i386/kernel/ldt.c 2005-08-08 21:13:56.000000000 -0700 +++ linux-2.6.13/arch/i386/kernel/ldt.c 2005-08-08

Add Xen accessors for LDT updates. Todo: Bring back return values from write_ldt_entry. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/arch/i386/kernel/ldt.c =================================================================== --- linux-2.6.13.orig/arch/i386/kernel/ldt.c 2005-08-08 21:13:56.000000000 -0700 +++ linux-2.6.13/arch/i386/kernel/ldt.c 2005-08-08

This most curious patch allows the fixmap on i386 to be unfixed. The = result is that we can create a dynamically sizable hole at the top of = kernel linear address space. I know at least some virtualization = developers are interested in being able to achieve this to achieve = run-time sizing of a hole in which a hypervisor can live, or at least to = test out the performance

This most curious patch allows the fixmap on i386 to be unfixed. The = result is that we can create a dynamically sizable hole at the top of = kernel linear address space. I know at least some virtualization = developers are interested in being able to achieve this to achieve = run-time sizing of a hole in which a hypervisor can live, or at least to = test out the performance

Create a configurable hole in the linear address space at the top of memory. A more advanced interface is needed to negotiate how much space the hypervisor is allowed to steal, but in the end, it seems most likely that a fixed constant size will be chosen for the compiled kernel, potentially propagated to an information page used by paravirtual initialization to determine interface compatibility.

Create a configurable hole in the linear address space at the top of memory. A more advanced interface is needed to negotiate how much space the hypervisor is allowed to steal, but in the end, it seems most likely that a fixed constant size will be chosen for the compiled kernel, potentially propagated to an information page used by paravirtual initialization to determine interface compatibility.