From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] KVM-PPC: Fix mtsrin in book3s_64 mmu
Date: Sun, 20 Dec 2009 09:31:27 +0000 [thread overview]
Message-ID: <4B2DEEEF.5060908@redhat.com> (raw)
In-Reply-To: <1261242459-388-1-git-send-email-agraf@suse.de>
On 12/19/2009 07:07 PM, Alexander Graf wrote:
> We were shifting the Ks/Kp/N bits one bit too far on mtsrin. It took
> me some time to figure that out, so I also put in some debugging and a
> comment explaining the conversion.
>
> This fixes current OpenBIOS boot on PPC64 KVM.
>
Applied and queued for 2.6.33. Thanks.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] KVM-PPC: Fix mtsrin in book3s_64 mmu
Date: Sun, 20 Dec 2009 11:31:27 +0200 [thread overview]
Message-ID: <4B2DEEEF.5060908@redhat.com> (raw)
In-Reply-To: <1261242459-388-1-git-send-email-agraf@suse.de>
On 12/19/2009 07:07 PM, Alexander Graf wrote:
> We were shifting the Ks/Kp/N bits one bit too far on mtsrin. It took
> me some time to figure that out, so I also put in some debugging and a
> comment explaining the conversion.
>
> This fixes current OpenBIOS boot on PPC64 KVM.
>
Applied and queued for 2.6.33. Thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-20 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 17:07 [PATCH] KVM-PPC: Fix mtsrin in book3s_64 mmu Alexander Graf
2009-12-19 17:07 ` Alexander Graf
2009-12-19 19:02 ` Hollis Blanchard
2009-12-19 19:02 ` Hollis Blanchard
2009-12-20 9:31 ` Avi Kivity [this message]
2009-12-20 9:31 ` 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=4B2DEEEF.5060908@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@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 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.