Re: Some questions about the spi mem framework

Hi Boris, On Thu, 2018-05-17 at 09:42 +0200, Boris Brezillon wrote: > On Thu, 17 May 2018 15:35:04 +0800 > Xiangsheng Hou wrote: > > > On Thu, 2018-05-17 at 09:13 +0200, Boris Brezillon wrote: > > > On Thu, 17 May 2018 14:58:24 +0800 > > > Xiangsheng Hou

Re: Some questions about the spi mem framework

Hi Boris, On Thu, 2018-05-17 at 09:42 +0200, Boris Brezillon wrote: > On Thu, 17 May 2018 15:35:04 +0800 > Xiangsheng Hou wrote: > > > On Thu, 2018-05-17 at 09:13 +0200, Boris Brezillon wrote: > > > On Thu, 17 May 2018 14:58:24 +0800 > > > Xiangsheng Hou wrote: > > > > > > > Hi Boris, > > >

Re: [PATCH] scripts/tags.sh: don't rely on parsing `ls` for $ALLSOURCE_ARCHS generation

2018-05-16 9:13 GMT+09:00 Joey Pabalinas : > Parsing `ls` is fragile at best and _will_ fail when $tree > contains spaces. Replace this with a glob-generated string > and directly assign it to $ALLSOURCE_ARCHS; use a subshell > so `cd` doesn't affect the current working

Re: [PATCH] scripts/tags.sh: don't rely on parsing `ls` for $ALLSOURCE_ARCHS generation

2018-05-16 9:13 GMT+09:00 Joey Pabalinas : > Parsing `ls` is fragile at best and _will_ fail when $tree > contains spaces. Replace this with a glob-generated string > and directly assign it to $ALLSOURCE_ARCHS; use a subshell > so `cd` doesn't affect the current working directory. > >

Re: [RFC PATCH linux-next] USB: dwc3: dwc3_get_extcon() can be static

On 17.05.2018 18:06, kbuild test robot wrote: > Fixes: 5f0b74e54890 ("USB: dwc3: get extcon device by OF graph bindings") > Signed-off-by: kbuild test robot It should be static of course, my bad. Reviewed-by: Andrzej Hajda  -- Regards Andrzej >

Re: [RFC PATCH linux-next] USB: dwc3: dwc3_get_extcon() can be static

On 17.05.2018 18:06, kbuild test robot wrote: > Fixes: 5f0b74e54890 ("USB: dwc3: get extcon device by OF graph bindings") > Signed-off-by: kbuild test robot It should be static of course, my bad. Reviewed-by: Andrzej Hajda  -- Regards Andrzej > --- > drd.c |2 +- > 1 file changed, 1

Re: [PATCH v3 1/2] media: rc: introduce BPF_PROG_RAWIR_EVENT

On Thu, May 17, 2018 at 2:45 PM, Sean Young wrote: > Hi, > > Again thanks for a thoughtful review. This will definitely will improve > the code. > > On Thu, May 17, 2018 at 10:02:52AM -0700, Y Song wrote: >> On Wed, May 16, 2018 at 2:04 PM, Sean Young wrote: >> >

Re: [PATCH v3 1/2] media: rc: introduce BPF_PROG_RAWIR_EVENT

On Thu, May 17, 2018 at 2:45 PM, Sean Young wrote: > Hi, > > Again thanks for a thoughtful review. This will definitely will improve > the code. > > On Thu, May 17, 2018 at 10:02:52AM -0700, Y Song wrote: >> On Wed, May 16, 2018 at 2:04 PM, Sean Young wrote: >> > Add support for

Re: [PATCH 1/4] soc: qcom: mdt_loader: Add check to make scm calls

On Thu 17 May 04:32 PDT 2018, Vikash Garodia wrote: > In order to invoke scm calls, ensure that the platform > has the required support to invoke the scm calls in > secure world. > > Signed-off-by: Vikash Garodia > --- > drivers/soc/qcom/mdt_loader.c | 21

Re: [PATCH 1/4] soc: qcom: mdt_loader: Add check to make scm calls

On Thu 17 May 04:32 PDT 2018, Vikash Garodia wrote: > In order to invoke scm calls, ensure that the platform > has the required support to invoke the scm calls in > secure world. > > Signed-off-by: Vikash Garodia > --- > drivers/soc/qcom/mdt_loader.c | 21 + > 1 file

Re: [PATCH v2] ipc: Adding new return type vm_fault_t

On Wed, 16 May 2018, Souptick Joarder wrote: On Thu, May 10, 2018 at 7:34 PM, Souptick Joarder wrote: On Wed, Apr 25, 2018 at 10:04 AM, Souptick Joarder wrote: Use new return type vm_fault_t for fault handler. For now, this is just documenting

