All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nathan Lynch <nathanl@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: tyreld@linux.ibm.com
Subject: Re: [PATCH] powerpc/pseries: delete scanlog
Date: Wed, 17 Nov 2021 21:37:42 +1100	[thread overview]
Message-ID: <877dd7m5jd.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <87sfvvijjw.fsf@linux.ibm.com>

Nathan Lynch <nathanl@linux.ibm.com> writes:
> Nathan Lynch <nathanl@linux.ibm.com> writes:
>> Remove the pseries scanlog driver.
>>
>> This code supports functions from Power4-era servers that are not present
>> on targets currently supported by arch/powerpc. System manuals from this
>> time have this description:
>>
>>   Scan Dump data is a set of chip data that the service processor gathers
>>   after a system malfunction. It consists of chip scan rings, chip trace
>>   arrays, and Scan COM (SCOM) registers. This data is stored in the
>>   scan-log partition of the system’s Nonvolatile Random Access
>>   Memory (NVRAM).
>>
>> PowerVM partition firmware development doesn't recognize the associated
>> function call or property, and they don't see any references to them in
>> their codebase. It seems to have been specific to non-virtualized
>> pseries.
>
> Just bumping this to see if there are any objections.

Not an objection, I like nothing better than dropping old unused cruft,
but are we sure it's safe to remove the proc file?

I see that rtas_errd still looks for it, have you checked that it will
handle the absence of the file gracefully and continue doing whatever
else it does?

On further inspection it looks like the code that looks for it in
rtas_errd is #if 0'ed out (??), so maybe it's dead.

Anyway if you can test that rtas_errd still works that'd be good.

Presumably there's no other code that cares about the proc file.

cheers

  reply	other threads:[~2021-11-17 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 17:32 [PATCH] powerpc/pseries: delete scanlog Nathan Lynch
2021-11-17  2:48 ` Nathan Lynch
2021-11-17 10:37   ` Michael Ellerman [this message]
2021-11-17 14:47     ` Nathan Lynch
2021-11-18  0:26       ` Michael Ellerman
2021-11-25  9:36 ` Michael Ellerman

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=877dd7m5jd.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nathanl@linux.ibm.com \
    --cc=tyreld@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 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.