From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Mackerras <paulus@samba.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Alexander Graf <agraf@suse.de>,
Scott Wood <scottwood@freescale.com>
Subject: Re: Preparing kvm/next for first pull request of 3.15 merge window
Date: Wed, 26 Mar 2014 09:19:52 +0000 [thread overview]
Message-ID: <53329BB8.2040202@redhat.com> (raw)
In-Reply-To: <20140326035142.GB30363@iris.ozlabs.ibm.com>
Il 26/03/2014 04:51, Paul Mackerras ha scritto:
>> > I would like to know from ARM and PPC maintainers *now* (before the
>> > merge window opens) what will be in 3.15. Also, PPC guys, please
>> > make sure the pull requests will be based on commit e724f080f5dd
>> > (KVM: PPC: Book3S HV: Fix register usage when loading/saving VRSAVE,
>> > 2014-03-13).
> Alex has 5 commits in his kvm-ppc-queue branch that should go in.
> That tree is based on your kvm-3.14-2 tag, not on e724f080f5dd.
> Would you accept a pull request for that from me on Alex's behalf
> since he's away?
Yes, of course.
> Do you need me to rebase it at all?
These are:
1ac4484979 PPC: KVM: Introduce hypervisor call H_GET_TCE
e0a7be38c9 PPC: KVM: fix RESUME_GUEST check before returning from
kvmppc_run_core()
013e98e657 PPC: KVM: fix RESUME_GUEST check before ending CEDE in
kvmppc_run_core()
e8a7f11fe0 PPC: KVM: fix VCPU run for HV KVM (v2)
26d96ec97c PPC: KVM: introduce helper to check RESUME_GUEST and related
I would consider rebasing; but you know better than me the effect of the
two host-crash-fixing patches and how the testability/bisectability of
kvm-ppc-queue is affected.
In particular, how likely is it that reverse-bisection ("which commit
fixed the bug?") would end up on e724f080f5dd rather than one of the
four RESUME_GUEST commits?
> There is also the set of 8 patches that I just posted and Scott
> acked. I can make a branch based on e724f080f5dd and send you a pull
> request.
Yes, thanks!
Paolo
> Let me know what you would prefer regarding Alex's kvm-ppc-queue
> branch.
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Mackerras <paulus@samba.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Alexander Graf <agraf@suse.de>,
Scott Wood <scottwood@freescale.com>
Subject: Re: Preparing kvm/next for first pull request of 3.15 merge window
Date: Wed, 26 Mar 2014 10:19:52 +0100 [thread overview]
Message-ID: <53329BB8.2040202@redhat.com> (raw)
In-Reply-To: <20140326035142.GB30363@iris.ozlabs.ibm.com>
Il 26/03/2014 04:51, Paul Mackerras ha scritto:
>> > I would like to know from ARM and PPC maintainers *now* (before the
>> > merge window opens) what will be in 3.15. Also, PPC guys, please
>> > make sure the pull requests will be based on commit e724f080f5dd
>> > (KVM: PPC: Book3S HV: Fix register usage when loading/saving VRSAVE,
>> > 2014-03-13).
> Alex has 5 commits in his kvm-ppc-queue branch that should go in.
> That tree is based on your kvm-3.14-2 tag, not on e724f080f5dd.
> Would you accept a pull request for that from me on Alex's behalf
> since he's away?
Yes, of course.
> Do you need me to rebase it at all?
These are:
1ac4484979 PPC: KVM: Introduce hypervisor call H_GET_TCE
e0a7be38c9 PPC: KVM: fix RESUME_GUEST check before returning from
kvmppc_run_core()
013e98e657 PPC: KVM: fix RESUME_GUEST check before ending CEDE in
kvmppc_run_core()
e8a7f11fe0 PPC: KVM: fix VCPU run for HV KVM (v2)
26d96ec97c PPC: KVM: introduce helper to check RESUME_GUEST and related
I would consider rebasing; but you know better than me the effect of the
two host-crash-fixing patches and how the testability/bisectability of
kvm-ppc-queue is affected.
In particular, how likely is it that reverse-bisection ("which commit
fixed the bug?") would end up on e724f080f5dd rather than one of the
four RESUME_GUEST commits?
> There is also the set of 8 patches that I just posted and Scott
> acked. I can make a branch based on e724f080f5dd and send you a pull
> request.
Yes, thanks!
Paolo
> Let me know what you would prefer regarding Alex's kvm-ppc-queue
> branch.
next prev parent reply other threads:[~2014-03-26 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 17:29 Preparing kvm/next for first pull request of 3.15 merge window Paolo Bonzini
2014-03-25 17:29 ` Paolo Bonzini
2014-03-25 18:33 ` Christoffer Dall
2014-03-25 18:33 ` Christoffer Dall
2014-03-25 20:35 ` Christian Borntraeger
2014-03-25 20:35 ` Christian Borntraeger
2014-03-26 9:32 ` Paolo Bonzini
2014-03-26 9:32 ` Paolo Bonzini
2014-03-26 3:51 ` Paul Mackerras
2014-03-26 3:51 ` Paul Mackerras
2014-03-26 9:19 ` Paolo Bonzini [this message]
2014-03-26 9:19 ` Paolo Bonzini
2014-03-26 10:32 ` Greg Kurz
2014-03-26 10:32 ` Greg Kurz
2014-03-26 11:46 ` Paul Mackerras
2014-03-26 11:46 ` Paul Mackerras
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=53329BB8.2040202@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=paulus@samba.org \
--cc=scottwood@freescale.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.