Re: [PATCH v2] ipc: Adding new return type vm_fault_t

On Wed, 16 May 2018, Souptick Joarder wrote: On Thu, May 10, 2018 at 7:34 PM, Souptick Joarder wrote: On Wed, Apr 25, 2018 at 10:04 AM, Souptick Joarder wrote: Use new return type vm_fault_t for fault handler. For now, this is just documenting that the function returns a VM_FAULT value

[PATCH] perf/x86/intel/uncore: allocate pmu index for pci device dynamically

Some boxes/devices of uncore are exported as pcie devices. However, the box number is different on different micro-architecture. For example, the max memory channels for Broadwell is up to 8. However, there are only 2 channels for Broadwell-DE, 4 channels for Broadwell-EP, and 8 channels for

[PATCH] perf/x86/intel/uncore: allocate pmu index for pci device dynamically

Some boxes/devices of uncore are exported as pcie devices. However, the box number is different on different micro-architecture. For example, the max memory channels for Broadwell is up to 8. However, there are only 2 channels for Broadwell-DE, 4 channels for Broadwell-EP, and 8 channels for

[RFC PATCH net-next] tcp: tcp_rack_reo_wnd() can be static

Fixes: 20b654dfe1be ("tcp: support DUPACK threshold in RACK") Signed-off-by: kbuild test robot --- tcp_recovery.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/ipv4/tcp_recovery.c b/net/ipv4/tcp_recovery.c index 30cbfb6..71593e4 100644 ---

[RFC PATCH net-next] tcp: tcp_rack_reo_wnd() can be static

Fixes: 20b654dfe1be ("tcp: support DUPACK threshold in RACK") Signed-off-by: kbuild test robot --- tcp_recovery.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/ipv4/tcp_recovery.c b/net/ipv4/tcp_recovery.c index 30cbfb6..71593e4 100644 --- a/net/ipv4/tcp_recovery.c

[net-next:master 1200/1233] net/ipv4/tcp_recovery.c:24:5: sparse: symbol 'tcp_rack_reo_wnd' was not declared. Should it be static?

tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master head: 538e2de104cfb4ef1acb35af42427bff42adbe4d commit: 20b654dfe1beaca60ab51894ff405a049248433d [1200/1233] tcp: support DUPACK threshold in RACK reproduce: # apt-get install sparse git checkout

[net-next:master 1200/1233] net/ipv4/tcp_recovery.c:24:5: sparse: symbol 'tcp_rack_reo_wnd' was not declared. Should it be static?

tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master head: 538e2de104cfb4ef1acb35af42427bff42adbe4d commit: 20b654dfe1beaca60ab51894ff405a049248433d [1200/1233] tcp: support DUPACK threshold in RACK reproduce: # apt-get install sparse git checkout

Re: [PATCH v2] kbuild: check for pkg-config on make {menu,n,g,x}config

Hi Randy, 2018-04-07 6:37 GMT+09:00 Randy Dunlap : > On 03/14/2018 10:50 PM, Masahiro Yamada wrote: >> 2018-03-13 11:30 GMT+09:00 Randy Dunlap : >>> From: Randy Dunlap >>> >>> Each of 'make {menu,n,g,x}config' uses (needs)

Re: [PATCH v2] kbuild: check for pkg-config on make {menu,n,g,x}config

Hi Randy, 2018-04-07 6:37 GMT+09:00 Randy Dunlap : > On 03/14/2018 10:50 PM, Masahiro Yamada wrote: >> 2018-03-13 11:30 GMT+09:00 Randy Dunlap : >>> From: Randy Dunlap >>> >>> Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure >>> that other required files are present, but

Re: [PATCH v9 04/11] arm64: kexec_file: allocate memory walking through memblock list

Baoquan, On Fri, May 18, 2018 at 09:37:35AM +0800, Baoquan He wrote: > On 05/17/18 at 07:04pm, James Morse wrote: > > Hi Baoquan, > > > > On 17/05/18 03:15, Baoquan He wrote: > > > On 05/17/18 at 10:10am, Baoquan He wrote: > > >> On 05/07/18 at 02:59pm, AKASHI Takahiro wrote: > > >>> On Tue, May

Re: [PATCH v9 04/11] arm64: kexec_file: allocate memory walking through memblock list

Baoquan, On Fri, May 18, 2018 at 09:37:35AM +0800, Baoquan He wrote: > On 05/17/18 at 07:04pm, James Morse wrote: > > Hi Baoquan, > > > > On 17/05/18 03:15, Baoquan He wrote: > > > On 05/17/18 at 10:10am, Baoquan He wrote: > > >> On 05/07/18 at 02:59pm, AKASHI Takahiro wrote: > > >>> On Tue, May

