From: Paul Mackerras <paulus@ozlabs.org>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Book3S PR: Enable use on POWER9 inside HPT-mode guests
Date: Tue, 29 May 2018 01:59:44 +0000 [thread overview]
Message-ID: <20180529015944.GA16998@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <20180519055638.GA24787@fergus.ozlabs.ibm.com>
On Fri, May 25, 2018 at 12:48:31PM +0200, Greg Kurz wrote:
> I could reproduced the problem if I boot the L2 guest with an upstream
> kernel (commit d7b66b4ab034). I've tried to dump the log_buf but things
> didn't go well:
>
> $ grep 'd log_buf' System.map
> c000000001304f08 d log_buf_len
> c000000001304f10 d log_buf
>
> (qemu) x 0xc000000001304f08
> c000000001304f08: Cannot access memory
I would use "xp 0x1304f08".
> Since 4.16.0 works, I could bisect down to:
>
> commit dbfcf3cb9c681aa0c5d0bb46068f98d5b1823dd3
> Author: Paul Mackerras <paulus@ozlabs.org>
> Date: Thu Feb 16 16:03:39 2017 +1100
>
> powerpc/64: Call H_REGISTER_PROC_TBL when running as a HPT guest on POWER9
>
> The hcall is handled by QEMU, which then calls the KVM_PPC_CONFIGURE_V3_MMU
> ioctl, which fails since PR KVM doesn't implement it, and H_REGISTER_PROC_TBL
> fails with H_PARAMETER. The panic hence come from...
Hmmm. Maybe the kernel should check the ibm,architecture-vec-5
property in /chosen and only register the process table if it
indicates the hypervisor can support either hash or radix.
Paul.
next prev parent reply other threads:[~2018-05-29 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 5:56 [PATCH] KVM: PPC: Book3S PR: Enable use on POWER9 inside HPT-mode guests Paul Mackerras
2018-05-23 17:04 ` Greg Kurz
2018-05-23 23:12 ` Paul Mackerras
2018-05-25 10:48 ` Greg Kurz
2018-05-29 1:59 ` Paul Mackerras [this message]
2018-05-29 11:55 ` Greg Kurz
2018-05-31 6:02 ` 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=20180529015944.GA16998@fergus.ozlabs.ibm.com \
--to=paulus@ozlabs.org \
--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 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.