From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Artem Mygaiev <artem_mygaiev@epam.com>,
"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Lars Kurth <lars.kurth@citrix.com>,
Andrii Anisov <andrii.anisov@gmail.com>,
Alex_Agizim@epam.com, anastassios.nanos@onapp.com,
Julien Grall <julien.grall@arm.com>,
Dirk Behme <dirk.behme@de.bosch.com>,
Meng Xu <mengxu@seas.upenn.edu>,
stewart.hildebrand@dornerworks.com,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: Xen ARM community call - meeting minutes and date for the next one
Date: Wed, 14 Dec 2016 22:18:05 +0100 [thread overview]
Message-ID: <20161214211805.GO9606@toto> (raw)
In-Reply-To: <1481727540.3445.303.camel@citrix.com>
On Wed, Dec 14, 2016 at 03:59:00PM +0100, Dario Faggioli wrote:
> On Tue, 2016-12-13 at 19:00 +0000, Julien Grall wrote:
> > Hi all,
> >
> > Stefano suggested to move the call at 5pm and I haven't seen any
> > disagreement.
> >
> > So the call will be tomorrow (Wednesday 14th December at 5pm).
Hi all,
Thanks for the call today. I'm sending a link to EEMI the
power management framework that Xilinx co-developed with Aggios.
I don't have a link to the ARM specs for SCMI. I found some slides
though. Perhaps Julien has specs?
SCMI:
http://www.slideshare.net/linaroorg/las16200-scmi-system-management-and-control-interface
EEMI:
https://www.xilinx.com/support/documentation/user_guides/ug1200-eemi-api.pdf
Roughly, EEMI works top down by having the various SW layers request
power down/up and other settings to the layer beneath. The various
layers are responsible for recounting so that we don't shut down
something that is in use and also to isolate so that we don't
turn on or off anything that we don't own.
At the moment we tunnel API calls via SMC calls to EL3. For calls
that ATF at EL3 can implement it answers directly. If not, these
calls further propagate over a shared memory / IPI interface to
a dedicated tiny core (PMU) with power management firmware.
The PMU is responsible for mediating power/clock request changes
and making sure that the requesters don't mess with devices or
settings that don't belong to them.
So top down the idea is:
EL0 User-space uses devices (open/close or whatever).
EL1 OS/Kernel refcounts per process and requests power down/up of devs when not used.
EL2 Hypervisor (or dom0 or something not yet implemented) refcounts per guest and forwards the request down the chain if appropriate.
EL3 Trusted Firmware mediates between Normal and Secure world.
PMU Mediates between different CPU clusters and Programmable logic.
Best regards,
Edgar
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-14 21:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 13:48 Xen ARM community call - meeting minutes and date for the next one Julien Grall
2016-12-06 19:02 ` Stefano Stabellini
2016-12-09 14:12 ` Edgar E. Iglesias
2016-12-07 18:38 ` Dario Faggioli
2016-12-07 19:15 ` Dario Faggioli
2016-12-13 19:00 ` Julien Grall
2016-12-14 14:59 ` Dario Faggioli
2016-12-14 21:18 ` Edgar E. Iglesias [this message]
2016-12-15 13:38 ` Julien Grall
2016-12-20 17:45 ` Andrii Anisov
2016-12-20 18:00 ` Andrii Anisov
2016-12-20 18:01 ` Julien Grall
2016-12-21 8:12 ` Dirk Behme
2016-12-21 9:00 ` Andrii Anisov
[not found] ` <2a5febf2-31c2-9002-55c9-b39e809f01f0@de.bosch.com>
2017-01-12 15:39 ` Pooya.Keshavarzi
2017-01-12 18:50 ` Stefano Stabellini
2017-01-13 15:05 ` Pooya.Keshavarzi
2017-01-13 18:39 ` Stefano Stabellini
2017-01-19 14:59 ` Pooya Keshavarzi
2017-01-19 18:30 ` Stefano Stabellini
2017-01-13 10:47 ` Andrii Anisov
2017-01-13 15:24 ` Pooya.Keshavarzi
2016-12-20 18:36 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2017-03-28 15:23 Julien Grall
2017-03-28 16:40 ` Stefano Stabellini
2017-03-29 8:47 ` Artem Mygaiev
2017-03-29 10:06 ` Edgar E. Iglesias
2017-03-29 21:48 ` Julien Grall
2017-03-29 21:53 ` Stefano Stabellini
2017-03-30 15:41 ` Volodymyr Babchuk
2017-03-30 18:52 ` Stefano Stabellini
2017-03-30 19:19 ` Volodymyr Babchuk
2017-03-30 19:57 ` Julien Grall
2017-03-30 20:17 ` Volodymyr Babchuk
2017-03-31 10:08 ` Julien Grall
2017-03-30 19:58 ` Julien Grall
2017-04-04 11:25 ` Julien Grall
2017-03-30 20:24 Artem Mygaiev
2017-04-20 16:44 Julien Grall
2017-04-20 22:32 ` Stefano Stabellini
2017-05-02 18:00 ` Julien Grall
2017-05-03 16:50 ` Volodymyr Babchuk
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=20161214211805.GO9606@toto \
--to=edgar.iglesias@gmail.com \
--cc=Alex_Agizim@epam.com \
--cc=anastassios.nanos@onapp.com \
--cc=andrii.anisov@gmail.com \
--cc=artem_mygaiev@epam.com \
--cc=dario.faggioli@citrix.com \
--cc=dirk.behme@de.bosch.com \
--cc=edgar.iglesias@xilinx.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=mengxu@seas.upenn.edu \
--cc=sstabellini@kernel.org \
--cc=stewart.hildebrand@dornerworks.com \
--cc=xen-devel@lists.xen.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).