Re: [PATCH V2 3/3] arm64: defconfig: Select CONFIG_PINCTRL_IMX8MN by default

2019-07-16 Thread Shawn Guo
On Tue, Jun 11, 2019 at 08:25:35PM +0800, anson.hu...@nxp.com wrote: > From: Anson Huang > > Enable CONFIG_PINCTRL_IMX8MN by default to support i.MX8MN > pinctrl driver. > > Signed-off-by: Anson Huang > Reviewed-by: Dong Aisheng Applied, thanks.

Re: [PATCH v2] kbuild: Fail if gold linker is detected

2019-07-16 Thread Masahiro Yamada
On Wed, Jul 17, 2019 at 4:47 AM Thomas Gleixner wrote: > > The gold linker has known issues of failing the build both in random and in > predictible ways: > > - The x86/X32 VDSO build fails with: > >arch/x86/entry/vdso/vclock_gettime-x32.o:vclock_gettime.c:function do_hres: >error: reloca

Re: [RFC PATCH 0/5] PTP: add support for Intel's TGPIO controller

2019-07-16 Thread Felipe Balbi
Hi, Richard Cochran writes: > On Tue, Jul 16, 2019 at 10:20:33AM +0300, Felipe Balbi wrote: >> TGPIO is a new IP which allows for time synchronization between systems >> without any other means of synchronization such as PTP or NTP. The >> driver is implemented as part of the PTP framework sin

Re: [RFC PATCH 5/5] PTP: Add support for Intel PMC Timed GPIO Controller

2019-07-16 Thread Felipe Balbi
Hi, Shannon Nelson writes: > On 7/16/19 12:20 AM, Felipe Balbi wrote: >> Add a driver supporting Intel Timed GPIO controller available as part >> of some Intel PMCs. >> >> Signed-off-by: Felipe Balbi > > Hi Felipe, just a couple of quick comments: > > There are several places where a line is

