[RFC PATCH 04/20] x86/intel_rdt: Introduce test to determine if closid is in use

During CAT feature discovery the capacity bitmasks (CBMs) associated with all the classes of service are initialized to all ones, even if the class of service is not in use. Introduce a test that can be used to determine if a class of service is in use. This test enables code interested in parsing

[RFC PATCH 05/20] x86/intel_rdt: Print more accurate pseudo-locking availability

A region of cache is considered available for pseudo-locking when: * Cache area is in use by default COS. * Cache area is NOT in use by any other (other than default) COS. * Cache area is not shared with any other entity. Specifically, the cache area does not appear in "Bitmask of Shareable

[RFC PATCH 06/20] x86/intel_rdt: Create pseudo-locked regions

System administrator creates/removes pseudo-locked regions by creating/removing directories in the pseudo-lock subdirectory of the resctrl filesystem. Here we add directory creation and removal support. A "pseudo-lock region" is introduced, which represents an instance of a pseudo-locked cache

[RFC PATCH 06/20] x86/intel_rdt: Create pseudo-locked regions

System administrator creates/removes pseudo-locked regions by creating/removing directories in the pseudo-lock subdirectory of the resctrl filesystem. Here we add directory creation and removal support. A "pseudo-lock region" is introduced, which represents an instance of a pseudo-locked cache

[RFC PATCH 02/20] x86/intel_rdt: Make useful functions available internally

In preparation for support of pseudo-locking we move some static functions to be available for sharing amongst all RDT components. Signed-off-by: Reinette Chatre --- arch/x86/kernel/cpu/intel_rdt.h | 5 + arch/x86/kernel/cpu/intel_rdt_ctrlmondata.c | 2

[RFC PATCH 02/20] x86/intel_rdt: Make useful functions available internally

In preparation for support of pseudo-locking we move some static functions to be available for sharing amongst all RDT components. Signed-off-by: Reinette Chatre --- arch/x86/kernel/cpu/intel_rdt.h | 5 + arch/x86/kernel/cpu/intel_rdt_ctrlmondata.c | 2 +-

[RFC PATCH 14/20] x86/intel_rdt: Enable testing for pseudo-locked region

Introduce a new test that can be used to determine if a provided CBM intersects with an existing pseudo-locked region of cache domain. Signed-off-by: Reinette Chatre --- arch/x86/kernel/cpu/intel_rdt.h | 1 + arch/x86/kernel/cpu/intel_rdt_pseudo_lock.c |

[RFC PATCH 14/20] x86/intel_rdt: Enable testing for pseudo-locked region

Introduce a new test that can be used to determine if a provided CBM intersects with an existing pseudo-locked region of cache domain. Signed-off-by: Reinette Chatre --- arch/x86/kernel/cpu/intel_rdt.h | 1 + arch/x86/kernel/cpu/intel_rdt_pseudo_lock.c | 19 +++ 2

[RFC PATCH 13/20] x86/intel_rdt: Support schemata write - pseudo-locking core

When a user writes the requested pseudo-locking schemata it will trigger the pseudo-locking of equivalent sized memory. A successful return from this schemata write means that the pseudo-locking succeeded. To support the pseudo-locking we first initialize as much as we can about the region that

[RFC PATCH 13/20] x86/intel_rdt: Support schemata write - pseudo-locking core

When a user writes the requested pseudo-locking schemata it will trigger the pseudo-locking of equivalent sized memory. A successful return from this schemata write means that the pseudo-locking succeeded. To support the pseudo-locking we first initialize as much as we can about the region that

[RFC PATCH 17/20] x86/intel_rdt: Create character device exposing pseudo-locked region

Once a pseudo-locked region has been created it needs to be made available to user space to provide benefit there. A character device supporting mmap() is created for each pseudo-locked region. A user space application can now use mmap() system call to map pseudo-locked region into its virtual

[RFC PATCH 17/20] x86/intel_rdt: Create character device exposing pseudo-locked region

Once a pseudo-locked region has been created it needs to be made available to user space to provide benefit there. A character device supporting mmap() is created for each pseudo-locked region. A user space application can now use mmap() system call to map pseudo-locked region into its virtual

[RFC PATCH 12/20] x86/intel_rdt: Support CBM checking from value and character buffer

Validity check of capacity bitmask (CBM) is currently only done on character buffer when user writes new schemata to resctrl file. In preparation for support of CBM checking within other areas of the RDT code the CBM validity check is split up to support checking with CBM provided as character

[RFC PATCH 12/20] x86/intel_rdt: Support CBM checking from value and character buffer

