All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: preparing for 4.2.2 and 4.1.5
Date: Fri, 8 Mar 2013 12:01:34 +0000	[thread overview]
Message-ID: <5139D31E.8010005@citrix.com> (raw)
In-Reply-To: <512E3E9902000078000C19F7@nat28.tlf.novell.com>

On 27/02/13 16:12, Jan Beulich wrote:
> Aiming at a release towards the end of March, I'd like to cut RC1-s
> at the beginning of next week.
>
> Please indicate any bug fixes that so far may have been missed
> in the backports already done. Quite a few fixes are currently
> stuck in master's staging branch - these don't need to be named
> explicitly, I'm already planning to pull over the hypervisor ones
> as soon as they get out of staging (and I'm sure Ian is planning
> the same - if applicable at all - for the tools side).
>
> Ian - one thing I think is still open for 4.1.5 is the xz kernel
> decompression support that was explicitly requested on the list.
> Can this be expected to go in for RC1?
>
> Jan

Following the inclusion of 3c4cd2c6a0e1795c837dd0cfb15db08a5d6694eb
"x86/mm: Take the p2m lock even in shadow mode." into 4.2, can I request
7f05d3ff7692574f40d0b337d767a216f347dcdb "x86/mm: avoid locked lookups
in shadow emulation" which fixes the performance regression introduced
by the former

I have had these running in our testing for several weeks now without
incident.

~Andrew

>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2013-03-08 12:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 16:12 preparing for 4.2.2 and 4.1.5 Jan Beulich
2013-02-27 18:44 ` Alex Bligh
2013-02-28  7:31   ` Jan Beulich
2013-02-28  9:21     ` Alex Bligh
2013-02-28  9:32       ` Jan Beulich
2013-02-28 12:40         ` Stefano Stabellini
2013-02-28 18:31           ` Alex Bligh
2013-02-28 10:18 ` M A Young
2013-02-28 11:49   ` Ian Jackson
2013-02-28 15:31 ` Egger Christoph
2013-02-28 15:44   ` Jan Beulich
2013-03-01 15:23 ` Andrew Cooper
2013-03-01 15:39   ` Jan Beulich
2013-03-06 18:14 ` Andrew Cooper
2013-03-08  9:57   ` Jan Beulich
2013-03-08 11:18     ` Andrew Cooper
2013-03-08 12:01 ` Andrew Cooper [this message]
2013-03-08 12:53   ` Jan Beulich
2013-03-08 13:01 ` Jan Beulich
2013-03-10 22:53 ` Marek Marczykowski
2013-03-12 11:55   ` Ian Campbell
2013-03-12 11:57     ` Marek Marczykowski
2013-03-11 11:36 ` Alex Bligh
2013-03-11 13:35   ` Jan Beulich
2013-03-19  7:50 ` preparing for 4.2.2 and 4.1.5 / libxl blktap2 patch Pasi Kärkkäinen
2013-03-27  9:52   ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5139D31E.8010005@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.