From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Mackerras <paulus@samba.org>, kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org, Scott Wood <scottwood@freescale.com>,
agraf@suse.de
Subject: Re: [PATCH 0/2] Fixes for HV KVM on PPC for 3.14
Date: Thu, 13 Mar 2014 09:50:29 +0000 [thread overview]
Message-ID: <53217F65.8040104@redhat.com> (raw)
In-Reply-To: <20140313090107.GA32257@iris.ozlabs.ibm.com>
Il 13/03/2014 10:01, Paul Mackerras ha scritto:
> These two patches fix two things in hypervisor-mode KVM for the IBM
> POWER server processors. The first patch removes a hunk of extraneous
> code that got in as a result of a mistake I made in cleaning up after
> rebasing a patch. The second fixes a bug that causes host memory
> corruption. Both patches fix things that cause host crashes, so I'd
> like them in 3.14 if possible. The two patches only touch one file,
> arch/powerpc/kvm/book3s_hv_rmhandlers.S, so they can't possibly cause
> any problems for other architectures or other PPC platforms.
>
> The patches are against the master branch of the kvm tree but should
> apply equally on Linus' current master branch.
>
> Scott, please ack.
I had to do some conflict resolution when applying Alex's 3.14 pull
request, I'm glad it wasn't me who introduced the bug! :) Phew.
This means that kvm/next is also broken right now for PPC. I can merge
the patches into kvm/next too (in addition to sending them to Linus for
3.14). Would that help in any way?
Paolo
next prev parent reply other threads:[~2014-03-13 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 9:01 [PATCH 0/2] Fixes for HV KVM on PPC for 3.14 Paul Mackerras
2014-03-13 9:02 ` [PATCH 1/2] KVM: PPC: Book3S HV: Remove bogus duplicate code Paul Mackerras
2014-03-13 9:02 ` [PATCH 2/2] KVM: PPC: Book3S HV: Fix register usage when loading/saving VRSAVE Paul Mackerras
2014-03-13 9:50 ` Paolo Bonzini [this message]
2014-03-13 10:29 ` [PATCH 0/2] Fixes for HV KVM on PPC for 3.14 Paul Mackerras
2014-03-13 15:43 ` Scott Wood
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=53217F65.8040104@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox