public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: David Ahern <david.ahern@oracle.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched: Add cpu based entries to debugfs
Date: Mon, 06 Apr 2015 06:04:21 +0200	[thread overview]
Message-ID: <1428293061.11310.28.camel@gmx.de> (raw)
In-Reply-To: <5521EB33.7050405@oracle.com>

On Sun, 2015-04-05 at 20:10 -0600, David Ahern wrote:
> 
> Can someone clarify on the duplication concerns and such?

My concern was eg you display flags in /sys, but to tweak flags etc, 
you must visit /proc.  Seems to me the missing info should either be 
added to /proc (some under DEBUG?), or the lot should move to /sys.

I don't care all that much, making span etc visible anywhere is an win 
over boot flag + big box (esp. + serial console).

        -Mike

  reply	other threads:[~2015-04-06  4:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  2:13 [RFC PATCH] sched: Add cpu based entries to debugfs David Ahern
2015-03-30  2:32 ` Mike Galbraith
2015-03-30  2:48   ` David Ahern
2015-03-30  3:08     ` Mike Galbraith
2015-03-30 13:03       ` David Ahern
2015-03-30 14:45         ` Mike Galbraith
2015-03-30  7:44 ` Peter Zijlstra
2015-03-30  8:26   ` Mike Galbraith
2015-03-30  8:28     ` Peter Zijlstra
2015-03-30  8:43       ` Mike Galbraith
2015-03-30  9:18         ` Peter Zijlstra
2015-03-31  9:13           ` Ingo Molnar
2015-04-06  2:10             ` David Ahern
2015-04-06  4:04               ` Mike Galbraith [this message]
2015-03-30 13:02   ` David Ahern

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=1428293061.11310.28.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=david.ahern@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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