From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>, Viresh Kumar <viresh.kumar@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Hector Yuan <hector.yuan@mediatek.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains
Date: Wed, 19 May 2021 12:23:18 +0100 [thread overview]
Message-ID: <20210519112308.umxriuv75onuwvmc@bogus> (raw)
In-Reply-To: <CAL_JsqK6B40D8dRu8KoOsx6eSzRXx6KsSEu5mjDokPEAy+p4oA@mail.gmail.com>
On Mon, May 17, 2021 at 02:17:05PM -0500, Rob Herring wrote:
> On Mon, May 17, 2021 at 10:55 AM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > The CLKSCREW attack [0] exposed security vulnerabilities in energy management
> > implementations where untrusted software had direct access to clock and
> > voltage hardware controls. In this attack, the malicious software was able to
> > place the platform into unsafe overclocked or undervolted configurations. Such
> > configurations then enabled the injection of predictable faults to reveal
> > secrets.
> >
> > Many Arm-based systems used to or still use voltage regulator and clock
> > frameworks in the kernel. These frameworks allow callers to independently
> > manipulate frequency and voltage settings. Such implementations can render
> > systems susceptible to this form of attack.
> >
> > Attacks such as CLKSCREW are now being mitigated by not having direct and
> > independent control of clock and voltage in the kernel and moving that
> > control to a trusted entity, such as the SCP firmware or secure world
> > firmware/software which are to perform sanity checking on the requested
> > performance levels, thereby preventing any attempted malicious programming.
> >
> > With the advent of such an abstraction, there is a need to replace the
> > generic clock and regulator bindings used by such devices with a generic
> > performance domains bindings.
> >
> > [0] https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/tang
> >
> > Link: https://lore.kernel.org/r/20201116181356.804590-1-sudeep.holla@arm.com
> > Cc: Rob Herring <robh+dt@kernel.org>
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks Rob.
Viresh,
I noticed I haven't cc-ed linux-pm list, do you need me to post there or
are you happy to pick it up from here when Hector's mediatek cpufreq drivers
using this are ready to be merged ?
--
Regards,
Sudeep
next prev parent reply other threads:[~2021-05-19 11:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:54 [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains Sudeep Holla
2021-05-17 19:17 ` Rob Herring
2021-05-19 11:23 ` Sudeep Holla [this message]
2021-05-20 3:54 ` Viresh Kumar
2021-05-17 20:45 ` Rob Herring
2021-05-19 11:20 ` Sudeep Holla
2021-05-20 19:43 ` Rob Herring
2021-05-21 4:08 ` Viresh Kumar
2021-05-21 15:24 ` Sudeep Holla
2021-05-24 9:17 ` Viresh Kumar
2021-05-24 10:05 ` Sudeep Holla
2021-10-14 10:56 ` Ulf Hansson
2021-10-14 14:55 ` Sudeep Holla
2021-10-15 9:17 ` Ulf Hansson
2021-10-19 7:24 ` Viresh Kumar
2021-10-19 13:58 ` Ulf Hansson
2021-10-20 6:24 ` Viresh Kumar
2021-10-20 10:25 ` Sudeep Holla
2021-10-21 13:34 ` Ulf Hansson
2021-10-21 15:35 ` Sudeep Holla
2021-10-20 12:11 ` Rob Herring
2021-10-21 13:13 ` Ulf Hansson
2021-10-21 13:33 ` Sudeep Holla
2021-10-21 16:01 ` Ulf Hansson
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=20210519112308.umxriuv75onuwvmc@bogus \
--to=sudeep.holla@arm.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hector.yuan@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).