[PATCH v2 3/3] perf annotate: Support '--group' option

With the '--group' option, even for non-explicit group, perf annotate will enable the group output. For example, perf record -e cycles,branches ./div perf annotate main --stdio --group :Disassembly of section .text: : :

[PATCH v2 3/3] perf annotate: Support '--group' option

With the '--group' option, even for non-explicit group, perf annotate will enable the group output. For example, perf record -e cycles,branches ./div perf annotate main --stdio --group :Disassembly of section .text: : :

[PATCH v2 2/3] perf report: Use perf_evlist_forced_leader to support '--group'

Since we have created a new function perf_evlist_forced_leader, so now remove the old code and use perf_evlist_forced_leader instead. Signed-off-by: Jin Yao --- tools/perf/builtin-report.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH v2 2/3] perf report: Use perf_evlist_forced_leader to support '--group'

Since we have created a new function perf_evlist_forced_leader, so now remove the old code and use perf_evlist_forced_leader instead. Signed-off-by: Jin Yao --- tools/perf/builtin-report.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/tools/perf/builtin-report.c

[PATCH v2 1/3] perf evlist: Create a new function perf_evlist_forced_leader

For non-explicit group, perf report supports a option '--group' which can enable group output. We also need to support perf annotate with the same '--group'. Create a new function perf_evlist_forced_leader which contains common code to force setting the group leader. Signed-off-by: Jin Yao

[PATCH v2 1/3] perf evlist: Create a new function perf_evlist_forced_leader

For non-explicit group, perf report supports a option '--group' which can enable group output. We also need to support perf annotate with the same '--group'. Create a new function perf_evlist_forced_leader which contains common code to force setting the group leader. Signed-off-by: Jin Yao ---

[PATCH v2 0/3] perf annotate: Support '--group' option

For non-explicit group, perf report has already supported a option '--group' which can enable group output. This patch-set will support perf annotate with the same '--group'. For example, perf record -e cycles,branches ./div perf annotate main --stdio --group :

[PATCH v2 0/3] perf annotate: Support '--group' option

For non-explicit group, perf report has already supported a option '--group' which can enable group output. This patch-set will support perf annotate with the same '--group'. For example, perf record -e cycles,branches ./div perf annotate main --stdio --group :

[git pull] drm fixes for v4.17-rc6

Hi Linus, Pretty quiet week again, one vmwgfx regression fix, one core buffer overflow fix,one vc4 leak fix and three i915 fixes. Dave. The following changes since commit 76ef6b28ea4f81c3d511866a9b31392caa833126: drm: set FMODE_UNSIGNED_OFFSET for drm files (2018-05-15 14:46:04 +1000) are

[git pull] drm fixes for v4.17-rc6

Hi Linus, Pretty quiet week again, one vmwgfx regression fix, one core buffer overflow fix,one vc4 leak fix and three i915 fixes. Dave. The following changes since commit 76ef6b28ea4f81c3d511866a9b31392caa833126: drm: set FMODE_UNSIGNED_OFFSET for drm files (2018-05-15 14:46:04 +1000) are

[PATCH 3/5] kconfig: refactor GTK+ package checks for building gconf

Refactor the necessary package checks for building gconf in the same way as for qconf. Signed-off-by: Masahiro Yamada --- scripts/kconfig/Makefile | 43 +-- scripts/kconfig/gconf-cfg.sh | 23 +++ 2

[PATCH 5/5] kconfig: refactor ncurses package checks for building nconf

Building nconf requires ncurses, but its presence is not checked. Check and configure necessary packages as in the other GUI frontends. Signed-off-by: Masahiro Yamada --- scripts/kconfig/Makefile | 16 scripts/kconfig/nconf-cfg.sh | 22

[PATCH 3/5] kconfig: refactor GTK+ package checks for building gconf

Refactor the necessary package checks for building gconf in the same way as for qconf. Signed-off-by: Masahiro Yamada --- scripts/kconfig/Makefile | 43 +-- scripts/kconfig/gconf-cfg.sh | 23 +++ 2 files changed, 32 insertions(+),

[PATCH 5/5] kconfig: refactor ncurses package checks for building nconf

Building nconf requires ncurses, but its presence is not checked. Check and configure necessary packages as in the other GUI frontends. Signed-off-by: Masahiro Yamada --- scripts/kconfig/Makefile | 16 scripts/kconfig/nconf-cfg.sh | 22 ++ 2 files

[PATCH 0/5] kconfig: refactor package checks for GUI frontends

Kconfig supports 4 GUI frontends. Each of them needs some support packages, but checks them differently: qconf, gconf: check packages in Makefile (pkg-config is required) mconf: lxdialog/check-lxdialog.sh nconf: needs ncurses, but its presence is not checked This series refactor the

