linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Quentin Perret <quentin.perret@arm.com>
To: corbet@lwn.net, peterz@infradead.org, rjw@rjwysocki.net
Cc: mingo@redhat.com, morten.rasmussen@arm.com, qais.yousef@arm.com,
	patrick.bellasi@arm.com, dietmar.eggemann@arm.com,
	linux-doc@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, quentin.perret@arm.com
Subject: [PATCH 0/2] Documentation: Explain EAS and EM
Date: Thu, 10 Jan 2019 11:05:44 +0000	[thread overview]
Message-ID: <20190110110546.8101-1-quentin.perret@arm.com> (raw)

The recently introduced Energy Aware Scheduling (EAS) feature relies on
a large set of concepts, assumptions, and design choices that are
probably not obvious for an outsider. Moreover, enabling EAS on a
particular platform isn't straightforward because of all its
dependencies. This series tries to address this by introducing proper
documentation files for the scheduler's part of EAS and for the newly
introduced Energy Model (EM) framework. These are meant to explain not
only the design choices of EAS but also to list its dependencies in a
human-readable location.

The two new doc files are simple .txt to be consistent with the existing
documentation of the relevant subsystems, but I'm happy to translate to
.rst if deemed necessary.

All feedback is welcome.

Thanks !
Quentin

Quentin Perret (2):
  PM / EM: Document the Energy Model framework
  sched: Document Energy Aware Scheduling

 Documentation/power/energy-model.txt     | 144 ++++++++
 Documentation/scheduler/sched-energy.txt | 425 +++++++++++++++++++++++
 2 files changed, 569 insertions(+)
 create mode 100644 Documentation/power/energy-model.txt
 create mode 100644 Documentation/scheduler/sched-energy.txt

-- 
2.20.1


             reply	other threads:[~2019-01-10 11:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 11:05 Quentin Perret [this message]
2019-01-10 11:05 ` [PATCH 1/2] PM / EM: Document the Energy Model framework Quentin Perret
2019-01-17 14:47   ` Juri Lelli
2019-01-17 14:53     ` Quentin Perret
2019-01-21 11:37   ` [tip:sched/core] PM/EM: " tip-bot for Quentin Perret
2019-01-21 13:53   ` tip-bot for Quentin Perret
2019-01-21 14:10     ` Quentin Perret
2019-01-27 11:36   ` tip-bot for Quentin Perret
2019-01-10 11:05 ` [PATCH 2/2] sched: Document Energy Aware Scheduling Quentin Perret
2019-01-17 15:51   ` Juri Lelli
2019-01-18  9:16     ` Quentin Perret
2019-01-18  9:57       ` Rafael J. Wysocki
2019-01-18 10:34         ` Quentin Perret
2019-01-18 10:58           ` Rafael J. Wysocki
2019-01-18 11:01             ` Rafael J. Wysocki
2019-01-18 11:11               ` Quentin Perret
2019-01-18 11:20                 ` Rafael J. Wysocki
2019-01-18 11:26                   ` Quentin Perret
2019-01-18 12:34           ` Juri Lelli
2019-01-21 11:38   ` [tip:sched/core] sched/doc: " tip-bot for Quentin Perret
2019-01-21 13:54   ` tip-bot for Quentin Perret
2019-01-27 11:37   ` tip-bot for Quentin Perret

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=20190110110546.8101-1-quentin.perret@arm.com \
    --to=quentin.perret@arm.com \
    --cc=corbet@lwn.net \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=morten.rasmussen@arm.com \
    --cc=patrick.bellasi@arm.com \
    --cc=peterz@infradead.org \
    --cc=qais.yousef@arm.com \
    --cc=rjw@rjwysocki.net \
    /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).