From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Wang Dongsheng <dongsheng.wang@freescale.com>,
linux-kernel@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Paul Mackerras <paulus@samba.org>,
Olof Johansson <olof@lixom.net>,
Cody P Schafer <cody@linux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc: warn users of smt-snooze-delay that the API isn't there anymore
Date: Wed, 26 Feb 2014 09:40:02 +1100 [thread overview]
Message-ID: <1393368002.6314.10.camel@pasglop> (raw)
In-Reply-To: <530C4D57.1030905@linux.vnet.ibm.com>
On Tue, 2014-02-25 at 13:29 +0530, Deepthi Dharwar wrote:
> We currently do not use smt-snooze-delay in the kernel.
> The sysfs entries needs to be retained until we do a clean up
> ppc64_cpu
> util that uses these entries to determine SMT,
> clean up patch for this has already been posted out by Prerna.
> Once, we have the ppc64_cpu changes in, we can look to clean up these
> parts from the kernel.
We generally shouldn't change user visible interfaces.
People still have old versions of ppc64_cpu, we must not break them
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: Cody P Schafer <cody@linux.vnet.ibm.com>,
Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
Olof Johansson <olof@lixom.net>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Wang Dongsheng <dongsheng.wang@freescale.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: warn users of smt-snooze-delay that the API isn't there anymore
Date: Wed, 26 Feb 2014 09:40:02 +1100 [thread overview]
Message-ID: <1393368002.6314.10.camel@pasglop> (raw)
In-Reply-To: <530C4D57.1030905@linux.vnet.ibm.com>
On Tue, 2014-02-25 at 13:29 +0530, Deepthi Dharwar wrote:
> We currently do not use smt-snooze-delay in the kernel.
> The sysfs entries needs to be retained until we do a clean up
> ppc64_cpu
> util that uses these entries to determine SMT,
> clean up patch for this has already been posted out by Prerna.
> Once, we have the ppc64_cpu changes in, we can look to clean up these
> parts from the kernel.
We generally shouldn't change user visible interfaces.
People still have old versions of ppc64_cpu, we must not break them
Cheers,
Ben.
next prev parent reply other threads:[~2014-02-25 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 0:14 [PATCH] powerpc: warn users of smt-snooze-delay that the API isn't there anymore Cody P Schafer
2014-02-22 0:14 ` Cody P Schafer
2014-02-25 4:53 ` Madhavan Srinivasan
2014-02-25 4:53 ` Madhavan Srinivasan
2014-02-25 22:47 ` Cody P Schafer
2014-02-25 22:47 ` Cody P Schafer
2014-02-25 7:59 ` Deepthi Dharwar
2014-02-25 7:59 ` Deepthi Dharwar
2014-02-25 22:40 ` Benjamin Herrenschmidt [this message]
2014-02-25 22:40 ` Benjamin Herrenschmidt
2014-02-26 3:45 ` Michael Ellerman
2014-02-26 3:45 ` 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=1393368002.6314.10.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=cody@linux.vnet.ibm.com \
--cc=deepthi@linux.vnet.ibm.com \
--cc=dongsheng.wang@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=olof@lixom.net \
--cc=paul.gortmaker@windriver.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 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.