[PATCH 1/5] kbuild: do not display CHK for filechk

filechk displays two short logs; CHK for creating a temporary file, and UPD for really updating the target. IMHO, the build system can be quiet when the target file has not been updated. Signed-off-by: Masahiro Yamada --- scripts/Kbuild.include | 1 - 1 file

[PATCH 4/5] kconfig: refactor ncurses package checks for building mconf

The mconf (or its infrastructure, lxdiaglog) depends on ncurses. check-lxdialog.sh has additional checks in case pkg-config is not available. However, qconf and gconf already rely on pkg-config to check necessary packages. For simplification, drop the fallback code from check-lxdialog.sh and

[PATCH 1/5] kbuild: do not display CHK for filechk

filechk displays two short logs; CHK for creating a temporary file, and UPD for really updating the target. IMHO, the build system can be quiet when the target file has not been updated. Signed-off-by: Masahiro Yamada --- scripts/Kbuild.include | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH 4/5] kconfig: refactor ncurses package checks for building mconf

The mconf (or its infrastructure, lxdiaglog) depends on ncurses. check-lxdialog.sh has additional checks in case pkg-config is not available. However, qconf and gconf already rely on pkg-config to check necessary packages. For simplification, drop the fallback code from check-lxdialog.sh and

[PATCH 0/5] kconfig: refactor package checks for GUI frontends

Kconfig supports 4 GUI frontends. Each of them needs some support packages, but checks them differently: qconf, gconf: check packages in Makefile (pkg-config is required) mconf: lxdialog/check-lxdialog.sh nconf: needs ncurses, but its presence is not checked This series refactor the

[PATCH 2/5] kconfig: refactor Qt package checks for building qconf

Currently, the necessary package checks for building qconf is surrounded by ifeq ($(MAKECMDGOALS),xconfig) ... endif. Then, Make will restart when .tmp_qtcheck is generated. To simplify the Makefile, move the scripting to a separate file, and use filechk. The shell script is executed everytime

[PATCH 2/5] kconfig: refactor Qt package checks for building qconf

Currently, the necessary package checks for building qconf is surrounded by ifeq ($(MAKECMDGOALS),xconfig) ... endif. Then, Make will restart when .tmp_qtcheck is generated. To simplify the Makefile, move the scripting to a separate file, and use filechk. The shell script is executed everytime

[PATCH v2 7/7] memcg: supports movement of surplus hugepages statistics

When the task that charged surplus hugepages moves memory cgroup, it updates the statistical information correctly. Signed-off-by: TSUKADA Koutaro --- memcontrol.c | 99 +++ 1 file changed, 99 insertions(+) diff

[PATCH v2 7/7] memcg: supports movement of surplus hugepages statistics

When the task that charged surplus hugepages moves memory cgroup, it updates the statistical information correctly. Signed-off-by: TSUKADA Koutaro --- memcontrol.c | 99 +++ 1 file changed, 99 insertions(+) diff --git a/mm/memcontrol.c

[PATCH v2 6/7] Documentation, hugetlb: describe about charge_surplus_hugepages,

Add a description about charge_surplus_hugepages. Signed-off-by: TSUKADA Koutaro --- hugetlbpage.txt |6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/vm/hugetlbpage.txt b/Documentation/vm/hugetlbpage.txt index faf077d..af8d112 100644 ---

[PATCH v2 6/7] Documentation, hugetlb: describe about charge_surplus_hugepages,

Add a description about charge_surplus_hugepages. Signed-off-by: TSUKADA Koutaro --- hugetlbpage.txt |6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/vm/hugetlbpage.txt b/Documentation/vm/hugetlbpage.txt index faf077d..af8d112 100644 ---

Re: mmotm 2018-05-17-16-26 uploaded (autofs)

On 18/05/18 12:23, Randy Dunlap wrote: > On 05/17/2018 08:50 PM, Ian Kent wrote: >> On 18/05/18 08:21, Randy Dunlap wrote: >>> On 05/17/2018 04:26 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to

Re: mmotm 2018-05-17-16-26 uploaded (autofs)

On 18/05/18 12:23, Randy Dunlap wrote: > On 05/17/2018 08:50 PM, Ian Kent wrote: >> On 18/05/18 08:21, Randy Dunlap wrote: >>> On 05/17/2018 04:26 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to

[PATCH v2 5/7] hugetlb: add charge_surplus_hugepages attribute

Add an entry for charge_surplus_hugepages to sysfs. Signed-off-by: TSUKADA Koutaro --- hugetlb.c | 25 + 1 file changed, 25 insertions(+) diff --git a/mm/hugetlb.c b/mm/hugetlb.c index 9a9549c..2f9bdbc 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c

[PATCH v2 5/7] hugetlb: add charge_surplus_hugepages attribute

