Re: sched: tweak select_idle_sibling to look for idle threads

On Tue, May 10, 2016 at 05:26:05PM +0200, Mike Galbraith wrote: > On Tue, 2016-05-10 at 09:49 +0200, Mike Galbraith wrote: > > > Only whacking > > cfs_rq_runnable_load_avg() with a rock makes schbench -m -t > > -a work well. 'Course a rock in its gearbox also > > rendered load balancing

Re: sched: tweak select_idle_sibling to look for idle threads

On Tue, May 10, 2016 at 05:26:05PM +0200, Mike Galbraith wrote: > On Tue, 2016-05-10 at 09:49 +0200, Mike Galbraith wrote: > > > Only whacking > > cfs_rq_runnable_load_avg() with a rock makes schbench -m -t > > -a work well. 'Course a rock in its gearbox also > > rendered load balancing

Re: [RFC PATCH 13/21] reset: uniphier: add reset driver for UniPhier PH1-LD4 SoC

Hi Philipp, 2016-05-10 21:25 GMT+09:00 Philipp Zabel : > Hi Masahiro, > > Am Dienstag, den 10.05.2016, 18:50 +0900 schrieb Masahiro Yamada: >> This series is just for review. >> Please do not apply this patch. >> >> Signed-off-by: Masahiro Yamada

Re: [RFC PATCH 13/21] reset: uniphier: add reset driver for UniPhier PH1-LD4 SoC

Hi Philipp, 2016-05-10 21:25 GMT+09:00 Philipp Zabel : > Hi Masahiro, > > Am Dienstag, den 10.05.2016, 18:50 +0900 schrieb Masahiro Yamada: >> This series is just for review. >> Please do not apply this patch. >> >> Signed-off-by: Masahiro Yamada > > No need for all these tiny drivers. If you

Re: [PATCH v7 7/9] clk: mediatek: Enable critical clocks for MT2701

Hi Stephen, Mike, Lee, On Mon, 2016-05-09 at 15:13 -0700, Stephen Boyd wrote: > On 05/09, James Liao wrote: > > Hi Stephen, > > > > On Fri, 2016-05-06 at 16:12 -0700, Stephen Boyd wrote: > > > On 04/14, James Liao wrote: > > > > Some system clocks should be turned on by default on MT2701. > > >

Re: [PATCH v7 7/9] clk: mediatek: Enable critical clocks for MT2701

Hi Stephen, Mike, Lee, On Mon, 2016-05-09 at 15:13 -0700, Stephen Boyd wrote: > On 05/09, James Liao wrote: > > Hi Stephen, > > > > On Fri, 2016-05-06 at 16:12 -0700, Stephen Boyd wrote: > > > On 04/14, James Liao wrote: > > > > Some system clocks should be turned on by default on MT2701. > > >

Re: [PATCH 2/2] dt-bindings: rockchip-dw-mshc: add rockchip,default-drv-phase

On 2016/5/10 23:57, Doug Anderson wrote: (again, but not HTML) --8<-- I have less faith than you in the TRM. The TRM is full of minor errors and is often wrong about the default state of things. IMHO the only true way to find out is to boot up some SoCs and check.

Re: [PATCH 2/2] dt-bindings: rockchip-dw-mshc: add rockchip,default-drv-phase

On 2016/5/10 23:57, Doug Anderson wrote: (again, but not HTML) --8<-- I have less faith than you in the TRM. The TRM is full of minor errors and is often wrong about the default state of things. IMHO the only true way to find out is to boot up some SoCs and check.

[PATCH] audit: add support for session ID user filter

Define AUDIT_SESSIONID in the uapi and add support for specifying user filters based on the session ID. https://github.com/linux-audit/audit-kernel/issues/4 RFE: add a session ID filter to the kernel's user filter Signed-off-by: Richard Guy Briggs --- Like loginuid (auid),

[PATCH] audit: add support for session ID user filter

Define AUDIT_SESSIONID in the uapi and add support for specifying user filters based on the session ID. https://github.com/linux-audit/audit-kernel/issues/4 RFE: add a session ID filter to the kernel's user filter Signed-off-by: Richard Guy Briggs --- Like loginuid (auid), should this have a

Re: [RFC PATCH 12/21] reset: uniphier: add core support for UniPhier reset driver

Hi Philipp, 2016-05-10 22:54 GMT+09:00 Philipp Zabel : > Am Dienstag, den 10.05.2016, 18:50 +0900 schrieb Masahiro Yamada: > [...] >> +static int uniphier_reset_update(struct reset_controller_dev *rcdev, >> + unsigned long id, bool assert) >>

