[PATCH v4 1/7] cpufreq: blacklist SDM630/636/660 in cpufreq-dt-platdev

2021-01-19 Thread AngeloGioacchino Del Regno
Add the SDM630, SDM636 and SDM660 to the blacklist since the CPU scaling is handled out of this. Signed-off-by: AngeloGioacchino Del Regno --- drivers/cpufreq/cpufreq-dt-platdev.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c

[PATCH v4 3/3] arm64: qcom: qcs404: Change CPR nvmem-names

2021-01-19 Thread AngeloGioacchino Del Regno
The CPR driver's common functions were split and put in another file in order to support newer CPR revisions: to simplify the commonization, the expected names of the fuses had to be changed in order for both new and old support to use the same fuse name retrieval function and keeping the naming

Re: [PATCH] gcc-plugins: simplify GCC plugin-dev capability test

2021-01-19 Thread Thierry Reding
On Fri, Dec 18, 2020 at 08:33:37PM +, Jon Hunter wrote: > > On 18/12/2020 17:54, Linus Torvalds wrote: > > On Fri, Dec 18, 2020 at 7:33 AM Jon Hunter wrote: > >> > >> However, if you are saying that this is a problem/bug with our builders, > >> then of course we will have to get this fixed.

[PATCH v4 4/7] dt-bindings: cpufreq: cpufreq-qcom-hw: Convert to YAML bindings

2021-01-19 Thread AngeloGioacchino Del Regno
From: Manivannan Sadhasivam Convert Qualcomm cpufreq devicetree binding to YAML. Signed-off-by: Manivannan Sadhasivam Signed-off-by: AngeloGioacchino Del Regno --- .../bindings/cpufreq/cpufreq-qcom-hw.txt | 172 --- .../bindings/cpufreq/cpufreq-qcom-hw.yaml | 204

Re: [PATCH v6 04/49] soc: fsl: qe: introduce qe_io{read,write}* wrappers

2021-01-19 Thread Li Yang
On Tue, Jan 19, 2021 at 11:35 AM Christophe Leroy wrote: > > Hi Rasmus, > > Le 28/11/2019 à 15:55, Rasmus Villemoes a écrit : > > The QUICC engine drivers use the powerpc-specific out_be32() etc. In > > order to allow those drivers to build for other architectures, those > > must be replaced by

Re: [PATCH] sched/eas: Don't update misfit status if the task is pinned

2021-01-19 Thread Quentin Perret
On Tuesday 19 Jan 2021 at 17:42:44 (+), Qais Yousef wrote: > Hmm IIUC you want to still tag it as misfit so it'll be balanced within the > little cores in case there's another core with more spare capacity, right? Well yes but that's just a special case. But even you have big CPUs in the

[PATCH] nvme: fix handling mapping failure

2021-01-19 Thread Marc Orr
This patch ensures that when `nvme_map_data()` fails to map the addresses in a scatter/gather list: * The addresses are not incorrectly unmapped. The underlying scatter/gather code unmaps the addresses after detecting a failure. Thus, unmapping them again in the driver is a bug. * The DMA pool

Re: [PATCH v1] of: property: Add fw_devlink support for "gpio" and "gpios" binding

2021-01-19 Thread Saravana Kannan
On Tue, Jan 19, 2021 at 2:20 AM Linus Walleij wrote: > > On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven > wrote: > > > > Can we pull this into driver-core-next please? It fixes issues on some > > > boards with fw_devlink=on. > > > > On r8a77951-salvator-xs.dts, it introduces one more

[PATCH v4 1/3] cpuidle: qcom_spm: Detach state machine from main SPM handling

2021-01-19 Thread AngeloGioacchino Del Regno
In commit a871be6b8eee ("cpuidle: Convert Qualcomm SPM driver to a generic CPUidle driver") the SPM driver has been converted to a generic CPUidle driver: that was mainly made to simplify the driver and that was a great accomplishment; Though, it was ignored that the SPM driver is not used only on

[PATCH v4 0/3] Driver for Core Power Reduction v3, v4 and Hardened

2021-01-19 Thread AngeloGioacchino Del Regno
** ** NOTE: To "view the full picture", please look at the following ** patch series: ** https://patchwork.kernel.org/project/linux-arm-msm/list/?series=413355 ** This is a subset of that series. ** Changes in v4: - Huge patch series has been split for better

Re: [PATCH v1] of: property: Add fw_devlink support for "gpio" and "gpios" binding

2021-01-19 Thread Thierry Reding
On Tue, Jan 19, 2021 at 11:20:24AM +0100, Linus Walleij wrote: > On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven > wrote: > > > > Can we pull this into driver-core-next please? It fixes issues on some > > > boards with fw_devlink=on. > > > > On r8a77951-salvator-xs.dts, it introduces one

Re: [Patch v5 2/2] cgroup: svm: Encryption IDs cgroup documentation.

2021-01-19 Thread Vipin Sharma
On Mon, Jan 18, 2021 at 9:55 AM Randy Dunlap wrote: > > On 1/15/21 6:32 PM, Vipin Sharma wrote: > > Documentation of Encryption IDs controller. This new controller is used > > to track and limit usage of hardware memory encryption capabilities on > > the CPUs. > > > > Signed-off-by: Vipin Sharma

[PATCH 0/4] Drivers: hv: vmbus: Restrict devices and configurations on 'isolated' guests