Re: [PATCH v8 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable

2019-07-16 Thread Joe Perches
On Tue, 2019-07-16 at 12:26 +0800, Zhenzhong Duan wrote: > .. as "nopv" support needs it to be changeable at boot up stage. > > Checkpatch reports warning, so move variable declarations from > hypervisor.c to hypervisor.h [] > diff --git a/arch/x86/xen/enlighten_hvm.c b/arch/x86/xen/enlighten_hvm.

Re: [PATCH v5 14/15] arm64: defconfig: Enable SDMA on i.mx8mq/8mm

2019-07-16 Thread Shawn Guo
On Mon, Jun 10, 2019 at 04:17:52PM +0800, yibin.g...@nxp.com wrote: > From: Robin Gong > > Enable SDMA support on i.mx8mq/8mm chips, including enabling > CONFIG_FW_LOADER_USER_HELPER/CONFIG_FW_LOADER_USER_HELPER_FALLBACK > for firmware loaded by udev. > > Signed-off-by: Robin Gong Applied, tha

Re: [PATCH v8 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable

2019-07-16 Thread Juergen Gross
On 17.07.19 08:46, Joe Perches wrote: On Tue, 2019-07-16 at 12:26 +0800, Zhenzhong Duan wrote: .. as "nopv" support needs it to be changeable at boot up stage. Checkpatch reports warning, so move variable declarations from hypervisor.c to hypervisor.h [] diff --git a/arch/x86/xen/enlighten_hv

Re: [RFC PATCH 4/5] PTP: Add flag for non-periodic output

2019-07-16 Thread Felipe Balbi
Hi Richard, Richard Cochran writes: > On Tue, Jul 16, 2019 at 10:20:37AM +0300, Felipe Balbi wrote: >> When this new flag is set, we can use single-shot output. >> >> Signed-off-by: Felipe Balbi >> --- >> include/uapi/linux/ptp_clock.h | 4 +++- >> 1 file changed, 3 insertions(+), 1 deletio

Re: [PATCH v4 11/24] PM / devfreq: tegra30: Add debug messages

2019-07-16 Thread Chanwoo Choi
On 19. 7. 16. 오후 10:26, Dmitry Osipenko wrote: > 16.07.2019 15:23, Chanwoo Choi пишет: >> Hi Dmitry, >> >> Usually, the kernel log print for all users >> such as changing the frequency, fail or success. >> >> But, if the log just show the register dump, >> it is not useful for all users. It is just

Re: [PATCH v5 12/15] ARM: dts: imx6ul: add dma support on ecspi

2019-07-16 Thread Shawn Guo
On Mon, Jun 10, 2019 at 04:17:50PM +0800, yibin.g...@nxp.com wrote: > From: Robin Gong > > Add dma support on ecspi. > > Signed-off-by: Robin Gong Applied, thanks.

Re: [PATCH v5 13/15] ARM: dts: imx6sll: correct sdma compatible

2019-07-16 Thread Shawn Guo
On Mon, Jun 10, 2019 at 04:17:51PM +0800, yibin.g...@nxp.com wrote: > From: Robin Gong > > Correct sdma compatible since ecspi errata ERR009165 has been fixed > on i.mx6sll as i.mx6ul. > > Signed-off-by: Robin Gong Applied, thanks.

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Sowjanya Komatineni
On 7/16/19 11:33 PM, Dmitry Osipenko wrote: В Tue, 16 Jul 2019 22:55:52 -0700 Sowjanya Komatineni пишет: On 7/16/19 10:42 PM, Dmitry Osipenko wrote: В Tue, 16 Jul 2019 22:25:25 -0700 Sowjanya Komatineni пишет: On 7/16/19 9:11 PM, Dmitry Osipenko wrote: В Tue, 16 Jul 2019 19:35:49 -070

RE: [PATCH] phy: Change the configuration interface param to void* to make it more general

2019-07-16 Thread Zengtao (B)
Hi Maxime: Thanks for your reply. >-Original Message- >From: Maxime Ripard [mailto:maxime.rip...@bootlin.com] >Sent: Thursday, July 11, 2019 7:21 PM >To: Zengtao (B) >Cc: kis...@ti.com; Chen-Yu Tsai ; Paul Kocialkowski >; Sakari Ailus ; >linux-kernel@vger.kernel.org; linux-arm-ker...@lis

Re: [PATCH v4 03/24] PM / devfreq: tegra30: Handle possible round-rate error

2019-07-16 Thread Chanwoo Choi
On 19. 7. 16. 오후 10:09, Dmitry Osipenko wrote: > 16.07.2019 14:50, Chanwoo Choi пишет: >> On 19. 7. 8. 오전 7:32, Dmitry Osipenko wrote: >>> The EMC clock rate rounding technically could fail, hence let's handle >>> the error cases properly. >>> >>> Signed-off-by: Dmitry Osipenko >>> --- >>> driver

Re: [PREEMPT_RT] splat in v5.2-rt1: r t_mutex_owner(lock) != current

2019-07-16 Thread Juri Lelli
Hi Clark, On 16/07/19 17:55, Clark Williams wrote: > Saw this after applying my thermal lock to raw patch and the change in i915 > for lockdep. The > splat occurred on boot when creating the kdump initramfs. System is an Intel > NUC i7 with 32GB ram > and 256GB SSD for rootfs. > > The booting

Re: [PATCH v4 02/24] PM / devfreq: tegra30: Keep interrupt disabled while governor is stopped

2019-07-16 Thread Chanwoo Choi
On 19. 7. 16. 오후 10:03, Dmitry Osipenko wrote: > 16.07.2019 14:47, Chanwoo Choi пишет: >> On 19. 7. 8. 오전 7:32, Dmitry Osipenko wrote: >>> There is no real need to keep interrupt always-enabled, will be nicer >>> to keep it disabled while governor is inactive. >>> >>> Suggested-by: Thierry Reding

Re: linux-next: build failure after merge of the rdma tree

2019-07-16 Thread Masahiro Yamada
Hi Stephen, On Wed, Jul 17, 2019 at 8:28 AM Stephen Rothwell wrote: > > Hi, > > On Wed, 10 Jul 2019 14:30:36 +1000 Stephen Rothwell > wrote: > > > > On Wed, 10 Jul 2019 11:04:43 +1000 Stephen Rothwell > > wrote: > > > > > > On Tue, 9 Jul 2019 12:46:34 + Jason Gunthorpe > > > wrote: > >

[PATCH v2] kbuild: update compile-test headers for v5.3-rc1

2019-07-16 Thread Masahiro Yamada
- Some headers graduated from the blacklist - hyperv_timer.h joined the header-test when CONFIG_X86=y - nf_tables*.h joined the header-test when CONFIG_NF_TABLES is enabled. - The entry for nf_tables_offload.h was added to fix build error for the combination of CONFIG_NF_TABLES=n and CONFIG_

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Dmitry Osipenko
В Tue, 16 Jul 2019 22:55:52 -0700 Sowjanya Komatineni пишет: > On 7/16/19 10:42 PM, Dmitry Osipenko wrote: > > В Tue, 16 Jul 2019 22:25:25 -0700 > > Sowjanya Komatineni пишет: > > > >> On 7/16/19 9:11 PM, Dmitry Osipenko wrote: > >>> В Tue, 16 Jul 2019 19:35:49 -0700 > >>> Sowjanya Komatinen

Re: Correct use of DMA api (Some newbie questions)

2019-07-16 Thread Randy Dunlap
On 7/14/19 10:06 AM, Nikolai Zhubr wrote: > Hi all, > > After reading some (apparently contradictory) revisions of DMA api references > in Documentation/DMA-*.txt, some (contradictory) discussions thereof, and > even digging through the in-tree drivers in search for a good enlightening > exampl

Re: mmotm 2019-07-16-17-14 uploaded

2019-07-16 Thread Randy Dunlap
On 7/16/19 11:19 PM, Randy Dunlap wrote: > On 7/16/19 9:38 PM, Stephen Rothwell wrote: >> Hi Randy, >> >> On Tue, 16 Jul 2019 20:50:11 -0700 Randy Dunlap >> wrote: >>> >>> drivers/gpu/drm/amd/amdgpu/Kconfig contains this (from linux-next.patch): >>> >>> --- a/drivers/gpu/drm/amd/amdgpu/Kconfig~li

[PATCH v3 08/12] kbuild: export_report: read modules.order instead of .tmp_versions/*.mod

2019-07-16 Thread Masahiro Yamada
Towards the goal of removing MODVERDIR aka .tmp_versions, read out modules.order to get the list of modules to be processed. This is simpler than parsing *.mod files in .tmp_versions. Signed-off-by: Masahiro Yamada --- Changes in v3: - New patch Changes in v2: None scripts/export_report.pl

[PATCH v3 09/12] kbuild: create *.mod with full directory path and remove MODVERDIR

2019-07-16 Thread Masahiro Yamada
While descending directories, Kbuild produces objects for modules, but do not link final *.ko files; it is done in the modpost. To keep track of modules, Kbuild creates a *.mod file in $(MODVERDIR) for every module it is building. Some post-processing steps read the necessary information from *.mo

Re: mmotm 2019-07-16-17-14 uploaded

2019-07-16 Thread Randy Dunlap
On 7/16/19 9:38 PM, Stephen Rothwell wrote: > Hi Randy, > > On Tue, 16 Jul 2019 20:50:11 -0700 Randy Dunlap wrote: >> >> drivers/gpu/drm/amd/amdgpu/Kconfig contains this (from linux-next.patch): >> >> --- a/drivers/gpu/drm/amd/amdgpu/Kconfig~linux-next >> +++ a/drivers/gpu/drm/amd/amdgpu/Kconfig

[PATCH v3 01/12] kbuild: do not create empty modules.order in the prepare stage

2019-07-16 Thread Masahiro Yamada
Currently, $(objtree)/modules.order is touched in two places. In the 'prepare0' rule, scripts/Makefile.build creates an empty modules.order while processing 'obj=.' In the 'modules' rule, the top-level Makefile overwrites it with the correct list of modules. While this might be a good side-effec

[PATCH v3 07/12] kbuild: modpost: read modules.order instead of $(MODVERDIR)/*.mod

2019-07-16 Thread Masahiro Yamada
Towards the goal of removing MODVERDIR, read out modules.order to get the list of modules to be processed. This is simpler than parsing *.mod files in $(MODVERDIR). For external modules, $(KBUILD_EXTMOD)/modules.order should be read. Signed-off-by: Masahiro Yamada --- Changes in v3: - Add ifd

[PATCH v3 03/12] kbuild: remove duplication from modules.order in sub-directories

2019-07-16 Thread Masahiro Yamada
Currently, only the top-level modules.order drops duplicated entries. The modules.order files in sub-directories potentially contain duplication. To list out the paths of all modules, I want to use modules.order instead of parsing *.mod files in $(MODVERDIR). To achieve this, I want to rip off du

[PATCH v3 11/12] kbuild: remove 'prepare1' target

2019-07-16 Thread Masahiro Yamada
Now that there is no rule for 'prepare1', it can go away. Signed-off-by: Masahiro Yamada --- Changes in v3: None Changes in v2: None Makefile | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Makefile b/Makefile index 9ad9f8d1130d..14458ab3d6a8 100644 --- a/Makefile +

[PATCH v3 04/12] scsi: remove pointless $(MODVERDIR)/$(obj)/53c700.ver

2019-07-16 Thread Masahiro Yamada
Nothing depends on this, so it is dead code. Signed-off-by: Masahiro Yamada --- Changes in v3: None Changes in v2: None drivers/scsi/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/scsi/Makefile b/drivers/scsi/Makefile index aeda53901064..c00e3dd57990 10064

[PATCH v3 12/12] kbuild: split out *.mod out of {single,multi}-used-m rules

2019-07-16 Thread Masahiro Yamada
Currently, *.mod is created as a side-effect of obj-m. Split out *.mod as a dedicated build rule, which allows to unify the %.c -> %.o rule, and remove the single-used-m rule. This also makes the incremental build of allmodconfig faster because it saves $(NM) invocation when there is no change in

[PATCH v3 05/12] kbuild: modinst: read modules.order instead of $(MODVERDIR)/*.mod

2019-07-16 Thread Masahiro Yamada
Towards the goal of removing MODVERDIR, read out modules.order to get the list of modules to be installed. This is simpler than parsing *.mod files in $(MODVERDIR). For external modules, $(KBUILD_EXTMOD)/modules.order should be read. Signed-off-by: Masahiro Yamada --- Changes in v3: None Change

[PATCH v3 10/12] kbuild: remove the first line of *.mod files

2019-07-16 Thread Masahiro Yamada
The current format of *.mod is like this: line 1: directory path to the .ko file line 2: a list of objects linked into this module line 3: unresolved symbols (only when CONFIG_TRIM_UNUSED_KSYMS=y) Now that *.mod and *.ko are created in the same directory, the line 1 provides no valuable inf

[PATCH v3 02/12] kbuild: get rid of kernel/ prefix from in-tree modules.{order,builtin}

2019-07-16 Thread Masahiro Yamada
Removing the 'kernel/' prefix will make our life easier because we can simply do 'cat modules.order' to get all built modules with full paths. Currently, we parse the first line of '*.mod' files in $(MODVERDIR). Since we have duplicated functionality here, I plan to remove MODVERDIR entirely. In

[PATCH v3 06/12] kbuild: modsign: read modules.order instead of $(MODVERDIR)/*.mod

2019-07-16 Thread Masahiro Yamada
Towards the goal of removing MODVERDIR, read out modules.order to get the list of modules to be signed. This is simpler than parsing *.mod files in $(MODVERDIR). The modules_sign target is only supported for in-kernel modules. So, this commit does not take care of external modules. Signed-off-by:

[PATCH RFC v2 2/2] cpufreq: mediatek: Support vproc shared by multiple component

2019-07-16 Thread Hsin-Yi Wang
mt8183-cci shares vproc with small cluster. If the regulator is shared between several devices then the lowest request voltage that meets the system constraints will be used. However, previous mediatek cpufreq implementation would cause race condition if vproc is shared by multiple devices, which

[PATCH RFC v2 0/2] Use cpu based scaling passive governor for MT8183 CCI

2019-07-16 Thread Hsin-Yi Wang
This series depends on following series: 1. mt8183 cpufreq and cci devfreq from andrew-sh.cheng https://patchwork.kernel.org/cover/10946047/ 2. cpu based scaling support to passive_governor from Sibi Sankar https://lore.kernel.org/patchwork/patch/1101049/ This series uses cpu based scaling passiv

[PATCH RFC v2 1/2] devfreq: mt8183-cci: using cpu based scaling passive_governor

2019-07-16 Thread Hsin-Yi Wang
This is based on mediatek's devfreq patches[1]. In MT8183 SoC, CCI and little core cluster share same regulator. In original implementation, CCI frequency depends on regulator voltage, which results in bad memory access performance if tasks are loaded on other cpus other than little cluster (cpus

RE: [PATCH] infiniband: hw: qedr: Remove Unneeded variable rc

2019-07-16 Thread Michal Kalderon
> From: linux-rdma-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Hariprasad Kelam > > fix below issue reported by coccicheck > drivers/infiniband/hw/qedr/verbs.c:2454:5-7: Unneeded variable: "rc". > Return "0" on line 2499 > > Signed-off-by: Hariprasad Kelam > --- > drivers/infinib

[PATCH 2/3] dt-bindings: arm: Document i.MX8QXP AI_ML board binding

2019-07-16 Thread Manivannan Sadhasivam
Document devicetree binding of i.MX8QXP AI_ML board from Einfochips. Signed-off-by: Manivannan Sadhasivam --- Documentation/devicetree/bindings/arm/fsl.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm

[PATCH 0/3] Add support for i.MXQXP AI_ML board

2019-07-16 Thread Manivannan Sadhasivam
Hello, This patchset adds support for i.MXQXP AI_ML board from Einfochips. This board is one of the Consumer Edition boards of the 96Boards family based on i.MX8QXP SoC from NXP/Freescale. The initial support includes following peripherals which are tested and known to be working: 1. Debug seria

[PATCH 3/3] arm64: dts: freescale: Add support for i.MX8QXP AI_ML board

2019-07-16 Thread Manivannan Sadhasivam
Add support for i.MX8QXP AI_ML board from Einfochips. This board is one of the Consumer Edition boards of the 96Boards family based on i.MX8QXP SoC from NXP/Freescale. The initial support includes following peripherals which are tested and known to be working: 1. Debug serial via UART2 2. uSD 3.

[PATCH 1/3] dt-bindings: Add Vendor prefix for Einfochips

2019-07-16 Thread Manivannan Sadhasivam
Add devicetree vendor prefix for Einfochips. https://www.einfochips.com/ Signed-off-by: Manivannan Sadhasivam --- Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/d

Re: [PATCH v4] mmc: host: sdhci-sprd: Fix the incorrect soft reset operation when runtime resuming

2019-07-16 Thread Adrian Hunter
On 17/07/19 5:28 AM, Baolin Wang wrote: > In sdhci_runtime_resume_host() function, we will always do software reset > for all, which will cause Spreadtrum host controller work abnormally after > resuming. > > Thus for Spreadtrum platform that will not power down the SD/eMMC card during > runtime s

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Sowjanya Komatineni
On 7/16/19 10:42 PM, Dmitry Osipenko wrote: В Tue, 16 Jul 2019 22:25:25 -0700 Sowjanya Komatineni пишет: On 7/16/19 9:11 PM, Dmitry Osipenko wrote: В Tue, 16 Jul 2019 19:35:49 -0700 Sowjanya Komatineni пишет: On 7/16/19 7:18 PM, Sowjanya Komatineni wrote: On 7/16/19 3:06 PM, Sowjanya

Re: [PATCH] opp: Return genpd virtual devices from dev_pm_opp_attach_genpd()

2019-07-16 Thread Viresh Kumar
On 11-07-19, 15:09, Rajendra Nayak wrote: > Sorry for the delay Same here :) > I seem to have completely missed this patch. > I just gave this a try and here are some observations, > > I have a case where I have one device with 2 power domains, one of them > is scale-able (supports perf state) a

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Dmitry Osipenko
В Tue, 16 Jul 2019 22:25:25 -0700 Sowjanya Komatineni пишет: > On 7/16/19 9:11 PM, Dmitry Osipenko wrote: > > В Tue, 16 Jul 2019 19:35:49 -0700 > > Sowjanya Komatineni пишет: > > > >> On 7/16/19 7:18 PM, Sowjanya Komatineni wrote: > >>> On 7/16/19 3:06 PM, Sowjanya Komatineni wrote: >

Re: [PATCH 2/2] mm,memory_hotplug: Fix shrink_{zone,node}_span

2019-07-16 Thread Aneesh Kumar K.V
Oscar Salvador writes: > On Mon, 2019-07-15 at 21:41 +0530, Aneesh Kumar K.V wrote: >> Oscar Salvador writes: >> >> > Since [1], shrink_{zone,node}_span work on PAGES_PER_SUBSECTION >> > granularity. >> > The problem is that deactivation of the section occurs later on in >> > sparse_remove_sect

Re: [PATCH] Revert "kmemleak: allow to coexist with fault injection"

2019-07-16 Thread Michal Hocko
On Tue 16-07-19 16:28:21, Qian Cai wrote: > On Tue, 2019-07-16 at 22:07 +0200, Michal Hocko wrote: > > On Tue 16-07-19 15:21:17, Qian Cai wrote: > > [...] > > > Thanks to this commit, there are allocation with __GFP_DIRECT_RECLAIM that > > > succeeded would keep trying with __GFP_NOFAIL for kmemlea

RE: [LINUX PATCH v18 1/2] mtd: rawnand: nand_micron: Do not over write driver's read_page()/write_page()

2019-07-16 Thread Naga Sureshkumar Relli
Hi Boris, > -Original Message- > From: Boris Brezillon > Sent: Tuesday, July 16, 2019 1:15 PM > To: Naga Sureshkumar Relli > Cc: miquel.ray...@bootlin.com; bbrezil...@kernel.org; rich...@nod.at; > dw...@infradead.org; computersforpe...@gmail.com; marek.va...@gmail.com; > vigne...@ti.com;

Re: [PATCH] locking/lockdep: hide unused 'class' variable

2019-07-16 Thread Yuyang Du
Whoops. Thanks. On Mon, 15 Jul 2019 at 17:28, Arnd Bergmann wrote: > > The usage is now hidden in an #ifdef, so we need to move > the variable itself in there as well to avoid this warning: > > kernel/locking/lockdep_proc.c:203:21: error: unused variable 'class' > [-Werror,-Wunused-variable]

Re: [PATCH] Revert "kmemleak: allow to coexist with fault injection"

2019-07-16 Thread Michal Hocko
On Wed 17-07-19 01:50:31, Yang Shi wrote: > When running ltp's oom test with kmemleak enabled, the below warning was > triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is > passed in: > > WARNING: CPU: 105 PID: 2138 at mm/page_alloc.c:4608 > __alloc_pages_nodemask+0x1c31/0x1d5

Re: [PATCH] Revert "kmemleak: allow to coexist with fault injection"

2019-07-16 Thread Michal Hocko
On Wed 17-07-19 07:07:11, Michal Hocko wrote: > On Wed 17-07-19 01:50:31, Yang Shi wrote: > > When running ltp's oom test with kmemleak enabled, the below warning was > > triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is > > passed in: > > > > WARNING: CPU: 105 PID: 2138 at m

Re: [Xen-devel][PATCH v3] xen/pv: Fix a boot up hang revealed by int3 self test

2019-07-16 Thread Juergen Gross
On 14.07.19 11:15, Zhenzhong Duan wrote: Commit 7457c0da024b ("x86/alternatives: Add int3_emulate_call() selftest") is used to ensure there is a gap setup in int3 exception stack which could be used for inserting call return address. This gap is missed in XEN PV int3 exception entry path, then b

Re: [PATCH v8 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable

2019-07-16 Thread Juergen Gross
On 16.07.19 06:26, Zhenzhong Duan wrote: .. as "nopv" support needs it to be changeable at boot up stage. Checkpatch reports warning, so move variable declarations from hypervisor.c to hypervisor.h Signed-off-by: Zhenzhong Duan Reviewed-by: Juergen Gross ... and complete series applied to

Re: [PATCH v2 3/3] nvme-pci: Add support for Apple 2018+ models

2019-07-16 Thread Benjamin Herrenschmidt
On Wed, 2019-07-17 at 06:50 +0200, Christoph Hellwig wrote: > > # Conflicts: > > # drivers/nvme/host/core.c > > I thought you were going to fix this up :) Haha yeah I was ... > But I can do that and this version of the series looks fine to me. Thanks ! Cheers, Ben.

Re: [PATCH v2 3/3] nvme-pci: Add support for Apple 2018+ models

2019-07-16 Thread Christoph Hellwig
> # Conflicts: > # drivers/nvme/host/core.c I thought you were going to fix this up :) But I can do that and this version of the series looks fine to me.

Re: [PATCH 11/13] arm64: dts: qcom: qcs404: Add CPR and populate OPP table

2019-07-16 Thread Viresh Kumar
On 16-07-19, 12:53, Niklas Cassel wrote: > Here I cheated and simply used get_cpu_device(0). > > Since I cheated, I used get_cpu_device(0) always, > so even when CPU1,CPU2,CPU3 is attached, dev_pm_opp_get_opp_count(cpu0) is > still 0. > > I added a print in > [3.836533] cpr_set_performance: n

Re: [Xen-devel][PATCH v3] xen/pv: Fix a boot up hang revealed by int3 self test

2019-07-16 Thread Juergen Gross
On 14.07.19 11:15, Zhenzhong Duan wrote: Commit 7457c0da024b ("x86/alternatives: Add int3_emulate_call() selftest") is used to ensure there is a gap setup in int3 exception stack which could be used for inserting call return address. This gap is missed in XEN PV int3 exception entry path, then b

Re: [PATCH 1/3] mm: document zone device struct page reserved fields

2019-07-16 Thread Christoph Hellwig
On Tue, Jul 16, 2019 at 09:31:33PM -0700, John Hubbard wrote: > OK, so just delete all the _zd_pad_* fields? Works for me. It's misleading to > calling something padding, if it's actually unavailable because it's used > in the other union, so deleting would be even better than commenting. > > In t

Re: mmotm 2019-07-16-17-14 uploaded

2019-07-16 Thread Stephen Rothwell
Hi Randy, On Tue, 16 Jul 2019 20:50:11 -0700 Randy Dunlap wrote: > > drivers/gpu/drm/amd/amdgpu/Kconfig contains this (from linux-next.patch): > > --- a/drivers/gpu/drm/amd/amdgpu/Kconfig~linux-next > +++ a/drivers/gpu/drm/amd/amdgpu/Kconfig > @@ -27,7 +27,12 @@ config DRM_AMDGPU_CIK > config D

Re: [PATCH 1/3] mm: document zone device struct page reserved fields

2019-07-16 Thread John Hubbard
On 7/16/19 9:22 PM, Christoph Hellwig wrote: > On Tue, Jul 16, 2019 at 06:20:23PM -0700, John Hubbard wrote: >>> - unsigned long _zd_pad_1;/* uses mapping */ >>> + /* >>> +* The following fields are used to hold the source >>> +

linux-next: Tree for Jul 17

2019-07-16 Thread Stephen Rothwell
Hi all, Please do not add v5.4 material to your linux-next included branches until after v5.3-rc1 has been released. Changes since 20190716: The kbuild tree lost its build failure. The xfs tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree):

Re: [PATCH v7] cpufreq/pasemi: fix an use-after-free in pas_cpufreq_cpu_init()

2019-07-16 Thread Viresh Kumar
On 17-07-19, 11:55, Wen Yang wrote: > The cpu variable is still being used in the of_get_property() call > after the of_node_put() call, which may result in use-after-free. > > Fixes: a9acc26b75f6 ("cpufreq/pasemi: fix possible object reference leak") > Signed-off-by: Wen Yang > Cc: "Rafael J. Wy

[PATCH v8 5/5] x86/xen: Add "nopv" support for HVM guest

2019-07-16 Thread Zhenzhong Duan
PVH guest needs PV extentions to work, so "nopv" parameter should be ignored for PVH but not for HVM guest. If PVH guest boots up via the Xen-PVH boot entry, xen_pvh is set early, we know it's PVH guest and ignore "nopv" parameter directly. If PVH guest boots up via the normal boot entry same as

[PATCH v8 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable

2019-07-16 Thread Zhenzhong Duan
.. as "nopv" support needs it to be changeable at boot up stage. Checkpatch reports warning, so move variable declarations from hypervisor.c to hypervisor.h Signed-off-by: Zhenzhong Duan Cc: Boris Ostrovsky Cc: Juergen Gross Cc: Stefano Stabellini Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Bor

Re: [PATCH 1/3] mm: document zone device struct page reserved fields

2019-07-16 Thread Christoph Hellwig
On Tue, Jul 16, 2019 at 06:20:23PM -0700, John Hubbard wrote: > > - unsigned long _zd_pad_1;/* uses mapping */ > > + /* > > +* The following fields are used to hold the source > > +* page anonymous mapping informati

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Dmitry Osipenko
В Tue, 16 Jul 2019 19:35:49 -0700 Sowjanya Komatineni пишет: > On 7/16/19 7:18 PM, Sowjanya Komatineni wrote: > > > > On 7/16/19 3:06 PM, Sowjanya Komatineni wrote: > >> > >> On 7/16/19 3:00 PM, Dmitry Osipenko wrote: > >>> 17.07.2019 0:35, Sowjanya Komatineni пишет: > On 7/16/19 2:21

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Sowjanya Komatineni
On 7/16/19 8:54 PM, Dmitry Osipenko wrote: В Tue, 16 Jul 2019 19:18:19 -0700 Sowjanya Komatineni пишет: On 7/16/19 3:06 PM, Sowjanya Komatineni wrote: On 7/16/19 3:00 PM, Dmitry Osipenko wrote: 17.07.2019 0:35, Sowjanya Komatineni пишет: On 7/16/19 2:21 PM, Dmitry Osipenko wrote: 17.07.2

Re: [PATCH v2 1/2] dt-bindings: mmc: Document Aspeed SD controller

2019-07-16 Thread Andrew Jeffery
On Wed, 17 Jul 2019, at 00:27, Rob Herring wrote: > On Mon, Jul 15, 2019 at 6:36 PM Andrew Jeffery wrote: > > > > > > > > On Tue, 16 Jul 2019, at 07:47, Rob Herring wrote: > > > On Thu, Jul 11, 2019 at 9:32 PM Andrew Jeffery wrote: > > > > > > > > The ASPEED SD/SDIO/eMMC controller exposes two

[PATCH v7] cpufreq/pasemi: fix an use-after-free in pas_cpufreq_cpu_init()

2019-07-16 Thread Wen Yang
The cpu variable is still being used in the of_get_property() call after the of_node_put() call, which may result in use-after-free. Fixes: a9acc26b75f6 ("cpufreq/pasemi: fix possible object reference leak") Signed-off-by: Wen Yang Cc: "Rafael J. Wysocki" Cc: Viresh Kumar Cc: Michael Ellerman

Re: mmotm 2019-07-16-17-14 uploaded

2019-07-16 Thread Randy Dunlap
On 7/16/19 8:50 PM, Randy Dunlap wrote: > On 7/16/19 5:15 PM, a...@linux-foundation.org wrote: >> The mm-of-the-moment snapshot 2019-07-16-17-14 has been uploaded to >> >>http://www.ozlabs.org/~akpm/mmotm/ >> >> mmotm-readme.txt says >> >> README for mm-of-the-moment: >> >> http://www.ozlabs.or

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Dmitry Osipenko
В Tue, 16 Jul 2019 19:18:19 -0700 Sowjanya Komatineni пишет: > On 7/16/19 3:06 PM, Sowjanya Komatineni wrote: > > > > On 7/16/19 3:00 PM, Dmitry Osipenko wrote: > >> 17.07.2019 0:35, Sowjanya Komatineni пишет: > >>> On 7/16/19 2:21 PM, Dmitry Osipenko wrote: > 17.07.2019 0:12, Sowjanya

Re: mmotm 2019-07-16-17-14 uploaded

2019-07-16 Thread Randy Dunlap
On 7/16/19 5:15 PM, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2019-07-16-17-14 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my -m

Re: [PATCH 2/3 v3] dt-bindings: gpio: aspeed: Add SGPIO support

2019-07-16 Thread Andrew Jeffery
Hello Hongwei, On Wed, 17 Jul 2019, at 07:18, Hongwei Zhang wrote: > Add bindings to support SGPIO on AST2400 or AST2500. > > Signed-off-by: Hongwei Zhang > --- > .../devicetree/bindings/gpio/sgpio-aspeed.txt | 55 > ++ > 1 file changed, 55 insertions(+) > create mode

Re: [PATCH] dax: Fix missed PMD wakeups

2019-07-16 Thread Dan Williams
On Fri, Jul 12, 2019 at 2:14 AM Jan Kara wrote: > > On Thu 11-07-19 08:25:50, Matthew Wilcox wrote: > > On Thu, Jul 11, 2019 at 07:13:50AM -0700, Matthew Wilcox wrote: > > > However, the XA_RETRY_ENTRY might be a good choice. It doesn't normally > > > appear in an XArray (it may appear if you're

[PATCH] acpica: fix -Wnull-pointer-arithmetic warnings

2019-07-16 Thread Qian Cai
Clang generate quite a few of those warnings. drivers/acpi/scan.c:759:28: warning: arithmetic on a null pointer treated as a cast from integer to pointer is a GNU extension [-Wnull-pointer-arithmetic] status = acpi_get_handle(ACPI_ROOT_OBJECT, obj->string.pointer,

Re: [PATCH v7 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable

2019-07-16 Thread Juergen Gross
On 17.07.19 04:09, Zhenzhong Duan wrote: On 2019/7/16 18:57, Juergen Gross wrote: On 11.07.19 14:02, Zhenzhong Duan wrote: .. as "nopv" support needs it to be changeable at boot up stage. Checkpatch report warning, so move variable declarations from hypervisor.c to hypervisor.h Signed-off-by

Re: [PATCH 2/3 v3] ARM: dts: aspeed: Add SGPIO driver

2019-07-16 Thread Andrew Jeffery
Hello Hongwei, Please send patches and feedback on prior iterations separately. Please send the output of `git format-patch ...`directly; format-patch spits the patch out in email form ready to go and can be fed straight to `git send-email`. On Wed, 17 Jul 2019, at 06:54, Hongwei Zhang wrote: >

Re: properly communicate queue limits to the DMA layer v2

2019-07-16 Thread Martin K. Petersen
Christoph, > I think all the patches on the block side went into 5.2, but it's been > a while, so I might misremember.. I checked my notes and the reason I held them back was that I was waiting for a response from Broadcom wrt. the megaraid segment size limitation. However, given that mpt3sas

Re: [PATCH] skbuff: fix compilation warnings in skb_dump()

2019-07-16 Thread Joe Perches
On Tue, 2019-07-16 at 17:04 +0200, Willem de Bruijn wrote: > On Tue, Jul 16, 2019 at 4:56 PM Qian Cai wrote: > > Fix them by using the proper types, and also fix some checkpatch > > warnings by using pr_info(). > > > > WARNING: printk() should include KERN_ facility level > > + prin

Re: [RFC PATCH 2/3] sched: change scheduler to give preference to soft affinity CPUs

2019-07-16 Thread Subhra Mazumdar
On 7/2/19 10:58 PM, Peter Zijlstra wrote: On Wed, Jun 26, 2019 at 03:47:17PM -0700, subhra mazumdar wrote: The soft affinity CPUs present in the cpumask cpus_preferred is used by the scheduler in two levels of search. First is in determining wake affine which choses the LLC domain and secondly

Re: [PATCH v3] virtio_pmem: fix sparse warning

2019-07-16 Thread Dan Williams
On Fri, Jul 12, 2019 at 7:11 AM Michael S. Tsirkin wrote: > > On Fri, Jul 12, 2019 at 10:46:10AM +0530, Pankaj Gupta wrote: > > This patch fixes below sparse warning related to __virtio > > type in virtio pmem driver. This is reported by Intel test > > bot on linux-next tree. > > > > nd_virtio.c:5

[PATCH] KVM: x86/vPMU: reset pmc->counter to 0 for pmu fixed_counters

2019-07-16 Thread Like Xu
To avoid semantic inconsistency, the fixed_counters in Intel vPMU need to be reset to 0 in intel_pmu_reset() as gp_counters does. Signed-off-by: Like Xu --- arch/x86/kvm/vmx/pmu_intel.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/arch/x86/kvm/vmx/pmu_intel.c b

Re: [PATCH] opp: Return genpd virtual devices from dev_pm_opp_attach_genpd()

2019-07-16 Thread Viresh Kumar
On 16-07-19, 12:43, Niklas Cassel wrote: > On Mon, Jul 08, 2019 at 11:30:11AM +0530, Viresh Kumar wrote: > > The cpufreq drivers don't need to do runtime PM operations on the > > virtual devices returned by dev_pm_domain_attach_by_name() and so the > > virtual devices weren't shared with the caller

Re: [kbuild:kbuild 5/19] drivers/atm/eni.o: warning: objtool: eni_init_one()+0xe42: indirect call found in RETPOLINE build

2019-07-16 Thread Masahiro Yamada
On Wed, Jul 17, 2019 at 1:20 AM Josh Poimboeuf wrote: > > On Tue, Jul 16, 2019 at 07:42:49AM -0500, Seth Forshee wrote: > > On Tue, Jul 16, 2019 at 03:57:24PM +0900, Masahiro Yamada wrote: > > > (+ Josh Poimboeuf) > > > > > > On Tue, Jul 16, 2019 at 8:44 AM kbuild test robot wrote: > > > > > > >

Re: [PATCH -next] scsi: lpfc: Remove unnecessary null check before kfree

2019-07-16 Thread Martin K. Petersen
YueHaibing, > A null check before a kfree is redundant, so remove it. > This is detected by coccinelle. Applied to 5.4/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH v1] scsi: ufs: change msleep to usleep_range

2019-07-16 Thread Martin K. Petersen
Bean, > This patch is to change msleep() to usleep_range() based on > Documentation/timers/timers-howto.txt. It suggests using > usleep_range() for small msec(1ms - 20ms) since msleep() will often > sleep longer than desired value. Applied to 5.4/scsi-queue, thanks! -- Martin K. Petersen

[PATCH 2/2] mmc: sdhci: sdhci-pci-core: Add Genesis Logic GL975x support

2019-07-16 Thread Ben Chuang
Add support for the GL9750 and GL9755 chipsets. Signed-off-by: Ben Chuang Co-developed-by: Michael K Johnson Signed-off-by: Michael K Johnson --- drivers/mmc/host/sdhci-gli.h | 27 drivers/mmc/host/sdhci-pci-core.c | 220 ++ drivers/mmc/host/sdhci-pci.h

[PATCH 1/2] mmc: sdhci: Add PLL Enable support to internal clock setup

2019-07-16 Thread Ben Chuang
The GL9750 and GL9755 chipsets, and possibly others, require PLL Enable setup as part of the internal clock setup as described in 3.2.1 Internal Clock Setup Sequence of SD Host Controller Simplified Specification Version 4.20. This changes the timeouts to the new specification of 150ms for each st

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Sowjanya Komatineni
On 7/16/19 7:18 PM, Sowjanya Komatineni wrote: On 7/16/19 3:06 PM, Sowjanya Komatineni wrote: On 7/16/19 3:00 PM, Dmitry Osipenko wrote: 17.07.2019 0:35, Sowjanya Komatineni пишет: On 7/16/19 2:21 PM, Dmitry Osipenko wrote: 17.07.2019 0:12, Sowjanya Komatineni пишет: On 7/16/19 1:47 PM,

Re: [PATCH] scsi: libfc: fix null pointer dereference on a null lport

2019-07-16 Thread Martin K. Petersen
Colin, > Currently if lport is null then the null lport pointer is dereference > when printing out debug via the FC_LPORT_DB macro. Fix this by using > the more generic FC_LIBFC_DBG debug macro instead that does not use > lport. Applied to 5.3/scsi-fixes, thanks! -- Martin K. Petersen Or

[PATCH v4] mmc: host: sdhci-sprd: Fix the incorrect soft reset operation when runtime resuming

2019-07-16 Thread Baolin Wang
In sdhci_runtime_resume_host() function, we will always do software reset for all, which will cause Spreadtrum host controller work abnormally after resuming. Thus for Spreadtrum platform that will not power down the SD/eMMC card during runtime suspend, we should not do software reset for all. To

Re: [PATCH 2/2] mm,memory_hotplug: Fix shrink_{zone,node}_span

2019-07-16 Thread Dan Williams
On Mon, Jul 15, 2019 at 2:24 PM Oscar Salvador wrote: > > On Mon, 2019-07-15 at 21:41 +0530, Aneesh Kumar K.V wrote: > > Oscar Salvador writes: > > > > > Since [1], shrink_{zone,node}_span work on PAGES_PER_SUBSECTION > > > granularity. > > > The problem is that deactivation of the section occurs

Re: [PATCH V5 11/18] clk: tegra210: Add support for Tegra210 clocks

2019-07-16 Thread Sowjanya Komatineni
On 7/16/19 3:06 PM, Sowjanya Komatineni wrote: On 7/16/19 3:00 PM, Dmitry Osipenko wrote: 17.07.2019 0:35, Sowjanya Komatineni пишет: On 7/16/19 2:21 PM, Dmitry Osipenko wrote: 17.07.2019 0:12, Sowjanya Komatineni пишет: On 7/16/19 1:47 PM, Dmitry Osipenko wrote: 16.07.2019 22:26, Sowjany

Re: [PATCH v3 3/5] locking/qspinlock: Introduce CNA into the slow path of qspinlock

2019-07-16 Thread Waiman Long
On 7/15/19 3:25 PM, Alex Kogan wrote: > +/* > + * Implement a NUMA-aware version of MCS (aka CNA, or compact NUMA-aware > lock). > + * > + * In CNA, spinning threads are organized in two queues, a main queue for > + * threads running on the same node as the current lock holder, and a > + * seconda

Re: [PATCH v5] net: netfilter: Fix rpfilter dropping vrf packets by mistake

2019-07-16 Thread linmiaohe
> On Tue, Jul 17, 2019 at 19:17:36PM +, Pablo wrote: > > On Tue, Jul 02, 2019 at 03:59:36AM +, Miaohe Lin wrote: > > When firewalld is enabled with ipv4/ipv6 rpfilter, vrf > > ipv4/ipv6 packets will be dropped. Vrf device will pass through > > netfilter hook twice. One with enslaved device

Re: [PATCH v7 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable

2019-07-16 Thread Zhenzhong Duan
On 2019/7/16 18:57, Juergen Gross wrote: On 11.07.19 14:02, Zhenzhong Duan wrote: .. as "nopv" support needs it to be changeable at boot up stage. Checkpatch report warning, so move variable declarations from hypervisor.c to hypervisor.h Signed-off-by: Zhenzhong Duan Cc: Boris Ostrovsky Cc

[PATCH] gve: replace kfree with kvfree

2019-07-16 Thread Chuhong Yuan
Variables allocated by kvzalloc should not be freed by kfree. Because they may be allocated by vmalloc. So we replace kfree with kvfree here. Signed-off-by: Chuhong Yuan --- drivers/net/ethernet/google/gve/gve_main.c | 22 +++--- drivers/net/ethernet/google/gve/gve_rx.c | 4 ++

Re: [GIT PULL] Btrfs updates for 5.3

2019-07-16 Thread pr-tracker-bot
The pull request you sent on Mon, 15 Jul 2019 10:57:01 +0200: > git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.3-tag has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/a18f8775419d3df282dd83efdb51c5a64d092f31 Thank you! -- Deet-doot-dot, I am a bot.

Re: [PATCH v7 2/3] KVM: vmx: Emulate MSR IA32_UMWAIT_CONTROL

2019-07-16 Thread Tao Xu
On 7/17/2019 9:17 AM, Tao Xu wrote: On 7/17/2019 12:03 AM, Eduardo Habkost wrote: On Fri, Jul 12, 2019 at 04:29:06PM +0800, Tao Xu wrote: UMWAIT and TPAUSE instructions use IA32_UMWAIT_CONTROL at MSR index E1H to determines the maximum time in TSC-quanta that the processor can reside in eithe

  1   2   3   4   5   6   7   >