From: Alexander Graf <agraf@suse.de>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 1/4] KVM: PPC: Book3S HV: Save and restore CR in __kvmppc_vcore_entry
Date: Mon, 05 Mar 2012 19:11:25 +0000 [thread overview]
Message-ID: <4F550FDD.7020504@suse.de> (raw)
On 02/03/2012 11:53 AM, Paul Mackerras wrote:
> The ABI specifies that CR fields CR2--CR4 are nonvolatile across function
> calls. Currently __kvmppc_vcore_entry doesn't save and restore the CR,
> leading to CR2--CR4 getting corrupted with guest values, possibly leading
> to incorrect behaviour in its caller. This adds instructions to save
> and restore CR at the points where we save and restore the nonvolatile
> GPRs.
>
> Signed-off-by: Paul Mackerras<paulus@samba.org>
Thanks, applied all to kvm-ppc-next. Please CC kvm@vger when you send
patches. Failing to do so might mean the whole pull request gets blocked
by Avi when it gets to him, because he doesn't read kvm-ppc@vger.
Alex
next reply other threads:[~2012-03-05 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 19:11 Alexander Graf [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-03 10:53 [PATCH 1/4] KVM: PPC: Book3S HV: Save and restore CR in __kvmppc_vcore_entry 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=4F550FDD.7020504@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox