From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>, Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, kvm-ppc@vger.kernel.org
Subject: "KVM: PPC: booke: Improve timer register emulation" breaks Book3s HV
Date: Tue, 06 Dec 2011 04:03:00 +0000 [thread overview]
Message-ID: <20111206040300.GA12018@drongo> (raw)
I'm not sure why yet, but commit 8a97c432 ("KVM: PPC: booke: Improve
timer register emulation") in Alex's kvm-ppc-next branch is breaking
Book3S HV KVM on POWER7. Guest cpus fail to spin up, and even with
just one cpu, the guest stalls every so often. If I stop the guest
and inspect the state with qemu, PC is at 0x900. Reverting 8a97c432
makes it work properly again.
Paul.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>, Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, kvm-ppc@vger.kernel.org
Subject: "KVM: PPC: booke: Improve timer register emulation" breaks Book3s HV
Date: Tue, 6 Dec 2011 15:03:00 +1100 [thread overview]
Message-ID: <20111206040300.GA12018@drongo> (raw)
I'm not sure why yet, but commit 8a97c432 ("KVM: PPC: booke: Improve
timer register emulation") in Alex's kvm-ppc-next branch is breaking
Book3S HV KVM on POWER7. Guest cpus fail to spin up, and even with
just one cpu, the guest stalls every so often. If I stop the guest
and inspect the state with qemu, PC is at 0x900. Reverting 8a97c432
makes it work properly again.
Paul.
next reply other threads:[~2011-12-06 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 4:03 Paul Mackerras [this message]
2011-12-06 4:03 ` "KVM: PPC: booke: Improve timer register emulation" breaks Book3s HV Paul Mackerras
2011-12-06 11:43 ` "KVM: PPC: booke: Improve timer register emulation" breaks Paul Mackerras
2011-12-06 11:43 ` "KVM: PPC: booke: Improve timer register emulation" breaks Book3s HV Paul Mackerras
2011-12-06 11:46 ` Alexander Graf
2011-12-06 11:46 ` Alexander Graf
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=20111206040300.GA12018@drongo \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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.