Re: [RFC PATCH 12/21] reset: uniphier: add core support for UniPhier reset driver

Hi Philipp, 2016-05-10 22:54 GMT+09:00 Philipp Zabel : > Am Dienstag, den 10.05.2016, 18:50 +0900 schrieb Masahiro Yamada: > [...] >> +static int uniphier_reset_update(struct reset_controller_dev *rcdev, >> + unsigned long id, bool assert) >> +{ >> + struct

Re: [PATCH v1] ION: Sys_heap: Add cached pool to spead up cached buffer alloc

On 2016/5/11 6:48, Laura Abbott wrote: > On 05/09/2016 04:35 AM, Chen Feng wrote: >> Add ion cached pool in system heap. This patch add a cached pool >> in system heap. It has a great improvement of alloc for cached >> buffer. >> > > Can you give some benchmark numbers here? > ok, My test is

Re: [PATCH v1] ION: Sys_heap: Add cached pool to spead up cached buffer alloc

On 2016/5/11 6:48, Laura Abbott wrote: > On 05/09/2016 04:35 AM, Chen Feng wrote: >> Add ion cached pool in system heap. This patch add a cached pool >> in system heap. It has a great improvement of alloc for cached >> buffer. >> > > Can you give some benchmark numbers here? > ok, My test is

Re: [PATCH 1/6] f2fs: support in batch multi blocks preallocation

On Wed, May 11, 2016 at 10:22:05AM +0800, Chao Yu wrote: > On 2016/5/11 5:41, Jaegeuk Kim wrote: > > + > > + f2fs_wait_on_page_writeback(dn->node_page, NODE, true); > > + > > + for (; count > 0; dn->ofs_in_node++) { > > + block_t blkaddr = > > +

Re: [PATCH 1/6] f2fs: support in batch multi blocks preallocation

On Wed, May 11, 2016 at 10:22:05AM +0800, Chao Yu wrote: > On 2016/5/11 5:41, Jaegeuk Kim wrote: > > + > > + f2fs_wait_on_page_writeback(dn->node_page, NODE, true); > > + > > + for (; count > 0; dn->ofs_in_node++) { > > + block_t blkaddr = > > +

Re: [PATCH 1/2] [v4] net: emac: emac gigabit ethernet controller driver

Florian Fainelli wrote: The Ethernet MAC should be started in ndo_open() and stopped in ndo_close(), in between, there are link state changes, but you are not supposed to stop or start your Ethernet MAC and its DMA for instance during link change, if that is a HW requirement, your HW is pretty

Re: [PATCH 1/2] [v4] net: emac: emac gigabit ethernet controller driver

Florian Fainelli wrote: The Ethernet MAC should be started in ndo_open() and stopped in ndo_close(), in between, there are link state changes, but you are not supposed to stop or start your Ethernet MAC and its DMA for instance during link change, if that is a HW requirement, your HW is pretty

Re: [PATCH 1/6] f2fs: support in batch multi blocks preallocation

On 2016/5/11 5:41, Jaegeuk Kim wrote: > + > + f2fs_wait_on_page_writeback(dn->node_page, NODE, true); > + > + for (; count > 0; dn->ofs_in_node++) { > + block_t blkaddr = > + datablock_addr(dn->node_page, dn->ofs_in_node); > + if (blkaddr ==

Re: [PATCH 1/6] f2fs: support in batch multi blocks preallocation

On 2016/5/11 5:41, Jaegeuk Kim wrote: > + > + f2fs_wait_on_page_writeback(dn->node_page, NODE, true); > + > + for (; count > 0; dn->ofs_in_node++) { > + block_t blkaddr = > + datablock_addr(dn->node_page, dn->ofs_in_node); > + if (blkaddr ==

linux-next: manual merge of the dt-rh tree with the iommu tree

Hi Rob, Today's linux-next merge of the dt-rh tree got a conflict in: drivers/iommu/arm-smmu.c between commit: d54663573131 ("iommu/arm-smmu: Use per-domain page sizes.") from the iommu tree and commit: cb6c27bb0912 ("iommu/arm-smmu: Make use of phandle iterators in device-tree

linux-next: manual merge of the dt-rh tree with the iommu tree

Hi Rob, Today's linux-next merge of the dt-rh tree got a conflict in: drivers/iommu/arm-smmu.c between commit: d54663573131 ("iommu/arm-smmu: Use per-domain page sizes.") from the iommu tree and commit: cb6c27bb0912 ("iommu/arm-smmu: Make use of phandle iterators in device-tree

Re: [LKP] [lkp] [net] 9317bb6982: INFO: task cat-kmsg:893 blocked for more than 300 seconds.

Eric Dumazet writes: > On Mon, May 9, 2016 at 6:26 PM, Huang, Ying > wrote: >> Hi, Eric, >> >> kernel test robot writes: >>> FYI, we noticed the following commit: >>> >>> git://internal_merge_and_test_tree

Re: [LKP] [lkp] [net] 9317bb6982: INFO: task cat-kmsg:893 blocked for more than 300 seconds.

Eric Dumazet writes: > On Mon, May 9, 2016 at 6:26 PM, Huang, Ying > wrote: >> Hi, Eric, >> >> kernel test robot writes: >>> FYI, we noticed the following commit: >>> >>> git://internal_merge_and_test_tree devel-catchup-201604281529 >>> commit 9317bb69824ec8d078b0b786b6971aedb0af3d4f ("net:

[PATCH] dt: add Atmel Captouch bindings

From: Daniel Hung-yu Wu Add binding for Atmel Capacitive Touch Button device. Signed-off-by: Daniel Hung-yu Wu Signed-off-by: Grant Grundler --- .../devicetree/bindings/input/atmel,captouch.txt | 34 ++ 1 file

[PATCH] dt: add Atmel Captouch bindings

From: Daniel Hung-yu Wu Add binding for Atmel Capacitive Touch Button device. Signed-off-by: Daniel Hung-yu Wu Signed-off-by: Grant Grundler --- .../devicetree/bindings/input/atmel,captouch.txt | 34 ++ 1 file changed, 34 insertions(+) create mode 100644

[PATCH 2/3 V2] Input: add Atmel Captouch Button driver

From: Daniel Hung-yu Wu Add I2C driver for Atmel Capacitive Touch Button device. Signed-off-by: Hung-yu Wu Signed-off-by: Grant Grundler --- drivers/input/misc/Kconfig | 11 ++ drivers/input/misc/Makefile | 1 +

[PATCH 2/3 V2] Input: add Atmel Captouch Button driver

From: Daniel Hung-yu Wu Add I2C driver for Atmel Capacitive Touch Button device. Signed-off-by: Hung-yu Wu Signed-off-by: Grant Grundler --- drivers/input/misc/Kconfig | 11 ++ drivers/input/misc/Makefile | 1 + drivers/input/misc/atmel_captouch.c | 287

[PATCH 2/4] perf script: fix symbol insertion behavior in db-export

Use the dso__insert_symbol function instead of symbols__insert in order to properly update the dso symbol cache. If the cache is not updated, then duplicate symbols can be unintentionally created, inserted, and exported. This change prevents duplicate symbols from being exported due to

[PATCH 2/4] perf script: fix symbol insertion behavior in db-export

Use the dso__insert_symbol function instead of symbols__insert in order to properly update the dso symbol cache. If the cache is not updated, then duplicate symbols can be unintentionally created, inserted, and exported. This change prevents duplicate symbols from being exported due to

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

Hi, On 2016/5/10 20:50, Arnd Bergmann wrote: On Tuesday 10 May 2016 20:39:41 Zhangjian wrote: Hi, On 2016/5/10 19:48, Arnd Bergmann wrote: On Tuesday 10 May 2016 17:47:26 Zhangjian wrote: On 2016/5/10 16:36, Arnd Bergmann wrote: On Tuesday 10 May 2016 15:42:07 Zhangjian wrote: On 2016/5/6

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

Hi, On 2016/5/10 20:50, Arnd Bergmann wrote: On Tuesday 10 May 2016 20:39:41 Zhangjian wrote: Hi, On 2016/5/10 19:48, Arnd Bergmann wrote: On Tuesday 10 May 2016 17:47:26 Zhangjian wrote: On 2016/5/10 16:36, Arnd Bergmann wrote: On Tuesday 10 May 2016 15:42:07 Zhangjian wrote: On 2016/5/6

[PATCH 3/4] perf script: fix callchain addresses in db-export

Remove the call to map_ip, because it has already been called when assembling the callchain. Calling it a second time can result in incorrect addresses being used. This can have effects such as duplicate symbols being created and exported. Signed-off-by: Chris Phlipot ---

[PATCH 4/4] perf script: fix export of callchains with recursion in db-export

When an IP with an unresolved symbol occurs in the callchain more than once (ie. recursion), then duplicate symbols can be created because the callchain nodes are never updated after they are first created. To fix this issue we call dso__find_symbol whenever we encounter a NULL symbol, in case we

[PATCH 3/4] perf script: fix callchain addresses in db-export

Remove the call to map_ip, because it has already been called when assembling the callchain. Calling it a second time can result in incorrect addresses being used. This can have effects such as duplicate symbols being created and exported. Signed-off-by: Chris Phlipot ---

[PATCH 4/4] perf script: fix export of callchains with recursion in db-export

When an IP with an unresolved symbol occurs in the callchain more than once (ie. recursion), then duplicate symbols can be created because the callchain nodes are never updated after they are first created. To fix this issue we call dso__find_symbol whenever we encounter a NULL symbol, in case we

[PATCH 0/4] perf script: fix duplicate symbols in db-export

This patch set contains 3 fixes for duplicate symbol creation in the db-export implementation and one new symbol API required for the fixes. commit 9c7b37cd63d0 already removed the majority of duplicates, but these fixes take care of the remaining corner cases. each patch (except for the 1st,

[PATCH 1/4] perf symbols: add dso__insert_symbol function

The current method for inserting symbols is to use the symbols__insert function. However symbols__insert does not update the dso symbol cache. This causes problems in the following scenario: 1. symbol not found at ip using dso__find_symbol 2. symbol inserted at ip using the existing

[PATCH 0/4] perf script: fix duplicate symbols in db-export

This patch set contains 3 fixes for duplicate symbol creation in the db-export implementation and one new symbol API required for the fixes. commit 9c7b37cd63d0 already removed the majority of duplicates, but these fixes take care of the remaining corner cases. each patch (except for the 1st,

[PATCH 1/4] perf symbols: add dso__insert_symbol function

The current method for inserting symbols is to use the symbols__insert function. However symbols__insert does not update the dso symbol cache. This causes problems in the following scenario: 1. symbol not found at ip using dso__find_symbol 2. symbol inserted at ip using the existing

Re: [patch] [SCSI] eata_pio: missing break statement

> "Dan" == Dan Carpenter writes: Dan> This missing break statement bug predates git. It's a very minor Dan> thing, it means that we print a '?' instead of a 'z' in dmesg. Applied to 4.7/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [patch] [SCSI] eata_pio: missing break statement

> "Dan" == Dan Carpenter writes: Dan> This missing break statement bug predates git. It's a very minor Dan> thing, it means that we print a '?' instead of a 'z' in dmesg. Applied to 4.7/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [RFC PATCH 01/21] mfd: uniphier: add UniPhier MFD driver

Hi Lee, 2016-05-10 20:26 GMT+09:00 Lee Jones : >> +}; >> +MODULE_DEVICE_TABLE(of, uniphier_mfd_match); > > NACK. Please do not mix MFD and DT registration. OK, thanks for review. My basic thought was: - Add an MFD node to my DTS only once. If I need to expand it

Re: [RFC PATCH 01/21] mfd: uniphier: add UniPhier MFD driver

Hi Lee, 2016-05-10 20:26 GMT+09:00 Lee Jones : >> +}; >> +MODULE_DEVICE_TABLE(of, uniphier_mfd_match); > > NACK. Please do not mix MFD and DT registration. OK, thanks for review. My basic thought was: - Add an MFD node to my DTS only once. If I need to expand it in the future, I will

Re: [PATCH v2 2/9] perf script: Add options for custom vdso path

在 2016/5/10 21:44, Arnaldo Carvalho de Melo 写道: Em Tue, May 10, 2016 at 07:40:30AM +, He Kuang escreveu: When unwinding callchains on a different machine, vdso info should be provided so the unwind process won't be interrupted if address falls into vdso region. Currently, perf does try

Re: [PATCH v2 2/9] perf script: Add options for custom vdso path

在 2016/5/10 21:44, Arnaldo Carvalho de Melo 写道: Em Tue, May 10, 2016 at 07:40:30AM +, He Kuang escreveu: When unwinding callchains on a different machine, vdso info should be provided so the unwind process won't be interrupted if address falls into vdso region. Currently, perf does try

[PATCH 1/3] Save dump_root into pid_namespace

In current system, when we set core_pattern to a pipe, both pipe program and program's output are in host's filesystem. But when we set core_pattern to a file, the container will write dump into container's filesystem. Reason of above different is: In pipe_mode dump_pattern setting, the process

[PATCH 0/3] Write dump into container's filesystem for pipe_type core_pattern

In current system, when we set core_pattern to a pipe, both pipe program and program's output are in host's filesystem. But when we set core_pattern to a file, the container will write dump into container's filesystem. For example, when we set following core_pattern: # echo "|/my_dump_pipe %s %c

[PATCH 1/3] Save dump_root into pid_namespace

In current system, when we set core_pattern to a pipe, both pipe program and program's output are in host's filesystem. But when we set core_pattern to a file, the container will write dump into container's filesystem. Reason of above different is: In pipe_mode dump_pattern setting, the process

[PATCH 0/3] Write dump into container's filesystem for pipe_type core_pattern

In current system, when we set core_pattern to a pipe, both pipe program and program's output are in host's filesystem. But when we set core_pattern to a file, the container will write dump into container's filesystem. For example, when we set following core_pattern: # echo "|/my_dump_pipe %s %c

[PATCH 2/3] Make dump_pipe thread possilbe to select the rootfs

To make the dump_pipe thread run in container's filesystem, we need to make it possible to select its fs_root from fork. Then the dump_pipe thread will exec user_defined pipe program in container's fs_root, and the problem will also write dumpdata into the same fs_root. Signed-off-by: Zhao Lei

[PATCH 3/3] Write dump into container's filesystem for pipe_type core_pattern

In current system, when we set core_pattern to a pipe, both pipe program and program's output are in host's filesystem. But when we set core_pattern to a file, the container will write dump into container's filesystem. For example, when we set following core_pattern: # echo "|/my_dump_pipe %s %c

[PATCH 3/3] Write dump into container's filesystem for pipe_type core_pattern

In current system, when we set core_pattern to a pipe, both pipe program and program's output are in host's filesystem. But when we set core_pattern to a file, the container will write dump into container's filesystem. For example, when we set following core_pattern: # echo "|/my_dump_pipe %s %c

[PATCH 2/3] Make dump_pipe thread possilbe to select the rootfs

To make the dump_pipe thread run in container's filesystem, we need to make it possible to select its fs_root from fork. Then the dump_pipe thread will exec user_defined pipe program in container's fs_root, and the problem will also write dumpdata into the same fs_root. Signed-off-by: Zhao Lei

Re: [tpmdd-devel] [BUG, bisect] tpm: Remove all uses of drvdata from the TPM Core

Stefan, On Tue, May 10, 2016 at 11:05:43AM -0400, Stefan Berger wrote: > Jeremiah Mahler wrote on 05/10/2016 09:55:23 AM: > > > > > all, > > > > My machine is locking up during suspend and I have bisected the > > problem to this patch (e89f8b1ade9cc1a) in the latest

Re: [tpmdd-devel] [BUG, bisect] tpm: Remove all uses of drvdata from the TPM Core

Stefan, On Tue, May 10, 2016 at 11:05:43AM -0400, Stefan Berger wrote: > Jeremiah Mahler wrote on 05/10/2016 09:55:23 AM: > > > > > all, > > > > My machine is locking up during suspend and I have bisected the > > problem to this patch (e89f8b1ade9cc1a) in the latest linux-next > > (20160506)

Re: [PATCH 2/2] ARM64: dts: rockchip: enable eMMC for rk3399 EVB

Hi, On Wed, May 11, 2016 at 08:59:24AM +0800, Shawn Lin wrote: > On 2016/5/11 8:02, Brian Norris wrote: > >The 'mmc-hs400-enhanced-strobe' property has been acked by Rob Herring, > >though it's still not merged. > > > > Hi Brain, > > I'm not sure whether it's acceptable to upstream new property

Re: [PATCH 2/2] ARM64: dts: rockchip: enable eMMC for rk3399 EVB

Hi, On Wed, May 11, 2016 at 08:59:24AM +0800, Shawn Lin wrote: > On 2016/5/11 8:02, Brian Norris wrote: > >The 'mmc-hs400-enhanced-strobe' property has been acked by Rob Herring, > >though it's still not merged. > > > > Hi Brain, > > I'm not sure whether it's acceptable to upstream new property

Re: [PATCH 1/2] ARM64: dts: rockchip: add sdhci/emmc for rk3399

+ Huang Lin On 2016/5/11 8:02, Brian Norris wrote: The bindings for rk3399's SDHCI + eMMC PHY have been accepted, so let's support eMMC now. Note that 'rockchip,rk3399-sdhci-5.1' is not documented, but per Heiko's previous suggestion, we don't want to clutter the arasan doc, and it's just a

Re: [PATCH 1/2] ARM64: dts: rockchip: add sdhci/emmc for rk3399

+ Huang Lin On 2016/5/11 8:02, Brian Norris wrote: The bindings for rk3399's SDHCI + eMMC PHY have been accepted, so let's support eMMC now. Note that 'rockchip,rk3399-sdhci-5.1' is not documented, but per Heiko's previous suggestion, we don't want to clutter the arasan doc, and it's just a

Re: [PATCH] bcache: bch_writeback_thread() is not freezable

On Mon, 2 May 2016, Jiri Kosina wrote: > On Tue, 19 Apr 2016, Jiri Kosina wrote: > > > From: Jiri Kosina > > > > bch_writeback_thread() is calling try_to_freeze(), but that's just an > > expensive no-op given the fact that the thread is not marked freezable. > > > > I/O

Re: [PATCH] bcache: bch_writeback_thread() is not freezable

On Mon, 2 May 2016, Jiri Kosina wrote: > On Tue, 19 Apr 2016, Jiri Kosina wrote: > > > From: Jiri Kosina > > > > bch_writeback_thread() is calling try_to_freeze(), but that's just an > > expensive no-op given the fact that the thread is not marked freezable. > > > > I/O helper kthreads,

linux-next: build failure after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) failed like this: sound/soc/intel/boards/bxt_rt298.c:257:3: error: unknown field 'be_id' specified in initializer .be_id = 0, ^ sound/soc/intel/boards/bxt_rt298.c:274:3: error: unknown field 'be_id'

linux-next: build failure after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) failed like this: sound/soc/intel/boards/bxt_rt298.c:257:3: error: unknown field 'be_id' specified in initializer .be_id = 0, ^ sound/soc/intel/boards/bxt_rt298.c:274:3: error: unknown field 'be_id'

Re: [PATCH] Staging: wlan-ng: fix comments style

Hi Greg, On Mon, May 09, 2016 at 02:26:13PM +0200, Kroah-Hartman wrote: On Sun, May 08, 2016 at 10:45:16AM -0400, YU Bo wrote: The patch fixed warning reported by checkpatch.pl: Block comments use a trailing */ on a separate line. Signed-off-by: YU Bo ---

Re: [PATCH] Staging: wlan-ng: fix comments style

Hi Greg, On Mon, May 09, 2016 at 02:26:13PM +0200, Kroah-Hartman wrote: On Sun, May 08, 2016 at 10:45:16AM -0400, YU Bo wrote: The patch fixed warning reported by checkpatch.pl: Block comments use a trailing */ on a separate line. Signed-off-by: YU Bo --- drivers/staging/wlan-ng/prism2mgmt.h

Re: [PATCH 2/2] ARM64: dts: rockchip: enable eMMC for rk3399 EVB

On 2016/5/11 8:02, Brian Norris wrote: The 'mmc-hs400-enhanced-strobe' property has been acked by Rob Herring, though it's still not merged. Hi Brain, I'm not sure whether it's acceptable to upstream new property which isn't merged yet. My major concern is that as the patchset supporting

Re: [PATCH 2/2] ARM64: dts: rockchip: enable eMMC for rk3399 EVB

On 2016/5/11 8:02, Brian Norris wrote: The 'mmc-hs400-enhanced-strobe' property has been acked by Rob Herring, though it's still not merged. Hi Brain, I'm not sure whether it's acceptable to upstream new property which isn't merged yet. My major concern is that as the patchset supporting

Re: PROBLEM: Scheduling latency not respected in CFS with HRTICK enabled

2016-05-11 8:53 GMT+08:00 Wanpeng Li : > 2016-05-06 23:43 GMT+08:00 Tomasz Grabiec : > [...] >> prev_comm=python prev_pid=873 prev_prio=120 prev_state=R ==> >> next_comm=python next_pid=874 next_prio=120 >> python 874 [002] 3273334.932741:

Re: PROBLEM: Scheduling latency not respected in CFS with HRTICK enabled

2016-05-11 8:53 GMT+08:00 Wanpeng Li : > 2016-05-06 23:43 GMT+08:00 Tomasz Grabiec : > [...] >> prev_comm=python prev_pid=873 prev_prio=120 prev_state=R ==> >> next_comm=python next_pid=874 next_prio=120 >> python 874 [002] 3273334.932741: probe:hrtick: (8109b430) >> python 874

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote: > +static int shiftfs_rename2(struct inode *olddir, struct dentry *old, > +struct inode *newdir, struct dentry *new, > +unsigned int flags) > +{ > + struct dentry *rodd =

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote: > +static int shiftfs_rename2(struct inode *olddir, struct dentry *old, > +struct inode *newdir, struct dentry *new, > +unsigned int flags) > +{ > + struct dentry *rodd =

Re: PROBLEM: Scheduling latency not respected in CFS with HRTICK enabled

2016-05-06 23:43 GMT+08:00 Tomasz Grabiec : [...] > prev_comm=python prev_pid=873 prev_prio=120 prev_state=R ==> > next_comm=python next_pid=874 next_prio=120 > python 874 [002] 3273334.932741: probe:hrtick: (8109b430) > python 874 [002] 3273334.932742:

Re: PROBLEM: Scheduling latency not respected in CFS with HRTICK enabled

2016-05-06 23:43 GMT+08:00 Tomasz Grabiec : [...] > prev_comm=python prev_pid=873 prev_prio=120 prev_state=R ==> > next_comm=python next_pid=874 next_prio=120 > python 874 [002] 3273334.932741: probe:hrtick: (8109b430) > python 874 [002] 3273334.932742: sched:sched_stat_runtime: >

Re: [PATCH v6 00/14] ACPI NUMA support for ARM64

On Wed, Apr 27, 2016 at 8:07 PM, David Daney wrote: > From: David Daney > > Based on git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git > for-next/core branch at commit 643d703d2d2d ("arm64: compat: Check for > AArch32 state") > > ACPI

Re: [PATCH v6 00/14] ACPI NUMA support for ARM64

On Wed, Apr 27, 2016 at 8:07 PM, David Daney wrote: > From: David Daney > > Based on git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git > for-next/core branch at commit 643d703d2d2d ("arm64: compat: Check for > AArch32 state") > > ACPI 5.1 already introduced NUMA support for ARM64,

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote: > mount -t shiftfs Note to self: do not eat while reading l-k...

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote: > mount -t shiftfs Note to self: do not eat while reading l-k...

Re: [PATCH v2 4/8] powerpc: add io{read,write}64 accessors

On Tue, 2016-05-10 at 18:50 +, Scott Wood wrote: > On 05/09/2016 03:20 AM, Horia Ioan Geanta Neag wrote: > > On 5/5/2016 6:37 PM, Horia Geantă wrote: > > > This will allow device drivers to consistently use io{read,write}XX > > > also for 64-bit accesses. > > > > > > Signed-off-by: Horia

Re: [PATCH v2 4/8] powerpc: add io{read,write}64 accessors

On Tue, 2016-05-10 at 18:50 +, Scott Wood wrote: > On 05/09/2016 03:20 AM, Horia Ioan Geanta Neag wrote: > > On 5/5/2016 6:37 PM, Horia Geantă wrote: > > > This will allow device drivers to consistently use io{read,write}XX > > > also for 64-bit accesses. > > > > > > Signed-off-by: Horia

[PATCH v2] kdump: Fix gdb macros work work with newer and 64-bit kernels

From: Corey Minyard Lots of little changes needed to be made to clean these up, remove the four byte pointer assumption and traverse the pid queue properly. Also consolidate the traceback code into a single function instead of having three copies of it. Signed-off-by: Corey

[PATCH v2] kdump: Fix gdb macros work work with newer and 64-bit kernels

From: Corey Minyard Lots of little changes needed to be made to clean these up, remove the four byte pointer assumption and traverse the pid queue properly. Also consolidate the traceback code into a single function instead of having three copies of it. Signed-off-by: Corey Minyard ---

Re: [PATCH 3/3] blk-throttle: don't parse cgroup path if trace isn't enabled

On Tue, May 10, 2016 at 11:52:15AM -0400, Jeff Moyer wrote: > Shaohua Li writes: > > > if trace isn't enabled, parsing cgroup path just wastes cpu > > > > Signed-off-by: Shaohua Li > > --- > > block/blk-throttle.c | 5 ++--- > > include/linux/blktrace_api.h |

Re: [PATCH 3/3] blk-throttle: don't parse cgroup path if trace isn't enabled

On Tue, May 10, 2016 at 11:52:15AM -0400, Jeff Moyer wrote: > Shaohua Li writes: > > > if trace isn't enabled, parsing cgroup path just wastes cpu > > > > Signed-off-by: Shaohua Li > > --- > > block/blk-throttle.c | 5 ++--- > > include/linux/blktrace_api.h | 9 + > > 2 files

[PATCH 08/10] block-throttle: handle high limit

Handle high limit like we handle low limit including downgrade/upgrade/idle detection logic. If cgroup has high limit, its throttling limit is high limit. Otherwise the throttling limit is max limit. queue downgrades from LIMIT_HIGH/LIMIT_MAX to LIMIT_LOW if cgroup is below low limit. queue

[PATCH 08/10] block-throttle: handle high limit

Handle high limit like we handle low limit including downgrade/upgrade/idle detection logic. If cgroup has high limit, its throttling limit is high limit. Otherwise the throttling limit is max limit. queue downgrades from LIMIT_HIGH/LIMIT_MAX to LIMIT_LOW if cgroup is below low limit. queue

[PATCH 03/10] block-throttle: configure bps/iops limit for cgroup in low limit

each queue will have a state machine. Initially queue is in LOW_LIMIT state, which means all cgroups will be throttled according to their low limit. After all cgroups with low limit cross the limit, the queue state gets upgraded to high/max state. This will guarantee cgroups with low limit have at

[PATCH 03/10] block-throttle: configure bps/iops limit for cgroup in low limit

each queue will have a state machine. Initially queue is in LOW_LIMIT state, which means all cgroups will be throttled according to their low limit. After all cgroups with low limit cross the limit, the queue state gets upgraded to high/max state. This will guarantee cgroups with low limit have at

[PATCH 02/10] block-throttle: add .low interface

Add low limit for cgroup and corresponding cgroup interface. Signed-off-by: Shaohua Li --- block/blk-throttle.c | 142 +++ 1 file changed, 110 insertions(+), 32 deletions(-) diff --git a/block/blk-throttle.c b/block/blk-throttle.c

[PATCH 07/10] block-throttle: add .high interface

Add high limit for cgroup and corresponding cgroup interface. Signed-off-by: Shaohua Li --- block/blk-throttle.c | 74 1 file changed, 69 insertions(+), 5 deletions(-) diff --git a/block/blk-throttle.c b/block/blk-throttle.c

[PATCH 05/10] block-throttle: add downgrade logic

When queue state machine is in higher state, say LIMIT_MAX state without LIMIT_HIGH state, but a cgroup is below its low limit for some time, the queue should be downgraded to lower state as cgroup's low limit doesn't meet. Signed-off-by: Shaohua Li --- block/blk-throttle.c | 160

[PATCH 02/10] block-throttle: add .low interface

Add low limit for cgroup and corresponding cgroup interface. Signed-off-by: Shaohua Li --- block/blk-throttle.c | 142 +++ 1 file changed, 110 insertions(+), 32 deletions(-) diff --git a/block/blk-throttle.c b/block/blk-throttle.c index

[PATCH 07/10] block-throttle: add .high interface

Add high limit for cgroup and corresponding cgroup interface. Signed-off-by: Shaohua Li --- block/blk-throttle.c | 74 1 file changed, 69 insertions(+), 5 deletions(-) diff --git a/block/blk-throttle.c b/block/blk-throttle.c index

[PATCH 05/10] block-throttle: add downgrade logic

When queue state machine is in higher state, say LIMIT_MAX state without LIMIT_HIGH state, but a cgroup is below its low limit for some time, the queue should be downgraded to lower state as cgroup's low limit doesn't meet. Signed-off-by: Shaohua Li --- block/blk-throttle.c | 160

[PATCH 00/10]block-throttle: add low/high limit

Hi, This patch set adds low/high limit for blk-throttle cgroup. The interface is io.low and io.high. low limit implements best effort bandwidth/iops protection. If one cgroup doesn't reach its low limit, no other cgroups can use more bandwidth/iops than their low limit. cgroup without low limit

[PATCH 04/10] block-throttle: add upgrade logic for LIMIT_LOW state

When queue is in LIMIT_LOW state and all cgroups with low limit cross the bps/iops limitation, we will upgrade queue's state to LIMIT_HIGH/LIMIT_MAX For a cgroup hierarchy, there are two cases. Children has lower low limit than parent. Parent's low limit is meaningless. If children's bps/iops

[PATCH 09/10] blk-throttle: make sure expire time isn't too big

cgroup could be throttled to a limit but when other cgroups are idle, queue enters a higher state and so the group should be throttled to a higher limit. It's possible the cgroup is sleeping because of throttle and other cgroups don't dispatch IO any more. In this case, nobody can trigger current

RE: [PATCH][RFC] cpufreq: intel_pstate: Avoid time-costly synchronization if schedutil is not enabled

Hi, > -Original Message- > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of > Rafael J. Wysocki > Sent: Wednesday, May 11, 2016 3:07 AM > To: Chen, Yu C > Cc: linux...@vger.kernel.org; Srinivas Pandruvada; Rafael J. Wysocki; Len > Brown; Viresh Kumar; Zhang, Rui; Linux

[PATCH 00/10]block-throttle: add low/high limit

Hi, This patch set adds low/high limit for blk-throttle cgroup. The interface is io.low and io.high. low limit implements best effort bandwidth/iops protection. If one cgroup doesn't reach its low limit, no other cgroups can use more bandwidth/iops than their low limit. cgroup without low limit

[PATCH 04/10] block-throttle: add upgrade logic for LIMIT_LOW state

When queue is in LIMIT_LOW state and all cgroups with low limit cross the bps/iops limitation, we will upgrade queue's state to LIMIT_HIGH/LIMIT_MAX For a cgroup hierarchy, there are two cases. Children has lower low limit than parent. Parent's low limit is meaningless. If children's bps/iops

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