Validity check of capacity bitmask (CBM) is currently only done on character buffer when user writes new schemata to resctrl file. In preparation for support of CBM checking within other areas of the RDT code the CBM validity check is split up to support checking with CBM provided as character

[RFC PATCH 16/20] x86/intel_rdt: Create debugfs files for pseudo-locking testing

There is no simple yes/no test to determine if pseudo-locking was successful. In order to test pseudo-locking we expose a debugfs file for each pseudo-locked region that will record the latency of reading the pseudo-locked memory at a stride of 32 bytes (hardcoded). These numbers will give us an

[RFC PATCH 16/20] x86/intel_rdt: Create debugfs files for pseudo-locking testing

There is no simple yes/no test to determine if pseudo-locking was successful. In order to test pseudo-locking we expose a debugfs file for each pseudo-locked region that will record the latency of reading the pseudo-locked memory at a stride of 32 bytes (hardcoded). These numbers will give us an

[RFC PATCH 15/20] x86/intel_rdt: Prevent new allocations from pseudo-locked regions

When a user requests a new cache allocation we need to enforce that it does not intersect with an existing pseudo-locked region. An allocation with a bitmask intersection with a pseudo-locked region will enable cache allocations to that region and thus evict pseudo-locked data. Signed-off-by:

[RFC PATCH 15/20] x86/intel_rdt: Prevent new allocations from pseudo-locked regions

When a user requests a new cache allocation we need to enforce that it does not intersect with an existing pseudo-locked region. An allocation with a bitmask intersection with a pseudo-locked region will enable cache allocations to that region and thus evict pseudo-locked data. Signed-off-by:

[RFC PATCH 07/20] x86/intel_rdt: Connect pseudo-locking directory to operations

As a dependent of RDT/CAT we hook up the pseudo-locking files initialization to that of RDT/CAT. The initial operations of mkdir/rmdir used to create pseudo-locked regions are now hooked up also. Signed-off-by: Reinette Chatre ---

[RFC PATCH 07/20] x86/intel_rdt: Connect pseudo-locking directory to operations

As a dependent of RDT/CAT we hook up the pseudo-locking files initialization to that of RDT/CAT. The initial operations of mkdir/rmdir used to create pseudo-locked regions are now hooked up also. Signed-off-by: Reinette Chatre --- arch/x86/kernel/cpu/intel_rdt_rdtgroup.c | 17 -

[RFC PATCH 03/20] x86/intel_rdt: Introduce hooks to create pseudo-locking files

We create a new file to host pseudo-locking specific code. The first of this code are the functions that create the initial pseudo_lock directory with its first file, "avail", starting by reporting zero. This will be expanded in future commits. Signed-off-by: Reinette Chatre

[RFC PATCH 01/20] x86/intel_rdt: Documentation for Cache Pseudo-Locking

Add description of Cache Pseudo-Locking feature, its interface, as well as an example of its usage. Signed-off-by: Reinette Chatre --- Documentation/x86/intel_rdt_ui.txt | 229 - 1 file changed, 228 insertions(+), 1 deletion(-)

[RFC PATCH 00/20] Intel(R) Resource Director Technology Cache Pseudo-Locking enabling

Dear Maintainers, Cache Allocation Technology (CAT), part of Intel(R) Resource Director Technology (Intel(R) RDT), enables a user to specify the amount of cache space into which an application can fill. Cache pseudo-locking builds on the fact that a CPU can still read and write data pre-allocated

[RFC PATCH 03/20] x86/intel_rdt: Introduce hooks to create pseudo-locking files

We create a new file to host pseudo-locking specific code. The first of this code are the functions that create the initial pseudo_lock directory with its first file, "avail", starting by reporting zero. This will be expanded in future commits. Signed-off-by: Reinette Chatre ---

[RFC PATCH 01/20] x86/intel_rdt: Documentation for Cache Pseudo-Locking

Add description of Cache Pseudo-Locking feature, its interface, as well as an example of its usage. Signed-off-by: Reinette Chatre --- Documentation/x86/intel_rdt_ui.txt | 229 - 1 file changed, 228 insertions(+), 1 deletion(-) diff --git

[RFC PATCH 00/20] Intel(R) Resource Director Technology Cache Pseudo-Locking enabling

Dear Maintainers, Cache Allocation Technology (CAT), part of Intel(R) Resource Director Technology (Intel(R) RDT), enables a user to specify the amount of cache space into which an application can fill. Cache pseudo-locking builds on the fact that a CPU can still read and write data pre-allocated

Re: linux-next: Tree for Nov 7

Hi Andrew, On Mon, 13 Nov 2017 16:03:14 -0800 Andrew Morton wrote: > > Does this kernel have "fs/binfmt_elf.c: drop MAP_FIXED usage from > elf_map" applied? That patch was dropped due to runtime issues. next-20171107 has that patch in it, next-20171108 does not. --

