From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
Cc: skiboot@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [Skiboot] [PATCH 1/2] SLW: Remove stop1_lite and stop0 stop states
Date: Mon, 07 May 2018 01:37:07 +1000 [thread overview]
Message-ID: <8736z44wyk.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <877eok9qs1.fsf@concordia.ellerman.id.au>
Michael Ellerman <mpe@ellerman.id.au> writes:
> Stewart Smith <stewart@linux.vnet.ibm.com> writes:
> ...
>>
>> Slightly stupid question: should we be disabling these here or should
>> Linux be better and deciding what states to use?
>>
>> I'm inclined to say this is a Linux problem as it should make the
>> decision of what hardware feature to used based on the ones OPAL says
>> *can* be used.
>
> Yeah I agree.
>
> Firmware shouldn't be implementing the policy around what states to use,
> it should tell the operating system (which might be Linux) what states
> are available and what their features are.
Yeah... I think I should work out somewhere to put this in the
documentation, a kind of design philosophy we can point back to.
> The exception to that would be that we have unfixable crash bugs in
> existing kernels, in that case firmware might have to filter out states
> that are known to cause those.
s/in/with/ and *cough* stop11 for example.
--
Stewart Smith
OPAL Architect, IBM.
prev parent reply other threads:[~2018-05-06 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1525079529-2284-1-git-send-email-akshay.adiga@linux.vnet.ibm.com>
2018-05-01 3:47 ` [Skiboot] [PATCH 1/2] SLW: Remove stop1_lite and stop0 stop states Nicholas Piggin
2018-05-03 9:06 ` Akshay Adiga
2018-05-03 9:28 ` Nicholas Piggin
2018-05-03 10:03 ` Stewart Smith
2018-05-03 10:15 ` Nicholas Piggin
2018-05-10 8:59 ` Akshay Adiga
2018-05-10 10:02 ` Nicholas Piggin
2018-05-04 1:02 ` Michael Ellerman
2018-05-06 15:37 ` Stewart Smith [this message]
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=8736z44wyk.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=skiboot@lists.ozlabs.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.