Add an entry for charge_surplus_hugepages to sysfs. Signed-off-by: TSUKADA Koutaro --- hugetlb.c | 25 + 1 file changed, 25 insertions(+) diff --git a/mm/hugetlb.c b/mm/hugetlb.c index 9a9549c..2f9bdbc 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c @@ -2662,6 +2662,30

[PATCH v2 4/7] mm, sysctl: make charging surplus hugepages controllable

Make the default hugetlb surplus hugepage controlable by /proc/sys/vm/charge_surplus_hugepages. Signed-off-by: TSUKADA Koutaro --- include/linux/hugetlb.h |2 ++ kernel/sysctl.c |7 +++ mm/hugetlb.c| 21 + 3 files

[PATCH v2 4/7] mm, sysctl: make charging surplus hugepages controllable

Make the default hugetlb surplus hugepage controlable by /proc/sys/vm/charge_surplus_hugepages. Signed-off-by: TSUKADA Koutaro --- include/linux/hugetlb.h |2 ++ kernel/sysctl.c |7 +++ mm/hugetlb.c| 21 + 3 files changed, 30 insertions(+)

[PATCH v2 3/7] memcg: use compound_order rather than hpage_nr_pages

The current memcg implementation assumes that the compound page is THP. In order to be able to charge surplus hugepage, we use compound_order. Signed-off-by: TSUKADA Koutaro --- memcontrol.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH v2 3/7] memcg: use compound_order rather than hpage_nr_pages

The current memcg implementation assumes that the compound page is THP. In order to be able to charge surplus hugepage, we use compound_order. Signed-off-by: TSUKADA Koutaro --- memcontrol.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/mm/memcontrol.c

Re: [PATCH 1/2] perf script: Show virtual addresses instead of offsets

Arnaldo, We already have a binary offset handy in perf code but there is no way to dump it with perf script. We can derive it from symname+symoff but that's a manual work. Will it be good to have a '-F binoff' option? Ravi On 05/18/2018 01:29 AM, Arnaldo Carvalho de Melo wrote: > Em Thu, May

Re: [PATCH 1/2] perf script: Show virtual addresses instead of offsets

Arnaldo, We already have a binary offset handy in perf code but there is no way to dump it with perf script. We can derive it from symname+symoff but that's a manual work. Will it be good to have a '-F binoff' option? Ravi On 05/18/2018 01:29 AM, Arnaldo Carvalho de Melo wrote: > Em Thu, May

[PATCH v2 2/7] hugetlb: support migrate charging for surplus hugepages

Surplus hugepages allocated for migration also charge to memory cgroup. Signed-off-by: TSUKADA Koutaro --- hugetlb.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/mm/hugetlb.c b/mm/hugetlb.c index 679c151f..2e7b543 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c @@

[PATCH v2 2/7] hugetlb: support migrate charging for surplus hugepages

Surplus hugepages allocated for migration also charge to memory cgroup. Signed-off-by: TSUKADA Koutaro --- hugetlb.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/mm/hugetlb.c b/mm/hugetlb.c index 679c151f..2e7b543 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c @@ -1687,6 +1687,8 @@

[PATCH v2 1/7] hugetlb: introduce charge_surplus_huge_pages to struct hstate

The charge_surplus_huge_pages indicates to charge surplus huge pages obteined from the normal page pool to memory cgroup. The default value is false. This patch implements the core part of charging surplus hugepages. Use the private and mem_cgroup member of the second entry of compound hugepage

[PATCH v2 1/7] hugetlb: introduce charge_surplus_huge_pages to struct hstate

The charge_surplus_huge_pages indicates to charge surplus huge pages obteined from the normal page pool to memory cgroup. The default value is false. This patch implements the core part of charging surplus hugepages. Use the private and mem_cgroup member of the second entry of compound hugepage

[PATCH v2 0/7] mm: pages for hugetlb's overcommit may be able to charge to memcg

Thanks to Mike Kravetz for comment on the previous version patch. The purpose of this patch-set is to make it possible to control whether or not to charge surplus hugetlb pages obtained by overcommitting to memory cgroup. In the future, I am trying to accomplish limiting the memory usage of

[PATCH v2 0/7] mm: pages for hugetlb's overcommit may be able to charge to memcg

Thanks to Mike Kravetz for comment on the previous version patch. The purpose of this patch-set is to make it possible to control whether or not to charge surplus hugetlb pages obtained by overcommitting to memory cgroup. In the future, I am trying to accomplish limiting the memory usage of

Re: mmotm 2018-05-17-16-26 uploaded (autofs)

