public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Cc: david.vrabel@citrix.com, imammedo@redhat.com, Ian.Campbell@eu.citrix.com
Subject: [GIT PULL] (xen) stable/bug.fixes for 3.1-rc5.
Date: Tue, 6 Sep 2011 12:10:46 -0400	[thread overview]
Message-ID: <20110906161046.GA5548@dumpdata.com> (raw)

Hey Linus,

Please git pull the following branch from my backup git server:

git pull git://oss.oracle.com/git/kwilk/xen.git stable/bug.fixes

It is based off git commit 60c5f08e154fd235056645e050f2cd5671b19125
Jeremy Fitzhardinge (1):
    xen/tracing: Fix tracing config option properly

Which you pulled in earlier (3.1-rc3?).

We got some ecstatic bug-fixes - one in particular has been in the tree since 2.6.27!
They are (in order of "oh-my-what-a-bug"):
 1). Don't enable the interrupts when a page fault has occurred - this ended up triggering
     when we were executing a IRQ handler and re-enabling the IRQ line!
 2). Respect the dom0_mem=max:X argument that the hypervisor can use to limit the amount
     of memory the initial Linux kernel would use. Without it, on largish (32GB>) the
     initial domain had tons of unused 'struct page' that were never going to be used.
 3). Lastly, print out a warning when the user uses specific Linux kernel parameters
     that we cannot handle ("nosmp" or "noapic").

The credit list is:

David Vrabel (1):
      xen: use maximum reservation to limit amount of usable RAM

Igor Mammedov (1):
      xen: x86_32: do not enable iterrupts when returning from exception in interrupt context

Konrad Rzeszutek Wilk (1):
      xen/smp: Warn user why they keel over - nosmp or noapic and what to use instead.

Diff stat:

 arch/x86/xen/setup.c      |   19 +++++++++++++++++++
 arch/x86/xen/smp.c        |   10 ++++++++++
 arch/x86/xen/xen-asm_32.S |    8 +++++---
 3 files changed, 34 insertions(+), 3 deletions(-)


                 reply	other threads:[~2011-09-06 16:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110906161046.GA5548@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=imammedo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox