[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071015215406.GA1588@kroah.com>
Date: Mon, 15 Oct 2007 14:54:06 -0700
From: Greg KH <greg@...ah.com>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
xen-devel@...ts.xensource.com, LKML <linux-kernel@...r.kernel.org>,
Andi Kleen <ak@...e.de>, Chris Wright <chrisw@...s-sol.org>,
virtualization@...ts.osdl.org,
Andrew Morton <akpm@...ux-foundation.org>,
Keir Fraser <keir@...source.com>,
Stable Kernel <stable@...nel.org>
Subject: Re: [stable] [PATCH 00/12] xen/paravirt_ops patches for 2.6.24
On Mon, Oct 15, 2007 at 01:48:40PM -0700, Jeremy Fitzhardinge wrote:
> Hi Linus,
>
> Here's a set of patches to update paravirt_ops and Xen for 2.6.24
>
> A quick overview of the patchset:
>
> paravirt_ops:
> Remove the monolithic paravirt_ops structure, and replace it with
> smaller structures of related functions. Also, clean up the handling
> of lazy mode to make it easier to implement.
>
> x86/mm/init.c: remove a chunk of dead code
>
> Xen:
> - remove duplicate includes
> - yield if the target vcpu of an IPI is not currently running
> - add post-batch callbacks for multicalls [*]
> - deal with unpinning pagetables when another vcpu still [*]
> has a cr3 reference
> - deal with split ptelocks by pinning each pte page
> separately under lock
> - determine the kernel/hypervisor address split dynamically
> - use the right arg structure for register_vcpu_info [*]
> - add extra debugging output for failed multicalls
>
> XFS:
> - eagerly unmap vmapped areas to avoid confict with Xen
>
> [*] bugfix needed for 2.6.23. I've also cc:d them to stable@...nel.org
Yeah, but you cc:ed all 12 patches to stable@. The majority of which we
don't want to take, right? Which specific ones should stable@ care
about?
thanks,
greg k-h
-
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