Re: linux-next: Tree for Nov 7

Hi Andrew, On Mon, 13 Nov 2017 16:03:14 -0800 Andrew Morton wrote: > > Does this kernel have "fs/binfmt_elf.c: drop MAP_FIXED usage from > elf_map" applied? That patch was dropped due to runtime issues. next-20171107 has that patch in it, next-20171108 does not. -- Cheers, Stephen Rothwell

Re: mmotm 2017-11-10-15-56 uploaded (lib/test_find_bit.c)

On 11/13/2017 04:17 PM, Andrew Morton wrote: > On Fri, 10 Nov 2017 18:00:57 -0800 Randy Dunlap wrote: > >> On 11/10/2017 03:56 PM, a...@linux-foundation.org wrote: >>> The mm-of-the-moment snapshot 2017-11-10-15-56 has been uploaded to >>> >>>

Re: mmotm 2017-11-10-15-56 uploaded (lib/test_find_bit.c)

On 11/13/2017 04:17 PM, Andrew Morton wrote: > On Fri, 10 Nov 2017 18:00:57 -0800 Randy Dunlap wrote: > >> On 11/10/2017 03:56 PM, a...@linux-foundation.org wrote: >>> The mm-of-the-moment snapshot 2017-11-10-15-56 has been uploaded to >>> >>>http://www.ozlabs.org/~akpm/mmotm/ >>> >>>

Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown

On Mon, 13 Nov 2017 14:09:10 -0800 Linus Torvalds wrote: > On Mon, Nov 13, 2017 at 1:44 PM, David Howells wrote: > > > > Whilst that may be true, we either have to check signatures on every bit of > > firmware that the appropriate driver

Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown

On Mon, 13 Nov 2017 14:09:10 -0800 Linus Torvalds wrote: > On Mon, Nov 13, 2017 at 1:44 PM, David Howells wrote: > > > > Whilst that may be true, we either have to check signatures on every bit of > > firmware that the appropriate driver doesn't say is meant to be signed or > > not > > bother.

Re: [PATCH 11/14] nubus: Repopulate /proc/bus/nubus/s/

On Mon, 13 Nov 2017, Geert Uytterhoeven wrote: > On Sat, Nov 11, 2017 at 7:12 AM, Finn Thain > wrote: > > > --- > > drivers/nubus/nubus.c | 117 +++--- > > drivers/nubus/proc.c | 170 > >

Re: [PATCH 11/14] nubus: Repopulate /proc/bus/nubus/s/

On Mon, 13 Nov 2017, Geert Uytterhoeven wrote: > On Sat, Nov 11, 2017 at 7:12 AM, Finn Thain > wrote: > > > --- > > drivers/nubus/nubus.c | 117 +++--- > > drivers/nubus/proc.c | 170 > > +++--- > >

Re: [PATCH 12/14] nubus: Rename struct nubus_dev

On Mon, 13 Nov 2017, Geert Uytterhoeven wrote: > Hi Finn, > > On Sat, Nov 11, 2017 at 7:12 AM, Finn Thain > wrote: > > It is misleading to use "dev" to mean a functional resource. And in > > adopting the Linux Driver Model, struct nubus_board will embed a > >

Re: [PATCH 12/14] nubus: Rename struct nubus_dev

On Mon, 13 Nov 2017, Geert Uytterhoeven wrote: > Hi Finn, > > On Sat, Nov 11, 2017 at 7:12 AM, Finn Thain > wrote: > > It is misleading to use "dev" to mean a functional resource. And in > > adopting the Linux Driver Model, struct nubus_board will embed a > > struct device. Drivers will then

Re: [PATCH 2/2] drm/vc4: Ensure interrupts are disabled

Stefan Schake writes: > The overflow mem work callback vc4_overflow_mem_work reenables its > associated interrupt upon completion. To ensure all interrupts are disabled > when we return from vc4_irq_uninstall, we need to disable it again if > cancel_work_sync indicated

Re: [PATCH 2/2] drm/vc4: Ensure interrupts are disabled

Stefan Schake writes: > The overflow mem work callback vc4_overflow_mem_work reenables its > associated interrupt upon completion. To ensure all interrupts are disabled > when we return from vc4_irq_uninstall, we need to disable it again if > cancel_work_sync indicated pending work. Is there a

Re: mmotm 2017-11-10-15-56 uploaded (lib/test_find_bit.c)

