Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

Hi Juri, On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wrote: > On 10/01/19 11:05, Quentin Perret wrote: [...] > > +The idea behind introducing an EM is to allow the scheduler to evaluate the > > +implications of its decisions rather than blindly applying energy-saving > > +techniques th

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret wrote: > > Hi Juri, > > On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wrote: > > On 10/01/19 11:05, Quentin Perret wrote: > [...] > > > +The idea behind introducing an EM is to allow the scheduler to evaluate > > > the > > > +implications

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

Hi Rafael, On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote: > On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret > wrote: > > > > Hi Juri, > > > > On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wrote: > > > On 10/01/19 11:05, Quentin Perret wrote: > > [...] > > > > +The

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

On Fri, Jan 18, 2019 at 11:34 AM Quentin Perret wrote: > > Hi Rafael, > > On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote: > > On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret > > wrote: > > > > > > Hi Juri, > > > > > > On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wr

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

On Fri, Jan 18, 2019 at 11:58 AM Rafael J. Wysocki wrote: > > On Fri, Jan 18, 2019 at 11:34 AM Quentin Perret > wrote: > > > > Hi Rafael, > > > > On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote: > > > On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret > > > wrote: > > > > > > >

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

On Friday 18 Jan 2019 at 12:01:35 (+0100), Rafael J. Wysocki wrote: > On Fri, Jan 18, 2019 at 11:58 AM Rafael J. Wysocki wrote: > > > > On Fri, Jan 18, 2019 at 11:34 AM Quentin Perret > > wrote: > > > > > > Hi Rafael, > > > > > > On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

On Fri, Jan 18, 2019 at 12:11 PM Quentin Perret wrote: > > On Friday 18 Jan 2019 at 12:01:35 (+0100), Rafael J. Wysocki wrote: > > On Fri, Jan 18, 2019 at 11:58 AM Rafael J. Wysocki > > wrote: > > > > > > On Fri, Jan 18, 2019 at 11:34 AM Quentin Perret > > > wrote: > > > > > > > > Hi Rafael, >

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

On Friday 18 Jan 2019 at 12:20:57 (+0100), Rafael J. Wysocki wrote: > On Fri, Jan 18, 2019 at 12:11 PM Quentin Perret > wrote: > > > > On Friday 18 Jan 2019 at 12:01:35 (+0100), Rafael J. Wysocki wrote: > > > On Fri, Jan 18, 2019 at 11:58 AM Rafael J. Wysocki > > > wrote: > > > > > > > > On Fri

Re: [PATCH 2/2] sched: Document Energy Aware Scheduling

Hi, On 18/01/19 10:34, Quentin Perret wrote: > Hi Rafael, > > On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote: > > On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret > > wrote: > > > > > > Hi Juri, > > > > > > On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wrote: > > >

[PATCH] Documentation: DMA-API: fix two typos

This patch fixes two typos, a missing "e" and dma-api/driver_filter was incorrectly typed dma-api/driver-filter. Signed-off-by: Corentin Labbe --- Documentation/DMA-API.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/DMA-API.txt b/Documentation/DMA-API.t

[PATCH v2] dma-debug: add dumping facility via debugfs

While debugging a DMA mapping leak, I needed to access debug_dma_dump_mappings() but easily from user space. This patch adds a /sys/kernel/debug/dma-api/dump file which contain all current DMA mapping. Signed-off-by: Corentin Labbe --- Changes since v1: - Use DEFINE_SHOW_ATTRIBUTE - Add Document

Re: [PATCH 1/1 RESEND] doc: net: fix bad references to network drivers

From: Otto Sabart Date: Mon, 14 Jan 2019 12:56:36 +0100 > Fix "reference to nonexisting document" warnings. > > Fixes: b255e500c8dc ("net: documentation: build a directory structure > for drivers") Please do not chop up Fixes: tags, keep the entire text on one continuous line. I fixed it up fo

[PATCH v2 0/1] doc: networking: integrate scaling document into doc tree

Changes in v2: * Changed formatting of sections according to kernel documentation conventions [0]. * All commits from this series were squashed into one. [0] https://www.kernel.org/doc/html/latest/doc-guide/sphinx.html Otto Sabart (1): doc: networking: integrate scaling document into doc tree

[PATCH v2 1/1] doc: networking: integrate scaling document into doc tree

Convert scaling document into reStructuredText and add reference to scaling document into main table of contents in network documentation. There are no semantic changes. There are no references to "scaling.txt" file. Whole kernel tree was checked using: $ grep -r "scaling\.txt" Signed-off-by: Ot

[PATCH] doc:process: remove note from 'stable api nonsense'

The link referred by the note can't be retrieved: this patch just remove that old note. Signed-off-by: Federico Vaga --- Documentation/process/stable-api-nonsense.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Documentation/process/stable-api-nonsense.rst b/Documentat

[PATCH v5] coding-style: Clarify the expectations around bool

There has been some confusion since checkpatch started warning about bool use in structures, and people have been avoiding using it. Many people feel there is still a legitimate place for bool in structures, so provide some guidance on bool usage derived from the entire thread that spawned the che

[RFC] Provide in-kernel headers for making it easy to extend the kernel

From: "Joel Fernandes (Google)" Introduce in-kernel headers and other artifacts which are made available as an archive through proc (/proc/kheaders.tgz file). This archive makes it possible to build kernel modules, run eBPF programs, and other tracing programs that need to extend the kernel for t