Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1203884

Re: [PATCH v5 3/6] cpufreq: powernv: Register for OCC related opal_message notification

Path csiph.com!au2pb.net!feeder.erje.net!us.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From Stewart Smith <stewart@linux.vnet.ibm.com>
Newsgroups linux.kernel
Subject Re: [PATCH v5 3/6] cpufreq: powernv: Register for OCC related opal_message notification
Date Mon, 10 Aug 2015 10:20:02 +0200
Message-ID <pVQtk-m5-15@gated-at.bofh.it> (permalink)
References <pMMoW-My-7@gated-at.bofh.it> <pMMoX-My-27@gated-at.bofh.it> <pVKnT-78c-3@gated-at.bofh.it> <pVQ9Y-88c-5@gated-at.bofh.it>
X-Original-To Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>, rjw@rjwysocki.net
X-Helo d01dlp02.pok.ibm.com
X-Mailfrom stewart@linux.vnet.ibm.com
X-Rcptto linux-pm@vger.kernel.org
User-Agent Notmuch/0.18+16~gec02089 (http://notmuchmail.org) Emacs/23.1.1 (x86_64-redhat-linux-gnu)
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Tm-As-Mml disable
X-Content-Scanned Fidelis XPS MAILER
X-Cbid 15081008-0045-0000-0000-000000FC8314
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 19
Organization linux.* mail to news gateway
X-Original-Cc linux-pm@vger.kernel.org, viresh.kumar@linaro.org, linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, joel@jms.id.au
X-Original-Date Mon, 10 Aug 2015 18:19:08 +1000
X-Original-Message-ID <m3zj1zd08z.fsf@oc8180480414.ibm.com>
X-Original-References <1437033863-15864-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com> <1437033863-15864-4-git-send-email-shilpa.bhat@linux.vnet.ibm.com> <m3y4hjex8q.fsf@oc8180480414.ibm.com> <55C857F8.6090502@linux.vnet.ibm.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1203884

Show key headers only | View raw


Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com> writes:
>> Also, do we export this information via sysfs somewhere? It would seem
>> to want to go along with other cpufreq/cpu info there.
>
> No we don't export the throttling status of the cpu via sysfs. Since the
> throttling state is common across the chip, the per_cpu export will be
> redundant. Did you mean something like one of the below:
>
> 1)/sys/devices/system/cpu/cpufreq/chipN_throttle
>
> 2)/sys/devices/system/cpu/cpuN/cpufreq/throttle

yeah, I was thinking something like that.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Re: [PATCH v5 3/6] cpufreq: powernv: Register for OCC related opal_message notification Stewart Smith <stewart@linux.vnet.ibm.com> - 2015-08-10 03:50 +0200
  Re: [PATCH v5 3/6] cpufreq: powernv: Register for OCC related opal_message  notification Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com> - 2015-08-10 10:00 +0200
    Re: [PATCH v5 3/6] cpufreq: powernv: Register for OCC related  opal_message notification Viresh Kumar <viresh.kumar@linaro.org> - 2015-08-10 10:00 +0200
    Re: [PATCH v5 3/6] cpufreq: powernv: Register for OCC related opal_message notification Stewart Smith <stewart@linux.vnet.ibm.com> - 2015-08-10 10:20 +0200

csiph-web