[PATCH, RFC 03/62] mm/ksm: Do not merge pages with different KeyIDs

KeyID indicates what key to use to encrypt and decrypt page's content. Depending on the implementation a cipher text may be tied to physical address of the page. It means that pages with an identical plain text would appear different if KSM would look at a cipher text. It effectively disables KSM f

[PATCH, RFC 04/62] mm/page_alloc: Unify alloc_hugepage_vma()

We don't need to have separate implementations of alloc_hugepage_vma() for NUMA and non-NUMA. Using variant based on alloc_pages_vma() we would cover both cases. This is preparation patch for allocation encrypted pages. alloc_pages_vma() will handle allocation of encrypted pages. With this change

Re: [PATCH] nvme-pci: mark expected switch fall-through

On 5/8/19 2:18 AM, Christoph Hellwig wrote: > Thanks, > > applied to nvme-5.2. > Great. :) Thanks, Christoph. -- Gustavo

[PATCH, RFC 14/62] x86/mm: Map zero pages into encrypted mappings correctly

Zero pages are never encrypted. Keep KeyID-0 for them. Signed-off-by: Kirill A. Shutemov --- arch/x86/include/asm/pgtable.h | 19 +++ 1 file changed, 19 insertions(+) diff --git a/arch/x86/include/asm/pgtable.h b/arch/x86/include/asm/pgtable.h index 50b3e2d963c9..59c3dd50b8d5 10

[PATCH, RFC 05/62] mm/page_alloc: Handle allocation for encrypted memory

For encrypted memory, we need to allocate pages for a specific encryption KeyID. There are two cases when we need to allocate a page for encryption: - Allocation for an encrypted VMA; - Allocation for migration of encrypted page; The first case can be covered within alloc_page_vma(). We know

[PATCH, RFC 01/62] mm: Do no merge VMAs with different encryption KeyIDs

VMAs with different KeyID do not mix together. Only VMAs with the same KeyID are compatible. Signed-off-by: Kirill A. Shutemov --- fs/userfaultfd.c | 7 --- include/linux/mm.h | 9 - mm/madvise.c | 2 +- mm/mempolicy.c | 3 ++- mm/mlock.c | 2 +- mm/mmap.c

Re: [PATCH 4/4] checkpatch: replace magic value for TAB size

On Wed, 2019-05-08 at 14:27 +0200, Antonio Borneo wrote: > The size of 8 characters used for both TAB and indentation is > embedded as magic value allover the checkpatch script, and this > makes the script less readable. > > Replace the magic value 8 with the perl variable "$tabsize". > From the c

[PATCH, RFC 02/62] mm: Add helpers to setup zero page mappings

When kernel setups an encrypted page mapping, encryption KeyID is derived from a VMA. KeyID is going to be part of vma->vm_page_prot and it will be propagated transparently to page table entry on mk_pte(). But there is an exception: zero page is never encrypted and its mapping must use KeyID-0, re

Re: [PATCH 2/6] x86: hv: hv_init.c: Replace alloc_page() with kmem_cache_alloc()

Maya Nakamura writes: > On Fri, Apr 12, 2019 at 09:52:47AM +0200, Vitaly Kuznetsov wrote: >> Maya Nakamura writes: >> >> > On Fri, Apr 05, 2019 at 01:31:02PM +0200, Vitaly Kuznetsov wrote: >> >> Maya Nakamura writes: >> >> >> >> > @@ -98,18 +99,20 @@ EXPORT_SYMBOL_GPL(hyperv_pcpu_input_arg);

Re: [PATCH] arm64: dts: qcom: qcs404: Add PSCI cpuidle support

On Wed, May 08, 2019 at 02:48:19AM +0530, Amit Kucheria wrote: > On Tue, May 7, 2019 at 1:01 AM Niklas Cassel wrote: > > > > Add device bindings for CPUs to suspend using PSCI as the enable-method. > > > > Signed-off-by: Niklas Cassel > > --- > > arch/arm64/boot/dts/qcom/qcs404.dtsi | 15 +++

Re: [PATCH] ftrace: enable trampoline when rec count decrement to one

Hi, Steven On 2019/5/6 3:34, Steven Rostedt wrote: Thanks for the patch. There was some race condition that prevented me from doing this in the first place, but unfortunately, I don't remember what that was :-/ I'll have to think about this before applying this patch. Maybe there isn't a rac

[PATCH] ACPICA: acpica: Fix possible NULL pointer dereference in acpi_ut_remove_reference

BUG: kernel NULL pointer dereference, address: #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 0 P4D 0 Oops: [#1 CPU: 0 PID: 7393 Comm: modprobe Not tainted 5.1.0+ #34 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS

Re: [PATCH 2/8] soc: tegra: fuse: Change to the correct __dma_request_channel() prototype

