From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: yilzhang@redhat.com, david@gibson.dropbear.id.au
Subject: Re: powerpc/kexec: Fix kexec/kdump in P9 guest kernels
Date: Fri, 24 Nov 2017 20:46:41 +1100 (AEDT) [thread overview]
Message-ID: <3yjrtp24pQz9t20@ozlabs.org> (raw)
In-Reply-To: <20171124035102.28051-1-mpe@ellerman.id.au>
On Fri, 2017-11-24 at 03:51:02 UTC, Michael Ellerman wrote:
> The code that cleans up the IAMR/AMOR before kexec'ing failed to
> remember that when we're running as a guest AMOR is not writable, it's
> hypervisor privileged.
>
> They symptom is that the kexec stops before entering purgatory and
> nothing else is seen on the console. If you examine the state of the
> system all threads will be in the 0x700 program check handler.
>
> Fix it by making the write to AMOR dependent on HV mode.
>
> Fixes: 1e2a516e89fc ("powerpc/kexec: Fix radix to hash kexec due to IAMR/AMOR")
> Cc: stable@vger.kernel.org # v4.10+
> Reported-by: Yilin Zhang <yilzhang@redhat.com>
> Debugged-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> Acked-by: Balbir Singh <bsingharora@gmail.com>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> Tested-by: David Gibson <david@gibson.dropbear.id.au>
Applied to powerpc fixes.
https://git.kernel.org/powerpc/c/2621e945fbf1d6df5f3f0ba7be5bae
cheers
prev parent reply other threads:[~2017-11-24 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 3:51 [PATCH] powerpc/kexec: Fix kexec/kdump in P9 guest kernels Michael Ellerman
2017-11-24 4:13 ` Balbir Singh
2017-11-24 4:24 ` David Gibson
2017-11-24 9:46 ` Michael Ellerman [this message]
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=3yjrtp24pQz9t20@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=yilzhang@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;
as well as URLs for NNTP newsgroup(s).