From: Michael Ellerman <mpe@ellerman.id.au>
To: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH] powerpc/numa: add ability to disable and debug topology updates
Date: Wed, 17 Sep 2014 13:38:30 +1000 [thread overview]
Message-ID: <1410925110.1586.3.camel@concordia> (raw)
In-Reply-To: <20140915235455.GB5238@linux.vnet.ibm.com>
On Mon, 2014-09-15 at 16:54 -0700, Nishanth Aravamudan wrote:
> On 15.09.2014 [15:05:36 +1000], Michael Ellerman wrote:
> > On Tue, 2014-09-09 at 13:09 -0700, Nishanth Aravamudan wrote:
>
> > Does it really need to be a boot param, or could it be a debugfs or
> > sysctl flag? ie. do we need to disable it immediately at boot or would
> > it be OK if it was /etc/rc.local or similar that turned it off ?
>
> We need it off at boot, potentially. An LPAR does not indicate that it
> will or will not respond to the events in any synchronous fashion, so
> the hypervisor is free to send them to us whenever.
OK. I guess we're stuck with a boot time parameter for on/off then.
> > As far as the debug goes, we could just use pr_debug() with
> > CONFIG_DYNAMIC_DEBUG, it's not quite as easy to enable as a kernel
> > parameter but for the odd bit of debugging it should be fine.
>
> That's a good point, I wonder with that mechanism if we should perhaps
> extend/remove other static debugging methods in favor of that (e.g.,
> numa=debug)?
Yes definitely.
It's slightly more arcane to enable, ie. to turn on dynamic debugging in numa.c
at boot your command line needs:
dyndbg="file numa.c +p"
But that's fine unless it's an option you expect users to be using regularly
which none of these are.
cheers
next prev parent reply other threads:[~2014-09-17 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 20:09 [RFC PATCH] powerpc/numa: add ability to disable and debug topology updates Nishanth Aravamudan
2014-09-15 5:05 ` Michael Ellerman
2014-09-15 23:54 ` Nishanth Aravamudan
2014-09-17 3:38 ` Michael Ellerman [this message]
2014-09-16 19:42 ` Nathan Fontenot
2014-09-16 20:10 ` Nishanth Aravamudan
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=1410925110.1586.3.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nacc@linux.vnet.ibm.com \
--cc=paulus@samba.org \
/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).