On 05/17/2018 08:50 PM, Ian Kent wrote: > On 18/05/18 08:21, Randy Dunlap wrote: >> On 05/17/2018 04:26 PM, a...@linux-foundation.org wrote: >>> The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to >>> >>>http://www.ozlabs.org/~akpm/mmotm/ >>> >>> mmotm-readme.txt says >>> >>>

Re: mmotm 2018-05-17-16-26 uploaded (autofs)

On 05/17/2018 08:50 PM, Ian Kent wrote: > On 18/05/18 08:21, Randy Dunlap wrote: >> On 05/17/2018 04:26 PM, a...@linux-foundation.org wrote: >>> The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to >>> >>>http://www.ozlabs.org/~akpm/mmotm/ >>> >>> mmotm-readme.txt says >>> >>>

Re: [PATCH rdma-next 4/5] RDMA/hns: Add reset process for RoCE in hip08

On Fri, May 18, 2018 at 11:28:11AM +0800, Wei Hu (Xavier) wrote: > > > On 2018/5/17 23:14, Jason Gunthorpe wrote: > > On Thu, May 17, 2018 at 04:02:52PM +0800, Wei Hu (Xavier) wrote: > >> diff --git a/drivers/infiniband/hw/hns/hns_roce_hw_v2.c > >> b/drivers/infiniband/hw/hns/hns_roce_hw_v2.c >

Re: [PATCH rdma-next 4/5] RDMA/hns: Add reset process for RoCE in hip08

On Fri, May 18, 2018 at 11:28:11AM +0800, Wei Hu (Xavier) wrote: > > > On 2018/5/17 23:14, Jason Gunthorpe wrote: > > On Thu, May 17, 2018 at 04:02:52PM +0800, Wei Hu (Xavier) wrote: > >> diff --git a/drivers/infiniband/hw/hns/hns_roce_hw_v2.c > >> b/drivers/infiniband/hw/hns/hns_roce_hw_v2.c >

Re: Revert "dmaengine: pl330: add DMA_PAUSE feature"

On 17-05-18, 12:20, Frank Mori Hess wrote: > Sorry to keep coming back to this, but I'm experiencing a bit of > incredulity that you are saying what you seem to be saying. You seem > to be saying dmaengine provides no way to permanently stop a transfer > safely other than transferring the full

Re: Revert "dmaengine: pl330: add DMA_PAUSE feature"

On 17-05-18, 12:20, Frank Mori Hess wrote: > Sorry to keep coming back to this, but I'm experiencing a bit of > incredulity that you are saying what you seem to be saying. You seem > to be saying dmaengine provides no way to permanently stop a transfer > safely other than transferring the full

Re: [PATCH 0/3] Add support to disable sensor groups in P9

On 05/17/2018 06:08 PM, Guenter Roeck wrote: > On 05/16/2018 11:10 PM, Shilpasri G Bhat wrote: >> >> >> On 05/15/2018 08:32 PM, Guenter Roeck wrote: >>> On Thu, Mar 22, 2018 at 04:24:32PM +0530, Shilpasri G Bhat wrote: This patch series adds support to enable/disable OCC based

Re: [PATCH 0/3] Add support to disable sensor groups in P9

On 05/17/2018 06:08 PM, Guenter Roeck wrote: > On 05/16/2018 11:10 PM, Shilpasri G Bhat wrote: >> >> >> On 05/15/2018 08:32 PM, Guenter Roeck wrote: >>> On Thu, Mar 22, 2018 at 04:24:32PM +0530, Shilpasri G Bhat wrote: This patch series adds support to enable/disable OCC based

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

On Thu, May 17, 2018 at 10:53:32AM -0700, Laura Abbott wrote: > On 05/17/2018 10:08 AM, Michal Hocko wrote: > >On Thu 17-05-18 18:49:47, Michal Hocko wrote: > >>On Thu 17-05-18 16:58:32, Ville Syrjälä wrote: > >>>On Thu, May 17, 2018 at 04:36:29PM +0300, Ville Syrjälä wrote: > On Thu, May 17,

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

On Thu, May 17, 2018 at 10:53:32AM -0700, Laura Abbott wrote: > On 05/17/2018 10:08 AM, Michal Hocko wrote: > >On Thu 17-05-18 18:49:47, Michal Hocko wrote: > >>On Thu 17-05-18 16:58:32, Ville Syrjälä wrote: > >>>On Thu, May 17, 2018 at 04:36:29PM +0300, Ville Syrjälä wrote: > On Thu, May 17,

[PATCH v2 5/5] arm64: dts: rockchip: Add sdmmc UHS support for roc-rk3328-cc

From: Levin Du In roc-rk3328-cc board, the signal voltage of sdmmc is supplied by the vcc_sdio regulator, which is a mux between 1.8V and 3.3V, controlled by a special output only gpio pin labeled "gpiomut_pmuio_iout", corresponding bit 1 of the syscon GRF_SOC_CON10. This

