From: Oliver <oohall@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Andrew Donnellan <ajd@linux.ibm.com>
Subject: Re: [PATCH v2 5/5] powerpc/configs: Disable SCOM_DEBUGFS in powernv_defconfig
Date: Thu, 9 May 2019 15:53:32 +1000 [thread overview]
Message-ID: <CAOSf1CFjf-ZBswf4uCbD9C0tVnUdapSm67=pPo34uxi_VQhZuA@mail.gmail.com> (raw)
In-Reply-To: <1557380130.bkras9z1l5.astroid@bobo.none>
On Thu, May 9, 2019 at 3:38 PM Nicholas Piggin <npiggin@gmail.com> 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?
Yeah... If you're building powernv_defconfig then the odds are pretty
high that you'll want scom access.
>
> >
> > 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
> >
> >
next prev parent reply other threads:[~2019-05-09 5:55 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 [this message]
2019-05-09 5:54 ` Andrew Donnellan
2019-07-31 1:45 ` Andrew Donnellan
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='CAOSf1CFjf-ZBswf4uCbD9C0tVnUdapSm67=pPo34uxi_VQhZuA@mail.gmail.com' \
--to=oohall@gmail.com \
--cc=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 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.