Re: [PATCH] spi: Fix the logic around the maximum speed

Hi Fabio, Fabio Estevam wrote on Wed, 3 Feb 2021 14:10:15 -0300: > Hi Miquel, > > On Wed, Feb 3, 2021 at 2:06 PM Miquel Raynal > wrote: > > > > Commit 9326e4f1e5dd ("spi: Limit the spi device max speed to controller's > > max speed") > > rationaly introduced a new condition on which the

[PATCH v5 0/5] x86: Improve Minimum Alternate Stack Size

During signal entry, the kernel pushes data onto the normal userspace stack. On x86, the data pushed onto the user stack includes XSAVE state, which has grown over time as new features and larger registers have been added to the architecture. MINSIGSTKSZ is a constant provided in the kernel

[PATCH v5 3/5] x86/elf: Support a new ELF aux vector AT_MINSIGSTKSZ

Historically, signal.h defines MINSIGSTKSZ (2KB) and SIGSTKSZ (8KB), for use by all architectures with sigaltstack(2). Over time, the hardware state size grew, but these constants did not evolve. Today, literal use of these constants on several architectures may result in signal stack overflow,

Re: [RFC PATCH] sched/core: Fix premature p->migration_pending completion

On 01/27/21 19:30, Valentin Schneider wrote: > Fiddling some more with a TLA+ model of set_cpus_allowed_ptr() & friends > unearthed one more outstanding issue. This doesn't even involve > migrate_disable(), but rather affinity changes and execution of the stopper > racing with each other. > > My

[PATCH v5 1/5] uapi: Move the aux vector AT_MINSIGSTKSZ define to uapi

Move the AT_MINSIGSTKSZ definition to generic Linux from arm64. It is already used as generic ABI in glibc's generic elf.h, and this move will prevent future namespace conflicts. In particular, x86 will re-use this generic definition. Signed-off-by: Chang S. Bae Reviewed-by: Len Brown Cc:

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

On Tue, Feb 02, 2021 at 09:40:40PM +, Mike Leach wrote: > 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

Re: [PATCH v4 2/2] arm: dts: sc7180: Add support for gpu fuse

On 2/3/2021 4:22 AM, Bjorn Andersson wrote: On Fri 08 Jan 12:15 CST 2021, Akhil P Oommen wrote: Please align the $subject prefix with other changes in the same file. I fixed it up while picking up the patch this time. Will take of this in future. Thanks, Bjorn. -Akhil. Regards, Bjorn Add

[PATCH 1/1] tracepoint: cleanup: do not fail unregistration

This patch is only compile-tested. Signed-off-by: Mathieu Desnoyers --- include/linux/tracepoint.h | 2 +- kernel/tracepoint.c| 80 +- 2 files changed, 28 insertions(+), 54 deletions(-) diff --git a/include/linux/tracepoint.h

[PATCH v3 2/7] selftests: lib:test_seqnum_ops: add new test for seqnum_ops

Add a new selftest for testing seqnum_ops. This test loads test_seqnum_ops test module and unloads it. The test module runs tests and prints results to dmesg. Sequence Number api provides interfaces for unsigned atomic up counters leveraging atomic_t and atomic64_t ops underneath. There are a

Re: [PATCH v3 1/1] x86,sched: On AMD EPYC set freq_max = max_boost in schedutil invariant formula