On Fri, 10 Nov 2017 18:00:57 -0800 Randy Dunlap wrote: > On 11/10/2017 03:56 PM, a...@linux-foundation.org wrote: > > The mm-of-the-moment snapshot 2017-11-10-15-56 has been uploaded to > > > >http://www.ozlabs.org/~akpm/mmotm/ > > > > mmotm-readme.txt says > > > >

Re: mmotm 2017-11-10-15-56 uploaded (lib/test_find_bit.c)

On Fri, 10 Nov 2017 18:00:57 -0800 Randy Dunlap wrote: > On 11/10/2017 03:56 PM, a...@linux-foundation.org wrote: > > The mm-of-the-moment snapshot 2017-11-10-15-56 has been uploaded to > > > >http://www.ozlabs.org/~akpm/mmotm/ > > > > mmotm-readme.txt says > > > > README for

Re: [PATCH 1/3] perf help: Document missing options

Hi Arnaldo, On Mon, Nov 13, 2017 at 03:29:56PM -0300, Arnaldo Carvalho de Melo wrote: > Em Sun, Nov 12, 2017 at 10:10:45AM +0900, Sihyeon Jang escreveu: > > Cc: Jiri Olsa > > Cc: Namhyung Kim > > Signed-off-by: Sihyeon Jang > > ---

Re: [PATCH 1/3] perf help: Document missing options

Hi Arnaldo, On Mon, Nov 13, 2017 at 03:29:56PM -0300, Arnaldo Carvalho de Melo wrote: > Em Sun, Nov 12, 2017 at 10:10:45AM +0900, Sihyeon Jang escreveu: > > Cc: Jiri Olsa > > Cc: Namhyung Kim > > Signed-off-by: Sihyeon Jang > > --- > > tools/perf/Documentation/perf-help.txt | 14

[PATCH] HID: cp2112: Fix I2C_BLOCK_DATA transactions

The existing driver erroneously treats I2C_BLOCK_DATA and BLOCK_DATA commands the same. Fix the logic for I2C_BLOCK_DATA reads and writes. Signed-off-by: Eudean Sun --- drivers/hid/hid-cp2112.c | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git

[PATCH] HID: cp2112: Fix I2C_BLOCK_DATA transactions

The existing driver erroneously treats I2C_BLOCK_DATA and BLOCK_DATA commands the same. Fix the logic for I2C_BLOCK_DATA reads and writes. Signed-off-by: Eudean Sun --- drivers/hid/hid-cp2112.c | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git

Re: linux-next: Tree for Nov 7

On Sun, 12 Nov 2017 11:38:02 +1030 Joel Stanley wrote: > On Fri, Nov 10, 2017 at 11:00 PM, Michal Hocko wrote: > > Hi Joel, > > > > On Wed 08-11-17 15:20:50, Michal Hocko wrote: > > [...] > >> > There are a lot of messages on the way up that look like this: >

Re: linux-next: Tree for Nov 7

On Sun, 12 Nov 2017 11:38:02 +1030 Joel Stanley wrote: > On Fri, Nov 10, 2017 at 11:00 PM, Michal Hocko wrote: > > Hi Joel, > > > > On Wed 08-11-17 15:20:50, Michal Hocko wrote: > > [...] > >> > There are a lot of messages on the way up that look like this: > >> > > >> > [2.527460] Uhuuh,

Re: [RFC PATCH v2] fw_lockdown: new micro LSM module to prevent loading unsigned firmware

On Mon, Nov 13, 2017 at 08:51:54PM +0100, Luis R. Rodriguez wrote: > On Mon, Nov 13, 2017 at 02:36:47PM -0500, Mimi Zohar wrote: > > On Mon, 2017-11-13 at 20:05 +0100, Luis R. Rodriguez wrote: > > > > + * fw_lockdown_read_file - prevent loading of unsigned firmware > > > > + * @file: pointer to

Re: [RFC PATCH v2] fw_lockdown: new micro LSM module to prevent loading unsigned firmware

On Mon, Nov 13, 2017 at 08:51:54PM +0100, Luis R. Rodriguez wrote: > On Mon, Nov 13, 2017 at 02:36:47PM -0500, Mimi Zohar wrote: > > On Mon, 2017-11-13 at 20:05 +0100, Luis R. Rodriguez wrote: > > > > + * fw_lockdown_read_file - prevent loading of unsigned firmware > > > > + * @file: pointer to

Re: bit tweaks [was: Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11]

On Mon, Nov 13, 2017 at 3:30 PM, Linus Torvalds wrote: > > So let's just rewrite that mnt_flags conversion that way, justr to get > gcc to generate the obvious code. Oh wow. I tried to do the same thing in fs/namespace.c where it does the reverse bit translation,

Re: bit tweaks [was: Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11]

