From: Paul Mackerras <paulus@ozlabs.org>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Alexander Graf <agraf@suse.de>,
mihai.caraman@freescale.com, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] KVM: PPC: fix ONE_REG AltiVec support
Date: Thu, 14 Jan 2016 14:38:07 +1100 [thread overview]
Message-ID: <20160114033807.GA24745@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <20160113171751.24877.58919.stgit@bahia.huguette.org>
On Wed, Jan 13, 2016 at 06:28:17PM +0100, Greg Kurz wrote:
> The get and set operations got exchanged by mistake when moving the
> code from book3s.c to powerpc.c.
>
> Fixes: 3840edc8033ad5b86deee309c1c321ca54257452
> Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> ---
>
> I posted the very same patch before the holidays but it did not gain
> attention. It is very surprising that the error did not cause trouble
> for such a long time... I discovered it by accident while implementing
> gdbstubs for VSX registers in QEMU. But I guess it is also likely to
> break migration of guests that do AltiVec.
>
> I am not sure if Alex is available to handle this patch... since the
> error is obvious and the fix straightforward, can this patch be applied
> by someone else ? Paulus ? Paolo ?
I'll take it and add it to my upcoming pull request to Paolo.
Paul.
next prev parent reply other threads:[~2016-01-14 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 17:28 [PATCH] KVM: PPC: fix ONE_REG AltiVec support Greg Kurz
2016-01-14 3:38 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-16 17:24 Greg Kurz
2016-01-04 9:14 ` Greg Kurz
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=20160114033807.GA24745@fergus.ozlabs.ibm.com \
--to=paulus@ozlabs.org \
--cc=agraf@suse.de \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mihai.caraman@freescale.com \
--cc=pbonzini@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