07.05.2019 9:09, Baolin Wang пишет: > Since we've introduced one device node parameter for __dma_request_channel(), > thus change to the correct function prototype. > > Signed-off-by: Baolin Wang > --- > drivers/soc/tegra/fuse/fuse-tegra20.c |2 +- > 1 file changed, 1 insertion(+), 1 deletio

Re: [PATCH 1/4] checkpatch: fix multiple const * types

On Wed, May 8, 2019 at 4:51 PM Joe Perches wrote: ... > It might be better to use a max match like {0,4} instead of * > > perl is pretty memory intensive at multiple unrestricted matches > of somewhat complex patterns. Agree! Will send a V2! Thanks for the review! Antonio

[PATCH v1 1/2] fs: make all new mount api fds cloexec by default

This makes all file descriptors returned from new syscalls of the new mount api cloexec by default. >From a userspace perspective it is rarely the case that fds are supposed to be inherited across exec. In fact, most of the time userspace either needs to remember to pass the _CLOEXEC flag along or

Re: [PATCH v2] usb: core: verify devicetree nodes for disabled interfaces

Marek Szyprowski writes: > Hi > > On 2019-05-08 13:46, Måns Rullgård wrote: >> Marek Szyprowski writes: >>> Commit 01fdf179f4b0 ("usb: core: skip interfaces disabled in devicetree") >>> add support for disabling given USB device interface by adding nodes to >>> the USB host controller device. Th

[PATCH v4 17/27] Documentation: x86: convert resctrl_ui.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/index.rst | 1 + .../x86/{resctrl_ui.txt => resctrl_ui.rst}

[PATCH v4 04/27] Documentation: x86: convert exception-tables.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- ...eption-tables.txt => exception-tables.rst} | 247 ++ Documentation/x86/index.rst

[PATCH v4 12/27] Documentation: x86: convert protection-keys.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/index.rst | 1 + ...rotection-keys.txt => protection-keys.rst}

[PATCH v4 11/27] Documentation: x86: convert pat.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Cc: Mauro Carvalho Chehab --- Documentation/x86/index.rst | 1 + Documentation/x86/pat.rst | 242