2021-01-19 Thread Andrea Parri (Microsoft)
Hi all, To reduce the footprint of the code that will be exercised, and hence the exposure to bugs and vulnerabilities, restrict configurations and devices on 'isolated' VMs. Specs of the Isolation Configuration leaf (cf. patch #1) were derived from internal discussions with the Hyper-V team

[PATCH v4 0/3] CPR commonization in preparation for CPR3 driver

2021-01-19 Thread AngeloGioacchino Del Regno
** ** NOTE: To "view the full picture", please look at the following ** patch series: ** https://patchwork.kernel.org/project/linux-arm-msm/list/?series=413355 ** This is a subset of that series. ** In preparation for adding a driver for CPR3, CPR4 and CPR4-Hardened,

[PATCH v4 7/7] arm64: dts: pmi8998: Add the right interrupts for LAB/IBB SCP and OCP

2021-01-19 Thread AngeloGioacchino Del Regno
In commit 208921bae696 ("arm64: dts: qcom: pmi8998: Add nodes for LAB and IBB regulators") bindings for the lab/ibb regulators were added to the pmi8998 dt, but the original committer has never specified what the interrupts were for. LAB and IBB regulators provide two interrupts, SC-ERR (short

[PATCH 2/4] Drivers: hv: vmbus: Restrict vmbus_devices on isolated guests

2021-01-19 Thread Andrea Parri (Microsoft)
Only the VSCs or ICs that have been hardened and that are critical for the successful adoption of Confidential VMs should be allowed if the guest is running isolated. This change reduces the footprint of the code that will be exercised by Confidential VMs and hence the exposure to bugs and

[PATCH v3] perf: cs-etm: update ETM metadata format

2021-01-19 Thread Mike Leach
The current fixed metadata version format (version 0), means that adding metadata parameter items renders files from a previous version of perf unreadable. Per CPU parameters appear in a fixed order, but there is no field to indicate the number of ETM parameters per CPU. This patch updates the

[PATCH 4/4] hv_netvsc: Restrict configurations on isolated guests

2021-01-19 Thread Andrea Parri (Microsoft)
Restrict the NVSP protocol version(s) that will be negotiated with the host to be NVSP_PROTOCOL_VERSION_61 or greater if the guest is running isolated. Moreover, do not advertise the SR-IOV capability and ignore NVSP_MSG_4_TYPE_SEND_VF_ASSOCIATION messages in isolated guests, which are not

Re: [PATCH] nvme: fix handling mapping failure

2021-01-19 Thread Christoph Hellwig
On Tue, Jan 19, 2021 at 09:53:36AM -0800, Marc Orr wrote: > This patch ensures that when `nvme_map_data()` fails to map the > addresses in a scatter/gather list: > > * The addresses are not incorrectly unmapped. The underlying > scatter/gather code unmaps the addresses after detecting a failure.

[PATCH 1/4] x86/hyperv: Load/save the Isolation Configuration leaf

2021-01-19 Thread Andrea Parri (Microsoft)
If bit 22 of Group B Features is set, the guest has access to the Isolation Configuration CPUID leaf. On x86, the first four bits of EAX in this leaf provide the isolation type of the partition; we entail three isolation types: 'SNP' (hardware-based isolation), 'VBS' (software-based isolation),

Re: [PATCH v4 0/5] arm64: ARMv8.5-A: MTE: Add async mode support

2021-01-19 Thread Andrey Konovalov
On Mon, Jan 18, 2021 at 7:30 PM Vincenzo Frascino wrote: > > This patchset implements the asynchronous mode support for ARMv8.5-A > Memory Tagging Extension (MTE), which is a debugging feature that allows > to detect with the help of the architecture the C and C++ programmatic > memory errors

Re: [PATCH v5 02/14] mm/gup: check every subpage of a compound page during isolation

2021-01-19 Thread Jason Gunthorpe
On Mon, Jan 18, 2021 at 11:39:08PM -0500, Pavel Tatashin wrote: > When pages are isolated in check_and_migrate_movable_pages() we skip > compound number of pages at a time. However, as Jason noted, it is > not necessary correct that pages[i] corresponds to the pages that > we skipped. This is

Re: [PATCH v6 1/4] sgl_alloc_order: remove 4 GiB limit, sgl_free() warning

2021-01-19 Thread Bodo Stroesser
On 19.01.21 19:03, Jason Gunthorpe wrote: On Tue, Jan 19, 2021 at 06:24:49PM +0100, Bodo Stroesser wrote: I had a second look into math.h, but I don't find any reason why round_up could overflow. Can you give a hint please? #define round_up(x, y) x)-1) | __round_mask(x, y))+1)

Re: [PATCH v1 5/5] driver core: Set fw_devlink=on by default

2021-01-19 Thread Saravana Kannan
On Tue, Jan 19, 2021 at 1:05 AM Geert Uytterhoeven wrote: > > Hi Saravana, > > On Mon, Jan 18, 2021 at 10:19 PM Saravana Kannan wrote: > > On Mon, Jan 18, 2021 at 11:16 AM Geert Uytterhoeven > > wrote: > > > On Mon, Jan 18, 2021 at 6:59 PM Marc Zyngier wrote: > > > > On 2021-01-18 17:39, Geert

Re: [PATCH v4 1/5] arm64: mte: Add asynchronous mode support

2021-01-19 Thread Andrey Konovalov
On Mon, Jan 18, 2021 at 7:30 PM Vincenzo Frascino wrote: > > MTE provides an asynchronous mode for detecting tag exceptions. In > particular instead of triggering a fault the arm64 core updates a > register which is checked by the kernel after the asynchronous tag > check fault has occurred. > >

[PATCH v2] x86/vm86/32: Remove VM86_SCREEN_BITMAP support

2021-01-19 Thread Andy Lutomirski
The implementation was rather buggy. It unconditionally marked PTEs read-only, even for VM_SHARED mappings. I'm not sure whether this is actually a problem, but it certainly seems unwise. More importantly, it released the mmap lock before flushing the TLB, which could allow a racing CoW

[PATCH v2 3/4] x86/fpu: Make the EFI FPU calling convention explicit

2021-01-19 Thread Andy Lutomirski
EFI uses kernel_fpu_begin() to conform to the UEFI calling convention. This specifically requires initializing FCW, whereas no sane 64-bit kernel code should use legacy 387 operations that reference FCW. This should enable us to safely change the default semantics of kernel_fpu_begin() to stop

[PATCH v2 2/4] x86/mmx: Use KFPU_387 for MMX string operations

2021-01-19 Thread Andy Lutomirski
The default kernel_fpu_begin() doesn't work on systems that support XMM but haven't yet enabled CR4.OSFXSR. This causes crashes when _mmx_memcpy() is called too early because LDMXCSR generates #UD when the aforementioned bit is clear. Fix it by using kernel_fpu_begin_mask(KFPU_387) explicitly.

[PATCH v2 0/4] x86/fpu: Reduce unnecessary FNINIT and MXCSR usage

2021-01-19 Thread Andy Lutomirski
This series fixes two regressions: a boot failure on AMD K7 and a performance regression on everything. I did a double-take here -- the regressions were reported by different people, both named Krzysztof :) Changes from v1: - Fix MMX better -- MMX really does need FNINIT. - Improve the EFI

Re: [PATCH v4 19/21] regulator: hi6421v600-regulator: move it from staging

2021-01-19 Thread Mark Brown
On Tue, Jan 19, 2021 at 05:10:45PM +0100, Mauro Carvalho Chehab wrote: > +static int hi6421_spmi_regulator_get_voltage_sel(struct regulator_dev *rdev) > +{ > +static int hi6421_spmi_regulator_set_voltage_sel(struct regulator_dev *rdev, > + unsigned

[PATCH v2 1/4] x86/fpu: Add kernel_fpu_begin_mask() to selectively initialize state

2021-01-19 Thread Andy Lutomirski
Currently, requesting kernel FPU access doesn't distinguish which parts of the extended ("FPU") state are needed. This is nice for simplicity, but there are a few cases in which it's suboptimal: - The vast majority of in-kernel FPU users want XMM/YMM/ZMM state but do not use legacy 387

[PATCH v2 4/4] x86/fpu/64: Don't FNINIT in kernel_fpu_begin()

2021-01-19 Thread Andy Lutomirski
The remaining callers of kernel_fpu_begin() in 64-bit kernels don't use 387 instructions, so there's no need to sanitize the FPU state. Skip it to get most of the performance we lost back. Reported-by: Krzysztof Olędzki Signed-off-by: Andy Lutomirski --- arch/x86/include/asm/fpu/api.h | 12

Re: [PATCH] dmaengine: qcom: bam_dma: Add LOCK and UNLOCK flag bit support

2021-01-19 Thread Vinod Koul
On 18-01-21, 09:21, mda...@codeaurora.org wrote: > On 2021-01-15 11:28, Vinod Koul wrote: > > On 14-01-21, 01:20, mda...@codeaurora.org wrote: > > > On 2021-01-12 15:40, Vinod Koul wrote: > > > > On 12-01-21, 15:01, mda...@codeaurora.org wrote: > > > > > On 2020-12-21 23:03, mda...@codeaurora.org

Re: [PATCH 07/22] perf daemon: Add daemon command

2021-01-19 Thread Jiri Olsa
On Tue, Jan 19, 2021 at 01:08:17PM +0900, Namhyung Kim wrote: SNIP > > + if (!session) > > + return -ENOMEM; > > + > > + pr_debug("reconfig: found new session %s\n", name); > > + /* This is new session, trigger reconfig to start it.

Re: [PATCH v6 1/4] sgl_alloc_order: remove 4 GiB limit, sgl_free() warning

2021-01-19 Thread Bodo Stroesser
On 19.01.21 19:17, Jason Gunthorpe wrote: On Tue, Jan 19, 2021 at 07:08:32PM +0100, Bodo Stroesser wrote: On 19.01.21 19:03, Jason Gunthorpe wrote: On Tue, Jan 19, 2021 at 06:24:49PM +0100, Bodo Stroesser wrote: I had a second look into math.h, but I don't find any reason why round_up could

Re: [PATCH v1] of: property: Add fw_devlink support for "gpio" and "gpios" binding

2021-01-19 Thread Geert Uytterhoeven
Hi Saravana, On Tue, Jan 19, 2021 at 7:19 PM Saravana Kannan wrote: > On Tue, Jan 19, 2021 at 10:10 AM Geert Uytterhoeven > wrote: > > On Tue, Jan 19, 2021 at 6:54 PM Saravana Kannan > > wrote: > > > On Tue, Jan 19, 2021 at 2:20 AM Linus Walleij > > > wrote: > > > > On Tue, Jan 19, 2021 at

Re: [PATCH v23 03/15] mm/damon: Adaptively adjust regions

2021-01-19 Thread SeongJae Park
On Tue, 15 Dec 2020 12:54:36 +0100 SeongJae Park wrote: > From: SeongJae Park > > Even somehow the initial monitoring target regions are well constructed > to fulfill the assumption (pages in same region have similar access > frequencies), the data access pattern can be dynamically changed.

Re: [PATCH v9 10/17] PCI: endpoint: Allow user to create sub-directory of 'EPF Device' directory

2021-01-19 Thread Greg Kroah-Hartman
On Tue, Jan 19, 2021 at 12:34:05PM -0600, Bjorn Helgaas wrote: > [cc->to Greg] > > On Mon, Jan 04, 2021 at 08:59:02PM +0530, Kishon Vijay Abraham I wrote: > > Documentation/PCI/endpoint/pci-endpoint-cfs.rst explains how a user > > has to create a directory in-order to create a 'EPF Device' that >

Re: [PATCH] um: ubd: Fix crash from option parsing

2021-01-19 Thread Gabriel Krisman Bertazi
Paul Lawrence writes: > Below patch will cause NULL ptr dereferences if the optional filenames > are not present. > > Fixes: ef3ba87cb7c9 (um: ubd: Set device serial attribute from cmdline) > Signed-off-by: Paul Lawrence Looks good. Reviewed-by: Gabriel Krisman Bertazi Totally unrelated,

Re: [PATCH v9 10/17] PCI: endpoint: Allow user to create sub-directory of 'EPF Device' directory

2021-01-19 Thread Bjorn Helgaas
On Tue, Jan 19, 2021 at 12:34:07PM -0600, Bjorn Helgaas wrote: > [cc->to Greg] > > On Mon, Jan 04, 2021 at 08:59:02PM +0530, Kishon Vijay Abraham I wrote: > > Documentation/PCI/endpoint/pci-endpoint-cfs.rst explains how a user > > has to create a directory in-order to create a 'EPF Device' that >

Re: [PATCH v17 02/26] x86/cet/shstk: Add Kconfig option for user-mode control-flow protection

2021-01-19 Thread Yu, Yu-cheng
On 1/19/2021 3:06 AM, Borislav Petkov wrote: On Tue, Dec 29, 2020 at 01:30:29PM -0800, Yu-cheng Yu wrote: Shadow Stack provides protection against function return address corruption. It is active when the processor supports it, the kernel has CONFIG_X86_CET_USER enabled, and the application is

Re: [PATCH v1] of: property: Add fw_devlink support for "gpio" and "gpios" binding

2021-01-19 Thread Geert Uytterhoeven
Hi Saravana, On Tue, Jan 19, 2021 at 6:54 PM Saravana Kannan wrote: > On Tue, Jan 19, 2021 at 2:20 AM Linus Walleij > wrote: > > On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven > > wrote: > > > > Can we pull this into driver-core-next please? It fixes issues on some > > > > boards with

[PATCH v4 0/3] cpufreq-qcom-hw: Implement full OSM programming

2021-01-19 Thread AngeloGioacchino Del Regno
** ** NOTE: To "view the full picture", please look at the following ** patch series: ** https://patchwork.kernel.org/project/linux-arm-msm/list/?series=413355 ** This is a subset of that series. ** Changes in v4: - Huge patch series has been split for better

WARNING in cfg80211_bss_update

2021-01-19 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:66c55602 skbuff: back tiny skbs with kmalloc() in __netdev.. git tree: net console output: https://syzkaller.appspot.com/x/log.txt?x=121bf89f50 kernel config: https://syzkaller.appspot.com/x/.config?x=c60c9ff9cc916cbc

WARNING in smk_write_net6addr

2021-01-19 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:1d94330a Merge tag 'for-5.11/dm-fixes-1' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=124f589f50 kernel config: https://syzkaller.appspot.com/x/.config?x=ee2266946ed36986

Re: [PATCH v2 4/4] dt-bindings: usb: qcom,dwc3: Add bindings for SM8150, SM8250, SM8350

2021-01-19 Thread Vinod Koul
On 15-01-21, 09:47, Jack Pham wrote: > Add compatible strings for the USB DWC3 controller on QCOM SM8150, > SM8250 and SM8350 SoCs. > > Note the SM8150 & SM8250 compatibles are already being used in the > dts but was missing from the documentation. Reviewed-by: Vinod Koul -- ~Vinod

Re: [PATCHv2] drivers: bus: simple-pm-bus: Fix compatibility with simple-bus for auxdata

2021-01-19 Thread Tony Lindgren
* Rob Herring [210119 14:51]: > On Mon, Jan 18, 2021 at 2:41 AM Tony Lindgren wrote: > > - PRM power managment interrupts that also pinctrl driver uses > > I haven't looked at it, but can't one driver go find the other node > and the interrupts it needs? There's nothing wrong with a driver >

[PATCH v3 0/2] arm64: dts: meson: add support for Beelink GS-King-X

2021-01-19 Thread Christian Hewitt
This series adds bindings and device-tree for the Beelink (AZW) GS-King-X, which like GT-King and GT-King Pro is based on the W400 reference design. Changes since v2: - shorten audio card name to GSKING-X - add Neil's tested-by - add Martin's reviews Changes since v1: - move audio from TDM_B to

Re: [PATCH v5 08/14] mm/gup: do not allow zero page for pinned pages

2021-01-19 Thread Pavel Tatashin
On Tue, Jan 19, 2021 at 1:30 PM Jason Gunthorpe wrote: > > On Mon, Jan 18, 2021 at 11:39:14PM -0500, Pavel Tatashin wrote: > > Zero page should not be used for long term pinned pages. Once pages > > are pinned their physical addresses cannot changed until they are unpinned. > > > > Guarantee to

Re: [PATCH v9 01/17] Documentation: PCI: Add specification for the *PCI NTB* function device

2021-01-19 Thread Bjorn Helgaas
On Mon, Jan 04, 2021 at 08:58:53PM +0530, Kishon Vijay Abraham I wrote: > Add specification for the *PCI NTB* function device. The endpoint function > driver and the host PCI driver should be created based on this > specification. > > Signed-off-by: Kishon Vijay Abraham I A few typos below if

Re: [PATCH v9 17/17] Documentation: PCI: Add userguide for PCI endpoint NTB function

2021-01-19 Thread Bjorn Helgaas
On Mon, Jan 04, 2021 at 08:59:09PM +0530, Kishon Vijay Abraham I wrote: > Add documentation to help users use pci-epf-ntb function driver and > existing host side NTB infrastructure for NTB functionality. > > Signed-off-by: Kishon Vijay Abraham I > Reviewed-by: Randy Dunlap > --- >

Re: [PATCH v3 2/2] KVM: SVM: Add support for Virtual SPEC_CTRL

2021-01-19 Thread Sean Christopherson
On Fri, Jan 15, 2021, Babu Moger wrote: > --- > arch/x86/include/asm/svm.h |4 +++- > arch/x86/kvm/svm/sev.c |4 > arch/x86/kvm/svm/svm.c | 19 +++ > 3 files changed, 22 insertions(+), 5 deletions(-) > > diff --git a/arch/x86/include/asm/svm.h

Re: [PATCH v5 04/14] mm/gup: check for isolation errors

2021-01-19 Thread Pavel Tatashin
> This should have a fixme too, this is a bug. OK > > The patch looks OK, but I keep feeling this logic is all really > overcomplicated... I agree, I have a simplification patch for this logic, check out patch 12/14. > > Reviewed-by: Jason Gunthorpe Thank you for your review. Pasha

Re: [PATCH v5 03/14] mm/gup: return an error on migration failure

2021-01-19 Thread Jason Gunthorpe
On Mon, Jan 18, 2021 at 11:39:09PM -0500, Pavel Tatashin wrote: > When migration failure occurs, we still pin pages, which means > that we may pin CMA movable pages which should never be the case. > > Instead return an error without pinning pages when migration failure > happens. > > No need to

Re: [PATCH v5 08/14] mm/gup: do not allow zero page for pinned pages

2021-01-19 Thread Jason Gunthorpe
On Mon, Jan 18, 2021 at 11:39:14PM -0500, Pavel Tatashin wrote: > Zero page should not be used for long term pinned pages. Once pages > are pinned their physical addresses cannot changed until they are unpinned. > > Guarantee to always return real pages when they are pinned by adding >

Re: [PATCH v7 3/3] perf-stat: enable counting events for BPF programs

2021-01-19 Thread Arnaldo Carvalho de Melo
Em Tue, Jan 19, 2021 at 11:42:49AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Tue, Jan 19, 2021 at 11:31:44AM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Tue, Jan 19, 2021 at 12:48:19AM +, Song Liu escreveu: > > > > On Jan 18, 2021, at 11:38 AM, Arnaldo Carvalho de Melo > > > >

Re: [PATCH v3 4/4] dma-buf: heaps: add chunk heap to dmabuf heaps

2021-01-19 Thread John Stultz
On Tue, Jan 12, 2021 at 5:22 PM Minchan Kim wrote: > > From: Hyesoo Yu > > This patch supports chunk heap that allocates the buffers that > arranged into a list a fixed size chunks taken from CMA. > > The chunk heap driver is bound directly to a reserved_memory > node by following Rob Herring's

Re: [PATCH 5.10 077/152] kconfig: remove kvmconfig and xenconfig shorthands

2021-01-19 Thread Pavel Machek
Hi! > From: Masahiro Yamada > > [ Upstream commit 9bba03d4473df0b707224d4d2067b62d1e1e2a77 ] > > Linux 5.10 is out. Remove the 'kvmconfig' and 'xenconfig' shorthands > as previously announced. I don't believe this is suitable for stable. Best regards,

Re: [PATCH net 1/2] net: mrp: fix definitions of MRP test packets

2021-01-19 Thread Jakub Kicinski
On Tue, 19 Jan 2021 16:42:14 +0100 Rasmus Villemoes wrote: > On 28/12/2020 23.24, Jakub Kicinski wrote: > > On Wed, 23 Dec 2020 15:45:32 +0100 Rasmus Villemoes wrote: > >> Wireshark says that the MRP test packets cannot be decoded - and the > >> reason for that is that there's a two-byte hole

Re: [PATCH v4 2/5] kasan: Add KASAN mode kernel parameter

2021-01-19 Thread Andrey Konovalov
On Mon, Jan 18, 2021 at 7:30 PM Vincenzo Frascino wrote: > --- a/Documentation/dev-tools/kasan.rst > +++ b/Documentation/dev-tools/kasan.rst > @@ -162,6 +162,9 @@ particular KASAN features. > > - ``kasan=off`` or ``=on`` controls whether KASAN is enabled (default: > ``on``). > > +-

Re: [PATCH v2] kbuild: give the SUBLEVEL more room in KERNEL_VERSION

2021-01-19 Thread Masahiro Yamada
On Wed, Jan 20, 2021 at 12:25 AM Greg KH wrote: > > On Mon, Jan 18, 2021 at 02:54:53PM -0500, Sasha Levin wrote: > > SUBLEVEL only has 8 bits of space, which means that we'll overflow it > > once it reaches 256. > > > > Few of the stable branches will imminently overflow SUBLEVEL while > >

Re: [PATCH v1] of: property: Add fw_devlink support for "gpio" and "gpios" binding

2021-01-19 Thread Saravana Kannan
On Tue, Jan 19, 2021 at 10:10 AM Geert Uytterhoeven wrote: > > Hi Saravana, > > On Tue, Jan 19, 2021 at 6:54 PM Saravana Kannan wrote: > > On Tue, Jan 19, 2021 at 2:20 AM Linus Walleij > > wrote: > > > On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven > > > wrote: > > > > > Can we pull this

Re: [PATCH v5 04/14] mm/gup: check for isolation errors

2021-01-19 Thread Jason Gunthorpe
On Mon, Jan 18, 2021 at 11:39:10PM -0500, Pavel Tatashin wrote: > It is still possible that we pin movable CMA pages if there are isolation > errors and cma_page_list stays empty when we check again. > > Check for isolation errors, and return success only when there are no > isolation errors, and

[PATCH] um: ubd: Fix crash from option parsing

2021-01-19 Thread Paul Lawrence
Below patch will cause NULL ptr dereferences if the optional filenames are not present. Fixes: ef3ba87cb7c9 (um: ubd: Set device serial attribute from cmdline) Signed-off-by: Paul Lawrence --- arch/um/drivers/ubd_kern.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[GIT PULL] task_work fix for 5.11

2021-01-19 Thread Jens Axboe
Hi Linus, The TIF_NOTIFY_SIGNAL change inadvertently removed the unconditional task_work run we had in get_signal(). This caused a regression for some setups, since we're relying on eg fput() being run to close and release, for example, a pipe and wake the other end. For 5.11, I prefer the

Re: [PATCH v6 1/4] sgl_alloc_order: remove 4 GiB limit, sgl_free() warning

2021-01-19 Thread Jason Gunthorpe
On Tue, Jan 19, 2021 at 07:08:32PM +0100, Bodo Stroesser wrote: > On 19.01.21 19:03, Jason Gunthorpe wrote: > > On Tue, Jan 19, 2021 at 06:24:49PM +0100, Bodo Stroesser wrote: > > > > > > I had a second look into math.h, but I don't find any reason why round_up > > > could overflow. Can you give

Re: [PATCH v2 2/2] serial: 8250: Add new 8250-core based Broadcom STB driver

2021-01-19 Thread Florian Fainelli
On 1/19/2021 7:21 AM, Andy Shevchenko wrote: > On Fri, Jan 15, 2021 at 11:19 PM Al Cooper wrote: >> >> Add a UART driver for the new Broadcom 8250 based STB UART. The new >> UART is backward compatible with the standard 8250, but has some >> additional features. The new features include a high

Re: [PATCH v4 3/5] kasan: Add report for async mode

2021-01-19 Thread Andrey Konovalov
On Tue, Jan 19, 2021 at 3:46 PM Mark Rutland wrote: > > Given there's no information available, I think it's simpler and > preferable to handle the logging separately, as is done for > kasan_report_invalid_free(). For example, we could do something roughly > like: > > void

Re: [PATCH v4 5/5] arm64: mte: Inline mte_assign_mem_tag_range()

2021-01-19 Thread Andrey Konovalov
On Tue, Jan 19, 2021 at 4:45 PM Vincenzo Frascino wrote: > > Hi Catalin, > > On 1/19/21 2:45 PM, Catalin Marinas wrote: > > On Mon, Jan 18, 2021 at 06:30:33PM +, Vincenzo Frascino wrote: > >> mte_assign_mem_tag_range() is called on production KASAN HW hot > >> paths. It makes sense to inline

Re: [PATCH v2] hugetlbfs: correct obsolete function name in hugetlbfs_read_iter()

2021-01-19 Thread Mike Kravetz
On 1/17/21 10:32 PM, Miaohe Lin wrote: > Since commit 36e789144267 ("kill do_generic_mapping_read"), the function > do_generic_mapping_read() is renamed to do_generic_file_read(). And then > commit 47c27bc46946 ("fs: pass iocb to do_generic_file_read") renamed it > to generic_file_buffered_read().

[ANNOUNCE] v5.10.8-rt24

2021-01-19 Thread Sebastian Andrzej Siewior
Dear RT folks! I'm pleased to announce the v5.10.8-rt24 patch set. Changes since v5.10.8-rt23: - Added RT's version of __down_read_interruptible() which is used by stable tree since v5.10.6. - Updated the "tracing: Merge irqflags + preempt counter." patch to the latest version

Re: [PATCH] hugetlbfs: Use helper macro default_hstate in init_hugetlbfs_fs

2021-01-19 Thread Mike Kravetz
CC Andrew On 1/19/21 9:53 AM, Mike Kravetz wrote: > On 1/16/21 1:18 AM, Miaohe Lin wrote: >> Since commit e5ff215941d5 ("hugetlb: multiple hstates for multiple page >> sizes"), we can use macro default_hstate to get the struct hstate which >> we use by default. But init_hugetlbfs_fs() forgot to

Re: [PATCH v6 1/4] sgl_alloc_order: remove 4 GiB limit, sgl_free() warning

2021-01-19 Thread Jason Gunthorpe
On Tue, Jan 19, 2021 at 06:24:49PM +0100, Bodo Stroesser wrote: > > I had a second look into math.h, but I don't find any reason why round_up > could overflow. Can you give a hint please? #define round_up(x, y) x)-1) | __round_mask(x, y))+1)

[PATCH v4 2/3] soc: qcom: spm: Implement support for SAWv4.1, SDM630/660 L2 AVS

2021-01-19 Thread AngeloGioacchino Del Regno
Implement the support for SAW v4.1, used in at least MSM8998, SDM630, SDM660 and APQ variants and, while at it, also add the configuration for the SDM630/660 Silver and Gold cluster L2 Adaptive Voltage Scaler: this is also one of the prerequisites to allow the OSM controller to perform DCVS.

[PATCH 3/4] Drivers: hv: vmbus: Enforce 'VMBus version >= 5.2' on isolated guests

2021-01-19 Thread Andrea Parri (Microsoft)
Restrict the protocol version(s) that will be negotiated with the host to be 5.2 or greater if the guest is running isolated. This reduces the footprint of the code that will be exercised by Confidential VMs and hence the exposure to bugs and vulnerabilities. Signed-off-by: Andrea Parri

[PATCH v4 5/7] regulator: qcom-labibb: Implement short-circuit and over-current IRQs

2021-01-19 Thread AngeloGioacchino Del Regno
Short-Circuit Protection (SCP) and Over-Current Protection (OCP) are very important for regulators like LAB and IBB, which are designed to provide from very small to relatively big amounts of current to the device (normally, a display). Now that this regulator supports both voltage setting and

Re: Re: [RESEND PATCH v6 5/6] arm64: tegra: Audio graph header for Tegra210

2021-01-19 Thread Thierry Reding
On Tue, Jan 19, 2021 at 11:09:32PM +0530, Sameer Pujar wrote: > > > On 1/19/2021 10:45 PM, Thierry Reding wrote: > > On Tue, Jan 19, 2021 at 02:58:15PM +0530, Sameer Pujar wrote: > > > Expose a header which describes DT bindings required to use audio-graph > > > based sound card. All Tegra210

[PATCH v4 3/3] soc: qcom: spm: Add compatible for MSM8998 SAWv4.1 L2

2021-01-19 Thread AngeloGioacchino Del Regno
Add the SAWv4.1 parameters for MSM8998's Gold and Silver clusters. Signed-off-by: AngeloGioacchino Del Regno --- drivers/soc/qcom/spm.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/soc/qcom/spm.c b/drivers/soc/qcom/spm.c index 843732d12c54..2e6312663293 100644

Re: [Linux-stm32] [PATCH] iio: adc: stm32-adc: fix erroneous handling of spurious IRQs

2021-01-19 Thread Fabrice Gasnier
On 1/18/21 12:42 PM, Ahmad Fatoum wrote: > Hello Jonathan, > > On 16.01.21 18:53, Jonathan Cameron wrote: >> On Tue, 12 Jan 2021 16:24:42 +0100 >> Ahmad Fatoum wrote: >> >>> 1c6c69525b40 ("genirq: Reject bogus threaded irq requests") makes sure >>> that threaded IRQs either >>> - have

Re: Re: [RESEND PATCH v6 5/6] arm64: tegra: Audio graph header for Tegra210

2021-01-19 Thread Sameer Pujar
On 1/19/2021 10:45 PM, Thierry Reding wrote: On Tue, Jan 19, 2021 at 02:58:15PM +0530, Sameer Pujar wrote: Expose a header which describes DT bindings required to use audio-graph based sound card. All Tegra210 based platforms can include this header and add platform specific information.

WARNING in kmalloc_array

2021-01-19 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:0da0a8a0 Merge tag 'scsi-fixes' of git://git.kernel.org/pu.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1293e1f750 kernel config: https://syzkaller.appspot.com/x/.config?x=ee2266946ed36986

Re: [PATCH] sched/eas: Don't update misfit status if the task is pinned

2021-01-19 Thread Qais Yousef
On 01/19/21 16:55, Quentin Perret wrote: > On Tuesday 19 Jan 2021 at 16:40:27 (+), Qais Yousef wrote: > > On 01/19/21 15:35, Quentin Perret wrote: > > > Do you mean failing the sched_setaffinity syscall if e.g. the task > > > has a min clamp that is higher than the capacity of the CPUs to

Re: [PATCH 03/22] perf tools: Add debug_set_display_time function

2021-01-19 Thread Jiri Olsa
On Tue, Jan 19, 2021 at 11:59:22AM -0300, Arnaldo Carvalho de Melo wrote: SNIP > > +} > > 7812.70 ubuntu:18.04-x-sparc64: FAIL sparc64-linux-gnu-gcc > (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 > > util/debug.c: In function 'fprintf_time': > util/debug.c:63:32: error: format '%lu'

BUG: sleeping function called from invalid context in rxe_alloc_nl

2021-01-19 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:b4bb878f Add linux-next specific files for 20210119 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=12d34e9f50 kernel config: https://syzkaller.appspot.com/x/.config?x=7b1ca623d7cc5ca3 dashboard

[PATCH v3] dt-bindings: usb: qcom,dwc3: Add bindings for SM8150, SM8250, SM8350

2021-01-19 Thread Jack Pham
Add compatible strings for the USB DWC3 controller on QCOM SM8150, SM8250 and SM8350 SoCs. Note the SM8150 & SM8250 compatibles are already being used in the dts but was missing from the documentation. Acked-by: Felipe Balbi Signed-off-by: Jack Pham --- v3: Resend of #4/4 of

Re: [PATCH v2] driver core: Extend device_is_dependent()

2021-01-19 Thread Rafael J. Wysocki
On Fri, Jan 15, 2021 at 7:31 PM Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > If the device passed as the target (second argument) to > device_is_dependent() is not completely registered (that is, it has > been initialized, but not added yet), but the parent pointer of it > is set, it

Re: [PATCH 1/3] phy: qcom-qusb2: Allow specifying default clock scheme

2021-01-19 Thread Vinod Koul
On 14-01-21, 18:47, AngeloGioacchino Del Regno wrote: > The TCSR's PHY_CLK_SCHEME register is not available on all SoC > models, but some may still use a differential reference clock. > > In preparation for these SoCs, add a se_clk_scheme_default > configuration entry and declare it to true for

Re: [x86/mce] 7bb39313cd: netperf.Throughput_tps -4.5% regression

2021-01-19 Thread Feng Tang
Hi Boris, On Tue, Jan 19, 2021 at 02:17:59PM +0100, Borislav Petkov wrote: > On Tue, Jan 19, 2021 at 08:15:05PM +0800, Feng Tang wrote: > > On Tue, Jan 19, 2021 at 11:02:55AM +0100, Borislav Petkov wrote: > > > On Mon, Jan 18, 2021 at 08:27:21PM -0800, Paul E. McKenney wrote: > > > > I bet that

Re: [PATCH v1] cpufreq: tegra20: Use resource-managed API

2021-01-19 Thread Dmitry Osipenko
18.01.2021 09:39, Viresh Kumar пишет: > On 18-01-21, 02:18, Dmitry Osipenko wrote: >> Switch cpufreq-tegra20 driver to use resource-managed API. >> This removes the need to get opp_table pointer using >> dev_pm_opp_get_opp_table() in order to release OPP table that >> was requested by

Re: [PATCH v2 3/4] dt-bindings: phy: qcom,usb-snps-femto-v2: Add SM8250 and SM8350 bindings

2021-01-19 Thread Vinod Koul
On 15-01-21, 09:47, Jack Pham wrote: > Add the compatible strings for the USB2 PHYs found on QCOM > SM8250 & SM8350 SoCs. > > Note that the SM8250 compatible is already in use in the dts and > driver implementation but was missing from the documentation. Applied, thanks -- ~Vinod

Re: [PATCH v2 2/4] phy: qcom-qmp: Add SM8350 USB QMP PHYs

2021-01-19 Thread Vinod Koul
On 15-01-21, 09:47, Jack Pham wrote: > Add support for the USB DP & UNI PHYs found on SM8350. These use > version 5.0.0 of the QMP PHY IP and thus require new "V5" > definitions of the register offset macros for the QSERDES RX > and TX blocks. The QSERDES common and QPHY PCS blocks' register >

Re: [RFC PATCH 00/37] block: introduce bio_init_fields()

2021-01-19 Thread Josef Bacik
On 1/19/21 12:05 AM, Chaitanya Kulkarni wrote: Hi, This is a *compile only RFC* which adds a generic helper to initialize the various fields of the bio that is repeated all the places in file-systems, block layer, and drivers. The new helper allows callers to initialize various members such as

Re: [PATCH v1 2/4] s390/kvm: extend guest_translate for MVPG interpretation

2021-01-19 Thread Janosch Frank
On 12/18/20 3:18 PM, Claudio Imbrenda wrote: > Extend guest_translate to optionally return the address of the guest > DAT table which caused the exception, and change the return value to int. > > Also return the appropriate values in the low order bits of the address > indicating protection or

Re: [PATCH v2 1/4] dt-bindings: phy: qcom,qmp: Add SM8150, SM8250 and SM8350 USB PHY bindings

2021-01-19 Thread Vinod Koul
On 15-01-21, 09:47, Jack Pham wrote: > Add the compatible strings for the USB3 PHYs found on SM8150, SM8250 > and SM8350 SoCs. These require separate subschemas due to the different > required clock entries. > > Note the SM8150 and SM8250 compatibles have already been in place in > the dts as

Re: [PATCH 03/22] perf tools: Add debug_set_display_time function

2021-01-19 Thread Arnaldo Carvalho de Melo
Em Sat, Jan 02, 2021 at 11:04:22PM +0100, Jiri Olsa escreveu: > Allow to display time in perf debug output via new > debug_set_display_time function. > > It will be used in perf daemon command to get verbose > output into log file. > > The debug time format is: > > [2020-12-03

Re: [PATCH v4 3/5] kasan: Add report for async mode

2021-01-19 Thread Vincenzo Frascino
On 1/19/21 2:46 PM, Mark Rutland wrote: > On Tue, Jan 19, 2021 at 02:23:03PM +, Vincenzo Frascino wrote: >> On 1/19/21 1:04 PM, Catalin Marinas wrote: >>> On Mon, Jan 18, 2021 at 06:30:31PM +, Vincenzo Frascino wrote: > +bool kasan_report_async(unsigned long addr, size_t size,

Re: [PATCH 0/5] soundwire: fix ACK/NAK handling and improve log

2021-01-19 Thread Vinod Koul
On 15-01-21, 13:37, Bard Liao wrote: > The existing code reports a NAK only when ACK=0 > This is not aligned with the SoundWire 1.x specifications. > > Table 32 in the SoundWire 1.2 specification shows that a Device shall > not set NAK=1 if ACK=1. But Table 33 shows the Combined Response > may

[PATCH v3 2/2] arm64: dts: meson: add initial Beelink GS-King-X device-tree

2021-01-19 Thread Christian Hewitt
The Shenzen AZW (Beelink) GS-King-X is based on the Amlogic W400 reference board with an S922X-H chip. - 4GB LPDDR4 RAM - 64GB eMMC storage - 10/100/1000 Base-T Ethernet - AP6356S Wireless (802.11 a/b/g/n/ac, BT 4.1) - HDMI 2.1 video - S/PDIF optical output - 2x ESS9018 audio DACs - 4x Ricor

[PATCH v3 1/2] dt-bindings: arm: amlogic: add support for the Beelink GS-King-X

2021-01-19 Thread Christian Hewitt
The Shenzen AZW (Beelink) GS-King-X is based on the Amlogic W400 reference board with an S922X-H chip. Signed-off-by: Christian Hewitt Acked-by: Rob Herring Reviewed-by: Martin Blumenstingl --- Documentation/devicetree/bindings/arm/amlogic.yaml | 1 + 1 file changed, 1 insertion(+) diff

Re: [PATCH 2/2] soundwire: cadence: reduce timeout on transactions

2021-01-19 Thread Vinod Koul
On 15-01-21, 14:16, Bard Liao wrote: > From: Pierre-Louis Bossart > > Currently the timeout for SoundWire individual transactions is 2s. > > This is too large in comparison with the enumeration and completion > timeouts used in codec drivers. > > A command will typically be handled in less

<    3   4   5   6   7   8   9   10   11   12   >