From: Alexander Graf <agraf@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: "kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
kvm-ppc@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PULL 0/5] ppc patch queue 2012-05-16
Date: Wed, 16 May 2012 13:28:04 +0000 [thread overview]
Message-ID: <4FB3AB64.3060609@suse.de> (raw)
In-Reply-To: <4FB3AA52.7090409@redhat.com>
On 05/16/2012 03:23 PM, Avi Kivity wrote:
> On 05/16/2012 04:05 PM, Alexander Graf wrote:
>> Hi Avi,
>>
>> There are a few bugs in 3.4 that really should be fixed before people can
>> be all happy and fuzzy about KVM on PowerPC. These fixes are:
>>
>> * fix POWER7 bare metal with PR=y
>> * fix deadlock on HV=y book3s_64 mode in low memory cases
>> * fix invalid MMU scope of PR=y mode on book3s_64, possibly
>> leading to memory corruption
>>
>> This request and the patches are based on top of Linus's master branch. Please
>> either send these to Linus to get them into 3.4.0 or to linux-stable if it's too
>> late already.
>>
>> Alex
>>
>> The following changes since commit 568b44559d7ca269d367e694c74eb4436e7e3ccf:
>> Srivatsa S. Bhat (1):
>> mn10300/CPU hotplug: Add missing call to notify_cpu_starting()
>>
>> are available in the git repository at:
>>
>> git://github.com/agraf/linux-2.6.git for-upstream-3.4
>>
>> Alexander Graf (3):
>> KVM: PPC: Book3S: PR: Handle EMUL_ASSIST
>> KVM: PPC: Fix PR KVM on POWER7 bare metal
>>
> This one is already in 'next', which means it's queued for 3.5. While
> it won't bring about the end of the universe, please try to avoid this
> in the future by selecting the right branch to push into in advance
> (that's one of the consequences of the new workflow).
Hm. I figured that there's a pretty high chance that the patches won't
make it for 3.4.0, so they'd have to go into 3.4-stable, which then
again means it's a lot easier to see which ones are still outstanding
there. I still maintain a -next queue in parallel where patches destined
for 3.5 go into.
Which workflow would you prefer if not the one above?
Alex
next prev parent reply other threads:[~2012-05-16 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 13:05 [PULL 0/5] ppc patch queue 2012-05-16 Alexander Graf
2012-05-16 13:05 ` [PATCH 1/5] KVM: PPC: Book3S: PR: Handle EMUL_ASSIST Alexander Graf
2012-05-16 13:05 ` [PATCH 2/5] KVM: PPC: Fix PR KVM on POWER7 bare metal Alexander Graf
2012-05-16 13:05 ` [PATCH 3/5] KVM: PPC: Book3S: PR: Fix hsrr code Alexander Graf
2012-05-16 13:05 ` [PATCH 4/5] powerpc/kvm: Fix VSID usage in 64-bit "PR" KVM Alexander Graf
2012-05-16 13:05 ` [PATCH 5/5] KVM: PPC: Book3S HV: Fix bug leading to deadlock in guest HPT updates Alexander Graf
2012-05-16 13:23 ` [PULL 0/5] ppc patch queue 2012-05-16 Avi Kivity
2012-05-16 13:28 ` Alexander Graf [this message]
2012-05-16 13:34 ` 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=4FB3AB64.3060609@suse.de \
--to=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox