From: Stefan Berger <stefanb@linux.ibm.com>
To: Rob Herring <robh@kernel.org>
Cc: mpe@ellerman.id.au, linux-integrity@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
jarkko@kernel.org, rnsastry@linux.ibm.com, peterhuewe@gmx.de,
viparash@in.ibm.com
Subject: Re: [PATCH 0/2] Preserve TPM log across kexec
Date: Thu, 7 Mar 2024 17:32:09 -0500 [thread overview]
Message-ID: <38981112-9091-46d4-a815-8a5f47e15bb2@linux.ibm.com> (raw)
In-Reply-To: <20240307214245.GA3110385-robh@kernel.org>
On 3/7/24 16:42, Rob Herring wrote:
> On Wed, Mar 06, 2024 at 11:08:20AM -0500, Stefan Berger wrote:
>>
>>
>> On 3/6/24 10:55, Stefan Berger wrote:
>>> This series resolves an issue on PowerVM and KVM on Power where the memory
>>> the TPM log was held in may become inaccessible or corrupted after a kexec
>>> soft reboot. The solution on these two platforms is to store the whole log
>>> in the device tree because the device tree is preserved across a kexec with
>>> either of the two kexec syscalls.
>>>
>> FYI: This was the previous attempt that didn't work with the older kexec
>> syscall: https://lore.kernel.org/lkml/4afde78d-e138-9eee-50e0-dbd32f4dcfe0@linux.ibm.com/T/#m158630d214837e41858b03d4b025e6f96cb8f251
>
> Doesn't everyone else still need that? Is powerpc the only ones that
Are you referring to the old series with 'that' ? I more or less had to
abandon it because it wouldn't solve the problem for the old kexec
syscall, so that's why I am embedding the whole log now in the
devicetree since the DT is properly carried across the kexec soft reboot
on PowerVM and KVM for Power. Maybe other platforms will (have to)
follow, but I don't know.
> care about the old kexec syscall?
>
> Rob
prev parent reply other threads:[~2024-03-07 22:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 15:55 Stefan Berger
2024-03-06 15:55 ` [PATCH 1/2] powerpc/prom_init: Replace linux,sml-base/sml-size with linux,sml-log Stefan Berger
2024-03-07 10:41 ` Michael Ellerman
2024-03-07 15:11 ` Stefan Berger
2024-03-07 20:39 ` Conor Dooley
2024-03-07 21:15 ` Stefan Berger
2024-03-07 21:29 ` Conor Dooley
2024-03-07 21:52 ` Rob Herring
2024-03-08 12:23 ` Stefan Berger
2024-03-08 20:57 ` Rob Herring
2024-03-08 21:26 ` Stefan Berger
2024-03-12 10:32 ` Michael Ellerman
2024-03-12 16:22 ` Rob Herring
2024-03-12 19:15 ` Stefan Berger
2024-03-07 20:11 ` Jarkko Sakkinen
2024-03-06 15:55 ` [PATCH 2/2] tpm: of: If available Use linux,sml-log to get the log and its size Stefan Berger
2024-03-07 10:42 ` Michael Ellerman
2024-03-07 15:00 ` Stefan Berger
2024-03-07 11:35 ` Conor Dooley
2024-03-07 19:57 ` Jarkko Sakkinen
2024-03-07 20:00 ` Jarkko Sakkinen
2024-03-08 12:17 ` Stefan Berger
2024-03-11 20:09 ` Jarkko Sakkinen
2024-03-12 10:35 ` Michael Ellerman
2024-03-12 15:50 ` Jarkko Sakkinen
2024-03-12 19:08 ` Stefan Berger
2024-03-06 16:08 ` [PATCH 0/2] Preserve TPM log across kexec Stefan Berger
2024-03-07 21:42 ` Rob Herring
2024-03-07 22:32 ` Stefan Berger [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=38981112-9091-46d4-a815-8a5f47e15bb2@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=peterhuewe@gmx.de \
--cc=rnsastry@linux.ibm.com \
--cc=robh@kernel.org \
--cc=viparash@in.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
all inboxes | Powered by JetHome®