On Mon, Nov 13, 2017 at 3:30 PM, Linus Torvalds wrote: > > So let's just rewrite that mnt_flags conversion that way, justr to get > gcc to generate the obvious code. Oh wow. I tried to do the same thing in fs/namespace.c where it does the reverse bit translation, and gcc makes a _horrible_ mess

Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

> I wonder if there is some way to use the split format for the > intermediate files, but then for the very final link bring them all in > and make the end result be a traditional single binary. I'm not > talking the separate "dwp" package that packs multiple dwo files into > one, but to actually

Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

> I wonder if there is some way to use the split format for the > intermediate files, but then for the very final link bring them all in > and make the end result be a traditional single binary. I'm not > talking the separate "dwp" package that packs multiple dwo files into > one, but to actually

[PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up

Changes from v2 - Run spellchecker over the text and fix typos - Add acked-by Daniel Changes from v1 - Enhance commit msg - Prevent WARN in cpumask_test_cpu() in cpudl_find() when best_cpu == -1 -8<- >From 7735382d07ae6a61d740ae39ba2ecf169d43b8a2 Mon Sep 17 00:00:00 2001 From:

[PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up

Changes from v2 - Run spellchecker over the text and fix typos - Add acked-by Daniel Changes from v1 - Enhance commit msg - Prevent WARN in cpumask_test_cpu() in cpudl_find() when best_cpu == -1 -8<- >From 7735382d07ae6a61d740ae39ba2ecf169d43b8a2 Mon Sep 17 00:00:00 2001 From:

[PATCH v3 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value

Currently, migrating tasks to cpu0 unconditionally happens when the heap is empty, since cp->elements[].cpu was initialized to 0(=cpu0). We have to distinguish between the empty case and cpu0 to avoid the unnecessary migrations. Therefore, it has to return an invalid value e.i. -1 in that case.

[PATCH v3 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value

Currently, migrating tasks to cpu0 unconditionally happens when the heap is empty, since cp->elements[].cpu was initialized to 0(=cpu0). We have to distinguish between the empty case and cpu0 to avoid the unnecessary migrations. Therefore, it has to return an invalid value e.i. -1 in that case.

Re: [PATCH v5 06/11] intel_sgx: driver for Intel Software Guard Extensions

On Mon, 13 Nov 2017, Jarkko Sakkinen wrote: > + > + secs_epc = sgx_alloc_page(0); Use SGX_ALLOC_ATOMIC instead of 0 ? > + if (IS_ERR(secs_epc)) { > + ret = PTR_ERR(secs_epc); > + goto out; > + } > +out: > + if (encl) > + kref_put(>refcount,

Re: [PATCH v5 06/11] intel_sgx: driver for Intel Software Guard Extensions

On Mon, 13 Nov 2017, Jarkko Sakkinen wrote: > + > + secs_epc = sgx_alloc_page(0); Use SGX_ALLOC_ATOMIC instead of 0 ? > + if (IS_ERR(secs_epc)) { > + ret = PTR_ERR(secs_epc); > + goto out; > + } > +out: > + if (encl) > + kref_put(>refcount,

Re: [GIT PULL] Btrfs changes for 4.15

On 2017年11月13日 23:35, David Sterba wrote: > Hi, > > please pull the following btrfs changes. There are some new user features and > the usual load of invisible enhancements or cleanups. The branch merges > cleanly, has been frozen in case rc7 was the last one, so I send out the pull > request

Re: [GIT PULL] Btrfs changes for 4.15

On 2017年11月13日 23:35, David Sterba wrote: > Hi, > > please pull the following btrfs changes. There are some new user features and > the usual load of invisible enhancements or cleanups. The branch merges > cleanly, has been frozen in case rc7 was the last one, so I send out the pull > request

[PATCH v2 3/8] clocksource: owl: Adopt TIMER_OF_DECLARE()

Commit 1727339590fdb5a1ded881b540cd32121278d414 ("clocksource/drivers: Rename CLOCKSOURCE_OF_DECLARE to TIMER_OF_DECLARE") deprecated CLOCKSOURCE_OF_DECLARE(), so adopt the new macro TIMER_OF_DECLARE(). Reported-by: Daniel Lezcano Signed-off-by: Andreas Färber

[PATCH v2 3/8] clocksource: owl: Adopt TIMER_OF_DECLARE()

Commit 1727339590fdb5a1ded881b540cd32121278d414 ("clocksource/drivers: Rename CLOCKSOURCE_OF_DECLARE to TIMER_OF_DECLARE") deprecated CLOCKSOURCE_OF_DECLARE(), so adopt the new macro TIMER_OF_DECLARE(). Reported-by: Daniel Lezcano Signed-off-by: Andreas Färber --- v2: New (Daniel)

[PATCH v2 6/8] dt-bindings: power: Add Actions Semi S700 SPS

Define power domains for Actions Semi S700 SoC Smart Power System (SPS). Signed-off-by: Andreas Färber --- v2: New .../devicetree/bindings/power/actions,owl-sps.txt| 2 ++ include/dt-bindings/power/owl-s700-powergate.h | 20 2 files changed,

[PATCH v2 6/8] dt-bindings: power: Add Actions Semi S700 SPS

Define power domains for Actions Semi S700 SoC Smart Power System (SPS). Signed-off-by: Andreas Färber --- v2: New .../devicetree/bindings/power/actions,owl-sps.txt| 2 ++ include/dt-bindings/power/owl-s700-powergate.h | 20 2 files changed, 22 insertions(+)

[PATCH v2 5/8] arm64: dts: actions: Add S700 and CubieBoard7

Add Device Trees for S700 SoC and Cubietech CubieBoard7. Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged arch/arm64/boot/dts/actions/Makefile | 2 + arch/arm64/boot/dts/actions/s700-cubieboard7.dts | 47 +++ arch/arm64/boot/dts/actions/s700.dtsi

[PATCH v2 5/8] arm64: dts: actions: Add S700 and CubieBoard7

Add Device Trees for S700 SoC and Cubietech CubieBoard7. Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged arch/arm64/boot/dts/actions/Makefile | 2 + arch/arm64/boot/dts/actions/s700-cubieboard7.dts | 47 +++ arch/arm64/boot/dts/actions/s700.dtsi| 164

[PATCH v2 1/8] dt-bindings: arm: actions: Add S700 and CubieBoard7

Document the Actions Semi S700 SoC and the Cubietech CubieBoard7. Acked-by: Rob Herring Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged Documentation/devicetree/bindings/arm/actions.txt | 15 +++ 1 file changed, 15 insertions(+) diff

[PATCH v2 1/8] dt-bindings: arm: actions: Add S700 and CubieBoard7

Document the Actions Semi S700 SoC and the Cubietech CubieBoard7. Acked-by: Rob Herring Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged Documentation/devicetree/bindings/arm/actions.txt | 15 +++ 1 file changed, 15 insertions(+) diff --git

[PATCH v2 8/8] arm64: dts: actions: Add S700 SPS node

Add a node to the S700 Device Tree for the Smart Power System (SPS). Signed-off-by: Andreas Färber --- v2: New To be squashed into 5/8 if binding gets acked. arch/arm64/boot/dts/actions/s700.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v2 2/8] dt-bindings: timer: Add Actions Semi S700

Define a compatible string for the Actions Semi S700 SoC timer. Acked-by: Rob Herring Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged Documentation/devicetree/bindings/timer/actions,owl-timer.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 4/8] clocksource: owl: Prepare S700

Actions S700 has two 2Hz timers like S500, and four TIMx timers like S900. Signed-off-by: Andreas Färber --- v1 -> v2: * Adopted TIMER_OF_DECLARE() (Daniel) drivers/clocksource/owl-timer.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/clocksource/owl-timer.c

[PATCH v2 2/8] dt-bindings: timer: Add Actions Semi S700

Define a compatible string for the Actions Semi S700 SoC timer. Acked-by: Rob Herring Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged Documentation/devicetree/bindings/timer/actions,owl-timer.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 4/8] clocksource: owl: Prepare S700

Actions S700 has two 2Hz timers like S500, and four TIMx timers like S900. Signed-off-by: Andreas Färber --- v1 -> v2: * Adopted TIMER_OF_DECLARE() (Daniel) drivers/clocksource/owl-timer.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/clocksource/owl-timer.c

[PATCH v2 8/8] arm64: dts: actions: Add S700 SPS node

Add a node to the S700 Device Tree for the Smart Power System (SPS). Signed-off-by: Andreas Färber --- v2: New To be squashed into 5/8 if binding gets acked. arch/arm64/boot/dts/actions/s700.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v2 7/8] soc: actions: sps: Add S700

Add power domains for S700 SoC. Signed-off-by: Andreas Färber --- v2: New drivers/soc/actions/owl-sps.c | 42 ++ 1 file changed, 42 insertions(+) diff --git a/drivers/soc/actions/owl-sps.c b/drivers/soc/actions/owl-sps.c index

[PATCH v2 7/8] soc: actions: sps: Add S700

Add power domains for S700 SoC. Signed-off-by: Andreas Färber --- v2: New drivers/soc/actions/owl-sps.c | 42 ++ 1 file changed, 42 insertions(+) diff --git a/drivers/soc/actions/owl-sps.c b/drivers/soc/actions/owl-sps.c index

[PATCH v2 0/8] arm64: Add initial Actions Semi S700 and CubieBoard7 support

Hello, This series prepares the Actions Semi S700 SoC and Cubietech CubieBoard7. It boots equally far as the S900 based Bubblegum-96 these patches are based on, i.e. into an initrd with serial and all four cores up. v2 modifies the clocksource driver patches and adds SPS patches. Not having

[PATCH v2 0/8] arm64: Add initial Actions Semi S700 and CubieBoard7 support

Hello, This series prepares the Actions Semi S700 SoC and Cubietech CubieBoard7. It boots equally far as the S900 based Bubblegum-96 these patches are based on, i.e. into an initrd with serial and all four cores up. v2 modifies the clocksource driver patches and adds SPS patches. Not having

Re: [RESEND PATCH v2 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value

On 11/13/2017 9:46 PM, Daniel Bristot de Oliveira wrote: On 10/12/2017 09:57 AM, Byungchul Park wrote: On Tue, Oct 10, 2017 at 03:44:04PM +0900, Byungchul Park wrote: Currently, migrating tasks to cpu0 unconditionally happens when the heap is empty, since cp->elements[].cpu was initialized to

Re: [RESEND PATCH v2 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value

On 11/13/2017 9:46 PM, Daniel Bristot de Oliveira wrote: On 10/12/2017 09:57 AM, Byungchul Park wrote: On Tue, Oct 10, 2017 at 03:44:04PM +0900, Byungchul Park wrote: Currently, migrating tasks to cpu0 unconditionally happens when the heap is empty, since cp->elements[].cpu was initialized to

Re: bit tweaks [was: Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11]

On Mon, Nov 13, 2017 at 2:59 PM, Rasmus Villemoes wrote: >> Sadly, gcc makes a mess of it and actually generates code that looks >> like the original C.[...] > > Actually, new enough gcc (7.1, I think) does contain a pattern that does > this, but unfortunately only if

Re: bit tweaks [was: Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11]

On Mon, Nov 13, 2017 at 2:59 PM, Rasmus Villemoes wrote: >> Sadly, gcc makes a mess of it and actually generates code that looks >> like the original C.[...] > > Actually, new enough gcc (7.1, I think) does contain a pattern that does > this, but unfortunately only if one spells it > > y |= (x

Re: [PATCH] xen/9pfs: Add MODULE_LICENSE()

On Mon, 13 Nov 2017, Boris Ostrovsky wrote: > Since commit ba1029c9cbc5 ("modpost: detect modules without a > MODULE_LICENSE") modules without said macro will generate > > WARNING: modpost: missing MODULE_LICENSE() in net/9p/9pnet_xen.o > > Reported-by: Stephen Rothwell >

Re: [PATCH] xen/9pfs: Add MODULE_LICENSE()

On Mon, 13 Nov 2017, Boris Ostrovsky wrote: > Since commit ba1029c9cbc5 ("modpost: detect modules without a > MODULE_LICENSE") modules without said macro will generate > > WARNING: modpost: missing MODULE_LICENSE() in net/9p/9pnet_xen.o > > Reported-by: Stephen Rothwell > Signed-off-by: Boris

Re: [PATCH 4/9] posix-clocks: Enable compat syscalls always

On Mon, Nov 13, 2017 at 1:03 PM, Thomas Gleixner wrote: > On Fri, 10 Nov 2017, Deepa Dinamani wrote: >> >> -#ifdef CONFIG_COMPAT >> - >> COMPAT_SYSCALL_DEFINE2(nanosleep, struct compat_timespec __user *, rqtp, >> struct compat_timespec __user *, rmtp) >>

Re: [PATCH 4/9] posix-clocks: Enable compat syscalls always

On Mon, Nov 13, 2017 at 1:03 PM, Thomas Gleixner wrote: > On Fri, 10 Nov 2017, Deepa Dinamani wrote: >> >> -#ifdef CONFIG_COMPAT >> - >> COMPAT_SYSCALL_DEFINE2(nanosleep, struct compat_timespec __user *, rqtp, >> struct compat_timespec __user *, rmtp) >> { >> @@ -1574,7

[PATCH] xen/9pfs: Add MODULE_LICENSE()

Since commit ba1029c9cbc5 ("modpost: detect modules without a MODULE_LICENSE") modules without said macro will generate WARNING: modpost: missing MODULE_LICENSE() in net/9p/9pnet_xen.o Reported-by: Stephen Rothwell Signed-off-by: Boris Ostrovsky

[PATCH] xen/9pfs: Add MODULE_LICENSE()

Since commit ba1029c9cbc5 ("modpost: detect modules without a MODULE_LICENSE") modules without said macro will generate WARNING: modpost: missing MODULE_LICENSE() in net/9p/9pnet_xen.o Reported-by: Stephen Rothwell Signed-off-by: Boris Ostrovsky --- net/9p/trans_xen.c | 1 + 1 file changed, 1

[PATCH v1 4/4] PCI/ASPM: Add L1 Substates definitions

From: Bjorn Helgaas Add and use #defines for L1 Substate register fields instead of hard-coding the masks. Also update comments to use names from the spec. No functional change intended. Signed-off-by: Bjorn Helgaas --- drivers/pci/pcie/aspm.c

[PATCH v1 4/4] PCI/ASPM: Add L1 Substates definitions

From: Bjorn Helgaas Add and use #defines for L1 Substate register fields instead of hard-coding the masks. Also update comments to use names from the spec. No functional change intended. Signed-off-by: Bjorn Helgaas --- drivers/pci/pcie/aspm.c | 34 --

[PATCH v1 3/4] PCI/ASPM: Reformat ASPM register definitions

From: Bjorn Helgaas Reformat register field definitions in the style used elsewhere and align comments with names used in the spec. No functional change intended. Signed-off-by: Bjorn Helgaas --- include/uapi/linux/pci_regs.h | 28

[PATCH v1 3/4] PCI/ASPM: Reformat ASPM register definitions

From: Bjorn Helgaas Reformat register field definitions in the style used elsewhere and align comments with names used in the spec. No functional change intended. Signed-off-by: Bjorn Helgaas --- include/uapi/linux/pci_regs.h | 28 ++-- 1 file changed, 14

[PATCH v1 1/4] PCI/ASPM: Account for downstream device's Port Common_Mode_Restore_Time

From: Bjorn Helgaas Every Port that supports the L1.2 substate advertises its Port Common_Mode_Restore_Time, i.e., the time the Port requires to re-establish common mode when exiting L1.2 (see PCIe r3.1, sec 7.33.2). Per sec 5.5.3.3.1, when exiting L1.2, the Downstream Port

[PATCH v1 1/4] PCI/ASPM: Account for downstream device's Port Common_Mode_Restore_Time

From: Bjorn Helgaas Every Port that supports the L1.2 substate advertises its Port Common_Mode_Restore_Time, i.e., the time the Port requires to re-establish common mode when exiting L1.2 (see PCIe r3.1, sec 7.33.2). Per sec 5.5.3.3.1, when exiting L1.2, the Downstream Port (the device at the

[PATCH v1 2/4] PCI/ASPM: Use correct capability pointer to program LTR_L1.2_THRESHOLD

From: Bjorn Helgaas Previously we programmed the LTR_L1.2_THRESHOLD in the parent (upstream) device using the capability pointer of the *child* (downstream) device, which corrupted some random word of the parent's config space. Use the parent's L1 SS capability pointer to

[PATCH v1 2/4] PCI/ASPM: Use correct capability pointer to program LTR_L1.2_THRESHOLD

From: Bjorn Helgaas Previously we programmed the LTR_L1.2_THRESHOLD in the parent (upstream) device using the capability pointer of the *child* (downstream) device, which corrupted some random word of the parent's config space. Use the parent's L1 SS capability pointer to program its

[PATCH v1 0/4] PCI/ASPM: Fix some L1 substate configuration

The first two patches fix typos that cause incorrect L1 substate configuration. The last two are cosmetic for maintainability. These are minor enough that I'd like to squeeze them into v4.15 unless anybody objects. --- Bjorn Helgaas (4): PCI/ASPM: Account for downstream device's Port

[PATCH v1 0/4] PCI/ASPM: Fix some L1 substate configuration

The first two patches fix typos that cause incorrect L1 substate configuration. The last two are cosmetic for maintainability. These are minor enough that I'd like to squeeze them into v4.15 unless anybody objects. --- Bjorn Helgaas (4): PCI/ASPM: Account for downstream device's Port

[GIT PULL 2nd resend] leaking_addresses updates for 4.15

The following changes since commit: bebc6082da0a9f5d47a1ea2edc099bf671058bd4 Linux 4.14 (2017-11-12 10:46:13 -0800) are available in the git repository at: https://github.com/tcharding/linux tags/leaking_addresses-4.15 for you to fetch changes up to

[GIT PULL 2nd resend] leaking_addresses updates for 4.15

The following changes since commit: bebc6082da0a9f5d47a1ea2edc099bf671058bd4 Linux 4.14 (2017-11-12 10:46:13 -0800) are available in the git repository at: https://github.com/tcharding/linux tags/leaking_addresses-4.15 for you to fetch changes up to

<    1   2   3   4   5   6   7   8   9   10   >