linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Sourabh Jain <sourabhjain@linux.ibm.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/pseries: Fix scv instruction crash with kexec
Date: Fri, 28 Jun 2024 22:01:56 +1000	[thread overview]
Message-ID: <87bk3ll1hn.fsf@mail.lhotse> (raw)
In-Reply-To: <3b4b2943-49ad-4619-b195-bc416f1d1409@linux.ibm.com>

Sourabh Jain <sourabhjain@linux.ibm.com> writes:
> On 26/06/24 14:57, Michael Ellerman wrote:
>> Nicholas Piggin <npiggin@gmail.com> writes:
>>> kexec on pseries disables AIL (reloc_on_exc), required for scv
>>> instruction support, before other CPUs have been shut down. This means
>>> they can execute scv instructions after AIL is disabled, which causes an
>>> interrupt at an unexpected entry location that crashes the kernel.
>>>
>>> Change the kexec sequence to disable AIL after other CPUs have been
>>> brought down.
>>>
>>> As a refresher, the real-mode scv interrupt vector is 0x17000, and the
>>> fixed-location head code probably couldn't easily deal with implementing
>>> such high addresses so it was just decided not to support that interrupt
>>> at all.
>>>
>>> Reported-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>>   
>> Was this reported publicly? I don't remember it.
>
> No, I didn't report this issue publicly.

OK. It's always nice to have a public report so if someone else hits it,
either at the same time, or in the future, they can search the archive
and see that it's been reported.

But this now counts as a public report, so I'll just point the link at
this thread :)

cheers

  reply	other threads:[~2024-06-28 12:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 13:40 [PATCH] powerpc/pseries: Fix scv instruction crash with kexec Nicholas Piggin
2024-06-26  9:27 ` Michael Ellerman
2024-06-26  9:46   ` Sourabh Jain
2024-06-28 12:01     ` Michael Ellerman [this message]
2024-06-26  9:40 ` Gautam Menghani
2024-07-01  4:16   ` Sourabh Jain
2024-07-06 22:49 ` Michael Ellerman
2024-07-09 10:53 ` Michal Suchánek
2024-07-09 13:03   ` Michael Ellerman
2024-07-09 13:10     ` Michal Suchánek

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=87bk3ll1hn.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=sourabhjain@linux.ibm.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).