[PATCH v2 5/5] arm64: dts: rockchip: Add sdmmc UHS support for roc-rk3328-cc

From: Levin Du In roc-rk3328-cc board, the signal voltage of sdmmc is supplied by the vcc_sdio regulator, which is a mux between 1.8V and 3.3V, controlled by a special output only gpio pin labeled "gpiomut_pmuio_iout", corresponding bit 1 of the syscon GRF_SOC_CON10. This special pin can now be

[PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

From: Levin Du Some GPIOs sit in the GRF_SOC_CON registers of Rockchip SoCs, which do not belong to the general pinctrl. Adding gpio-syscon support makes controlling regulator or LED using these special pins very easy by reusing existing drivers, such as gpio-regulator and

[PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

From: Levin Du Some GPIOs sit in the GRF_SOC_CON registers of Rockchip SoCs, which do not belong to the general pinctrl. Adding gpio-syscon support makes controlling regulator or LED using these special pins very easy by reusing existing drivers, such as gpio-regulator and led-gpio.

[PATCH v2 1/5] gpio: syscon: allow fetching syscon from parent node

From: Heiko Stuebner Syscon nodes can be a simple-mfd and the syscon-users then be declared as children of this node. That way the parent-child structure can be better represented for devices that are fully embedded in the syscon. Therefore allow getting the syscon from the

[PATCH v2 1/5] gpio: syscon: allow fetching syscon from parent node

From: Heiko Stuebner Syscon nodes can be a simple-mfd and the syscon-users then be declared as children of this node. That way the parent-child structure can be better represented for devices that are fully embedded in the syscon. Therefore allow getting the syscon from the parent if neither a

[PATCH v2 3/5] arm64: dts: rockchip: Add gpio-mute to rk3328

From: Levin Du Adding a new gpio controller named "gpio-mute" to rk3328, providing access to the GPIO_MUTE pin defined in the syscon GRF_SOC_CON10. The GPIO_MUTE pin is referred to as < 1>. Signed-off-by: Levin Du --- Changes in v2: - Rename

[PATCH v2 4/5] arm64: dts: rockchip: Add io-domain to roc-rk3328-cc

From: Levin Du It is necessary for the io domain setting of the SoC to match the voltage supplied by the regulators. Signed-off-by: Levin Du --- Changes in v2: None Changes in v1: - Split from V0. arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 12

[PATCH v2 3/5] arm64: dts: rockchip: Add gpio-mute to rk3328

From: Levin Du Adding a new gpio controller named "gpio-mute" to rk3328, providing access to the GPIO_MUTE pin defined in the syscon GRF_SOC_CON10. The GPIO_MUTE pin is referred to as < 1>. Signed-off-by: Levin Du --- Changes in v2: - Rename gpio_syscon10 to gpio_mute in rk3328.dtsi

[PATCH v2 4/5] arm64: dts: rockchip: Add io-domain to roc-rk3328-cc

From: Levin Du It is necessary for the io domain setting of the SoC to match the voltage supplied by the regulators. Signed-off-by: Levin Du --- Changes in v2: None Changes in v1: - Split from V0. arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 12 1 file changed, 12

Re: mmotm 2018-05-17-16-26 uploaded (autofs)

On 18/05/18 08:21, Randy Dunlap wrote: > On 05/17/2018 04:26 PM, a...@linux-foundation.org wrote: >> The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to >> >>http://www.ozlabs.org/~akpm/mmotm/ >> >> mmotm-readme.txt says >> >> README for mm-of-the-moment: >> >>

Re: mmotm 2018-05-17-16-26 uploaded (autofs)

On 18/05/18 08:21, Randy Dunlap wrote: > On 05/17/2018 04:26 PM, a...@linux-foundation.org wrote: >> The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to >> >>http://www.ozlabs.org/~akpm/mmotm/ >> >> mmotm-readme.txt says >> >> README for mm-of-the-moment: >> >>

Re: [PATCH v2 3/9] security: define security_kernel_read_blob() wrapper

Casey Schaufler writes: > On 5/17/2018 7:48 AM, Mimi Zohar wrote: >> In order for LSMs and IMA-appraisal to differentiate between the original >> and new syscalls (eg. kexec, kernel modules, firmware), both the original >> and new syscalls must call an LSM hook. >> >>

Re: [PATCH v2 3/9] security: define security_kernel_read_blob() wrapper

Casey Schaufler writes: > On 5/17/2018 7:48 AM, Mimi Zohar wrote: >> In order for LSMs and IMA-appraisal to differentiate between the original >> and new syscalls (eg. kexec, kernel modules, firmware), both the original >> and new syscalls must call an LSM hook. >> >> Commit 2e72d51b4ac3

[PATCH v2 0/5] Add sdmmc UHS support to ROC-RK3328-CC board.

From: Levin Du Hi all, this is an attemp to add sdmmc UHS support to the ROC-RK3328-CC board. This patch series adds a new compatible `rockchip,gpio-syscon` to the gpio-syscon driver for general Rockchip SoC usage. A new gpio controller named `gpio_mute` is defined in

[PATCH v2 0/5] Add sdmmc UHS support to ROC-RK3328-CC board.

From: Levin Du Hi all, this is an attemp to add sdmmc UHS support to the ROC-RK3328-CC board. This patch series adds a new compatible `rockchip,gpio-syscon` to the gpio-syscon driver for general Rockchip SoC usage. A new gpio controller named `gpio_mute` is defined in rk3328.dtsi so that all

[PATCH v2] net: qcom/emac: Allocate buffers from local node

Currently we use non-NUMA aware allocation for TPD and RRD buffers, this patch modifies to use NUMA friendly allocation. Signed-off-by: Hemanth Puranik --- Change since v1: - Addressed comments related to ordering drivers/net/ethernet/qualcomm/emac/emac-mac.c | 6

[PATCH v2] net: qcom/emac: Allocate buffers from local node

Currently we use non-NUMA aware allocation for TPD and RRD buffers, this patch modifies to use NUMA friendly allocation. Signed-off-by: Hemanth Puranik --- Change since v1: - Addressed comments related to ordering drivers/net/ethernet/qualcomm/emac/emac-mac.c | 6 -- 1 file changed, 4

Re: [PATCH rdma-next 4/5] RDMA/hns: Add reset process for RoCE in hip08

On 2018/5/17 23:14, Jason Gunthorpe wrote: > On Thu, May 17, 2018 at 04:02:52PM +0800, Wei Hu (Xavier) wrote: >> diff --git a/drivers/infiniband/hw/hns/hns_roce_hw_v2.c >> b/drivers/infiniband/hw/hns/hns_roce_hw_v2.c >> index 86ef15f..e1c44a6 100644 >> +++

Re: [PATCH rdma-next 4/5] RDMA/hns: Add reset process for RoCE in hip08

On 2018/5/17 23:14, Jason Gunthorpe wrote: > On Thu, May 17, 2018 at 04:02:52PM +0800, Wei Hu (Xavier) wrote: >> diff --git a/drivers/infiniband/hw/hns/hns_roce_hw_v2.c >> b/drivers/infiniband/hw/hns/hns_roce_hw_v2.c >> index 86ef15f..e1c44a6 100644 >> +++

Re: [PATCHv2][SMB3] Add kernel trace support

Very nice. Acked-by: Ronnie Sahlberg Possibly change the output from pid=6633 tid=0x0 sid=0x0 cmd=0 mid=0 to cmd=0 mid=0 pid=6633 tid=0x0 sid=0x0 just to make it easier for human-searching. I think the cmd will be useful much more often than pid/tid/sid and this would

Re: [PATCHv2][SMB3] Add kernel trace support

Very nice. Acked-by: Ronnie Sahlberg Possibly change the output from pid=6633 tid=0x0 sid=0x0 cmd=0 mid=0 to cmd=0 mid=0 pid=6633 tid=0x0 sid=0x0 just to make it easier for human-searching. I think the cmd will be useful much more often than pid/tid/sid and this would make it easier to look

[PATCH v2] Print the memcg's name when system-wide OOM happened

From: yuzhoujian The dump_header does not print the memcg's name when the system oom happened. So users cannot locate the certain container which contains the task that has been killed by the oom killer. System oom report will contain the memcg's name after this

[PATCH v2] Print the memcg's name when system-wide OOM happened

From: yuzhoujian The dump_header does not print the memcg's name when the system oom happened. So users cannot locate the certain container which contains the task that has been killed by the oom killer. System oom report will contain the memcg's name after this patch. Changes since v1: -

[PATCH -mm] mm, huge page: Copy to access sub-page last when copy huge page

From: Huang Ying Huge page helps to reduce TLB miss rate, but it has higher cache footprint, sometimes this may cause some issue. For example, when copying huge page on x86_64 platform, the cache footprint is 4M. But on a Xeon E5 v3 2699 CPU, there are 18 cores, 36

[PATCH -mm] mm, huge page: Copy to access sub-page last when copy huge page

From: Huang Ying Huge page helps to reduce TLB miss rate, but it has higher cache footprint, sometimes this may cause some issue. For example, when copying huge page on x86_64 platform, the cache footprint is 4M. But on a Xeon E5 v3 2699 CPU, there are 18 cores, 36 threads, and only 45M LLC

  1   2   3   4   5   6   7   8   9   10   >