WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: 2.6.30 Xen merge plan (what's in xen.git)

To: Ingo Molnar <mingo@xxxxxxx>
Subject: [Xen-devel] Re: 2.6.30 Xen merge plan (what's in xen.git)
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 24 Mar 2009 11:08:40 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Dave Airlie <airlied@xxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 24 Mar 2009 11:09:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090324174859.GB31117@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <49C915A3.3020809@xxxxxxxx> <20090324174859.GB31117@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (X11/20090320)
Ingo Molnar wrote:
Branches which mostly or entirely Xen (only trivial non-Xen changes):

push2/xen/core

   Updates to existing Xen support, features, optimisations, etc.

push2/xen/control

   A set of usermode interfaces for Xen (/sys/hypervisor, /dev/evtchn,
   updates to xenbus and xenfs)

Will take a look.

Thanks.

push2/xen/dom0/core

   Core set of changes to add Xen dom0 functionality.  (Mostly
   Xen-only, but adds a new Xen mtrr driver.)

I suspect this makes limited sense without the arch dom0 changes so they should go with this bucket:

Yes, you wouldn't get much beyond some console messages and a crash without the rest.

Branches with non-trivial non-Xen changes:

push2/x86/paravirt

   Allow preemption while doing a lazy mmu update.

That's probably OK, just a bit late. If Thomas signs off on them then i guess it might be OK later in the window - he's the one who was struggling with paravirt lazy mmu fallout in the past. Thomas?

I've posted those patches several times over the last month. I needed to add a preempt_disable/enable pair in .29 to apply_to_page_range as a bugfix, which PeterZ, NickP and AKPM were not particularly happy about. This is the proper fix.

That said, they're not essential to the rest of the changes, and it would be fairly simple to drop them out (it would be a matter of clearing up some conflicts; no functional interactions).

push2/xen/dom0/apic

   Changes to hook the Xen dom0 apic model into the standard platform
   apic code.  HPA reviewed and OKed this.

push2/xen/dom0/pci

   Add a Xen pci driver and dma_ops implementations.  Small changes to
   x86 pci+swiotlb code to add some function calls.

push2/xen/dom0/agp

   Change the AGP driver to allocate its memory using the
   pci_alloc_coherent to get guaranteed physically contiguous memory,
   and use proper phys<->bus functions so that Xen's pseudo-phys <->
   machine mappings are handled properly.

hpa wanted dom0 changes in some cleaner fashion - he knows the details. (he'll be back in a few days)

When I spoke to him last week about this he said he was OK with it. He didn't make any specific (or even general) objections. Do you know which subsystem he was referring to?

   J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel