All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stable Kernel <stable@kernel.org>
Subject: [GIT PULL] Xen bugfixes
Date: Thu, 03 Dec 2009 15:46:11 -0800	[thread overview]
Message-ID: <4B184DC3.5020509@goop.org> (raw)

Hi Linus,

Please pull this set of bugfixes, mostly to do with Xen domain 
save/restore.  They're all stable material as well.

(Note, if you pull quickly from git.kernel.org, you may pick up some 
more changes that I rolled back pending maintainer approval; pulling 
from master might be safer.)

Thanks,
     J

The following changes since commit 82d6469916c6fcfa345636a49004c9d1753905d1:
   Jeremy Fitzhardinge (1):
         xen: mask extended topology info in cpuid

are available in the git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git bugfix

Ian Campbell (8):
       xen: re-register runstate area earlier on resume.
       xen: correctly restore pfn_to_mfn_list_list after resume
       xen: register timer interrupt with IRQF_TIMER
       xen: register runstate on secondary CPUs
       xen: call clock resume notifier on all CPUs
       xen: don't leak IRQs over suspend/resume.
       xen: improve error handling in do_suspend.
       xen: explicitly create/destroy stop_machine workqueues outside suspend/resume region.

Jeremy Fitzhardinge (5):
       xen/xenbus: make DEVICE_ATTR()s static
       xen: restore runstate_info even if !have_vcpu_info_placement
       xen: register runstate info for boot CPU early
       xen: don't call dpm_resume_noirq() with interrupts disabled.
       xen: use iret for return from 64b kernel to 32b usermode

Paolo Bonzini (3):
       xen: fix is_disconnected_device/exists_disconnected_device
       xen: improvement to wait_for_devices()
       xen: wait up to 5 minutes for device connetion

  arch/x86/xen/enlighten.c          |   27 ++++++++++----------
  arch/x86/xen/mmu.c                |    2 +-
  arch/x86/xen/smp.c                |    1 +
  arch/x86/xen/suspend.c            |   17 ++++++++++++-
  arch/x86/xen/time.c               |    7 ++---
  arch/x86/xen/xen-asm_64.S         |    4 +-
  arch/x86/xen/xen-ops.h            |    2 +
  drivers/xen/events.c              |    3 ++
  drivers/xen/manage.c              |   37 ++++++++++++++++++----------
  drivers/xen/xenbus/xenbus_probe.c |   48 ++++++++++++++++++++++++------------
  10 files changed, 98 insertions(+), 50 deletions(-)



             reply	other threads:[~2009-12-03 23:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 23:46 Jeremy Fitzhardinge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-09 23:51 [GIT PULL] Xen bugfixes Jeremy Fitzhardinge
2009-09-09 23:51 ` Jeremy Fitzhardinge
2009-09-10  5:16 ` Ingo Molnar
2009-09-10  5:16   ` Ingo Molnar
2009-09-10 17:16   ` Jeremy Fitzhardinge
2009-09-10 17:16     ` Jeremy Fitzhardinge
2009-09-10 17:26     ` Ingo Molnar
2009-09-10 17:26       ` Ingo Molnar
2009-09-10 19:02       ` Jeremy Fitzhardinge
2009-09-10 19:02         ` Jeremy Fitzhardinge

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=4B184DC3.5020509@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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.