[PATCH v4 27/27] Documentation: x86: convert x86_64/machinecheck to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/x86_64/index.rst | 1 + .../x86/x86_64/{machinecheck => machin

Re: [RFC PATCH v6 4/6] tracing/probe: Support user-space dereference

On Wed, 8 May 2019 13:11:43 +0900 Masami Hiramatsu wrote: > On Mon, 6 May 2019 11:52:26 -0400 > Steven Rostedt wrote: > > > On Mon, 18 Mar 2019 15:43:52 +0900 > > Masami Hiramatsu wrote: > > > > > +.. _user_mem_access: > > > +User Memory Access > > > +-- > > > +Kprobe events

Re: [PATCH v2] netfilter: xt_owner: Add supplementary groups option

On Wed, 2019-05-08 at 07:58 -0700, Eric Dumazet wrote: > > On 5/8/19 10:12 AM, Lukasz Pawelczyk wrote: > > The XT_SUPPL_GROUPS flag causes GIDs specified with XT_OWNER_GID to > > be also checked in the supplementary groups of a process. > > > > Signed-off-by: Lukasz Pawelczyk > > --- > > includ

[PATCH v1 2/2] fsopen: use square brackets around "fscontext"

Make the name of the anon inode fd "[fscontext]" instead of "fscontext". This is minor but most core-kernel anon inode fds carry square brackets around their name (cf. [1]). For the sake of consistency lets do the same for the mount api: [eventfd] [eventpoll] [fanotify] [fscontext] [io_uring] [pid

Re: ptrace warning due to "cgroup: get rid of cgroup_freezer_frozen_exit()"

On 05/07, Roman Gushchin wrote: > > --- a/kernel/signal.c > +++ b/kernel/signal.c > @@ -2484,9 +2484,6 @@ bool get_signal(struct ksignal *ksig) > sigdelset(¤t->pending.signal, SIGKILL); > recalc_sigpending(); > current->jobctl &= ~JOBCTL_TRAP_FREEZE;

[PATCH v4 21/27] Documentation: x86: convert x86_64/boot-options.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/index.rst | 1 + Documentation/x86/x86_64/boot-options.rst | 335

[PATCH v4 18/27] Documentation: x86: convert orc-unwinder.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/index.rst | 1 + .../{orc-unwinder.txt => orc-unwinder.rst}

[PATCH v4 16/27] Documentation: x86: convert microcode.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/index.rst | 1 + .../x86/{microcode.txt => microcode.rst}

[PATCH v4 22/27] Documentation: x86: convert x86_64/uefi.txt to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/x86_64/index.rst| 1 + .../x86/x86_64/{uefi.txt => uefi.rst}

[PATCH v4 26/27] Documentation: x86: convert x86_64/cpu-hotplug-spec to reST

This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- .../x86/x86_64/{cpu-hotplug-spec => cpu-hotplug-spec.rst}| 5 - Documentation/x86/x86_64/in

Re: [PATCH 4/4] checkpatch: replace magic value for TAB size

On Wed, May 8, 2019 at 4:52 PM Joe Perches wrote: ... > > In these cases the script will be probably modified and adapted, > > so there is no need (at least for the moment) to expose this > > setting on the script's command line. > > Disagree. Probably getter to add a --tabsize= option now. Ok,

Re: [PATCH 2/4] x86/kprobes: Fix frame pointer annotations

On Wed, May 08, 2019 at 07:42:48AM -0500, Josh Poimboeuf wrote: > On Wed, May 08, 2019 at 02:04:16PM +0200, Peter Zijlstra wrote: > > Do the x86_64 variants also want some ORC annotation? > > Maybe so. Though it looks like regs->ip isn't saved. The saved > registers might need to be tweaked. I

Re: [PATCH v2] netfilter: xt_owner: Add supplementary groups option

On 5/8/19 11:25 AM, Lukasz Pawelczyk wrote: > On Wed, 2019-05-08 at 07:58 -0700, Eric Dumazet wrote: >> >> On 5/8/19 10:12 AM, Lukasz Pawelczyk wrote: >>> The XT_SUPPL_GROUPS flag causes GIDs specified with XT_OWNER_GID to >>> be also checked in the supplementary groups of a process. >>> >>> Sig

Re: [PATCH v2 3/7] devcoredump: allow to create several coredump files in one device

2019年5月8日(水) 2:35 Heitke, Kenneth : > > > > On 5/7/2019 10:58 AM, Akinobu Mita wrote: > > @@ -292,6 +309,12 @@ void dev_coredumpm(struct device *dev, struct module > > *owner, > > if (device_add(&devcd->devcd_dev)) > > goto put_device; > > > > + for (i = 0; i < devcd->num_f

Re: [PATCH v2 4/7] nvme.h: add telemetry log page definisions

2019年5月8日(水) 2:28 Heitke, Kenneth : > > > > On 5/7/2019 10:58 AM, Akinobu Mita wrote: > > Copy telemetry log page definisions from nvme-cli. > > > > Cc: Johannes Berg > > Cc: Keith Busch > > Cc: Jens Axboe > > Cc: Christoph Hellwig > > Cc: Sagi Grimberg > > Cc: Minwoo Im > > Signed-off-by: Ak

Re: [RFC PATCH v2 11/17] sched: Basic tracking of matching tasks

On Fri, May 3, 2019 at 8:06 AM Tim Chen wrote: > > On 5/1/19 4:27 PM, Tim Chen wrote: > > On 4/28/19 11:15 PM, Aaron Lu wrote: > >> On Tue, Apr 23, 2019 at 04:18:16PM +, Vineeth Remanan Pillai wrote: > >>> +/* > >>> + * Find left-most (aka, highest priority) task matching @cookie. > >>> + */ >

Re: [PATCH] of: Add dummy for of_node_is_root if not CONFIG_OF

Hi, On Tue, May 7, 2019 at 3:17 PM Frank Rowand wrote: > > On 5/7/19 10:59 AM, Doug Anderson wrote: > > Hi, > > > > > > On Tue, May 7, 2019 at 10:52 AM Frank Rowand wrote: > >> > >> On 5/6/19 9:48 PM, Douglas Anderson wrote: > >>> We'll add a dummy to just return false. > >> > >> A more complete

Re: [PATCH 3/3] reset: Add reset controller support for BM1880 SoC

Hi Philipp, On Fri, May 03, 2019 at 04:55:21PM +0200, Philipp Zabel wrote: > Hi Manivannan, > > thank you for the patch. A few issues below: > > On Thu, 2019-04-25 at 18:25 +0530, Manivannan Sadhasivam wrote: > > Add reset controller support for Bitmain BM1880 SoC reusing the > > reset-simple dr

Re: [RESEND PATCH] gnss: get serial speed from subdrivers

On Wed, May 08, 2019 at 03:39:48PM +0200, Loys Ollivier wrote: > The default serial speed was hardcoded in the code. > Rename current-speed to default-speed. > Add a function parameter that lets the subdrivers specify their > default speed. > If not specified fallback to the device-tree default-spe

Re: [PATCH v2 4/7] nvme.h: add telemetry log page definisions

2019年5月8日(水) 2:53 Heitke, Kenneth : > > > > On 5/7/2019 10:58 AM, Akinobu Mita wrote: > > Copy telemetry log page definisions from nvme-cli. > > > > Cc: Johannes Berg > > Cc: Keith Busch > > Cc: Jens Axboe > > Cc: Christoph Hellwig > > Cc: Sagi Grimberg > > Cc: Minwoo Im > > Signed-off-by: Ak

Re: [PATCH v8 1/4] s390: ap: kvm: add PQAP interception for AQIC

On 5/2/19 1:34 PM, Pierre Morel wrote: We prepare the interception of the PQAP/AQIC instruction for the case the AQIC facility is enabled in the guest. First of all we do not want to change existing behavior when intercepting AP instructions without the SIE allowing the guest to use AP instructi

Re: [PATCH] packet: Fix error path in packet_init

On Wed, May 8, 2019 at 8:33 AM YueHaibing wrote: > > kernel BUG at lib/list_debug.c:47! > invalid opcode: [#1 > CPU: 0 PID: 11195 Comm: rmmod Tainted: GW 5.1.0+ #33 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS > rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.

[PATCH v2] pstore/ram: Improve backward compatibility with older Chromebooks

When you try to run an upstream kernel on an old ARM-based Chromebook you'll find that console-ramoops doesn't work. Old ARM-based Chromebooks, before ("ramoops: support upstream {console,pmsg,ftrace}-size properties") used to create a "ramoops" node at the top level t

Re: [PATCH v2 6/7] nvme-pci: add device coredump support

2019年5月8日(水) 6:28 Keith Busch : > > On Tue, May 07, 2019 at 02:31:41PM -0600, Heitke, Kenneth wrote: > > On 5/7/2019 10:58 AM, Akinobu Mita wrote: > > > + > > > +static int nvme_get_telemetry_log_blocks(struct nvme_ctrl *ctrl, void > > > *buf, > > > +size_t byte

Re: [PATCH v2 6/7] nvme-pci: add device coredump support

2019年5月8日(水) 9:25 Minwoo Im : > > > This is a bit of a mine field. The shutdown_lock is held when reclaiming > > requests that didn't see a response. If you're holding it here and your > > telemetry log page times out, we're going to deadlock. And since the > > controller is probably in a buggered

Re: [PATCH 0/3] x86_64/ftrace: Emulate calls from int3 when patching functions

On Wed, 8 May 2019 13:30:22 +0900 Masami Hiramatsu wrote: > > To solve this, an int3_emulate_call() is created for x86_64 to allow > > ftrace on x86_64 to emulate the call to ftrace_regs_caller() which will > > make sure all the registered handlers to that function are still called. > > And this

[PATCH] vfio: add myself as reviewer

I'm trying to look at vfio patches, and it's easier if I'm cc:ed. Signed-off-by: Cornelia Huck --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 920a0a1545b7..9c0cd7a49309 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -16454,6 +16454,7 @@ F:

Re: [PATCH] arm64: add support for rng-seed

On Wed, May 8, 2019 at 10:06 AM Hsin-Yi Wang wrote: > > On Wed, May 8, 2019 at 10:04 PM Rob Herring wrote: > > > > On Tue, May 7, 2019 at 11:08 PM Hsin-Yi Wang wrote: > > > > > > On Wed, May 8, 2019 at 3:47 AM Rob Herring wrote: > > > > > > > > +boot-architecture list as there was some discussi

Re: [PATCH v8 1/4] s390: ap: kvm: add PQAP interception for AQIC

On 08/05/2019 17:48, Tony Krowiak wrote: On 5/2/19 1:34 PM, Pierre Morel wrote: We prepare the interception of the PQAP/AQIC instruction for the case the AQIC facility is enabled in the guest. First of all we do not want to change existing behavior when intercepting AP instructions without the

Re: [PATCH v2] Documentation/trace: Add clarification how histogram onmatch works

Jon, Can you take this patch in your tree? Tom, Thanks for the review! -- Steve On Wed, 08 May 2019 08:15:26 -0500 Tom Zanussi wrote: > Hi Steve, > > On Tue, 2019-05-07 at 20:11 -0400, Steven Rostedt wrote: > > Tom, > > > > Can you review this patch. > > > > Sure. > > > Jon, > > >

Re: [PATCH v2] Documentation/trace: Add clarification how histogram onmatch works

On Wed, 8 May 2019 12:18:54 -0400 Steven Rostedt wrote: > Jon, > > Can you take this patch in your tree? Will do. jon

Re: [PATCH v2 1/1] usb: typec: tcpci: Clear the fault status register

On Wed, May 08, 2019 at 07:48:43AM -0600, Angus Ainslie wrote: > Hi Guenter > > On 2019-05-07 23:18, Guenter Roeck wrote: > >On 5/7/19 7:49 PM, Angus Ainslie wrote: > >>On 2019-05-07 20:03, Guenter Roeck wrote: > >>>On 5/7/19 5:27 PM, Angus Ainslie (Purism) wrote: > If the fault status registe

Re: [PATCH 1/8] soundwire: intel: filter SoundWire controller device search

+ /* +* On some Intel platforms, multiple children of the HDAS +* device can be found, but only one of them is the SoundWire +* controller. The SNDW device is always exposed with +* Name(_ADR, 0x4000) so filter accordingly +*/ + if (adr !=

[PATCH] selftests: fix install target to use default install path

Install target fails when INSTALL_PATH is undefined. Fix install target to use "output_dir/install as the default install location. "output_dir" is either the root of selftests directory under kernel source tree or output directory specified by O= or KBUILD_OUTPUT. e.g: make -C tools/testing/selft

Re: [PATCH] watchdog: sama5d4: fix WDD value to be always set to max

On Wed, May 08, 2019 at 02:15:03PM +, eugen.hris...@microchip.com wrote: > From: Eugen Hristev > > WDD value must be always set to max (0xFFF) otherwise the hardware > block will reset the board on the first ping of the watchdog. > Not sure why setting WDD to the same value as WDV would do t

Re: [PATCH 1/8] soundwire: intel: filter SoundWire controller device search

On 08-05-19, 11:20, Pierre-Louis Bossart wrote: > > > > > > + /* > > > > > + * On some Intel platforms, multiple children of the HDAS > > > > > + * device can be found, but only one of them is the SoundWire > > > > > + * controller. The SNDW device is always exposed with > > > >

Re: [RFC][PATCH 1/2] x86: Allow breakpoints to emulate call functions

On Tue, 7 May 2019 21:50:52 -0700 Linus Torvalds wrote: > > It's been a bane of mine for some time. > > Guys, I have basically a one-liner patch for your hangups. > > It's called "rename 'sp' to 'user_sp' on x86-32". > > Then we make the 'sp' field on x86-64 be a union, so that you can call

Re: [PATCH 1/2] coresight: Do not call smp_processor_id() from preemptible

Hi Suzuki, On Fri, 3 May 2019 at 10:04, Suzuki K Poulose wrote: > > Instead of using smp_processor_id() to figure out the node, > use the numa_node_id() for the current CPU node to avoid > splats like : > > BUG: using smp_processor_id() in preemptible [] code: perf/1743 > caller is allo

Re: [PATCH] fs,xfs: fix missed wakeup on l_flush_wait

On 7 May 2019, at 17:22, Dave Chinner wrote: > On Tue, May 07, 2019 at 01:05:28PM -0400, Rik van Riel wrote: >> The code in xlog_wait uses the spinlock to make adding the task to >> the wait queue, and setting the task state to UNINTERRUPTIBLE atomic >> with respect to the waker. >> >> Doing the w

[PATCH v2 0/2] mmc: sdhci-iproc: fixes for HS50 data hold time

This patch series fixes data hold timing issues for various sdhci-iproc ip blocks that do not meet the HS50 data hold time. NO_HISPD bit is set in quirks. Changes from v1: - Change fixes tag to Cc: sta...@vger.kernel.org to specify version to backport to Trac Hoang (2): mmc: sdhci-iproc: cyg

[PATCH v2 1/2] mmc: sdhci-iproc: cygnus: Set NO_HISPD bit to fix HS50 data hold time problem

From: Trac Hoang The iproc host eMMC/SD controller hold time does not meet the specification in the HS50 mode. This problem can be mitigated by disabling the HISPD bit; thus forcing the controller output data to be driven on the falling clock edges rather than the rising clock edges. This change

[PATCH v2 2/2] mmc: sdhci-iproc: Set NO_HISPD bit to fix HS50 data hold time problem

From: Trac Hoang The iproc host eMMC/SD controller hold time does not meet the specification in the HS50 mode. This problem can be mitigated by disabling the HISPD bit; thus forcing the controller output data to be driven on the falling clock edges rather than the rising clock edges. Cc: sta...

Re: [alsa-devel] [RFC PATCH 1/7] soundwire: Add sysfs support for master(s)

On 5/8/19 4:16 AM, Greg KH wrote: On Wed, May 08, 2019 at 01:16:06PM +0530, Vinod Koul wrote: On 07-05-19, 17:49, Pierre-Louis Bossart wrote: The model here is that Master device is PCI or Platform device and then creates a bus instance which has soundwire slave devices. So for any attrib

Re: [PATCH 1/2] coresight: Do not call smp_processor_id() from preemptible

On 08/05/2019 17:39, Mathieu Poirier wrote: Hi Suzuki, On Fri, 3 May 2019 at 10:04, Suzuki K Poulose wrote: Instead of using smp_processor_id() to figure out the node, use the numa_node_id() for the current CPU node to avoid splats like : BUG: using smp_processor_id() in preemptible [00

Re: [PATCH v2 1/2] ASoC: SOF: Add Comet Lake PCI IDs

On Tue, May 7, 2019 at 3:14 PM Pierre-Louis Bossart wrote: > > Minor nit-picks below. The Kconfig would work but select CANNONLAKE even > if you don't want it. > > > > > +config SND_SOC_SOF_COMETLAKE_LP > > + tristate > > + select SND_SOC_SOF_CANNONLAKE > > This should be > select SND_SOF_

Re: [PATCH] openvswitch: Replace removed NF_NAT_NEEDED with IS_ENABLED(CONFIG_NF_NAT)

From: Geert Uytterhoeven Date: Wed, 8 May 2019 08:52:32 +0200 > Commit 4806e975729f99c7 ("netfilter: replace NF_NAT_NEEDED with > IS_ENABLED(CONFIG_NF_NAT)") removed CONFIG_NF_NAT_NEEDED, but a new user > popped up afterwards. > > Fixes: fec9c271b8f1bde1 ("openvswitch: load and reference the NA

Re: [PATCH] net: dsa: lantiq: fix spelling mistake "brigde" -> "bridge"

From: Colin King Date: Wed, 8 May 2019 11:22:09 +0100 > From: Colin Ian King > > There are several spelling mistakes in dev_err messages. Fix these. > > Signed-off-by: Colin Ian King Applied.

[PATCH] platform/x86: acer-wmi: Mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. This patch fixes the following warnings: drivers/platform/x86/acer-wmi.c: In function ‘set_u32’: drivers/platform/x86/acer-wmi.c:1378:33: warning: this statement may fall through [-Wimpli

Re: [alsa-devel] [RFC PATCH 2/7] soundwire: add Slave sysfs support

Vinod, the question was not for dp0 and dpN, it's fine to have subdirectories there, but rather why we need separate devices for the master and slave properties. Slave does not have a separate device. IIRC the properties for Slave are in /sys/bus/soundwire/device//... I am not sure this is

Re: [PATCH v2 2/2] ASoC: Intel: Skylake: Add Cometlake PCI IDs

On Tue, May 7, 2019 at 3:31 PM Pierre-Louis Bossart wrote: > > On 5/7/19 4:53 PM, Evan Green wrote: > > Add PCI IDs for Intel CometLake platforms, which from a software > > point of view are extremely similar to Cannonlake platforms. > > Humm, I have mixed feelings here. > > Yes the hardware is ne

[PATCH v2 0/4] Add reset controller support for BM1880 SoC

Hello, This patchset adds reset controller support for Bitmain BM1880 SoC. BM1880 SoC has two reset controllers each controlling reset lines of different peripherals. And the reset-simple driver has been reused here. This patchset has been tested on 96Boards Sophon Edge board. Thanks, Mani Chan

Re: [PATCH] ftrace: enable trampoline when rec count decrement to one

On Wed, 8 May 2019 23:02:33 +0800 "chengjian (D)" wrote: > function tracer uses ftrace_caller() and livepatch uses > ftrace_regs_caller(). > > I can modify my testcase to trigger this race condition. > > > #enable livepatch > insmod klp_unshare_files.ko > cat /sys/kernel/debug/tracing/enabled

[PATCH v2 1/4] dt-bindings: reset: Add devicetree binding for BM1880 reset controller

Add devicetree binding for Bitmain BM1880 SoC reset controller. This SoC has two reset controllers each controlling reset lines of different peripherals. Signed-off-by: Manivannan Sadhasivam Reviewed-by: Rob Herring --- .../bindings/reset/bitmain,bm1880-reset.txt | 18 +++ .../dt-bindings/re

Re: [PATCH v2] netfilter: xt_owner: Add supplementary groups option

On 5/8/19 11:56 AM, Lukasz Pawelczyk wrote: > On Wed, 2019-05-08 at 08:41 -0700, Eric Dumazet wrote: >> >> On 5/8/19 11:25 AM, Lukasz Pawelczyk wrote: >>> On Wed, 2019-05-08 at 07:58 -0700, Eric Dumazet wrote: On 5/8/19 10:12 AM, Lukasz Pawelczyk wrote: > The XT_SUPPL_GROUPS flag causes

[PATCH v2 2/4] arm64: dts: bitmain: Add reset controller support for BM1880 SoC

Add reset controller support for Bitmain BM1880 SoC. This SoC has two reset controllers, each controlling reset lines of different peripherals. This commit also adds reset support to UART peripherals. Signed-off-by: Manivannan Sadhasivam Reviewed-by: Philipp Zabel --- arch/arm64/boot/dts/bitmai

[PATCH v2 3/4] reset: Add reset controller support for BM1880 SoC

Add reset controller support for Bitmain BM1880 SoC reusing the reset-simple driver. Signed-off-by: Manivannan Sadhasivam Reviewed-by: Philipp Zabel --- drivers/reset/Kconfig| 3 ++- drivers/reset/reset-simple.c | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/drive

[PATCH v2 4/4] reset: Switch to SPDX license identifier for reset-simple

Switch to SPDX license identifier for reset-simple driver. Cc: Maxime Ripard Signed-off-by: Manivannan Sadhasivam --- drivers/reset/reset-simple.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/reset/reset-simple.c b/drivers/reset/reset-simple.c index 5e8c86470

Re: [PATCH] mm: filemap: correct the comment about VM_FAULT_RETRY

Ping. Josef, any comment on this one? Thanks, Yang On 4/25/19 4:22 PM, Yang Shi wrote: The commit 6b4c9f446981 ("filemap: drop the mmap_sem for all blocking operations") changed when mmap_sem is dropped during filemap page fault and when returning VM_FAULT_RETRY. Correct the comment to r

Re: BUG: soft lockup in kvm_vm_ioctl

From: Dmitry Vyukov Date: Wed, May 8, 2019 at 1:25 PM To: Eric Biggers Cc: syzbot, KVM list, , David Miller, Artem Bityutskiy, , Josh Poimboeuf, LKML, , Andy Lutomirski, Ingo Molnar, Peter Zijlstra, Richard Weinberger, Rik van Riel, Steven Rostedt, syzkaller-bugs, Thomas Gleixner > From: Eric Big

Re: [PATCH, RFC 52/62] x86/mm: introduce common code for mem encryption

On Wed, May 08, 2019 at 05:44:12PM +0300, Kirill A. Shutemov wrote: > +EXPORT_SYMBOL_GPL(__mem_encrypt_dma_set); > + > +phys_addr_t __mem_encrypt_dma_clear(phys_addr_t paddr) > +{ > + if (sme_active()) > + return __sme_clr(paddr); > + > + return paddr & ~mktme_keyid_mask; > +} >

Re: [PATCH 02/16] treewide: rename match_string() -> __match_string()

(Trimming the lists but keeping lkml) Quoting Alexandru Ardelean (2019-05-08 04:28:28) > This change does a rename of match_string() -> __match_string(). > > There are a few parts to the intention here (with this change): > 1. Align with sysfs_match_string()/__sysfs_match_string() > 2. This helps

Re: [PATCH v2 1/2] ASoC: SOF: Add Comet Lake PCI IDs

On 5/8/19 11:42 AM, Evan Green wrote: On Tue, May 7, 2019 at 3:14 PM Pierre-Louis Bossart wrote: Minor nit-picks below. The Kconfig would work but select CANNONLAKE even if you don't want it. +config SND_SOC_SOF_COMETLAKE_LP + tristate + select SND_SOC_SOF_CANNONLAKE This shoul

[PATCH v4 1/2] firmware: arm_scmi: Fetch and store sensor scale

In preparation for dealing with scales within the SCMI HWMON driver, fetch and store the sensor unit scale into the scmi_sensor_info structure. In order to simplify computations for upper layer, take care of sign extending the scale to a full 8-bit signed value. Signed-off-by: Florian Fainelli --

[PATCH v7 13/18] x86/fsgsbase/64: Document GSBASE handling in the paranoid path

On a FSGSBASE system, the way to handle GSBASE in the paranoid path will be different from the existing SWAPGS-based. Document the reason and what is done by the (new) GSBASE handling. In non-paranoid path, it will keep working exactly like it does today. Signed-off-by: Chang S. Bae Cc: Andy Luto

[PATCH v7 04/18] kbuild: Raise the minimum required binutils version to 2.21

It helps to use some new instructions directly in assembly code. Suggested-by: Andi Kleen Signed-off-by: Chang S. Bae Reviewed-by: Andi Kleen Acked-by: Andrew Morton Cc: Andy Lutomirski Cc: Linux Torvalds Cc: Thomas Gleixner Cc: Ingo Molnar Cc: H. Peter Anvin --- Documentation/process/ch

[PATCH v7 18/18] x86/fsgsbase/64: Add documentation for FSGSBASE

From: Andi Kleen v2: Minor updates to documentation requested in review. v3: Update for new gcc and various improvements. v4: Address the typos pointed by Randy Dunlap Signed-off-by: Andi Kleen Signed-off-by: Chang S. Bae Cc: Randy Dunlap Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Andy Lutomir

[PATCH v7 08/18] x86/fsgsbase/64: When copying a thread, use the FSGSBASE instructions

Copy real FS/GSBASE values instead of approximation when FSGSBASE is enabled. Suggested-by: Andy Lutomirski Signed-off-by: Chang S. Bae Cc: Thomas Gleixner Cc: Ingo Molnar Cc: H. Peter Anvin Cc: Andi Kleen --- arch/x86/kernel/process_64.c | 15 +-- 1 file changed, 9 insertions(+

Re: [PATCH 4/4] checkpatch: replace magic value for TAB size

On Wed, 2019-05-08 at 17:32 +0200, Antonio Borneo wrote: > On Wed, May 8, 2019 at 4:52 PM Joe Perches wrote: > ... > > > In these cases the script will be probably modified and adapted, > > > so there is no need (at least for the moment) to expose this > > > setting on the script's command line. >

[PATCH v7 07/18] x86/fsgsbase/64: Preserve FS/GS state in __switch_to() if FSGSBASE is on

From: Andy Lutomirski With the new FSGSBASE instructions, we can efficiently read and write the FSBASE and GSBASE in __switch_to(). Use that capability to preserve the full state. This will enable user code to do whatever it wants with the new instructions without any kernel-induced gotchas. (

[PATCH] x86/kvm/pmu: Set AMD's virt PMU version to 1

From: Borislav Petkov After commit: 672ff6cff80c ("KVM: x86: Raise #GP when guest vCPU do not support PMU") my AMD guests started #GPing like this: general protection fault: [#1] PREEMPT SMP CPU: 1 PID: 4355 Comm: bash Not tainted 5.1.0-rc6+ #3 Hardware name: QEMU Standard PC (i44

[PATCH v7 05/18] x86/fsgsbase/64: Add intrinsics for FSGSBASE instructions

From: Andi Kleen Add C intrinsics and assembler macros for the new FSBASE and GSBASE instructions. Very straight forward. Used in followon patches. [ luto: Rename the variables from FS and GS to FSBASE and GSBASE and make safe to include on 32-bit kernels. ] Signed-off-by: Andi Kleen Signe

[PATCH v7 11/18] x86/fsgsbase/64: Introduce the FIND_PERCPU_BASE macro

On the paranoid entry, by far, SWAPGS is needed when entering from user space. A positive GSBASE means it is a user value and a negative GSBASE means it is a kernel value. When FSGSBASE is enabled, however, user space can write arbitrary values to GSBASE, so it will break the existing logic to diff

[PATCH v7 16/18] x86/fsgsbase/64: Enable FSGSBASE by default and add a chicken bit

From: Andy Lutomirski Now that FSGSBASE is fully supported, remove unsafe_fsgsbase, enable FSGSBASE by default, and add nofsgsbase to disable it. Signed-off-by: Andy Lutomirski Signed-off-by: Chang S. Bae Reviewed-by: Andi Kleen Cc: Thomas Gleixner Cc: Ingo Molnar Cc: H. Peter Anvin --- D

[PATCH v7 14/18] selftests/x86/fsgsbase: Test WRGSBASE

From: Andy Lutomirski This validates that GS and GSBASE are independently preserved across context switches. [ chang: Use FSGSBASE instructions directly instead of .byte ] Signed-off-by: Andy Lutomirski Reviewed-by: Andi Kleen Signed-off-by: Chang S. Bae Cc: Thomas Gleixner Cc: Ingo Molnar

[PATCH v7 15/18] selftests/x86/fsgsbase: Test ptracer-induced GSBASE write with FSGSBASE

This validates that GS and GSBASE are independently preserved in ptracer commands. Suggested-by: Andy Lutomirski Signed-off-by: Chang S. Bae Cc: Thomas Gleixner Cc: Ingo Molnar Cc: H. Peter Anvin Cc: Andi Kleen --- tools/testing/selftests/x86/fsgsbase.c | 11 +-- 1 file changed, 9 i

[PATCH v7 12/18] x86/fsgsbase/64: GSBASE handling with FSGSBASE in the paranoid path

Without FSGSBASE, user space cannot change GSBASE other than through the PRCTL. On the transition from user space to kernel, SWAPGS is used to swap the content of GSBASE and MSR_KERNEL_GS_BASE. However, SWAPGS should only be used if entering from user mode to kernel mode. Particularly in an super-a

[PATCH v7 17/18] x86/elf: Enumerate kernel FSGSBASE capability in AT_HWCAP2

From: Andi Kleen The kernel needs to explicitly enable FSGSBASE. So, the application needs to know if it can safely use these instructions. Just looking at the CPUID bit is not enough because it may be running in a kernel that does not enable the instructions. One way for the application would b

[PATCH v7 09/18] x86/entry/64: Add the READ_MSR_GSBASE macro

Factor out the RDMSR-based GSBASE read into a new macro. Signed-off-by: Chang S. Bae Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Andy Lutomirski Cc: H. Peter Anvin Cc: Andi Kleen Cc: Dave Hansen --- arch/x86/entry/calling.h | 9 + arch/x86/entry/entry_64.S | 12 2 files

[PATCH v7 10/18] x86/entry/64: Switch CR3 before SWAPGS on the paranoid entry

When FSGSBASE is enabled, GSBASE handling on the paranoid entry will need to retrieve the kernel GSBASE. Thus, the kernel page table should be in. As a preparation, the CR3 switching is moved to happen at first, before the SWAPGS. Current GSBASE switching mechanism is possible without the kernel p

[PATCH v7 01/18] x86/fsgsbase/64: Fix ARCH_SET_FS/GS behaviors for a remote task

When a ptracer writes to a ptracee's FS/GSBASE with a different value, the selector is also cleared. This behavior is not straightforward. The change will make the behavior simple and sensible, as it will (only) update the base when requested. Also, the condition check for comparing the base is re

<    1   2   3   4   5   6   7   8   >