From: Avi Kivity <avi@redhat.com>
To: Scott Wood <scottwood@freescale.com>, Alexander Graf <agraf@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [GIT PULL] KVM updates for the 2.6.37 merge window
Date: Mon, 25 Oct 2010 18:59:16 +0200 [thread overview]
Message-ID: <4CC5B764.5030007@redhat.com> (raw)
In-Reply-To: <20101025114924.6c05160c@udp111988uds.am.freescale.net>
On 10/25/2010 06:49 PM, Scott Wood wrote:
> On Sun, 24 Oct 2010 15:29:12 +0200
> Avi Kivity<avi@redhat.com> wrote:
>
> > Linus, the repository and branch
> >
> > git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.37
> >
> > contains the kvm updates for the 2.6.37 merge window. Major changes
> > this time around include powerpc paravirtualization, a virtual tsc
> > rework, and exposing npt to the guest for fast nested virtualization.
> > Please pull.
>
> How about these patches which are in kvm.git/next but not
> kvm-updates/2.6.37?
>
> PPC: KVM: Book E doesn't have __end_interrupts.
> KVM: PPC: e500: Call kvm_vcpu_uninit() before kvmppc_e500_tlb_uninit()
> KVM: PPC: BookE: fix sleep with interrupts disabled
> KVM: PPC: BookE: Load the lower half of MSR
>
Alex, if you want them in, please prepare backports for 2.6.36.1.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-10-25 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 13:29 [GIT PULL] KVM updates for the 2.6.37 merge window Avi Kivity
2010-10-24 23:28 ` Stephen Rothwell
2010-10-25 16:49 ` Scott Wood
2010-10-25 16:59 ` Avi Kivity [this message]
2010-10-26 15:55 ` Alexander Graf
2010-10-26 16:42 ` Avi Kivity
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=4CC5B764.5030007@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=scottwood@freescale.com \
--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 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.