From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: [GIT PULL] for-2.6.32/bug-fixes
Date: Thu, 27 Jan 2011 13:52:39 -0500 [thread overview]
Message-ID: <20110127185239.GC27853@dumpdata.com> (raw)
Jeremy,
Please pull in your stable/2.6.32.x the following git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git for-2.6.32/bug-fixes
which has patches since git commit 75cc13f5aa29b4f3227d269ca165dfa8937c94fe
Jeremy Fitzhardinge (1):
Merge commit 'v2.6.32.27' into xen/next-2.6.32
It has the bootup fixes found in 2.6.37/2.6.38 tree back-ported to 2.6.32.
I've done the normal boot-up tests on Intel and AMD hardware and while
they are not introducing any regressions - the 2.6.32.x suffers from some
other types of bugs (if I use dom0_mem it ends up OOM-ing).
Stefan Bader (1):
xen/p2m: Mark INVALID_P2M_ENTRY the mfn_list past max_pfn.
Stefano Stabellini (1):
xen/e820: Guard against E820_RAM not having page-aligned size or start.
arch/x86/xen/mmu.c | 12 ++++++++++++
arch/x86/xen/setup.c | 7 ++++++-
2 files changed, 18 insertions(+), 1 deletions(-)
next reply other threads:[~2011-01-27 18:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 18:52 Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-16 20:35 [GIT PULL] for-2.6.32/bug-fixes Konrad Rzeszutek Wilk
2011-05-17 9:48 ` Jan Beulich
2011-05-17 10:07 ` Jan Beulich
2011-05-17 14:16 ` Konrad Rzeszutek Wilk
2011-05-17 15:06 ` Jan Beulich
2011-05-17 15:57 ` Konrad Rzeszutek Wilk
2011-05-17 16:24 ` Jan Beulich
2011-05-17 16:43 ` Konrad Rzeszutek Wilk
2011-05-18 6:22 Jan Beulich
2011-05-18 13:24 ` Konrad Rzeszutek Wilk
2011-05-18 14:31 ` Jan Beulich
2011-05-18 14:56 ` Konrad Rzeszutek Wilk
2011-05-18 15:03 ` Jan Beulich
2011-05-18 15:13 ` Konrad Rzeszutek Wilk
2011-05-18 15:23 ` Jan Beulich
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=20110127185239.GC27853@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.