From: Andrew Donnellan <ajd@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 5/5] powerpc/configs: Disable SCOM_DEBUGFS in powernv_defconfig
Date: Wed, 31 Jul 2019 11:45:50 +1000 [thread overview]
Message-ID: <f6c744a6-3c25-c7a0-f4bf-b3ca239068f9@linux.ibm.com> (raw)
In-Reply-To: <316fb28d-b18b-c236-3063-27837b53e0d3@linux.ibm.com>
On 9/5/19 3:54 pm, Andrew Donnellan wrote:
> On 9/5/19 3:37 pm, Nicholas Piggin wrote:
>> Andrew Donnellan's on May 9, 2019 3:11 pm:
>>> SCOM_DEBUGFS is really not needed for anything other than low-level
>>> hardware debugging.
>>>
>>> opal-prd uses its own interface (/dev/prd) for SCOM access, so it
>>> doesn't
>>> need SCOM_DEBUGFS.
>>>
>>> At some point in the future we'll introduce a debug config fragment
>>> where
>>> this can go instead.
>>
>> That doesn't really explain why you want to disable it. It is useful
>> for low level hardware debugging, I added it.
>>
>> obscurity^Wsecurity?
>
> Mostly just a general feeling that it's not something we need to have by
> default. Security-wise, PRD still provides SCOM access, though we are
> going to look at how we can further lock that down. Shrinks the build by
> only a few kilobytes...
>
> mpe said he's planning on adding a debug.config where we can shift stuff
> like this, and if/when we do that I would like to see this moved there,
> but perhaps this patch can wait until then. I'll let mpe decide.
>
mpe do you have thoughts on this? I would like to see at least the rest
of this series merged.
Andrew
>
> Andrew
>
>
>>
>>>
>>> Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
>>> ---
>>> v1->v2:
>>> - new patch
>>> ---
>>> arch/powerpc/configs/powernv_defconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/powerpc/configs/powernv_defconfig
>>> b/arch/powerpc/configs/powernv_defconfig
>>> index ef2ef98d3f28..d5a6608cb2e0 100644
>>> --- a/arch/powerpc/configs/powernv_defconfig
>>> +++ b/arch/powerpc/configs/powernv_defconfig
>>> @@ -38,7 +38,7 @@ CONFIG_MODULE_UNLOAD=y
>>> CONFIG_MODVERSIONS=y
>>> CONFIG_MODULE_SRCVERSION_ALL=y
>>> CONFIG_PARTITION_ADVANCED=y
>>> -CONFIG_SCOM_DEBUGFS=y
>>> +# CONFIG_SCOM_DEBUGFS is not set
>>> CONFIG_OPAL_PRD=y
>>> CONFIG_PPC_MEMTRACE=y
>>> # CONFIG_PPC_PSERIES is not set
>>> --
>>> 2.20.1
>>>
>>>
>>
>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2019-07-31 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 5:11 [PATCH v2 1/5] powerpc/powernv: Move SCOM access code into powernv platform Andrew Donnellan
2019-05-09 5:11 ` [PATCH v2 2/5] powerpc/powernv: Remove dead SCOM access code Andrew Donnellan
2019-05-09 5:11 ` [PATCH v2 3/5] powerpc/powernv: Get rid of old scom_controller abstraction Andrew Donnellan
2019-05-09 5:11 ` [PATCH v2 4/5] powerpc/powernv: Fix checkpatch warnings in opal-xscom.c Andrew Donnellan
2019-05-09 5:11 ` [PATCH v2 5/5] powerpc/configs: Disable SCOM_DEBUGFS in powernv_defconfig Andrew Donnellan
2019-05-09 5:37 ` Nicholas Piggin
2019-05-09 5:53 ` Oliver
2019-05-09 5:54 ` Andrew Donnellan
2019-07-31 1:45 ` Andrew Donnellan [this message]
2019-07-31 12:00 ` Michael Ellerman
2019-06-04 2:01 ` [PATCH v2 1/5] powerpc/powernv: Move SCOM access code into powernv platform Andrew Donnellan
2019-07-31 11:37 ` Michael Ellerman
2019-08-10 10:20 ` 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=f6c744a6-3c25-c7a0-f4bf-b3ca239068f9@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).