Re: [PATCH v4 1/1] printf: add support for printing symbolic error names

On Fri, Oct 11, 2019 at 03:36:17PM +0200, Rasmus Villemoes wrote: > It has been suggested several times to extend vsnprintf() to be able > to convert the numeric value of ENOSPC to print "ENOSPC". This > implements that as a %p extension: With %pe, one can do > > if (IS_ERR(foo)) { >

RE: [RFC PATCH v3 4/6] psci: Add hvc call service for ptp_kvm.

Hi Paolo, > -Original Message- > From: Paolo Bonzini > Sent: Wednesday, October 9, 2019 5:13 PM > To: Jianyong Wu (Arm Technology China) ; Marc > Zyngier ; net...@vger.kernel.org; yangbo...@nxp.com; > john.stu...@linaro.org; t...@linutronix.de; sean.j.christopher...@intel.com; >

Re: [PATCH] arm64: dts: lx2160a: Correct CPU core idle state name

On Tue, Sep 17, 2019 at 03:33:56PM +0800, Ran Wang wrote: > lx2160a support PW15 but not PW20, correct name to avoid confusing. > > Signed-off-by: Ran Wang Applied, thanks.

Re: INFO: task hung in addrconf_verify_work (2)

On 10/13/19 9:42 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:    c208bdb9 tcp: improve recv_skip_hint for tcp_zerocopy_rece.. > git tree:   net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=15b6133b60 > kernel config: 

Re: [PATCH 3/3] soc: mediatek: pwrap: add support for MT6359 PMIC

On Fri, 2019-10-04 at 01:27 +0200, Matthias Brugger wrote: > > On 03/10/2019 09:48, Argus Lin wrote: > > MT6359 is a new power management IC and it is used for > > MT6779 SoCs. To define mt6359_regs for pmic register mapping > > and pmic_mt6359 for accessing register. > > > > Signed-off-by:

Re: [PATCH] dmaengine: sprd: Fix the link-list pointer register configuration issue

On 12-09-19, 13:47, Baolin Wang wrote: > From: Zhenfang Wang > > We will set the link-list pointer register point to next link-list > configuration's physical address, which can load DMA configuration > from the link-list node automatically. > > But the link-list node's physical address can be

Re: [PATCH v2 3/3] phy: qcom-qmp: Add SM8150 QMP UFS PHY support

On 08-10-19, 00:46, Jack Pham wrote: > Hi Vinod, > > On Fri, Sep 06, 2019 at 10:40:17AM +0530, Vinod Koul wrote: > > SM8150 UFS PHY is v4 of QMP phy. Add support for V4 QMP phy register > > defines and support for SM8150 QMP UFS PHY. > > > > Signed-off-by: Vinod Koul > > Reviewed-by: Bjorn

Re: [PATCH 3/3] ARM: at91: add Overkiz KIZBOX3 board

Hi Kamel, Thank you for the patch! Yet something to improve: [auto build test ERROR on robh/for-next] [cannot apply to v5.4-rc3 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

INFO: task hung in addrconf_verify_work (2)

Hello, syzbot found the following crash on: HEAD commit:c208bdb9 tcp: improve recv_skip_hint for tcp_zerocopy_rece.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=15b6133b60 kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522

Re: [PATCH v5 1/2] HID: logitech: Add MX Master over Bluetooth

Hi Mazin, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [cannot apply to v5.4-rc3 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to

Re: [PATCH v5 1/2] HID: logitech: Add MX Master over Bluetooth

On Sunday, October 13, 2019 9:28 PM, kbuild test robot wrote: > Hi Mazin, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on linus/master] > [cannot apply to v5.4-rc2 next-20191010] > [if your patch is applied to the wrong git tree, please drop us a note

Re: [PATCH 1/7] Add a new flags-accepting interface for anonymous inodes

Hi Daniel, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [cannot apply to v5.4-rc3 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to

Re: Regression in 4.14.147, 4.19.76, 5.2.18 leading to kernel panic on btrfs root fs mount

On Sun, Oct 13, 2019 at 07:04:12PM +0300, Andrew Macks wrote: Was not sure the correct way to escalate this quickly enough. I unfortunately discovered this issue while upgrading a server (remotely) to 4.19.78 (longterm). *Bug 205181* -

RE: [EXT] Re: [v2,2/2] dt-bindings: i2c-mux-pca954x: Add optional property i2c-mux-never-disable

> > > > > On Mon, Sep 30, 2019 at 11:25:03AM +0800, Biwen Li wrote: > > > The patch adds an optional property i2c-mux-never-disable > > > > > > Signed-off-by: Biwen Li > > > --- > > > Change in v2: > > > - update documentation > > > > > >

Re: [PATCHv7 15/33] posix-timers: Make clock_nanosleep() time namespace aware

Hi Dmitry, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

Re: [PATCH] hrtimer: annotate lockless access to timer->base

On Tue, Oct 8, 2019 at 10:32 AM Eric Dumazet wrote: > > Followup to commit dd2261ed45aa ("hrtimer: Protect lockless access > to timer->base") > > lock_hrtimer_base() fetches timer->base without lock exclusion. > > Compiler is allowed to read timer->base twice (even if considered dumb) > and we

Re: Potential uninitialized variables in power: supply: rt5033_battery:

Hi Sebastian: Thanks for your explanation and I will send the patch accordingly. On Sun, Oct 13, 2019 at 8:12 PM Sebastian Reichel wrote: > > Hi, > > On Thu, Oct 03, 2019 at 09:21:44PM -0700, Yizhuo Zhai wrote: > > drivers/power/supply/rt5033_battery.c: > > > > In function

Re: [PATCH v5 2/2] HID: logitech: Support WirelessDeviceStatus connect events

Hi Mazin, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to

Re: [PATCH v4 0/5] Powerpc/Watchpoint: Few important fixes

On 10/12/19 2:21 PM, Christophe Leroy wrote: Le 10/10/2019 à 06:44, Ravi Bangoria a écrit : @Christophe, Is patch5 works for you on 8xx? Getting the following : root@vgoip:~# ./ptrace-hwbreak test: ptrace-hwbreak tags: git_version:v5.4-rc2-710-gf0082e173fe4-dirty PTRACE_SET_DEBUGREG,

Re: [PATCH v4 0/5] Powerpc/Watchpoint: Few important fixes

On 10/12/19 1:01 PM, Christophe Leroy wrote: Le 10/10/2019 à 08:25, Ravi Bangoria a écrit : On 10/10/19 10:14 AM, Ravi Bangoria wrote: @Christophe, Is patch5 works for you on 8xx? Getting the following : root@vgoip:~# ./ptrace-hwbreak test: ptrace-hwbreak tags:

Re: [PATCH] power: supply: max17042_battery: fix the potential uninitialized use in max17042_write_verify_reg()

Hi, On Wed, Oct 02, 2019 at 08:44:06AM -0700, Yizhuo wrote: > In function max17042_write_verify_reg(), variable "read_value" > could be uninitialized if regmap_read() fails. However, > "read_value" is used to decide the control flow later in the if > statement, which is potentially unsafe. > >

Re: [PATCH v3 1/2] Serial: Ingenic: Add support for the X1000.

Hi Greg, I'm sorry, maybe it was a problem when I git send-email, causing the wrong patch to be sent to you. Just ignore the email about the serial patch please. Best regards! On 2019年10月12日 15:35, Greg KH wrote: On Sat, Oct 12, 2019 at 01:13:23PM +0800, Zhou Yanjie wrote: Add support for

Re: [PATCH] power: supply: max17042_battery: fix some usage of uninitialized variables

Hi, On Thu, Oct 03, 2019 at 10:29:48AM -0700, Yizhuo wrote: > Several functions in this file are trying to use regmap_read() to > initialize the specific variable, however, if regmap_read() fails, > the variable could be uninitialized but used directly, which is > potentially unsafe. The return

Re: [PATCH] fs/namespace.c: fix use-after-free of mount in mnt_warn_timestamp_expiry()

On Sun, Oct 13, 2019 at 07:04:10PM -0700, Deepa Dinamani wrote: > Thanks for the fix. > > Would it be better to move the check and warning to a place where the > access is still safe? > > -Deepa True, we could just do diff --git a/fs/namespace.c b/fs/namespace.c index

RE: [EXT] Re: [v2,2/2] dt-bindings: i2c-mux-pca954x: Add optional property i2c-mux-never-disable

> > On Mon, Sep 30, 2019 at 11:25:03AM +0800, Biwen Li wrote: > > The patch adds an optional property i2c-mux-never-disable > > > > Signed-off-by: Biwen Li > > --- > > Change in v2: > > - update documentation > > > > Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt | 1 + > > 1

Re: [PATCH] firmware: vpd: Add an interface to read VPD value

On Wed, Oct 9, 2019 at 10:05 PM Srinivas Kandagatla wrote: > > > > On 08/10/2019 16:14, Stephen Boyd wrote: > >> 3) As my use case does not use device tree, it is hard for ASoC > >> machine to access nvmem device. I am wondering if I can use > >> nvm_cell_lookup so machine driver can find the

Re: Potential uninitialized variables in power: supply: rt5033_battery:

Hi, On Thu, Oct 03, 2019 at 09:21:44PM -0700, Yizhuo Zhai wrote: > drivers/power/supply/rt5033_battery.c: > > In function rt5033_battery_get_present(), variable "val" could be > uninitialized if regmap_read() returns -EINVAL. However, "val" is > used to decide the return value, which is

Re: [PATCHv7 25/33] x86/vdso: Zap vvar pages on switch a time namspace

Hi Dmitry, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

kernel BUG at include/linux/rmap.h:LINE!

Hello, syzbot found the following crash on: HEAD commit:442630f6 Add linux-next specific files for 20191008 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=11450d9360 kernel config: https://syzkaller.appspot.com/x/.config?x=af1bfeef713eefdd

Re: [PATCH 3/3] perf tools: Make 'struct map_shared' truly shared

On Sun, Oct 13, 2019 at 05:14:27PM +0200, Jiri Olsa wrote: > Andi reported that maps cloning is eating lot of memory and > it's probably unnecessary, because they keep the same data. > > Changing 'struct map_shared' to be a pointer inside 'struct map', > so it can be shared on fork. Changing the

[PATCH v2 2/2] pinctrl: rockchip: add rk3308 SoC support

This patch do support pinctrl for RK3308 SoCs. Reviewed-by: Heiko Stuebner Signed-off-by: Jianqun Xu --- changes since v1: - Add type case for pull get/set - Add Reviewed-by: Heiko Stuebner drivers/pinctrl/pinctrl-rockchip.c | 379 + 1 file changed, 379

[PATCH v2 1/2] dt-bindings: pinctrl: rockchip: add rk3308 SoC support

Add rk3308 SoC support to rockchip pinctrl. Reviewed-by: Heiko Stuebner Signed-off-by: Jianqun Xu --- changes since v1: - Add Reviewed-by: Heiko Stuebner Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 0/2] pinctrl: rockchip: support rk3308 SoC

Add support for rk3308 SoC from rockchip. Jianqun Xu (2): dt-bindings: pinctrl: rockchip: add rk3308 SoC support pinctrl: rockchip: add rk3308 SoC support .../bindings/pinctrl/rockchip,pinctrl.txt | 1 + drivers/pinctrl/pinctrl-rockchip.c| 379 ++ 2 files

Re: [PATCH 2/7] Add a concept of a "secure" anonymous file

Hi Daniel, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

[PATCH v4 1/3] powerpc: Don't add -mabi= flags when building with Clang

When building pseries_defconfig, building vdso32 errors out: error: unknown target ABI 'elfv1' This happens because -m32 in clang changes the target to 32-bit, which does not allow the ABI to be changed, as the setABI virtual function is not overridden:

[PATCH v4 2/3] powerpc: Avoid clang warnings around setjmp and longjmp

Commit aea447141c7e ("powerpc: Disable -Wbuiltin-requires-header when setjmp is used") disabled -Wbuiltin-requires-header because of a warning about the setjmp and longjmp declarations. r367387 in clang added another diagnostic around this, complaining that there is no jmp_buf declaration. In

[PATCH v4 0/3] LLVM/Clang fixes for pseries_defconfig

Hi all, This series includes a set of fixes for LLVM/Clang when building pseries_defconfig. These have been floating around as standalone patches so I decided to gather them up as a series so it was easier to review/apply them. This has been broken for a bit now, it would be nice to get these

[PATCH v4 3/3] powerpc/prom_init: Use -ffreestanding to avoid a reference to bcmp

r374662 gives LLVM the ability to convert certain loops into a reference to bcmp as an optimization; this breaks prom_init_check.sh: CALLarch/powerpc/kernel/prom_init_check.sh Error: External symbol 'bcmp' referenced from prom_init.c make[2]: *** [arch/powerpc/kernel/Makefile:196:

KASAN: use-after-free Read in bpf_prog_kallsyms_find (2)

Hello, syzbot found the following crash on: HEAD commit:b212921b elf: don't use MAP_FIXED_NOREPLACE for elf execut.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=148abb3f60 kernel config: https://syzkaller.appspot.com/x/.config?x=1ec3be9936e004f6

WARNING: refcount bug in sock_wfree (2)

Hello, syzbot found the following crash on: HEAD commit:442630f6 Add linux-next specific files for 20191008 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=158fa6bf60 kernel config: https://syzkaller.appspot.com/x/.config?x=af1bfeef713eefdd

memory leak in sctp_get_port_local (3)

Hello, syzbot found the following crash on: HEAD commit:da940012 Merge tag 'char-misc-5.4-rc3' of git://git.kernel.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11c87fc760 kernel config: https://syzkaller.appspot.com/x/.config?x=e76c708f07645488

WARNING in vkms_gem_free_object

Hello, syzbot found the following crash on: HEAD commit:8ada228a Add linux-next specific files for 20191011 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=14c30b1b60 kernel config: https://syzkaller.appspot.com/x/.config?x=7cf4eed5fe42c31a

Re: [PATCHv7 25/33] x86/vdso: Zap vvar pages on switch a time namspace

Hi Dmitry, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

Re: [PATCHv7 22/33] time: Allocate per-timens vvar page

Hi Dmitry, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

[REGRESSION] kmemleak: commit c566586818 causes failure to boot

Commit c566586818 ("mm: kmemleak: use the memory pool for early allocations") causes my test kernels to fail to boot on using both kvm and using Google Compute Engine. A git bisect localized it to c566586818, and I confirmed by test building v5.4-rc3, which failed as above using KVM. When I

Re: [PATCH xfstests] generic/192: Move 'cd /' to the place where the program exits

I agree with your proposal. Indeed, '$here' is referenced in other places where executable files under src are used, including '$here/src/feature', '$here/src/seek_sanity_test', etc. I have a question about why many test cases execute 'cd /' before the end. For example, generic/124,

Re: [PATCH] kernel: dma: Make CMA boot parameters __ro_after_init

On Sat, Oct 12, 2019 at 05:59:18PM +0530, Shyam Saini wrote: > This parameters are not changed after early boot. > By making them __ro_after_init will reduce any attack surface in the > kernel. > > Link: https://lwn.net/Articles/676145/ > Cc: Christoph Hellwig > Cc: Marek Szyprowski > Cc: Robin

Re: [PATCHv7 22/33] time: Allocate per-timens vvar page

Hi Dmitry, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

Re: [PATCH] kasan: fix the missing underflow in memmove and memcpy with CONFIG_KASAN_GENERIC=y

On Tue, 2019-10-08 at 14:11 +0200, Dmitry Vyukov wrote: > On Tue, Oct 8, 2019 at 1:42 PM Qian Cai wrote: > > > On Oct 8, 2019, at 7:02 AM, Walter Wu wrote: > > > I don't know very well in UBSAN, but I try to build ubsan kernel and > > > test a negative number in memset and

[PATCH] media: imx7-mipi-csis: Add a check for devm_regulator_get

devm_regulator_get may return an error but mipi_csis_phy_init misses a check for it. This may lead to problems when regulator_set_voltage uses the unchecked pointer. This patch adds a check for devm_regulator_get to avoid potential risk. Signed-off-by: Chuhong Yuan ---

[PATCH] media: cxusb: detect cxusb_ctrl_msg error in query

Don't use uninitialized ircode[] in cxusb_rc_query() when cxusb_ctrl_msg() fails to populate its contents. syzbot reported: dvb-usb: bulk message failed: -22 (1/-30591) = BUG: KMSAN: uninit-value in ir_lookup_by_scancode

Re: [PATCH] fs/namespace.c: fix use-after-free of mount in mnt_warn_timestamp_expiry()

Thanks for the fix. Would it be better to move the check and warning to a place where the access is still safe? -Deepa > On Oct 9, 2019, at 12:19 AM, Eric Biggers wrote: > > From: Eric Biggers On Wed, Oct 9, 2019 at 12:19 AM Eric Biggers wrote: > > From: Eric Biggers > > After

Re: [PATCH v5 3/5] x86/kvm: Add "nopvspin" parameter to disable PV spinlocks

On 2019/10/13 17:02, Vitaly Kuznetsov wrote: Zhenzhong Duan writes: ...snip diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c index ef836d6..6e14bd4 100644 --- a/arch/x86/kernel/kvm.c +++ b/arch/x86/kernel/kvm.c @@ -825,18 +825,31 @@ __visible bool __kvm_vcpu_is_preempted(long cpu)

Re: [PATCH RFC v1 2/2] vhost: batching fetches

On 2019/10/13 上午4:36, Michael S. Tsirkin wrote: On Sat, Oct 12, 2019 at 03:30:52PM +0800, Jason Wang wrote: On 2019/10/11 下午9:46, Michael S. Tsirkin wrote: With this patch applied, new and old code perform identically. Lots of extra optimizations are now possible, e.g. we can fetch multiple

Re: [PATCH RFC v1 1/2] vhost: option to fetch descriptors through an independent struct

On 2019/10/13 上午4:27, Michael S. Tsirkin wrote: On Sat, Oct 12, 2019 at 03:28:49PM +0800, Jason Wang wrote: On 2019/10/11 下午9:45, Michael S. Tsirkin wrote: The idea is to support multiple ring formats by converting to a format-independent array of descriptors. This costs extra cycles, but

Re: [PATCH v5 2/5] x86/kvm: Change print code to use pr_*() format

On 2019/10/13 17:06, Vitaly Kuznetsov wrote: Zhenzhong Duan writes: pr_*() is preferred than printk(KERN_* ...), after change all the print in arch/x86/kernel/kvm.c will have "kvm_guest: xxx" style. No functional change. Signed-off-by: Zhenzhong Duan Cc: Paolo Bonzini Cc: Radim Krcmar

Re: [PATCH 1/3] perf tools: Allow to build with -ltcmalloc

> diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf > index a099a8a89447..8f1ba986d3bf 100644 > --- a/tools/perf/Makefile.perf > +++ b/tools/perf/Makefile.perf > @@ -114,6 +114,8 @@ include ../scripts/utilities.mak > # Define NO_LIBZSTD if you do not want support of Zstandard based

Re: [PATCH v5 1/2] HID: logitech: Add MX Master over Bluetooth

Hi Mazin, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to

Re: [PATCH] ipmi: Convert ipmi_debug_msg to pr_debug and use %*ph

Hi Joe, I love your patch! Perhaps something to improve: [auto build test WARNING on char-misc/char-misc-testing] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base'

[PATCH v2 2/4] perf/core: Provide a kernel-internal interface to pause perf_event

Exporting perf_event_pause() as an external accessor for kernel users (such as KVM) who may do both disable perf_event and read count with just one time to hold perf_event_ctx_lock. Also the value could be reset optionally. Suggested-by: Peter Zijlstra Signed-off-by: Like Xu ---

[PATCH v2 3/4] KVM: x86/vPMU: Reuse perf_event to avoid unnecessary pmc_reprogram_counter

The perf_event_create_kernel_counter() in the pmc_reprogram_counter() is a heavyweight and high-frequency operation, especially when host disables the watchdog (maximum 2100 ns) which leads to an unacceptable latency of the guest NMI handler. It limits the use of vPMUs in the guest. When a

[PATCH v2 1/4] perf/core: Provide a kernel-internal interface to recalibrate event period

Currently, perf_event_period() is used by user tools via ioctl. Based on naming convention, exporting perf_event_period() for kernel users (such as KVM) who may recalibrate the event period for their assigned counter according to their requirements. The perf_event_period() is an external

[PATCH v2 0/4] KVM: x86/vPMU: Efficiency optimization by reusing last created perf_event

Performance Monitoring Unit is designed to monitor micro architectural events which helps in analyzing how applications or operating systems are performing on the processors. In KVM/X86, version 2 Architectural PMU on Intel and AMD hosts have been enabled. This patch series is going to improve

[PATCH v2 4/4] KVM: x86/vPMU: Add lazy mechanism to release perf_event per vPMC

Currently, a host perf_event is created for a vPMC functionality emulation. It’s unpredictable to determine if a disabled perf_event will be reused. If they are disabled and are not reused for a considerable period of time, those obsolete perf_events would increase host context switch overhead

RE: [EXT] Re: [PATCH v3] thermal: qoriq: add thermal monitor unit version 2 support

Thanks Daniel for your help.. BR, Andy > -Original Message- > From: Daniel Lezcano > Sent: 2019年10月11日 22:32 > To: Andy Tang ; edubez...@gmail.com; > rui.zh...@intel.com; Anson Huang > Cc: Leo Li ; linux...@vger.kernel.org; > linux-kernel@vger.kernel.org > Subject: [EXT] Re: [PATCH v3]

Re: [PATCH] net: core: datagram: tidy up copy functions a bit

On 10/13/19 3:41 PM, Vito Caputo wrote: > I read it, thank you for your responses. > > Do you have any guidance to offer someone wanting to contribute with 1-2 > hours available per day? I don't want to cause a nuisance, but would > like to help where I can. My flawed assumption was that

[Patch v3 4/7] sched/fair: Enable CFS periodic tick to update thermal pressure

Introduce support in CFS periodic tick to trigger the process of computing average thermal pressure for a cpu. Signed-off-by: Thara Gopinath --- kernel/sched/fair.c | 5 + 1 file changed, 5 insertions(+) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 83ab35e..fe7c165 100644

[PATCH V2] clk: imx7ulp: Correct system clock source option #7

In the latest reference manual Rev.0,06/2019, the SCS's option #7 is no longer from upll, it is reserved, update clock driver accordingly. Fixes: b1260067ac3d ("clk: imx: add imx7ulp clk driver") Signed-off-by: Anson Huang Reviewed-by: Fabio Estevam --- Changes since V1: - no code

[Patch v3 2/7] sched: Add infrastructure to store and update instantaneous thermal pressure

Add thermal.c and thermal.h files that provides interface APIs to initialize, update/average, track, accumulate and decay thermal pressure per cpu basis. A per cpu structure max_capacity_info is introduced to keep track of instantaneous per cpu thermal pressure. Thermal pressure is the delta

[Patch v3 0/7] Introduce Thermal Pressure

Thermal governors can respond to an overheat event of a cpu by capping the cpu's maximum possible frequency. This in turn means that the maximum available compute capacity of the cpu is restricted. But today in the kernel, task scheduler is not notified of capping of maximum frequency of a cpu.

[Patch v3 1/7] sched/pelt.c: Add support to track thermal pressure

Extrapolating on the exisitng framework to track rt/dl utilization using pelt signals, add a similar mechanism to track thermal pressue. The difference here from rt/dl utilization tracking is that, instead of tracking time spent by a cpu running a rt/dl task through util_avg, the average thermal

[Patch v3 3/7] sched: Initialize per cpu thermal pressure structure

Initialize per cpu max_capacity_info during scheduler init. Signed-off-by: Thara Gopinath --- drivers/base/arch_topology.c | 1 + kernel/sched/core.c | 2 ++ 2 files changed, 3 insertions(+) diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c index

[Patch v3 5/7] sched/fair: update cpu_capcity to reflect thermal pressure

cpu_capacity relflects the maximum available capacity of a cpu. Thermal pressure on a cpu means this maximum available capacity is reduced. This patch reduces the average thermal pressure for a cpu from its maximum available capacity so that cpu_capacity reflects the actual available capacity.

[Patch v3 7/7] sched: thermal: Enable tuning of decay period

Thermal pressure follows pelt signas which means the decay period for thermal pressure is the default pelt decay period. Depending on soc charecteristics and thermal activity, it might be beneficial to decay thermal pressure slower, but still in-tune with the pelt signals. One way to achieve this

[Patch v3 6/7] thermal/cpu-cooling: Update thermal pressure in case of a maximum frequency capping

Thermal governors can request for a cpu's maximum supported frequency to be capped in case of an overheat event. This in turn means that the maximum capacity available for tasks to run on the particular cpu is reduced. Delta between the original maximum capacity and capped maximum capacity is

Re: [PATCH] ipmi: Convert ipmi_debug_msg to pr_debug and use %*ph

Hi Joe, I love your patch! Perhaps something to improve: [auto build test WARNING on char-misc/char-misc-testing] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base'

[no subject]

Здравствуйте! Вас интересуют клиентские базы данных?

Re: [PATCHv7 15/33] posix-timers: Make clock_nanosleep() time namespace aware

Hi Dmitry, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

Re: [PATCH] KVM: LAPIC: micro-optimize fixed mode ipi delivery

ping, On Fri, 20 Sep 2019 at 18:07, Wanpeng Li wrote: > > From: Wanpeng Li > > After disabling mwait/halt/pause vmexits, RESCHEDULE_VECTOR and > CALL_FUNCTION_SINGLE_VECTOR etc IPI is one of the main remaining > cause of vmexits observed in product environment which can't be > optimized by PV

[PATCH] cpuidle: not unset the driver if it already exist

__cpuidle_set_driver() check if there is an already exist driver and unset it before return with -EBUSY. The next call will succeed as it's just unset. This is strange as we should either keep old driver and return -EBUSY or unset and set new driver and return 0. Signed-off-by: Zhenzhong Duan

Re: [PATCHv7 06/33] alarmtimer: Provide get_timespec() callback

Hi Dmitry, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify

[PATCH v2 1/2] dt-bindings: pinctrl: rockchip: add rk3308 SoC support

Add rk3308 SoC support to rockchip pinctrl. Reviewed-by: Heiko Stuebner Signed-off-by: Jianqun Xu --- changes since v1: - Add Reviewed-by: Heiko Stuebner Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 0/2] pinctrl: rockchip: support rk3308 SoC

Add support for rk3308 SoC from rockchip. Jianqun Xu (2): dt-bindings: pinctrl: rockchip: add rk3308 SoC support pinctrl: rockchip: add rk3308 SoC support .../bindings/pinctrl/rockchip,pinctrl.txt | 1 + drivers/pinctrl/pinctrl-rockchip.c| 377 ++ 2 files

[PATCH v2 2/2] pinctrl: rockchip: add rk3308 SoC support

This patch do support pinctrl for RK3308 SoCs. Reviewed-by: Heiko Stuebner Signed-off-by: Jianqun Xu --- changes since v1: - Add Reviewed-by: Heiko Stuebner drivers/pinctrl/pinctrl-rockchip.c | 377 + 1 file changed, 377 insertions(+) diff --git

Linux 5.4-rc3

Things continue to look fairly normal, with rc3 being larger than rc2, as people are starting to find more regressions, but 5.4 so far remains on the smaller side of recent releases. The diffstat looks fairly flat too, although we had a couple of staging drivers being removed here that show up as

Re: [PATCH 3/3] Input: mms114 - add support for mms345l

Hi Dmitry, > > > > There was a related patch [2] that removes I2C_M_NOSTART for all models, > > > > but it seems abandoned and I do not have any other model for testing. > > > > Therefore, this patch implements the least instrusive solution > > > > and only removes I2C_M_NOSTART for MMS345L. > >

linux-next: manual merge of the bpf-next tree with the net tree

Hi all, Today's linux-next merge of the bpf-next tree got a conflict in: tools/lib/bpf/Makefile between commit: 1bd63524593b ("libbpf: handle symbol versioning properly for libbpf.a") from the net tree and commits: 5c26f9a78358 ("libbpf: Don't use cxx to test_libpf target")

Re: [PATCH v3][RESEND] adp5061: Add support for battery charging enable

Hi Alexandru, I love your patch! Yet something to improve: [auto build test ERROR on power-supply/for-next] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/netdevsim/fib.c between commit: 33902b4a4227 ("netdevsim: Fix error handling in nsim_fib_init and nsim_fib_exit") from the net tree and commit: a5facc4cac4d ("netdevsim: change fib accounting and

Re: [PATCH] net: core: datagram: tidy up copy functions a bit

On Sun, Oct 13, 2019 at 01:17:18PM -0700, Eric Dumazet wrote: > > > On 10/13/19 1:01 PM, Vito Caputo wrote: > > On Sun, Oct 13, 2019 at 12:30:41PM -0700, Eric Dumazet wrote: > >> > >> > >> On 10/12/19 4:55 AM, Vito Caputo wrote: > >>> Eliminate some verbosity by using min() macro and

Re: [PATCH] watchdog/hardlockup: reassign last_timestamp when enable nmi event

Hi Li, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to

Re: [PATCH 3/3] Input: mms114 - add support for mms345l

Hi Stephan, > > > There was a related patch [2] that removes I2C_M_NOSTART for all models, > > > but it seems abandoned and I do not have any other model for testing. > > > Therefore, this patch implements the least instrusive solution > > > and only removes I2C_M_NOSTART for MMS345L. > > > >

[PATCH 0/2] gup.c, gup_benchmark.c trivial fixes before the storm

Hi, These trivial fixes apply to today's linux.git (5.4-rc3, or maybe -rc4, by the time I send this). I found these while polishing up the Next And Final get_user_pages()+dma tracking patchset (which is in final testing and passing nicely...so far). Anyway, as these two patches apply cleanly

[PATCH 1/2] mm/gup_benchmark: add a missing "w" to getopt string

Even though gup_benchmark.c has code to handle the -w command-line option, the "w" is not part of the getopt string. It looks as if it has been missing the whole time. On my machine, this leads naturally to the following predictable result: $ sudo ./gup_benchmark -w ./gup_benchmark: invalid

[PATCH 2/2] mm/gup: fix a misnamed "write" argument: should be "flags"

In several routines, the "flags" argument is incorrectly named "write". Change it to "flags". You can see that this was a simple oversight, because the calling code passes "flags" to the fifth argument: gup_pgd_range(): ... if (!gup_huge_pd(__hugepd(pgd_val(pgd)), addr,

Re: [PATCH v2 for 5.4 2/4] media: hantro: Fix H264 max frmsize supported on RK3288

Le jeudi 10 octobre 2019 à 16:23 +0900, Tomasz Figa a écrit : > On Tue, Oct 8, 2019 at 11:12 PM Jonas Karlman wrote: > > On 2019-10-08 15:53, Tomasz Figa wrote: > > > On Tue, Oct 8, 2019 at 10:35 PM Tomasz Figa wrote: > > > > On Tue, Oct 8, 2019 at 7:42 PM Tomasz Figa wrote: > > > > > On Tue,

Re: [PATCH 2/2] gpio: Add xgs-iproc driver

On Fri, 2019-10-11 at 09:43 +0200, Linus Walleij wrote: > Hi Chris! > > Thanks for your patch! > > On Fri, Oct 4, 2019 at 3:25 AM Chris Packham > wrote: > > > This driver supports the Chip Common A GPIO controller present on a > > number of Broadcom switch ASICs with integrated SoCs. The

[PATCH] 8250-men-mcb: fix error checking when get_num_ports returns -ENODEV

From: Colin Ian King The current checking for failure on the number of ports fails when -ENODEV is returned from the call to get_num_ports. Fix this by making num_ports and loop counter i signed rather than unsigned ints. Also add check for num_ports being less than zero to check for -ve error

Re: [GIT PULL] tracing: Fixes for v5.4-rc2

The pull request you sent on Sun, 13 Oct 2019 15:07:02 -0400: > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git > trace-v5.4-rc2 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/d4615e5a46800d2193bf8ae98cb470206f5f635b Thank you! --

Re: clk: rockchip: Checking a kmemdup() call in rockchip_clk_register_pll()

Am Sonntag, 13. Oktober 2019, 10:45:09 CEST schrieb Markus Elfring: > >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/clk/rockchip/clk-pll.c?id=1c0cc5f1ae5ee5a6913704c0d75a6e99604ee30a#n913 > >>

  1   2   3   >