From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Cyril Bur <cyrilbur@gmail.com>,
Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
ego@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com
Subject: Re: [PATCH V8 1/3] powernv: powercap: Add support for powercap framework
Date: Fri, 28 Jul 2017 17:18:55 +1000 [thread overview]
Message-ID: <877eyt1128.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1501205974.3324.1.camel@gmail.com>
Cyril Bur <cyrilbur@gmail.com> writes:
> This is more for MPE and Stewart:
> If there is some mutual exclusion that needs to happen, it should be
> done in skiboot. We've had problems in the past with double entering
> skiboot and hard to interpret errors ending up in userspace, this
> solves that but it seems more like a coverup than an actual solution.
Yeah, I'd like us to be in a position where we don't force mutual
exclusion on such things out to the OS.
The real issue this papers over is the async token stuff you're
reworking. There's that, plus for this specific thing, you *could* go
and set a differnt powercap 180 times concurrently and we should do the
right thing in skiboot... but then you're sitting in skiboot rather than
sitting in linux being able to go run some other task on the thread.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2017-07-28 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 5:05 [PATCH V8 0/3] powernv : Add support for OPAL-OCC command/response interface Shilpasri G Bhat
2017-07-26 5:05 ` [PATCH V8 1/3] powernv: powercap: Add support for powercap framework Shilpasri G Bhat
2017-07-28 1:39 ` Cyril Bur
2017-07-28 4:04 ` Shilpasri G Bhat
2017-07-28 7:18 ` Stewart Smith [this message]
2017-07-26 5:05 ` [PATCH V8 2/3] powernv: Add support to set power-shifting-ratio Shilpasri G Bhat
2017-07-28 4:15 ` Cyril Bur
2017-07-26 5:05 ` [PATCH V8 3/3] powernv: Add support to clear sensor groups data Shilpasri G Bhat
2017-07-28 4:39 ` Cyril Bur
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=877eyt1128.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=cyrilbur@gmail.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=shilpa.bhat@linux.vnet.ibm.com \
--cc=svaidy@linux.vnet.ibm.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.