All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [GIT PULL stable-2.6.32.x] PV on HVM fixes
Date: Mon, 14 Mar 2011 16:09:49 -0700	[thread overview]
Message-ID: <4D7EA03D.5020802@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1103111605220.2968@kaball-desktop>

On 03/11/2011 10:56 AM, Stefano Stabellini wrote:
> Hi Jeremy,
> I backported the branch I have in linux-next plus some older PV on HVM
> fixes to stable-2.6.32.x. 
> Please pull:
>
> git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm

That branch doesn't exist there, but I merged "stable-2.6.32.x-pvhvm". 
Is that OK?

    J

> Ian Campbell (11):
>       xen: do not respond to unknown xenstore control requests
>       xen: use new schedop interface for suspend
>       xen: switch to new schedop hypercall by default.
>       xen: suspend: use HYPERVISOR_suspend for PVHVM case instead of open coding
>       xen: suspend: refactor cancellation flag into a structure
>       xen: suspend: pass extra hypercall argument via suspend_info struct
>       xen: suspend: add "arch" to pre/post suspend hooks
>       xen: suspend: refactor non-arch specific pre/post suspend hooks
>       xen: suspend: move arch specific pre/post suspend hooks into generic hooks
>       xen: suspend: pull pre/post suspend hooks out into suspend_info
>       xen: suspend: remove xen_hvm_suspend
>
> Stefano Stabellini (9):
>       xen: do not try to allocate the callback vector again at restore time
>       xen: do not set xenstored_ready before xenbus_probe on hvm
>       xen: do not initialize PV timers on HVM if !xen_have_vector_callback
>       xen: no need to delay xen_setup_shutdown_event for hvm guests anymore
>       xen: do not use xen_info on HVM, set pv_info name to "Xen HVM"
>       xen-blkfront: handle Xen major numbers other than XENVBD
>       xen: make the ballon driver work for hvm domains
>       xen: PV on HVM: support PV spinlocks and IPIs
>       xen: fix compile issue if XEN is enabled but XEN_PVHVM is disabled
>
>  arch/ia64/xen/suspend.c              |    9 +--
>  arch/x86/include/asm/xen/hypercall.h |   15 +++-
>  arch/x86/xen/enlighten.c             |    6 +-
>  arch/x86/xen/smp.c                   |   38 +++++++++
>  arch/x86/xen/suspend.c               |    8 +-
>  arch/x86/xen/time.c                  |    5 +-
>  arch/x86/xen/xen-ops.h               |    2 +
>  drivers/block/xen-blkfront.c         |    7 +-
>  drivers/xen/balloon.c                |   14 ++-
>  drivers/xen/events.c                 |    4 +-
>  drivers/xen/manage.c                 |  142 ++++++++++++++++++++-------------
>  drivers/xen/platform-pci.c           |    3 -
>  drivers/xen/xenbus/xenbus_probe.c    |    8 ++-
>  include/xen/interface/xen.h          |    4 +-
>  include/xen/xen-ops.h                |    6 +-
>  15 files changed, 177 insertions(+), 94 deletions(-)
>
> Cheers,
>
> Stefano
>

  reply	other threads:[~2011-03-14 23:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 18:56 [GIT PULL stable-2.6.32.x] PV on HVM fixes Stefano Stabellini
2011-03-14 23:09 ` Jeremy Fitzhardinge [this message]
2011-03-15 11:30   ` Stefano Stabellini

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=4D7EA03D.5020802@goop.org \
    --to=jeremy@goop.org \
    --cc=stefano.stabellini@eu.citrix.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.