On Wednesday, February 3, 2021 3:11:37 PM CET Rafael J. Wysocki wrote: > On Wed, Feb 3, 2021 at 2:53 PM Giovanni Gherdovich > wrote: > > > > [cut] > > > Fixes: 41ea667227ba ("x86, sched: Calculate frequency invariance for AMD > > systems") > > Fixes: 976df7e5730e ("x86, sched: Use midpoint of

Re: [PATCH mvebu v2 00/10] Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz

Hi Marek & Pali On 1/14/21 1:40 PM, Pali Rohár wrote: Hello! The armada-37xx-cpufreq driver changes base CPU speed from 1000 MHz to 800 MHz on EspressoBIN and Turris MOX. The commit message in patch 2/10 explains why and how can this be discovered. That patch 2/10 led us to discover another

Re: [PATCH 07/11] x86/fault: Split the OOPS code out from no_context()

> On Feb 3, 2021, at 10:56 AM, Borislav Petkov wrote: > > On Sun, Jan 31, 2021 at 09:24:38AM -0800, Andy Lutomirski wrote: >> Not all callers of no_context() want to run exception fixups. >> Separate the OOPS code out from the fixup code in no_context(). >> >> Cc: Dave Hansen >> Cc: Peter

Re: [PATCH 1/1] iscsi_ibft: KASAN false positive failure occurs in ibft_init()

Hey Dmitry, Rafael, George, please see below.. On Wed, Jan 27, 2021 at 10:10:07PM +0100, Dmitry Vyukov wrote: > On Wed, Jan 27, 2021 at 9:01 PM George Kennedy > wrote: > > > > Hi Dmitry, > > > > On 1/27/2021 1:48 PM, Dmitry Vyukov wrote: > > > > On Wed, Jan 27, 2021 at 7:44 PM Konrad Rzeszutek

Re: [PATCH 1/2] hwmon: lm75: Add NXP LM75A to of_match list

On 2/3/21 9:13 AM, Matwey V. Kornilov wrote: > > > сб, 30 янв. 2021 г. в 18:41, Guenter Roeck >: >> >> On 1/30/21 2:38 AM, Matwey V. Kornilov wrote: >> > NXP LM75A is compatible with original LM75A while it has improved >> > 11-bit precision. >> > >> >

[PATCH v2] platform/x86: Move all dell drivers to their own subdirectory

A user without a Dell system doesn't need to pick any of these drivers. Users with a Dell system can enable this submenu and all drivers behind it will be enabled. Suggested-by: Andy Shevchenko Signed-off-by: Mario Limonciello --- Changes from v1->v2: - Rename menu per Andy's suggestion -

Linux 5.11-rc6 compile error

I am seeing the following compile error on Linux 5.11-rc6. No issues on 5.11.0-rc5 with the same config. ld: arch/x86/built-in.a: member arch/x86/kernel/pci-swiotlb.o in archive is not an object make: *** [Makefile:1170: vmlinux] Error 1 CONFIG_SWIOTLB_XEN=y CONFIG_SWIOTLB=y I can debug

Re: [PATCH 1/2] misc/pvpanic: split-up generic and platform dependent code

a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Mihai-Carabas/misc-pvpanic-split-up-generic-and-platform-dependent-code/20210203-234431 base: https://git.kernel.org/pub/scm

Re: [PATCH -next] RISCV: Add some depends for NUMA

On Wed, Feb 3, 2021 at 6:20 AM Kefeng Wang wrote: > > The numa feature is useless for riscv32 platform(MAXPHYSMEM_1GB if 32bit), > and it should depends on SMP feature, this also fix the build error, > > riscv64-buildroot-linux-gnu-ld: mm/page_alloc.o: in function `.L0 ': >

Re: [Linaro-mm-sig] [PATCH 1/2] mm: replace BUG_ON in vm_insert_page with a return of an error

On Wed, Feb 3, 2021 at 12:52 AM Daniel Vetter wrote: > > On Wed, Feb 3, 2021 at 2:57 AM Matthew Wilcox wrote: > > > > On Tue, Feb 02, 2021 at 04:31:33PM -0800, Suren Baghdasaryan wrote: > > > Replace BUG_ON(vma->vm_flags & VM_PFNMAP) in vm_insert_page with > > > WARN_ON_ONCE and returning an

Re: [PATCH 13/14] cxl/mem: Add limited Get Log command (0401h)

On Wed, Feb 3, 2021 at 10:16 AM Konrad Rzeszutek Wilk wrote: > > On Wed, Feb 03, 2021 at 09:16:10AM -0800, Ben Widawsky wrote: > > On 21-02-02 15:57:03, Dan Williams wrote: > > > On Tue, Feb 2, 2021 at 3:51 PM Ben Widawsky > > > wrote: > > > > > > > > On 21-02-01 13:28:48, Konrad Rzeszutek Wilk

Re: [PATCH 5/9] perf tools: Support PERF_SAMPLE_WEIGHT_STRUCT

Em Tue, Feb 02, 2021 at 12:09:09PM -0800, kan.li...@linux.intel.com escreveu: > From: Kan Liang > > The new sample type, PERF_SAMPLE_WEIGHT_STRUCT, is an alternative of the > PERF_SAMPLE_WEIGHT sample type. Users can apply either the > PERF_SAMPLE_WEIGHT sample type or the

Re: [PATCH] x86: efi: avoid BUILD_BUG_ON() for non-constant p4d_index

On Wed, 3 Feb 2021 at 19:51, Nathan Chancellor wrote: > > On Wed, Jan 20, 2021 at 10:33:43AM +0100, Ard Biesheuvel wrote: > > On Mon, 18 Jan 2021 at 22:42, Arvind Sankar wrote: > > > > > > On Mon, Jan 18, 2021 at 09:24:09PM +0100, Borislav Petkov wrote: > > > > > > > As a matter of fact, it

Re: [Linaro-mm-sig] [PATCH 1/2] mm: replace BUG_ON in vm_insert_page with a return of an error

On Wed, Feb 3, 2021 at 9:20 PM Suren Baghdasaryan wrote: > > On Wed, Feb 3, 2021 at 12:52 AM Daniel Vetter wrote: > > > > On Wed, Feb 3, 2021 at 2:57 AM Matthew Wilcox wrote: > > > > > > On Tue, Feb 02, 2021 at 04:31:33PM -0800, Suren Baghdasaryan wrote: > > > > Replace BUG_ON(vma->vm_flags &

[PATCH 09/12] iommu/vt-d: Add DEV-MSI support

Add required support in the interrupt remapping driver for devices which generate dev-msi interrupts and use the intel remapping domain as the parent domain. Set the source-id of all dev-msi interrupt requests to the parent PCI device associated with it. Reviewed-by: Tony Luck Signed-off-by:

Re: [RFC v2 4/5] drm/dp: Extract i915's eDP backlight code into DRM helpers

On Mon, Jan 25, 2021 at 07:10:30PM -0500, Lyude Paul wrote: > Since we're about to implement eDP backlight support in nouveau using the > standard protocol from VESA, we might as well just take the code that's > already written for this and move it into a set of shared DRM helpers. > > Note that

Re: [PATCH v2] pwm: sunxi: Add Allwinner SoC PWM controller driver

Hello Thierry, hello Ban, On Wed, Feb 03, 2021 at 05:33:16PM +0100, Thierry Reding wrote: > On Wed, Feb 03, 2021 at 04:12:00PM +0100, Uwe Kleine-König wrote: > > On Wed, Feb 03, 2021 at 08:53:17PM +0800, Ban Tao wrote: > [...] > > > +#define PWM_GET_CLK_OFFSET(chan) (0x20 + ((chan >> 1) * 0x4)) >

[PATCH 10/12] iommu: Add capability IOMMU_CAP_VIOMMU_HINT

From: Lu Baolu Some IOMMU specification defines some kind of hint mechanism, through which BIOS can imply that OS runs in a virtualized environment. For example, the caching mode defined in VT-d spec and NpCache capability defined in the AMD IOMMU specification. This hint could also be used

[PATCH 12/12] irqchip: Add IMS (Interrupt Message Store) driver

From: Thomas Gleixner Generic IMS(Interrupt Message Store) irq chips and irq domain implementations for IMS based devices which store the interrupt messages in an array in device memory. Allocation and freeing of interrupts happens via the generic msi_domain_alloc/free_irqs() interface. No

[PATCH 04/12] genirq/proc: Take buslock on affinity write

From: Thomas Gleixner Until now interrupt chips which support setting affinity are not locking the associated bus lock for two reasons: - All chips which support affinity setting do not use buslock because they just can operated directly on the hardware. - All chips which use buslock do

[PATCH 0/4] mm/hugetlb: Early cow on fork, and a few cleanups

As reported by Gal [1], we still miss the code clip to handle early cow for hugetlb case, which is true. Again, it still feels odd to fork() after using a few huge pages, especially if they're privately mapped to me.. However I do agree with Gal and Jason in that we should still have that since

Re: [PATCH v3 04/15] PCI: Add pci_find_vsec_capability() to find a specific VSEC

Hi Gustavo, I love your patch! Perhaps something to improve: [auto build test WARNING on vkoul-dmaengine/next] [also build test WARNING on pci/next linux/master linus/master v5.11-rc6 next-20210125] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting

Re: [PATCH 06/24] perf daemon: Add config file support

Em Sun, Jan 31, 2021 at 12:48:38AM +0100, Jiri Olsa escreveu: > Adding support to configure daemon with config file. > > Each client or server invocation of perf daemon needs to know the > base directory, where all sessions data is stored. > > The base is defined with: > > daemon.base >

Re: [PATCH 1/3] dt-bindings: Fix undocumented compatible strings in examples

On Tue, Feb 02, 2021 at 04:33:56PM -0800, Stephen Boyd wrote: > Quoting Rob Herring (2021-02-02 12:55:42) > > > > diff --git > > a/Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-usb-clocks.yaml > > > > b/Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-usb-clocks.yaml >

Re: [PATCH 5/9] perf tools: Support PERF_SAMPLE_WEIGHT_STRUCT

On 2/3/2021 3:31 PM, Arnaldo Carvalho de Melo wrote: --- a/tools/perf/util/perf_event_attr_fprintf.c +++ b/tools/perf/util/perf_event_attr_fprintf.c @@ -35,7 +35,7 @@ static void __p_sample_type(char *buf, size_t size, u64 value) bit_name(BRANCH_STACK), bit_name(REGS_USER),

Re: [PATCH 2/9] perf tools: Support the auxiliary event

On 2/3/2021 3:02 PM, Arnaldo Carvalho de Melo wrote: Em Tue, Feb 02, 2021 at 12:09:06PM -0800,kan.li...@linux.intel.com escreveu: From: Kan Liang diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c index c26ea822..c48f6de 100644 --- a/tools/perf/util/evsel.c +++

Re: [PATCH V3] clk: imx: Fix reparenting of UARTs not associated with sdout

On Thu, Jan 21, 2021 at 4:24 AM Abel Vesa wrote: > > On 21-01-21 10:56:17, Sascha Hauer wrote: > > On Wed, Jan 20, 2021 at 06:14:21PM +0200, Abel Vesa wrote: > > > On 21-01-20 16:50:01, Sascha Hauer wrote: > > > > On Wed, Jan 20, 2021 at 05:28:13PM +0200, Abel Vesa wrote: > > > > > On 21-01-20

Re: [PATCH bpf-next v3] bpf: Propagate stack bounds to registers in atomics w/ BPF_FETCH

On Wed, Feb 3, 2021 at 9:07 AM Yonghong Song wrote: > > > > On 2/2/21 5:50 AM, Brendan Jackman wrote: > > When BPF_FETCH is set, atomic instructions load a value from memory > > into a register. The current verifier code first checks via > > check_mem_access whether we can access the memory, and

Re: [virtio-dev] Re: [PATCH v2 2/9] ALSA: virtio: add virtio sound driver

On Wed, 03 Feb 2021 18:34:12 +0100, Anton Yakovlev wrote: > > Hi Takashi, > > > On 03.02.2021 17:59, Takashi Iwai wrote: > > On Tue, 02 Feb 2021 00:18:09 +0100, > > Anton Yakovlev wrote: > +/** > + * virtsnd_reset_fn() - Kernel worker's function to reset the device. > + * @work:

Re: BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1df5/0x2650

> Can you pretty please not line-wrap console output? It's unreadable. GMail doesn't make it easy, I'll send a link to a pastebin next time. Let me know if you'd like me to regenerate the decoded stack. > > edfd9b7838ba5e47f19ad8466d0565aba5c59bf0 is the first bad commit > > commit

Re: [PATCH 1/2] ima: Free IMA measurement buffer on error

On 1/22/21 2:30 PM, Thiago Jung Bauermann wrote: Hi Lakshmi, Lakshmi Ramasubramanian writes: IMA allocates kernel virtual memory to carry forward the measurement list, from the current kernel to the next kernel on kexec system call, in ima_add_kexec_buffer() function. In error code paths

[PATCH v3 10/15] dmaengine: dw-edma: Change linked list and data blocks offset and sizes

Changes the linked list and data blocks offset and sizes to follow the recommendation given by the hardware team for the IPK solution. Although the previous data blocks offset and sizes are still valid and functional, using them that might present some issues related to the IPK solution, since

[PATCH v3 06/15] dmaengine: dw-edma: Add device_prep_interleave_dma() support

Add device_prep_interleave_dma() support to Synopsys DMA driver. This feature implements a similar data transfer mechanism to the scatter-gather implementation. Signed-off-by: Gustavo Pimentel --- drivers/dma/dw-edma/dw-edma-core.c | 85 ++

[PATCH v3 13/15] dmaengine: dw-edma: Change DMA abreviation from lower into upper case

To keep code consistent, some comments with dma keyword written in lower case are now in upper case. Signed-off-by: Gustavo Pimentel --- drivers/dma/dw-edma/dw-edma-core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/dma/dw-edma/dw-edma-core.c

[PATCH v3 09/15] dmaengine: dw-edma: Improve the linked list and data blocks definition

In the previous implementation the driver assumes that only existed 2 memory spaces that would be equal distributed amount the write/read channels. This might not be the case on some other implementations, therefore this patches changes this requirement so that each write/read channel has their

[PATCH v3 14/15] dmaengine: dw-edma: Revert fix scatter-gather address calculation

Reverting the applied patch because it caused a regression on ARC700 platform (32 bits). Signed-off-by: Gustavo Pimentel --- drivers/dma/dw-edma/dw-edma-core.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/dma/dw-edma/dw-edma-core.c

Re: [for-next][PATCH 14/15] tracepoint: Do not fail unregistering a probe due to memory failure

- On Feb 3, 2021, at 11:05 AM, rostedt rost...@goodmis.org wrote: > From: "Steven Rostedt (VMware)" > > The list of tracepoint callbacks is managed by an array that is protected > by RCU. To update this array, a new array is allocated, the updates are > copied over to the new array, and

[PATCH v3 00/15] dmaengine: dw-edma: HDMA support

This patch series adds the HDMA support, as long the IP design has set the compatible register map parameter, which allows compatibility at some degree for the existing Synopsys DesignWare eDMA driver that is already available on the Kernel. The HDMA "Hyper-DMA" IP is an enhancement of the eDMA

[PATCH v3 07/15] dmaengine: dw-edma: Improve number of channels check

It was added some extra checks to ensure that the driver doesn't try to use more DMA channels than actually are available in hardware. Signed-off-by: Gustavo Pimentel --- drivers/dma/dw-edma/dw-edma-core.c | 21 + drivers/dma/dw-edma/dw-edma-core.h | 2 ++ 2 files changed,

Re: [PATCH] arch: sh: kernel: Change to correct spelling archtecture to architecture in the file relocate_kernel.S

On 2/3/21 7:25 AM, Bhaskar Chowdhury wrote: Normally a patch description is required . If the patch committer wants to take it as is, the typo fix LGTM. > Signed-off-by: Bhaskar Chowdhury > --- > arch/sh/kernel/relocate_kernel.S | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

[PATCH v3 15/15] dmaengine: dw-edma: Add pcim_iomap_table return checker

Detected by CoverityScan CID 16555 ("Dereference null return") Signed-off-by: Gustavo Pimentel --- drivers/dma/dw-edma/dw-edma-pcie.c | 15 +++ 1 file changed, 15 insertions(+) diff --git a/drivers/dma/dw-edma/dw-edma-pcie.c b/drivers/dma/dw-edma/dw-edma-pcie.c index

[PATCH v3 03/15] dmaengine: dw-edma: Add support for the HDMA feature

Add support for the HDMA feature. This new feature enables the current eDMA IP to use a deeper prefetch of the linked list, which reduces the algorithm execution latency observed when loading the elements of the list, causing more stable and higher data transfer. Signed-off-by: Gustavo Pimentel

[PATCH v3 02/15] dmaengine: dw-edma: Fix comments offset characters' alignment

Fix comments offset characters' alignment to follow the same structure of similar comments. Signed-off-by: Gustavo Pimentel --- drivers/dma/dw-edma/dw-edma-v0-regs.h | 214 +- 1 file changed, 107 insertions(+), 107 deletions(-) diff --git

Re: [PATCH] ARM: dts: zynq: Add address-cells property to interrupt controllers

On Wed, Feb 3, 2021 at 10:49 AM Rob Herring wrote: > > On Wed, Feb 3, 2021 at 8:44 AM Andre Przywara wrote: > > > > On Wed, 3 Feb 2021 15:15:19 +0100 > > Michal Simek wrote: > > > > > On 2/3/21 3:12 PM, Rob Herring wrote: > > > > On Wed, Feb 3, 2021 at 1:01 AM Michal Simek > > > > wrote: > >

[ANNOUNCE] v5.10.12-rt26

Dear RT folks! I'm pleased to announce the v5.10.12-rt26 patch set. Changes since v5.10.12-rt25: - Updated the "tracing: Merge irqflags + preempt counter." patch to the version Steven posted for upstream inclusion. - Update the work-in-progress softirq patch. One difference is that

[PATCH v3 5/7] drivers/staging/rtl8723bs: convert event_seq to use seqnum_ops

Sequence Number api provides interfaces for unsigned atomic up counters leveraging atomic_t and atomic64_t ops underneath. Convert it to use seqnum_ops. event_seq atomic_t variables are atomic counters. Convert them to use seqnum_ops. Signed-off-by: Shuah Khan ---

Re: [PATCH] clk: at91: Fix the declaration of the clocks

On Wed, Feb 3, 2021 at 7:43 AM Tudor Ambarus wrote: > > These are all "early clocks" that require initialization just at > of_clk_init() time. Use CLK_OF_DECLARE() to declare them. > > This also fixes a problem that was spotted when fw_devlink was > set to 'on' by default: the boards failed to

Re: [PATCH 0/6] Support second Image Signal Processor on rk3399

Hey Heiko, I have tested your patch set on my nanoPC-T4, here is a complete log with: - relevant kernel log entries - system information - media ctl output - sysfs entry information https://paste.debian.net/1183874/ Additionally, to your patchset I have applied the following patches:

[PATCH v3 6/7] drivers/staging/rtl8188eu: convert event_seq to use seqnum_ops

Sequence Number api provides interfaces for unsigned atomic up counters leveraging atomic_t and atomic64_t ops underneath. Convert it to use seqnum_ops. event_seq atomic_t variables are atomic counters. Convert them to use seqnum_ops. Signed-off-by: Shuah Khan ---

[PATCH v3 7/7] kobject: convert uevent_seqnum to seqnum_ops

Sequence Number api provides interfaces for unsigned atomic up counters leveraging atomic_t and atomic64_t ops underneath. Convert uevent_seqnum atomic counter to use seqnum_ops. Signed-off-by: Shuah Khan --- include/linux/kobject.h | 3 ++- kernel/ksysfs.c | 3 ++-

[GIT PULL] arm64 fixes for 5.11-rc7

Hi Linus, Please pull the arm64 fixes below. Thanks. The following changes since commit a1df829ead5877d4a1061e976a50e2e665a16f24: ACPI/IORT: Do not blindly trust DMA masks from firmware (2021-01-27 12:26:24 +) are available in the Git repository at:

[PATCH v3 4/5] ACPI: video: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() instances in acpi_video.c with acpi_handle_debug() calls and the ACPI_EXCEPTION()/ACPI_ERROR()/ ACPI_WARNING() instances in there with acpi_handle_info() calls, which among other things causes the excessive log levels of those messages to be

Re: Conflict with Mickaël Salaün's blacklist patches [was [PATCH v5 0/4] Add EFI_CERT_X509_GUID support for dbx/mokx entries]

This looks good to me, and it still works for my use case. Eric's patchset only looks for asymmetric keys in the blacklist keyring, so even if we use the same keyring we don't look for the same key types. My patchset only allows blacklist keys (i.e. hashes, not asymmetric keys) to be added by user

[PATCH v3 2/5] ACPI: battery: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() instances in battery.c with acpi_handle_debug() and acpi_handle_info() calls, respectively, which among other things causes the excessive log level of the messages previously printed via ACPI_EXCEPTION() to be increased.

[PATCH v3 3/5] ACPI: button: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() instance in button.c with an acpi_handle_debug() call, drop the _COMPONENT and ACPI_MODULE_NAME() definitions that are not used any more, drop the no longer needed ACPI_BUTTON_COMPONENT definition from the headers and update the

Re: [RFC PATCH] sched/core: Fix premature p->migration_pending completion

On 03/02/21 17:23, Qais Yousef wrote: > On 01/27/21 19:30, Valentin Schneider wrote: >> Fiddling some more with a TLA+ model of set_cpus_allowed_ptr() & friends >> unearthed one more outstanding issue. This doesn't even involve >> migrate_disable(), but rather affinity changes and execution of the

Re: [PATCH][RESEND] lib/vsprintf: make-printk-non-secret printks all addresses as unhashed

On Wed, Feb 03, 2021 at 12:58:41PM -0600, Timur Tabi wrote: > On 2/3/21 7:31 AM, Petr Mladek wrote: > > Also please make sure that lib/test_printf.c will work with > > the new option. > > As you suspected, it doesn't work: > > [ 206.966478] test_printf: loaded. > [ 206.966528] test_printf:

Re: [PATCH] perf tools: Resolve symbols against debug file first

On Thu, Jan 28, 2021 at 11:43:07AM +0100, Jiri Slaby wrote: > On 13. 01. 21, 11:46, Jiri Olsa wrote: > > On Wed, Jan 13, 2021 at 09:01:28AM +0100, Jiri Slaby wrote: > > > With LTO, there are symbols like these: > > > /usr/lib/debug/usr/lib64/libantlr4-runtime.so.4.8-4.8-1.4.x86_64.debug > > >

Re: [PATCH] fcntl: make F_GETOWN(EX) return 0 on dead owner task

On Wed, Feb 03, 2021 at 03:41:56PM +0300, Pavel Tikhomirov wrote: > Currently there is no way to differentiate the file with alive owner > from the file with dead owner but pid of the owner reused. That's why > CRIU can't actually know if it needs to restore file owner or not, > because if it

Re: [PATCH][RESEND] lib/vsprintf: make-printk-non-secret printks all addresses as unhashed

On Wed, 3 Feb 2021 12:35:07 -0800 Kees Cook wrote: > > With a big notice that all pointers of unhashed, I don't think we need to > > print it failed when we expect it to fail. > > > > If anything, skip the test and state: > > > > test_printf: hash test skipped because

[PATCH 0/3] vfio/type1: batch page pinning

Hi, The VFIO type1 driver is calling pin_user_pages_remote() once per 4k page, so let's do it once per 512 4k pages to bring VFIO in line with other drivers such as IB and vDPA. qemu guests with at least 2G memory start about 8% faster on a Xeon server, with more detailed results in the last

[PATCH 1/3] vfio/type1: change success value of vaddr_get_pfn()

vaddr_get_pfn() simply returns 0 on success. Have it report the number of pfns successfully gotten instead, whether from page pinning or follow_fault_pfn(), which will be used later when batching pinning. Change the last check in vfio_pin_pages_remote() for consistency with the other two.

Re: [PATCH 0/2] Allow reading process DMA buf stats from fdinfo

On Thu, Jan 28, 2021 at 1:24 PM Kalesh Singh wrote: > > Android captures per-process system memory state when certain low memory > events (e.g a foreground app kill) occur, to identify potential memory > hoggers. In order to measure how much memory a process actually consumes, > it is necessary

Re: [PATCH] bpf: Check for integer overflow when using roundup_pow_of_two()

Hello: This patch was applied to bpf/bpf.git (refs/heads/master): On Wed, 27 Jan 2021 06:36:53 + you wrote: > On 32-bit architecture, roundup_pow_of_two() can return 0 when the argument > has upper most bit set due to resulting 1UL << 32. Add a check for this > case. > > Fixes: d5a3b1f

[PATCH 06/12] platform-msi: Add device MSI infrastructure

From: Thomas Gleixner Add device specific MSI domain infrastructure for devices which have their own resource management and interrupt chip. These devices are not related to PCI and contrary to platform MSI they do not share a common resource and interrupt chip. They provide their own domain

[PATCH 08/12] genirq: Set auxiliary data for an interrupt

Introduce a new function pointer in the irq_chip structure(irq_set_auxdata) which is responsible for updating data which is stored in a shared register or data storage. For example, the idxd driver uses the auxiliary data API to enable/set and disable PASID field that is in the IMS entry

[PATCH 07/12] irqdomain/msi: Provide msi_alloc/free_store() callbacks

From: Thomas Gleixner For devices which don't have a standard storage for MSI messages like the upcoming IMS (Interrupt Message Store) it's required to allocate storage space before allocating interrupts and after freeing them. This could be achieved with the existing callbacks, but that would

[PATCH 05/12] genirq/msi: Provide and use msi_domain_set_default_info_flags()

From: Thomas Gleixner MSI interrupts have some common flags which should be set not only for PCI/MSI interrupts. Move the PCI/MSI flag setting into a common function so it can be reused. Signed-off-by: Thomas Gleixner Signed-off-by: Megha Dey --- drivers/pci/msi.c | 7 +--

Re: [PATCH 03/14] cxl/mem: Find device capabilities

On Wed, Feb 3, 2021 at 9:23 AM Ben Widawsky wrote: > > On 21-02-03 17:15:34, Christoph Hellwig wrote: > > On Tue, Feb 02, 2021 at 10:24:18AM -0800, Ben Widawsky wrote: > > > > > + /* Cap 4000h - CXL_CAP_CAP_ID_MEMDEV */ > > > > > + struct { > > > > > + void __iomem

Re: [PATCH 09/24] perf daemon: Add signalfd support

Em Sun, Jan 31, 2021 at 12:48:41AM +0100, Jiri Olsa escreveu: > Using signalfd fd for tracking SIGCHLD signals as > notification for perf session termination. > > This way we don't need to actively check for child > status, but we are notified if there's change. > > Suggested-by: Alexei Budankov

Re: [PATCH 02/14] cxl/mem: Map memory device registers

On Tue, Feb 02, 2021 at 10:31:51AM -0800, Ben Widawsky wrote: > > > + if (reg_type == CXL_REGLOC_RBI_MEMDEV) { > > > + rc = 0; > > > + cxlm = cxl_mem_create(pdev, reg_lo, reg_hi); > > > + if (!cxlm) > > > + rc =

Re: [PATCH 1/2] misc/pvpanic: split-up generic and platform dependent code

On 2/3/21 6:43 AM, Mihai Carabas wrote: > diff --git a/drivers/misc/pvpanic/Kconfig b/drivers/misc/pvpanic/Kconfig > new file mode 100644 > index ..12bb017 > --- /dev/null > +++ b/drivers/misc/pvpanic/Kconfig > @@ -0,0 +1,14 @@ > +config PVPANIC > + bool "pvpanic device support" > +

[PATCH v5 2/5] x86/signal: Introduce helpers to get the maximum signal frame size

Signal frames do not have a fixed format and can vary in size when a number of things change: support XSAVE features, 32 vs. 64-bit apps. Add the code to support a runtime method for userspace to dynamically discover how large a signal stack needs to be. Introduce a new variable, max_frame_size,

[PATCH v5 4/5] x86/signal: Detect and prevent an alternate signal stack overflow

The kernel pushes context on to the userspace stack to prepare for the user's signal handler. When the user has supplied an alternate signal stack, via sigaltstack(2), it is easy for the kernel to verify that the stack size is sufficient for the current hardware context. Check if writing the

Re: [PATCH v2 04/11] PCI: dwc: pcie-kirin: add support for Kirin 970 PCIe controller

Em Wed, 3 Feb 2021 08:34:21 -0600 Rob Herring escreveu: > On Wed, Feb 3, 2021 at 1:02 AM Mauro Carvalho Chehab > wrote: > > > > From: Manivannan Sadhasivam > > > > Add support for HiSilicon Kirin 970 (hi3670) SoC PCIe controller, based > > on Synopsys DesignWare PCIe controller IP. > > > >

Re: [PATCH v2 09/11] PCI: dwc: pcie-kirin: allow using multiple reset GPIOs

Em Wed, 3 Feb 2021 16:18:01 +0100 Krzysztof Wilczyński escreveu: > Hi Mauro, > > Thank you for working on this! > > > @@ -151,8 +152,10 @@ struct kirin_pcie { > > struct clk *phy_ref_clk; > > struct clk *pcie_aclk; > > struct clk *pcie_aux_clk; > > - int

[RESEND PATCH] nvmem: qcom-spmi-sdam: Fix uninitialized pdev pointer

"sdam->pdev" is uninitialized and it is used to print error logs. Fix it. Since device pointer can be used from sdam_config, use it directly thereby removing pdev pointer. Cc: sta...@vger.kernel.org Signed-off-by: Subbaraman Narayanamurthy --- drivers/nvmem/qcom-spmi-sdam.c | 7 +++ 1 file

Re: [PATCH 13/14] cxl/mem: Add limited Get Log command (0401h)

On Wed, Feb 03, 2021 at 09:16:10AM -0800, Ben Widawsky wrote: > On 21-02-02 15:57:03, Dan Williams wrote: > > On Tue, Feb 2, 2021 at 3:51 PM Ben Widawsky wrote: > > > > > > On 21-02-01 13:28:48, Konrad Rzeszutek Wilk wrote: > > > > On Fri, Jan 29, 2021 at 04:24:37PM -0800, Ben Widawsky wrote: > >

Re: [PATCH v2 00/28] Allow parallel MMU operations with TDP MMU

On 03/02/21 18:54, Sean Christopherson wrote: On Wed, Feb 03, 2021, Paolo Bonzini wrote: Looks good! I'll wait for a few days of reviews, I guess I know what I'm doing this afternoon :-) but I'd like to queue this for 5.12 and I plan to make it the default in 5.13 or 5.12-rc (depending on

Re: [RESEND PATCH v18 0/3] userspace MHI client interface driver

On Wed, 3 Feb 2021 19:28:28 +0100 Loic Poulain wrote: > On Wed, 3 Feb 2021 at 19:05, Jakub Kicinski wrote: > > On Wed, 03 Feb 2021 09:45:06 +0530 Manivannan Sadhasivam wrote: > > > The current patchset only supports QMI channel so I'd request you to > > > review the chardev node created for it.

Re: [PATCH 3/8] sched/fair: Tweak misfit-related capacity checks

On 03/02/21 15:15, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> @@ -113,6 +113,13 @@ int __weak arch_asym_cpu_priority(int cpu) >> */ >> #define fits_capacity(cap, max) ((cap) * 1280 < (max) * 1024) >> >> +/* >> + * The margin used when comparing CPU capacities. >>

Re: [PATCH 6/8] sched/fair: Filter out locally-unsolvable misfit imbalances

On 03/02/21 15:16, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> Consider the following (hypothetical) asymmetric CPU capacity topology, >> with some amount of capacity pressure (RT | DL | IRQ | thermal): >> >> DIE [ ] >> MC [][] >>0 1 2 3

Re: [PATCH 1/8] sched/fair: Clean up active balance nr_balance_failed trickery

>> @@ -9805,9 +9810,6 @@ static int load_balance(int this_cpu, struct rq >> *this_rq, >> active_load_balance_cpu_stop, busiest, >> >active_balance_work); >> } >> - >> -/* We've

Re: [PATCH 7/8] sched/fair: Attempt misfit active balance when migration_type != migrate_misfit

On 03/02/21 15:16, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> Giving group_misfit_task a higher group_classify() priority than >> group_imbalance doesn't seem like the right thing to do. Instead, make >> need_active_balance() return true for any migration_type when the >

Re: [PATCH 0/8] sched/fair: misfit task load-balance tweaks

Hi Qais, On 03/02/21 15:14, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> Hi folks, >> >> Here is this year's series of misfit changes. On the menu: >> >> o Patch 1 is an independent active balance cleanup >> o Patch 2 adds some more sched_asym_cpucapacity static branches

[PATCH v3 1/5] ACPI: AC: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() instances in ac.c with acpi_handle_debug() and acpi_handle_info() calls, respectively, which among other things causes the excessive log level of the messages previously printed via ACPI_EXCEPTION() to be increased.

[PATCH v3 0/5] ACPI: More cleanups related to printing messages

Hi All, On Tuesday, February 2, 2021 7:11:47 PM CET Rafael J. Wysocki wrote: > > On Monday, February 1, 2021 7:14:38 PM CET Rafael J. Wysocki wrote: > > > > This series is a continuation of the effort to drop ACPICA-specific debug > > code from non-ACPICA pieces of the ACPI subsystem and to

Re: [PATCH] x86: efi: avoid BUILD_BUG_ON() for non-constant p4d_index

On Wed, Jan 20, 2021 at 10:33:43AM +0100, Ard Biesheuvel wrote: > On Mon, 18 Jan 2021 at 22:42, Arvind Sankar wrote: > > > > On Mon, Jan 18, 2021 at 09:24:09PM +0100, Borislav Petkov wrote: > > > > > > As a matter of fact, it seems like the four assertions could be > > > > > > combined > > > > >

Re: [PATCH v2 25/28] KVM: x86/mmu: Allow zapping collapsible SPTEs to use MMU read lock

On Wed, Feb 3, 2021 at 3:34 AM Paolo Bonzini wrote: > > On 02/02/21 19:57, Ben Gardon wrote: > > @@ -1485,7 +1489,9 @@ void kvm_tdp_mmu_zap_collapsible_sptes(struct kvm > > *kvm, > > struct kvm_mmu_page *root; > > int root_as_id; > > > > - for_each_tdp_mmu_root_yield_safe(kvm,

Re: [PATCH] lib/vsprintf: make-printk-non-secret printks all addresses as unhashed

On Tue, Feb 02, 2021 at 02:51:00PM -0800, Linus Torvalds wrote: > On Tue, Feb 2, 2021 at 2:34 PM Steven Rostedt wrote: > > > > "I also suspect that everybody has already accepted that KASLR isn't > >really working locally anyway (due to all the hw leak models with > >cache and TLB

[PATCH] platform/x86: Move all dell drivers to their own subdirectory

A user without a Dell system doesn't need to pick any of these drivers. Suggested-by: Andy Shevchenko Signed-off-by: Mario Limonciello --- MAINTAINERS | 22 +-- drivers/platform/x86/Kconfig | 182 +-

  1   2   3   4   5   6   7   8   9   10   >