[...]
> > >
> > > This patch causes a number of statistically significant
> > > regressions
> > > (with significance of 1%) on the two systems I've tested it
> > > on. On
> > > my
> >
> > Sure. These patches are targeted to Atom clients where some of
> > these
> > server like workload may
[...]
> > >
> > > This patch causes a number of statistically significant
> > > regressions
> > > (with significance of 1%) on the two systems I've tested it
> > > on. On
> > > my
> >
> > Sure. These patches are targeted to Atom clients where some of
> > these
> > server like workload may
On Tue, 4 Sep 2018 17:16:31 -0700
Kees Cook wrote:
> On Fri, Aug 24, 2018 at 12:42 AM, Martin Schwidefsky
> wrote:
> > Harald Freudenberger (5):
> > s390/zcrypt: hex string mask improvements for apmask and aqmask.
>
> This (and an earlier 2017 commit) adds VLAs, which are being
>
On Tue, 4 Sep 2018 17:16:31 -0700
Kees Cook wrote:
> On Fri, Aug 24, 2018 at 12:42 AM, Martin Schwidefsky
> wrote:
> > Harald Freudenberger (5):
> > s390/zcrypt: hex string mask improvements for apmask and aqmask.
>
> This (and an earlier 2017 commit) adds VLAs, which are being
>
Hello,
On Wed, Sep 05, 2018 at 09:24:26AM +0800, Anson Huang wrote:
> In noirq suspend/resume stage with no_console_suspend enabled,
> imx_uart_console_write() may be called to print out log_buf
> message by printk(), so there will be race condition between
> imx_uart_console_write() and
Hello,
On Wed, Sep 05, 2018 at 09:24:26AM +0800, Anson Huang wrote:
> In noirq suspend/resume stage with no_console_suspend enabled,
> imx_uart_console_write() may be called to print out log_buf
> message by printk(), so there will be race condition between
> imx_uart_console_write() and
On Wed, Sep 05, 2018 at 09:24:27AM +0800, Anson Huang wrote:
> On some i.MX SoCs' low power mode, such as i.MX7D's LPSR(low power
> state retention), UART iomux settings will be lost, need to add
> pinctrl sleep/default mode switch during suspend/resume to make
> sure UART iomux settings are
On Wed, Sep 05, 2018 at 09:24:27AM +0800, Anson Huang wrote:
> On some i.MX SoCs' low power mode, such as i.MX7D's LPSR(low power
> state retention), UART iomux settings will be lost, need to add
> pinctrl sleep/default mode switch during suspend/resume to make
> sure UART iomux settings are
The smp_mb() in cpuhp_thread_fun() appears to be misplaced, and
need to be after the load of st->should_run, to prevent
reordering of the later load/stores w.r.t. the load of
st->should_run.
Signed-off-by: Neeraj Upadhyay
---
kernel/cpu.c | 6 +++---
1 file changed, 3 insertions(+), 3
The smp_mb() in cpuhp_thread_fun() appears to be misplaced, and
need to be after the load of st->should_run, to prevent
reordering of the later load/stores w.r.t. the load of
st->should_run.
Signed-off-by: Neeraj Upadhyay
---
kernel/cpu.c | 6 +++---
1 file changed, 3 insertions(+), 3
On (09/05/18 14:36), Sergey Senozhatsky wrote:
>
> OK, thanks for the report!
> So I think that your case is CON_PRINTBUFFER related as well. We have
> a number of logbuf messages before we parse quiet and console_loglevel.
> Those messages pass the suppress_message() test. Then when we finally
>
On (09/05/18 14:36), Sergey Senozhatsky wrote:
>
> OK, thanks for the report!
> So I think that your case is CON_PRINTBUFFER related as well. We have
> a number of logbuf messages before we parse quiet and console_loglevel.
> Those messages pass the suppress_message() test. Then when we finally
>
Fix a compile warning "SAVE_FLAGS redefined" introduced recently by
tip.git commit: 6da63eb241a05b0e676d6 ("x86/paravirt: Move the
pv_irq_ops under the PARAVIRT_XXL umbrella").
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/paravirt.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix a compile warning "SAVE_FLAGS redefined" introduced recently by
tip.git commit: 6da63eb241a05b0e676d6 ("x86/paravirt: Move the
pv_irq_ops under the PARAVIRT_XXL umbrella").
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/paravirt.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On (09/05/18 06:53), Hans de Goede wrote:
> >
> > Do you use earlycon?
>
> No, I'm seeing this with the regular/normal console stuff.
OK, thanks for the report!
So I think that your case is CON_PRINTBUFFER related as well. We have
a number of logbuf messages before we parse quiet and
On (09/05/18 06:53), Hans de Goede wrote:
> >
> > Do you use earlycon?
>
> No, I'm seeing this with the regular/normal console stuff.
OK, thanks for the report!
So I think that your case is CON_PRINTBUFFER related as well. We have
a number of logbuf messages before we parse quiet and
On 29.08.2018 08:22, Gustavo A. R. Silva wrote:
> There is a NULL pointer dereference in case memory resources
> for *parse* are not successfully allocated.
>
> Fix this by adding a new goto label and make the execution
> path jump to it in case vzalloc() fails.
>
> Addresses-Coverity-ID:
On 29.08.2018 08:22, Gustavo A. R. Silva wrote:
> There is a NULL pointer dereference in case memory resources
> for *parse* are not successfully allocated.
>
> Fix this by adding a new goto label and make the execution
> path jump to it in case vzalloc() fails.
>
> Addresses-Coverity-ID:
On 05/09/18 02:55, Frank Rowand wrote:
> On 08/30/18 12:05, Rob Herring wrote:
>> Only some old OpenFirmware implementations rely on default sizes. Any
>> FDT and modern implementation should have explicit properties. Make the
>> OF_ROOT_NODE_*_CELLS_DEFAULT defines private so we don't get any
On 05/09/18 02:55, Frank Rowand wrote:
> On 08/30/18 12:05, Rob Herring wrote:
>> Only some old OpenFirmware implementations rely on default sizes. Any
>> FDT and modern implementation should have explicit properties. Make the
>> OF_ROOT_NODE_*_CELLS_DEFAULT defines private so we don't get any
Hi,
On 05-09-18 04:35, Sergey Senozhatsky wrote:
Hi,
On (09/04/18 20:01), Hans de Goede wrote:
Commit 375899cddcbb ("printk: make sure to print log on console."), moved
the checking of the loglevel of messages from flush time to the actual
log time.
This introduces one problem, some early
Hi,
On 05-09-18 04:35, Sergey Senozhatsky wrote:
Hi,
On (09/04/18 20:01), Hans de Goede wrote:
Commit 375899cddcbb ("printk: make sure to print log on console."), moved
the checking of the loglevel of messages from flush time to the actual
log time.
This introduces one problem, some early
On Wed, Sep 5, 2018 at 12:26 AM, Christoph Hellwig wrote:
> On Tue, Sep 04, 2018 at 06:15:12PM +0530, Anup Patel wrote:
>> This patch selects following GENERIC_IRQ kconfig options:
>> GENERIC_IRQ_MULTI_HANDLER
>
> This is already selected by arch/riscv/Kconfig.
>
>> GENERIC_IRQ_PROBE
>
> This is
On Wed, Sep 5, 2018 at 12:26 AM, Christoph Hellwig wrote:
> On Tue, Sep 04, 2018 at 06:15:12PM +0530, Anup Patel wrote:
>> This patch selects following GENERIC_IRQ kconfig options:
>> GENERIC_IRQ_MULTI_HANDLER
>
> This is already selected by arch/riscv/Kconfig.
>
>> GENERIC_IRQ_PROBE
>
> This is
On Wed, Sep 5, 2018 at 12:20 AM, Christoph Hellwig wrote:
> On Tue, Sep 04, 2018 at 06:15:10PM +0530, Anup Patel wrote:
>> The mechanism to trigger IPI is generally part of interrupt-controller
>> driver for various architectures. On RISC-V, we have an option to trigger
>> IPI using SBI or SOC
On Wed, Sep 5, 2018 at 12:20 AM, Christoph Hellwig wrote:
> On Tue, Sep 04, 2018 at 06:15:10PM +0530, Anup Patel wrote:
>> The mechanism to trigger IPI is generally part of interrupt-controller
>> driver for various architectures. On RISC-V, we have an option to trigger
>> IPI using SBI or SOC
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove direct access to device_node.type, add
> of_node_is_type() and of_node_get_device_type() helpers to check and
> retrieve the device type.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> include/linux/of.h | 12
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove direct access to device_node.type, add
> of_node_is_type() and of_node_get_device_type() helpers to check and
> retrieve the device type.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> include/linux/of.h | 12
On Fri, 31 Aug 2018 15:17:44 +
Matteo Croce wrote:
> On Fri, Aug 31, 2018 at 3:49 AM Nicholas Piggin wrote:
> >
> > On Tue, 28 Aug 2018 15:00:14 +
> > Matteo Croce wrote:
> >
> > > On Tue, Aug 28, 2018 at 2:35 PM Nicholas Piggin
> > > wrote:
> > > >
> > > > On Tue, 28 Aug 2018
On Fri, 31 Aug 2018 15:17:44 +
Matteo Croce wrote:
> On Fri, Aug 31, 2018 at 3:49 AM Nicholas Piggin wrote:
> >
> > On Tue, 28 Aug 2018 15:00:14 +
> > Matteo Croce wrote:
> >
> > > On Tue, Aug 28, 2018 at 2:35 PM Nicholas Piggin
> > > wrote:
> > > >
> > > > On Tue, 28 Aug 2018
Hi all,
Changes since 20180904:
Dropped trees: xarray, ida (temporarily)
The net-next tree still had its build failure for which I reverted
a commit.
The devicetree tree gained a build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 1853
2252 files changed
Hi all,
Changes since 20180904:
Dropped trees: xarray, ida (temporarily)
The net-next tree still had its build failure for which I reverted
a commit.
The devicetree tree gained a build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 1853
2252 files changed
Hi Linus,
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git
tags/nds32-for-linus-4.19-tag1
for you to
Hi Linus,
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git
tags/nds32-for-linus-4.19-tag1
for you to
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove device_node.name pointer, add helper functions
> for node name comparisons which are a common pattern throughout the kernel.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/base.c | 22 ++
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove device_node.name pointer, add helper functions
> for node name comparisons which are a common pattern throughout the kernel.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/base.c | 22 ++
add config file
Signed-off-by: Lei Yang
---
tools/testing/selftests/efivarfs/config | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/testing/selftests/efivarfs/config
diff --git a/tools/testing/selftests/efivarfs/config
b/tools/testing/selftests/efivarfs/config
new file mode
add config file
Signed-off-by: Lei Yang
---
tools/testing/selftests/efivarfs/config | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/testing/selftests/efivarfs/config
diff --git a/tools/testing/selftests/efivarfs/config
b/tools/testing/selftests/efivarfs/config
new file mode
sorry, the title should be :"cgroup: kselftests: add test_core to
.gitignore"
Lei
On 2018年09月05日 10:39, Lei Yang wrote:
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git
sorry, the title should be :"cgroup: kselftests: add test_core to
.gitignore"
Lei
On 2018年09月05日 10:39, Lei Yang wrote:
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Jacek,
On 5 September 2018 at 04:19, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> On 09/04/2018 01:01 PM, Baolin Wang wrote:
>> This patch implements the 'pattern_set'and 'pattern_clear'
>> interfaces to support SC27XX LED breathing mode.
>>
>> Signed-off-by: Baolin Wang
>> ---
>> Changes from
Hi Jacek,
On 5 September 2018 at 04:19, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> On 09/04/2018 01:01 PM, Baolin Wang wrote:
>> This patch implements the 'pattern_set'and 'pattern_clear'
>> interfaces to support SC27XX LED breathing mode.
>>
>> Signed-off-by: Baolin Wang
>> ---
>> Changes from
On Wed, Sep 05, 2018 at 01:00:37AM +, Schaufler, Casey wrote:
> Sorry, I've been working in security too long for my
> optimistic streak to be very wide.
Eheh. So I was simply trying to follow in context, but it wasn't
entirely clear, so I tried to take it out of context and then it was
even
On Wed, Sep 05, 2018 at 01:00:37AM +, Schaufler, Casey wrote:
> Sorry, I've been working in security too long for my
> optimistic streak to be very wide.
Eheh. So I was simply trying to follow in context, but it wasn't
entirely clear, so I tried to take it out of context and then it was
even
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/cgroup/.gitignore
b/tools/testing/selftests/cgroup/.gitignore
index 95eb3a5..adacda5 100644
---
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/cgroup/.gitignore
b/tools/testing/selftests/cgroup/.gitignore
index 95eb3a5..adacda5 100644
---
Hi,
On (09/04/18 20:01), Hans de Goede wrote:
> Commit 375899cddcbb ("printk: make sure to print log on console."), moved
> the checking of the loglevel of messages from flush time to the actual
> log time.
>
> This introduces one problem, some early boot messages are printed before
>
Hi,
On (09/04/18 20:01), Hans de Goede wrote:
> Commit 375899cddcbb ("printk: make sure to print log on console."), moved
> the checking of the loglevel of messages from flush time to the actual
> log time.
>
> This introduces one problem, some early boot messages are printed before
>
Some leds on our board are active low leds, which means these leds
are lighted when the corresponding gpio line is low, while the
original leds-gpio driver default all leds are active high leds.
This patch adds a devicetree node "light-state", whose value should
be "high" for active high leds and
Some leds on our board are active low leds, which means these leds
are lighted when the corresponding gpio line is low, while the
original leds-gpio driver default all leds are active high leds.
This patch adds a devicetree node "light-state", whose value should
be "high" for active high leds and
This series adds PCIe host controller driver for Socionext UniPhier SoCs.
This controller is based on the DesignWare PCIe core. This driver
supports LD20 and PXs3 SoCs.
Kunihiko Hayashi (2):
dt-bindings: pci: add UniPhier PCIe host controller description
pci: dwc: add UniPhier PCIe host
This introduces specific glue layer for UniPhier platform to support
PCIe host controller that is based on the Designware PCIe Core, and
this driver supports Root Complex (host) mode.
Signed-off-by: Kunihiko Hayashi
---
drivers/pci/controller/dwc/Kconfig | 9 +
Add DT bindings for PCIe controller implemented in UniPhier SoCs when
configured in Root Complex (host) mode. This controller is based on
the Designware PCIe Core.
Signed-off-by: Kunihiko Hayashi
---
.../devicetree/bindings/pci/uniphier-pcie.txt | 78 ++
1 file changed,
This series adds PCIe host controller driver for Socionext UniPhier SoCs.
This controller is based on the DesignWare PCIe core. This driver
supports LD20 and PXs3 SoCs.
Kunihiko Hayashi (2):
dt-bindings: pci: add UniPhier PCIe host controller description
pci: dwc: add UniPhier PCIe host
This introduces specific glue layer for UniPhier platform to support
PCIe host controller that is based on the Designware PCIe Core, and
this driver supports Root Complex (host) mode.
Signed-off-by: Kunihiko Hayashi
---
drivers/pci/controller/dwc/Kconfig | 9 +
Add DT bindings for PCIe controller implemented in UniPhier SoCs when
configured in Root Complex (host) mode. This controller is based on
the Designware PCIe Core.
Signed-off-by: Kunihiko Hayashi
---
.../devicetree/bindings/pci/uniphier-pcie.txt | 78 ++
1 file changed,
It uses modprobe $TEST_DRIVER in sysctl.sh, so update
config to use "m" instead
Signed-off-by: Lei Yang
---
tools/testing/selftests/sysctl/config | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/sysctl/config
b/tools/testing/selftests/sysctl/config
It uses modprobe $TEST_DRIVER in sysctl.sh, so update
config to use "m" instead
Signed-off-by: Lei Yang
---
tools/testing/selftests/sysctl/config | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/sysctl/config
b/tools/testing/selftests/sysctl/config
On 08/30/18 12:05, Rob Herring wrote:
> This is a small restructuring and clean-up of handling root node
> #size-cells and #address-cells (or lack of). As only Sparc needs a
> different default value and only for #address-cells, we can handle that
> locally and remove one more dependency on
Srinivas Pandruvada writes:
> On Mon, 2018-09-03 at 23:53 -0700, Francisco Jerez wrote:
>> Eero Tamminen writes:
>>
>> > Hi,
>> >
>> > On 31.08.2018 20:28, Srinivas Pandruvada wrote:
>> > ...
>> > > As per testing Eero Tamminen, the results are comparable to the
>> > > patchset
>> > >
On 08/30/18 12:05, Rob Herring wrote:
> This is a small restructuring and clean-up of handling root node
> #size-cells and #address-cells (or lack of). As only Sparc needs a
> different default value and only for #address-cells, we can handle that
> locally and remove one more dependency on
Srinivas Pandruvada writes:
> On Mon, 2018-09-03 at 23:53 -0700, Francisco Jerez wrote:
>> Eero Tamminen writes:
>>
>> > Hi,
>> >
>> > On 31.08.2018 20:28, Srinivas Pandruvada wrote:
>> > ...
>> > > As per testing Eero Tamminen, the results are comparable to the
>> > > patchset
>> > >
On 08/30/18 12:05, Rob Herring wrote:
> Only some old OpenFirmware implementations rely on default sizes. Any
> FDT and modern implementation should have explicit properties. Make the
> OF_ROOT_NODE_*_CELLS_DEFAULT defines private so we don't get any outside
> users.
>
> This also gets us one
On 08/30/18 12:05, Rob Herring wrote:
> Only some old OpenFirmware implementations rely on default sizes. Any
> FDT and modern implementation should have explicit properties. Make the
> OF_ROOT_NODE_*_CELLS_DEFAULT defines private so we don't get any outside
> users.
>
> This also gets us one
Hi all,
On Wed, 5 Sep 2018 10:39:06 +1000 Stephen Rothwell
wrote:
>
> After merging the devicetree tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
> function of_fdt_limit_memory() to
Hi all,
On Wed, 5 Sep 2018 10:39:06 +1000 Stephen Rothwell
wrote:
>
> After merging the devicetree tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
> function of_fdt_limit_memory() to
On 08/30/18 12:05, Rob Herring wrote:
> Now that we initialize dt_root_addr_cells and dt_root_size_cells earlier,
> use them and simplify of_fdt_limit_memory.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/fdt.c | 23 +--
> 1 file changed, 1
On 08/30/18 12:05, Rob Herring wrote:
> Now that we initialize dt_root_addr_cells and dt_root_size_cells earlier,
> use them and simplify of_fdt_limit_memory.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/fdt.c | 23 +--
> 1 file changed, 1
On 08/30/18 12:05, Rob Herring wrote:
> Scan the root node properties (#{size,address}-cells) earlier,
^^^
before mdesc->dt_fixup() is called
> so that
> the dt_root_addr_cells and dt_root_size_cells
On 08/30/18 12:05, Rob Herring wrote:
> Scan the root node properties (#{size,address}-cells) earlier,
^^^
before mdesc->dt_fixup() is called
> so that
> the dt_root_addr_cells and dt_root_size_cells
On Thu, Aug 30, 2018 at 12:47:27PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> This simplifies the code. No change in behavior.
>
> Signed-off-by: Eric Biggers
> ---
> lib/parser.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/lib/parser.c
On Thu, Aug 30, 2018 at 12:47:27PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> This simplifies the code. No change in behavior.
>
> Signed-off-by: Eric Biggers
> ---
> lib/parser.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/lib/parser.c
In resctrl filesystem, we have some mount options to enable
L3/L2 CDP and MBA Software Controller features if platform supports them:
mount -t resctrl resctrl [-o cdp[,cdpl2][,mba_MBps]] /sys/fs/resctrl
But currently only "cdp" option can be displayed. "cdpl2" and "mba_MBps"
options are not
In resctrl filesystem, we have some mount options to enable
L3/L2 CDP and MBA Software Controller features if platform supports them:
mount -t resctrl resctrl [-o cdp[,cdpl2][,mba_MBps]] /sys/fs/resctrl
But currently only "cdp" option can be displayed. "cdpl2" and "mba_MBps"
options are not
On some i.MX SoCs' low power mode, such as i.MX7D's LPSR(low power
state retention), UART iomux settings will be lost, need to add
pinctrl sleep/default mode switch during suspend/resume to make
sure UART iomux settings are correct after resume.
Signed-off-by: Anson Huang
---
On some i.MX SoCs' low power mode, such as i.MX7D's LPSR(low power
state retention), UART iomux settings will be lost, need to add
pinctrl sleep/default mode switch during suspend/resume to make
sure UART iomux settings are correct after resume.
Signed-off-by: Anson Huang
---
In noirq suspend/resume stage with no_console_suspend enabled,
imx_uart_console_write() may be called to print out log_buf
message by printk(), so there will be race condition between
imx_uart_console_write() and imx_uart_save/restore_context(),
need to add lock to protect the registers
In noirq suspend/resume stage with no_console_suspend enabled,
imx_uart_console_write() may be called to print out log_buf
message by printk(), so there will be race condition between
imx_uart_console_write() and imx_uart_save/restore_context(),
need to add lock to protect the registers
Hi, Uwe
Anson Huang
Best Regards!
> -Original Message-
> From: Uwe Kleine-König
> Sent: Wednesday, September 5, 2018 4:32 AM
> To: Anson Huang
> Cc: gre...@linuxfoundation.org; jsl...@suse.com;
> linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org; dl-linux-imx
>
> Subject:
Hi, Uwe
Anson Huang
Best Regards!
> -Original Message-
> From: Uwe Kleine-König
> Sent: Wednesday, September 5, 2018 4:32 AM
> To: Anson Huang
> Cc: gre...@linuxfoundation.org; jsl...@suse.com;
> linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org; dl-linux-imx
>
> Subject:
Hi Shuah,
I wrote some tests for the new memory.oom.group feature in cgroups 2.
In the process, I discovered a few small bugs in the cgroups tests, which
I have fixed as well in a separate commit.
This is my first ever patch to Linux, so let me know if you see any issues or
improvements that
Hi Shuah,
I wrote some tests for the new memory.oom.group feature in cgroups 2.
In the process, I discovered a few small bugs in the cgroups tests, which
I have fixed as well in a separate commit.
This is my first ever patch to Linux, so let me know if you see any issues or
improvements that
From: Jay Kamat
Add tests for memory.oom.group for the following cases:
- Killing all processes in a leaf cgroup, but leaving the
parent untouched
- Killing all processes in a parent and leaf cgroup
- Keeping processes marked by OOM_SCORE_ADJ_MIN alive when considered
for being killed by the
From: Jay Kamat
Fix a couple issues with cg_read_strcmp(), to improve correctness of
cgroup tests
- Fix cg_read_strcmp() always returning 0 for empty "needle" strings
- Fix a memory leak in cg_read_strcmp()
Fixes: 84092dbcf901 ("selftests: cgroup: add memory controller self-tests")
From: Jay Kamat
Add tests for memory.oom.group for the following cases:
- Killing all processes in a leaf cgroup, but leaving the
parent untouched
- Killing all processes in a parent and leaf cgroup
- Keeping processes marked by OOM_SCORE_ADJ_MIN alive when considered
for being killed by the
From: Jay Kamat
Fix a couple issues with cg_read_strcmp(), to improve correctness of
cgroup tests
- Fix cg_read_strcmp() always returning 0 for empty "needle" strings
- Fix a memory leak in cg_read_strcmp()
Fixes: 84092dbcf901 ("selftests: cgroup: add memory controller self-tests")
> -Original Message-
> From: Andrea Arcangeli [mailto:aarca...@redhat.com]
> Sent: Tuesday, September 04, 2018 4:37 PM
> To: Schaufler, Casey
> Cc: Jiri Kosina ; Tim Chen ;
> Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Woodhouse, David ; Oleg
> Nesterov ;
> -Original Message-
> From: Andrea Arcangeli [mailto:aarca...@redhat.com]
> Sent: Tuesday, September 04, 2018 4:37 PM
> To: Schaufler, Casey
> Cc: Jiri Kosina ; Tim Chen ;
> Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Woodhouse, David ; Oleg
> Nesterov ;
On Tue, Sep 04, 2018 at 01:35:34PM -0700, Vito Caputo wrote:
> On Tue, Sep 04, 2018 at 04:18:18PM -0400, Jeff Layton wrote:
> > On Tue, 2018-09-04 at 14:54 -0400, J. Bruce Fields wrote:
> > > On Tue, Sep 04, 2018 at 06:23:48PM +0200, Rogier Wolff wrote:
> > > > On Tue, Sep 04, 2018 at 12:12:03PM
On Tue, Sep 04, 2018 at 01:35:34PM -0700, Vito Caputo wrote:
> On Tue, Sep 04, 2018 at 04:18:18PM -0400, Jeff Layton wrote:
> > On Tue, 2018-09-04 at 14:54 -0400, J. Bruce Fields wrote:
> > > On Tue, Sep 04, 2018 at 06:23:48PM +0200, Rogier Wolff wrote:
> > > > On Tue, Sep 04, 2018 at 12:12:03PM
On 08/31/2018 09:09 AM, Steven Sistare wrote:
On 8/30/2018 4:24 PM, subhra mazumdar wrote:
Introduce pipe_ll_usec field for pipes that indicates the amount of micro
seconds a thread should spin if pipe is empty or full before sleeping. This
is similar to network sockets. Workloads like
On 08/31/2018 09:09 AM, Steven Sistare wrote:
On 8/30/2018 4:24 PM, subhra mazumdar wrote:
Introduce pipe_ll_usec field for pipes that indicates the amount of micro
seconds a thread should spin if pipe is empty or full before sleeping. This
is similar to network sockets. Workloads like
Hi Rob,
After merging the devicetree tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
function of_fdt_limit_memory() to the variable .init.data:dt_root_addr_cells
The function
Hi Rob,
After merging the devicetree tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
function of_fdt_limit_memory() to the variable .init.data:dt_root_addr_cells
The function
On 09/04/2018 02:54 PM, Thomas Gleixner wrote:
On Thu, 30 Aug 2018, subhra mazumdar wrote:
+void pipe_busy_wait(struct pipe_inode_info *pipe)
+{
+ unsigned long wait_flag = pipe->pipe_wait_flag;
+ unsigned long start_time = pipe_busy_loop_current_time();
+
+
On 09/04/2018 02:54 PM, Thomas Gleixner wrote:
On Thu, 30 Aug 2018, subhra mazumdar wrote:
+void pipe_busy_wait(struct pipe_inode_info *pipe)
+{
+ unsigned long wait_flag = pipe->pipe_wait_flag;
+ unsigned long start_time = pipe_busy_loop_current_time();
+
+
On Fri, Aug 24, 2018 at 12:42 AM, Martin Schwidefsky
wrote:
> Harald Freudenberger (5):
> s390/zcrypt: hex string mask improvements for apmask and aqmask.
This (and an earlier 2017 commit) adds VLAs, which are being
removed[1] from the kernel:
drivers/s390/crypto/ap_bus.c:980:3: warning:
On Fri, Aug 24, 2018 at 12:42 AM, Martin Schwidefsky
wrote:
> Harald Freudenberger (5):
> s390/zcrypt: hex string mask improvements for apmask and aqmask.
This (and an earlier 2017 commit) adds VLAs, which are being
removed[1] from the kernel:
drivers/s390/crypto/ap_bus.c:980:3: warning:
Hi Stefan,
On Tue, 4 Sep 2018 22:07:15 +0200 (CEST) Stefan Wahren
wrote:
>
> > Eric Anholt hat am 4. September 2018 um 19:41 geschrieben:
> >
> > Stephen Rothwell writes:
> >
> > > Fetching the bcm2835 tree (git://github.com/anholt/linux.git#for-next)
> > > produces this error:
> > >
> >
Hi Stefan,
On Tue, 4 Sep 2018 22:07:15 +0200 (CEST) Stefan Wahren
wrote:
>
> > Eric Anholt hat am 4. September 2018 um 19:41 geschrieben:
> >
> > Stephen Rothwell writes:
> >
> > > Fetching the bcm2835 tree (git://github.com/anholt/linux.git#for-next)
> > > produces this error:
> > >
> >
1 - 100 of 1168 matches
Mail list logo
