[PATCH 10/12] btrfs: zstd use the passed through level instead of default

Zstd currently only supports the default level of compression. This patch switches to using the level passed in for btrfs zstd configuration. Zstd workspaces now keep track of the requested level as this can differ from the size of the workspace. Signed-off-by: Dennis Zhou Reviewed-by: Nikolay B

[PATCH 06/12] btrfs: add compression interface in (get/put)_workspace()

There are two levels of workspace management. First, alloc()/free() which are responsible for actually creating and destroy workspaces. Second, at a higher level, get()/put() which is the compression code asking for a workspace from a workspace_manager. The compression code shouldn't really care h

[RFC][QEMU PATCH] KVM: Support for guest free page hinting

This patch enables QEMU to recieve free page address from the guest and to use madvise to make them available to the host. --- hw/virtio/trace-events| 1 + hw/virtio/virtio-balloon.c| 82 +++ hw/virtio/virtio.c

[RFC][Patch v8 1/7] KVM: Support for guest free page hinting

This patch includes the following: 1. Basic skeleton for the support 2. Enablement of x86 platform to use the same Signed-off-by: Nitesh Narayan Lal --- arch/x86/Kbuild | 2 +- arch/x86/kvm/Kconfig | 8 arch/x86/kvm/Makefile| 2 ++ include/linux/gfp.h

[PATCH 11/12] btrfs: make zstd memory requirements monotonic

It is possible based on the level configurations that a higher level workspace uses less memory than a lower level workspace. In order to reuse workspaces, this must be made a monotonic relationship. This precomputes the required memory for each level and enforces the monotonicity between level and

[PATCH 08/12] btrfs: plumb level through the compression interface

Zlib compression supports multiple levels, but doesn't require changing in how a workspace itself is created and managed. Zstd introduces a different memory requirement such that higher levels of compression require more memory. This requires changes in how the alloc()/get() methods work for zstd.

[PATCH 07/12] btrfs: move to fn pointers for get/put workspaces

The previous patch added generic helpers for get_workspace() and put_workspace(). Now, we can migrate ownership of the workspace_manager to be in the compression type code as the compression code itself doesn't care beyond being able to get a workspace. The init/cleanup and get/put methods are abst

[PATCH 09/12] btrfs: change set_level() to bound the level passed in

Currently, the only user of set_level() is zlib which sets an internal workspace parameter. As level is now plumbed into get_workspace(), this can be handled there rather than separately. This repurposes set_level() to bound the level passed in so it can be used when setting the mounts compression

[PATCH 04/12] btrfs: unify compression ops with workspace_manager

Make the workspace_manager own the interface operations rather than managing index-paired arrays for the workspace_manager and compression operations. Signed-off-by: Dennis Zhou Reviewed-by: Nikolay Borisov Reviewed-by: Josef Bacik --- fs/btrfs/compression.c | 11 +++ 1 file changed, 7

[PATCH 01/12] btrfs: add helpers for compression type and level

It is very easy to miss places that rely on a certain bitshifting for decyphering the type_level overloading. Add helpers to do this instead. Signed-off-by: Dennis Zhou Reviewed-by: Nikolay Borisov Reviewed-by: Josef Bacik Cc: Omar Sandoval --- fs/btrfs/compression.c | 2 +- fs/btrfs/compres

[PATCH 05/12] btrfs: add helper methods for workspace manager init and cleanup

Workspace manager init and cleanup code is open coded inside a for loop over the compression types. This forces each compression type to rely on the same workspace manager implementation. This patch creates helper methods that will be the generic implementation for btrfs workspace management. Sign

[PATCH 02/12] btrfs: rename workspaces_list to workspace_manager

This is in preparation for zstd compression levels. As each level will require different sized workspaces, workspaces_list is no longer a really fitting name. Signed-off-by: Dennis Zhou Reviewed-by: Nikolay Borisov Reviewed-by: Josef Bacik --- fs/btrfs/compression.c | 46 +-

[PATCH v2 00/12] btrfs: add zstd compression level support

Hi everyone, V2 had only a handful of changes outside of minor feedback. 0001: - use functions over macros 0003: - BTRFS_NR_WORKSPACE_MANAGERS is added instead of overriding BTRFS_COMPRESS_TYPES 0011 (new): - address monotonic memory requirement for zstd workspaces 0012: - increase reclaim timer

Re: [PATCH 0/9] Analogix ANX6345 RGB-(e)DP bridge support

On Mon, Feb 4, 2019 at 4:22 AM Torsten Duwe wrote: > > On Thu, Oct 18, 2018 at 03:33:18PM +0800, Icenowy Zheng wrote: > > This patchset brings the support for Analogix ANX6345 RGB-(e)DP bridge, > > which is used by some Allwinner A64 laptops, such as Pinebook and Olimex > > TERES-I. > > > > So wha

[PATCH v3 2/4] dt-bindings: Add LM96000 as a trivial device

The LM96000 is a temperature sensor and fan controller based on the LM85. Signed-off-by: Jeremy Gebben --- Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetr

[PATCH v3 3/4] hwmon: (lm85) support the LM96000

It has been supported as a generic lm85 for quite some time. Signed-off-by: Jeremy Gebben --- Documentation/hwmon/lm85 | 6 +- drivers/hwmon/lm85.c | 9 +++-- 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/Documentation/hwmon/lm85 b/Documentation/hwmon/lm85 index 7c4

Re: [PATCH v3 5/5] Revert "scsi: ufs: disable vccq if it's not needed by UFS device"

On 2/4/2019 12:51 PM, Avri Altman wrote: This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490. Calling ufshcd_set_vccq_rail_unused hangs my system. It seems vccq is not *not* needed. This patch essentially implements the UFS_DEVICE_NO_VCCQ quirk, Which is needed for both Samsung and H

Re: [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted

On Mon, Feb 04, 2019 at 04:14:20PM -0200, Thiago Jung Bauermann wrote: > > Hello Michael, > > Michael S. Tsirkin writes: > > > On Tue, Jan 29, 2019 at 03:42:44PM -0200, Thiago Jung Bauermann wrote: > >> > >> Fixing address of powerpc mailing list. > >> > >> Thiago Jung Bauermann writes: > >> >

Re: [PATCH] config: arm: omap2: remove PROVE_LOCKING from defconfig

* Lukasz Luba [181113 10:22]: > Hi Tony, > > On 11/8/18 5:59 PM, Tony Lindgren wrote: > > Hi, > > > > * Lukasz Luba [181009 08:36]: > >> PROVE_LOCKING enables LOCKDEP, which causes big overhead on cache and > >> bus transactions. > >> > >> On some ARM big.LITTLE architecutres (Exynos 5433) the

May God bless you

Dear Friend, 3/2/2019 My beloved in Christ, Donation of Two Million,Four Hundred Thousand British pounds forcharity Less privileged peoples orphanages work, please reply tome.via my private email address ( mrskathleenjaco...@yahoo.com ) Yours in Christ, Mrs. KATHLEEN JACOB

Re: [PATCH v3 5/5] Revert "scsi: ufs: disable vccq if it's not needed by UFS device"

On Mon 04 Feb 11:51 PST 2019, Avri Altman wrote: > > > This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490. > > > > Calling ufshcd_set_vccq_rail_unused hangs my system. > > It seems vccq is not *not* needed. > This patch essentially implements the UFS_DEVICE_NO_VCCQ quirk, > Which is ne

[PATCH 1/4] elf: don't be afraid of overflow

Number of ELF program headers is 16-bit by spec, so total size comfortably fits into "unsigned int". Space savings: 7 bytes! add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-7 (-7) Function old new delta load_elf_phdrs

Re: [PATCH v4 01/16] block: sed-opal: fix typos and formatting

On Mon, 4 Feb 2019, Christoph Hellwig wrote: On Fri, Feb 01, 2019 at 09:50:08PM +0100, David Kozub wrote: This should make no change in functionality. The formatting changes were triggered by checkpatch.pl. Signed-off-by: David Kozub Reviewed-by: Scott Bauer --- block/sed-opal.c | 19 ++

Re: [RFC/PATCH 00/14] perf record: Add support to store data in directory

On Mon, Feb 04, 2019 at 12:05:38PM -0800, Stephane Eranian wrote: SNIP > > > > > > > > > > > > [jolsa@krava perf]$ ll result_1/ > > > > > > total 348 > > > > > > -rw---. 1 jolsa jolsa 27624 Feb 4 11:35 data.0 > > > > > > -rw---. 1 jolsa jolsa 56672 Feb 4 11:35 data.1 > > > > > > -rw

[PATCH 3/4] elf: spread const a little

Signed-off-by: Alexey Dobriyan --- fs/binfmt_elf.c |8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) --- a/fs/binfmt_elf.c +++ b/fs/binfmt_elf.c @@ -57,8 +57,6 @@ #endif static int load_elf_binary(struct linux_binprm *bprm); -static unsigned long elf_map(struct file *, unsign

[PATCH 2/4] elf: use list_for_each_entry()

Signed-off-by: Alexey Dobriyan --- fs/binfmt_elf.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) --- a/fs/binfmt_elf.c +++ b/fs/binfmt_elf.c @@ -2030,7 +2030,6 @@ static int fill_note_info(struct elfhdr *elf, int phdrs, struct elf_note_info *info,

Re: [PATCH v3 2/4] dt-bindings: Add LM96000 as a trivial device

On Mon, Feb 4, 2019 at 2:19 PM Jeremy Gebben wrote: > > The LM96000 is a temperature sensor and fan controller based > on the LM85. > > Signed-off-by: Jeremy Gebben > --- > Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++ > 1 file changed, 2 insertions(+) Reviewed-by: Rob Herring

Re: [PATCH] perf utils: silent "Couldn't synthesize bpf events" warning for EPERM

On Mon, Feb 04, 2019 at 07:33:06PM +, Song Liu wrote: > > > > On Feb 4, 2019, at 11:31 AM, Song Liu wrote: > > > > Synthesizing BPF events is only supported for root. Silent warning msg > > when non-root user runs perf-record. great, it was annoying ;-) Tested-by: Jiri Olsa thanks, jirk

Re: remove exofs, the T10 OSD code and block/scsi bidi support V4

On 01/02/19 09:55, Christoph Hellwig wrote: > The only real user of the T10 OSD protocol, the pNFS object layout > driver never went to the point of having shipping products, and we > removed it 1.5 years ago. Exofs is just a simple example without > real life users. > > The code has been mostly

[PATCH v3 01/15] habanalabs: add skeleton driver

This patch adds the habanalabs skeleton driver. The driver does nothing at this stage except very basic operations. It contains the minimal code to insmod and rmmod the driver and to create a /dev/hlX file per PCI device. Signed-off-by: Oded Gabbay --- drivers/misc/Kconfig |

[PATCH v3 00/15] Habana Labs kernel driver

Hello, This is v3 of the Habana Labs kernel driver patch-set. It contains minor fixes according to reviews done on v2. In addition, it is rebased on v5.0-rc5. Link to v2 cover letter: https://lkml.org/lkml/2019/1/30/1003 Link to v1 cover letter: https://lwn.net/Articles/777342/ I would appricate

[PATCH v3 07/15] habanalabs: add h/w queues module

This patch adds the H/W queues module and the code to initialize Goya's various compute and DMA engines and their queues. Goya has 5 DMA channels, 8 TPC engines and a single MME engine. For each channel/engine, there is a H/W queue logic which is used to pass commands from the user to the H/W. Tha

[PATCH v3 03/15] habanalabs: add basic Goya support

This patch adds a basic support for the Goya device. The code initializes the device's PCI controller and PCI bars. It also initializes various S/W structures and adds some basic helper functions. Signed-off-by: Oded Gabbay --- drivers/misc/habanalabs/Makefile| 4 + drivers/misc/ha

[PATCH v3 12/15] habanalabs: add virtual memory and MMU modules

From: Omer Shpigelman This patch adds the Virtual Memory and MMU modules. Goya has an internal MMU which provides process isolation on the internal DDR. The internal MMU also performs translations for transactions that go from Goya to the Host. The driver is responsible for allocating and freei

[PATCH v3 09/15] habanalabs: add sysfs and hwmon support

This patch add the sysfs and hwmon entries that are exposed by the driver. Goya has several sensors, from various categories such as temperature, voltage, current, etc. The driver exposes those sensors in the standard hwmon mechanism. In addition, the driver exposes a couple of interfaces in sysf

[PATCH v3 10/15] habanalabs: add device reset support

This patch adds support for doing various on-the-fly reset of Goya. The driver supports two types of resets: 1. soft-reset 2. hard-reset Soft-reset is done when the device detects a timeout of a command submission that was given to the device. The soft-reset process only resets the engines that a

[PATCH v3 08/15] habanalabs: add event queue and interrupts

This patch adds support for receiving events from Goya's control CPU and for receiving MSI-X interrupts from Goya's DMA engines and CPU. Goya's PCI controller supports up to 8 MSI-X interrupts, which only 6 of them are currently used. The first 5 interrupts are dedicated for Goya's DMA engine queu

[PATCH v3 14/15] habanalabs: add debugfs support

This patch adds debugfs support to the driver. It allows the user-space to display information that is contained in the internal structures of the driver, such as: - active command submissions - active user virtual memory mappings - number of allocated command buffers It also enables the user to p

[PATCH v3 15/15] Update MAINTAINERS and CREDITS with habanalabs info

The habanalabs driver was written from scratch from the very first days of Habana and is maintained by Oded Gabbay. Signed-off-by: Oded Gabbay --- CREDITS | 2 +- MAINTAINERS | 9 + 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/CREDITS b/CREDITS index e818eb6a3e71..0

[PATCH v3 11/15] habanalabs: add command submission module

This patch adds the main flow for the user to submit work to the device. Each work is described by a command submission object (CS). The CS contains 3 arrays of command buffers: One for execution, and two for context-switch (store and restore). For each CB, the user specifies on which queue to pu

[PATCH v3 13/15] habanalabs: implement INFO IOCTL

This patch implements the INFO IOCTL. That IOCTL is used by the user to query information that is relevant/needed by the user in order to submit deep learning jobs to Goya. The information is divided into several categories, such as H/W IP, Events that happened, DDR usage and more. Signed-off-by:

[PATCH v3 04/15] habanalabs: add context and ASID modules

This patch adds two modules - ASID and context. Each user process that opens a device's file must have at least one context before it is able to "work" with the device. Each context has its own device address-space and contains information about its runtime state (its active command submissions).

[PATCH v3 05/15] habanalabs: add command buffer module

This patch adds the command buffer (CB) module, which allows the user to create and destroy CBs and to map them to the user's process address-space. A command buffer is a memory blocks that reside in DMA-able address-space and is physically contiguous so it can be accessed by the device without MM

[PATCH 4/4] elf: save allocation per exec

2 ELF header aren't that large to allocate them on heap. However, code is bloated by 1.5 KB (!!!) with gcc 8.2 and stack size grows by ~340 bytes. The problem is that 2 elf headers are only 128 bytes. I'm shocked and the patch should not be applied probably. Signed-off-by: Alexey Dobriyan ---

Re: [PATCH V6 2/5] perf/x86/kvm: Avoid unnecessary work in guest filtering

On 2/4/2019 2:43 PM, Borislav Petkov wrote: On Mon, Feb 04, 2019 at 01:57:49PM -0500, Liang, Kan wrote: You mean a given microcode revision X applying to multiple stepping, right? Yes, the range thing. You specify a range of steppings: kabylake mobile with steppings 9-12 kabylake desktop

Re: perf: python3 + tests attr.py failing

On Mon, Feb 04, 2019 at 12:10:42PM -0300, Arnaldo Carvalho de Melo wrote: > Noticed this now when building with PYTHON=python3, can you take a look? > For now I'm reinstalling python2-devel and building with it, i.e. > removing that PYTHON=python3 make command line variable. > > [root@quaco ~]# pe

Re: [PATCH] x86/ima: require signed kernel modules

On Thu, Jan 31, 2019 at 02:18:59PM -0500, Mimi Zohar wrote: > diff --git a/kernel/module.c b/kernel/module.c > index 2ad1b5239910..70a9709d19eb 100644 > --- a/kernel/module.c > +++ b/kernel/module.c > @@ -275,16 +275,23 @@ static void module_assert_mutex_or_preempt(void) > > static bool sig_enfo

[PATCHv2] arm64: defconfig: enable fpga and service layer

From: Richard Gong Enable FPGA framework, Intel Stratix10 SoC FPGA manager, Stratix10 service layer, and Altera Freeze Bridge drivers. Intel Stratix10 service layer driver was added with commit 7ca5ce896524 ("firmware: add Intel Stratix10 service layer driver"). Intel Stratix10 service layer pr

Re: [RFC PATCH 3/4] kvm: Add guest side support for free memory hints

On Mon, 2019-02-04 at 11:44 -0800, Dave Hansen wrote: > On 2/4/19 10:15 AM, Alexander Duyck wrote: > > +#ifdef CONFIG_KVM_GUEST > > +#include > > +extern struct static_key_false pv_free_page_hint_enabled; > > + > > +#define HAVE_ARCH_FREE_PAGE > > +void __arch_free_page(struct page *page, unsigned

[PATCH] x86/resctrl: Remove duplicate MSR_MISC_FEATURE_CONTROL definition

The definition of MSR_MISC_FEATURE_CONTROL was first introduced in commit 98af74599ea0 ("x86 msr_index.h: Define MSR_MISC_FEATURE_CONTROL") and present in Linux since v4.11. The Cache Pseudo-Locking code added this duplicate definition in more recent commit f2a177292bd0 ("x86/intel_rdt: Discover s

Re: [PATCH v4 3/6] rpmsg: add rpmsg support for mt8183 SCP.

Hi Pi-Hsun, On Thu, Jan 31, 2019 at 05:31:28PM +0800, Pi-Hsun Shih wrote: > Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly. > > Signed-off-by: Pi-Hsun Shih > --- > Changes from v3: > - Change from unprepare to stop, to stop the rpmsg driver before the >rproc is stopp

Re: mm: race in put_and_wait_on_page_locked()

On Mon, 4 Feb 2019, Artem Savkov wrote: > Hi Hugh, > > Your recent patch 9a1ea439b16b "mm: put_and_wait_on_page_locked() while > page is migrated" seems to have introduced a race into page migration > process. I have a host that eagerly reproduces the following BUG under > stress: > > [ 302.847

[tip:ras/core] x86/MCE/AMD, EDAC/mce_amd: Add new MP5, NBIO, and PCIE SMCA bank types

Commit-ID: cbfa447edd6a3825fdb8a4ffae74ff7208f2d2c0 Gitweb: https://git.kernel.org/tip/cbfa447edd6a3825fdb8a4ffae74ff7208f2d2c0 Author: Yazen Ghannam AuthorDate: Fri, 1 Feb 2019 22:55:51 + Committer: Borislav Petkov CommitDate: Sun, 3 Feb 2019 13:01:44 +0100 x86/MCE/AMD, EDAC/mce_a

[tip:ras/core] x86/MCE/AMD, EDAC/mce_amd: Add new McaTypes for CS, PSP, and SMU units

Commit-ID: 3ad7e748c12cc771df6020a552def3e1727e8a17 Gitweb: https://git.kernel.org/tip/3ad7e748c12cc771df6020a552def3e1727e8a17 Author: Yazen Ghannam AuthorDate: Fri, 1 Feb 2019 22:55:52 + Committer: Borislav Petkov CommitDate: Sun, 3 Feb 2019 13:01:57 +0100 x86/MCE/AMD, EDAC/mce_a

[tip:ras/core] x86/MCE/AMD, EDAC/mce_amd: Add new error descriptions for some SMCA bank types

Commit-ID: 8a5dd2cd2f2e94878cacc969655a69ca214795ab Gitweb: https://git.kernel.org/tip/8a5dd2cd2f2e94878cacc969655a69ca214795ab Author: Yazen Ghannam AuthorDate: Fri, 1 Feb 2019 22:55:52 + Committer: Borislav Petkov CommitDate: Sun, 3 Feb 2019 13:05:16 +0100 x86/MCE/AMD, EDAC/mce_a

[tip:ras/core] EDAC, mce_amd: Match error descriptions to latest documentation

Commit-ID: e03447ee718b331be8f3abc388c7bf7d325dfab4 Gitweb: https://git.kernel.org/tip/e03447ee718b331be8f3abc388c7bf7d325dfab4 Author: Yazen Ghannam AuthorDate: Fri, 1 Feb 2019 22:55:53 + Committer: Borislav Petkov CommitDate: Sun, 3 Feb 2019 13:16:50 +0100 EDAC, mce_amd: Match er

[tip:ras/core] EDAC, mce_amd: Print ExtErrorCode and description on a single line

Commit-ID: 1c1522d32ac49065f88e5a8b3d6e3a5613b20118 Gitweb: https://git.kernel.org/tip/1c1522d32ac49065f88e5a8b3d6e3a5613b20118 Author: Yazen Ghannam AuthorDate: Fri, 1 Feb 2019 22:55:54 + Committer: Borislav Petkov CommitDate: Mon, 4 Feb 2019 19:29:13 +0100 EDAC, mce_amd: Print Ex

Re: [PATCH v3 08/10] x86/setcpuid: Add kernel option setcpuid

On 2/4/19 11:57 AM, Borislav Petkov wrote: > On Mon, Feb 04, 2019 at 11:05:52AM -0800, Dave Hansen wrote: >> But, we're not being very persuasive because we kinda forgot about the >> "if and only if" condition that you mentioned. > But why does it have to be a cmdline parameter instead of > being a

Re: [PATCH] selftests: ir: fix warning: ‘%s’ directive output may be truncated

On Thu, Jan 31, 2019 at 12:43:12PM -0700, Shuah Khan wrote: > Fix the following warning by sizing the buffer to max. of sysfs > path max. size + d_name max. size. > > gcc -Wall -O2 -I../../../include/uapi ir_loopback.c -o > ../tools/testing/selftests/ir/ir_loopback > ir_loopback.c: In function ‘

Re: [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning

Hi Anand, On Mon, Feb 4, 2019 at 9:04 PM Anand Moon wrote: [...] > > > @@ -36,6 +43,8 @@ > > > regulator-min-microvolt = <500>; > > > regulator-max-microvolt = <500>; > > > > > > + vin-supply = <&p5v0>; > > did you find out why this patch fixe

I have rescinded the GPL from a number of people (regarding GPC-Slots 2)

Some decisions I have made regarding my GPC-Slots 2 game: I had chosen, as was my want, to rescind the license I extended from a few choice individuals. I can do this because GPC-Slots 2 is my copyrighted work. I built it. I never transferred the copyright over to anyone. The individuals are

Re: [PATCH] arm64: dts: qcs404: evb: Fix voltages for s5 and l3

On Mon, Feb 04, 2019 at 11:25:10AM -0800, Bjorn Andersson wrote: > On Mon 04 Feb 10:23 PST 2019, Mark Brown wrote: > > On Mon, Feb 04, 2019 at 08:03:37AM -0800, Bjorn Andersson wrote: > Okay, I don't see a big problem with expecting the DT to only contain > values that the hardware can actually do

[PATCH -next] efi/arm64: return zero from ptdump_init()

The commit e2a2e56e4082 ("arm64: dump: no need to check return value of debugfs_create functions") converted ptdump_debugfs_register() from void, but forgot to fix the efi version of ptdump_init(). drivers/firmware/efi/arm-runtime.c: In function 'ptdump_init': drivers/firmware/efi/arm-runtime.c:52

Re: [PATCH V2] lightnvm: pblk: fix race condition on GC

Thanks Heiner, it's awesome to get this fixed! Reviewed-by: Hans Holmberg On Mon, Feb 4, 2019 at 9:19 AM Javier González wrote: > > > On 1 Feb 2019, at 03.38, Heiner Litz wrote: > > > > This patch fixes a race condition where a write is mapped to the last > > sectors of a line. The write is sy

Re: [PATCH 0/2] Add Apple SPI keyboard and trackpad driver

Hi Ronald, This changeset adds a driver for the SPI keyboard and trackpad on recent MacBook's and MacBook Pro's. The driver has seen a fair amount of use over the last 2 years (basically anybody running linux on these machines), with only relatively small changes in the last year or so. For thos

Re: [PATCH v4 03/16] block: sed-opal: unify space check in add_token_*

On Mon, 4 Feb 2019, Christoph Hellwig wrote: On Fri, Feb 01, 2019 at 09:50:10PM +0100, David Kozub wrote: From: Jonas Rabenstein All add_token_* functions have a common set of conditions that have to be checked. Use a common function for those checks in order to avoid different behaviour as w

Re: [PATCH V2] lightnvm: pblk: prevent stall due to wb threshold

On Mon, Feb 4, 2019 at 9:14 AM Javier González wrote: > > > > On 31 Jan 2019, at 21.10, Hans Holmberg wrote: > > > > On Thu, Jan 31, 2019 at 5:33 PM Javier González wrote: > >>> On 31 Jan 2019, at 11.41, Hans Holmberg wrote: > >>> > >>> Hi Javier! > >>> > >>> How did you test this? I'm trying t

[PATCH 2/2] tracing: Use strncpy instead of memcpy for string keys in hist triggers

From: Tom Zanussi Because there may be random garbage beyond a string's null terminator, it's not correct to copy the the complete character array for use as a hist trigger key. This results in multiple histogram entries for the 'same' string key. So, in the case of a string key, use strncpy in

[PATCH 0/2] A couple hist trigger patches

From: Tom Zanussi Hi, Here are a couple miscellaneous hist trigger patches which can be applied independently of the onchange/snapshot patches. The first is just an additional use of str_has_prefix() that was apparently missed in the original str_has_prefix() conversion, with an update suggeste

[PATCH 1/2] tracing: Use str_has_prefix() in synth_event_create()

From: Tom Zanussi Since we now have a str_has_prefix() that returns the length, we can use that instead of explicitly calculating it. Signed-off-by: Tom Zanussi Cc: Joe Perches --- kernel/trace/trace_events_hist.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/

Re: [PATCH v4 03/16] block: sed-opal: unify space check in add_token_*

On Mon, Feb 04, 2019 at 10:07:09PM +0100, David Kozub wrote: > It is eventually used for the second time in 11/16 block: sed-opal: ioctl > for writing to shadow mbr. > > If you feel strongly about this I can exclude it from this commit and > introduce it in 11/16 (where it then will called from he

Re: [PATCH v3 08/10] x86/setcpuid: Add kernel option setcpuid

On Mon, Feb 04, 2019 at 11:05:52AM -0800, Dave Hansen wrote: > On 2/4/19 9:49 AM, Thomas Gleixner wrote: > > On Fri, 1 Feb 2019, Fenghua Yu wrote: > >> This option behaves like existing kernel option clearcpuid. > > > > No it does NOT. clearcpuid allows to disable things. > > > > This allows to e

[PATCH] xfs: allow disabling xfs tracepoints via Kconfig

linux/tracepoints.h allows individual subsystems to disable their tracepoints. Add such a knob for xfs. Disabling XFS_TRACEPOINTS reduces the resident size of xfs.ko by about a third, or ~350 KiB. $ size /tmp/xfs/{a,b}/xfs.ko textdata bss dec hex filename 6717264129 632

Re: [PATCH v2 1/2] rtc: add AB-RTCMC-32.768kHz-EOZ9 RTC support

On 03/02/2019 03:36:54+0300, Artem Panfilov wrote: > Hi Alexandre, > > On 31.01.2019 0:48, Alexandre Belloni wrote: > > >> +#endif /* CONFIG_RTC_DRV_ABEOZ9_HWMON */ > > This comment is not correct > > Thank you for your remarks. Can I add HMON support as Kconfig build option? > I'm not sure th

[RFC PATCH 2/4] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux

When available, use the cpu_id field from __rseq_abi on Linux to implement sched_getcpu(). Fall-back on the vgetcpu vDSO if unavailable. Benchmarks: x86-64: Intel E5-2630 v3@2.40GHz, 16-core, hyperthreading glibc sched_getcpu(): 13.7 ns (baseline) glibc sched_getcpu() using r

[RFC PATCH 1/4] glibc: Perform rseq(2) registration at C startup and thread creation (v7)

Register rseq(2) TLS for each thread (including main), and unregister for each thread (excluding main). "rseq" stands for Restartable Sequences. See the rseq(2) man page proposed here: https://lkml.org/lkml/2018/9/19/647 This patch is based on glibc-2.29. The rseq(2) system call was merged into

[PATCH V3] doc:it_IT: add translations in process/

This patch adds the Italian translation for the following documents in Documentation/process: - applying-patches - submit-checklist - submitting-drivers - changes - stable api nonsense Signed-off-by: Federico Vaga --- V3 - update according to recent change 8f7e6d134bda (doc/docs-next) doc: pro

[PATCH] ASoC: wcd9335: fix semicolon.cocci warnings

From: kbuild test robot sound/soc/codecs/wcd-clsh-v2.c:545:2-3: Unneeded semicolon sound/soc/codecs/wcd-clsh-v2.c:211:2-3: Unneeded semicolon sound/soc/codecs/wcd-clsh-v2.c:250:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Fixes: cc2

Re: [PATCH] xfs: allow disabling xfs tracepoints via Kconfig

On Mon, Feb 04, 2019 at 10:20:35PM +0100, Rasmus Villemoes wrote: > linux/tracepoints.h allows individual subsystems to disable their > tracepoints. Add such a knob for xfs. Disabling XFS_TRACEPOINTS > reduces the resident size of xfs.ko by about a third, or ~350 KiB. LOL. :) > $ size /tmp/xfs/{a

Re: [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted

On Mon, Feb 04, 2019 at 04:15:41PM -0200, Thiago Jung Bauermann wrote: > > Christoph Hellwig writes: > > > On Tue, Jan 29, 2019 at 09:36:08PM -0500, Michael S. Tsirkin wrote: > >> This has been discussed ad nauseum. virtio is all about compatibility. > >> Losing a couple of lines of code isn't w

Re: [PATCH 3.16 000/305] 3.16.63-rc1 review

On Sun, Feb 03, 2019 at 02:45:07PM +0100, Ben Hutchings wrote: > This is the start of the stable review cycle for the 3.16.63 release. > There are 305 patches in this series, which will be posted as responses > to this one. If anyone has any issues with these being applied, please > let me know. >

Re: [PATCH v3 08/10] x86/setcpuid: Add kernel option setcpuid

On Mon, Feb 04, 2019 at 12:46:30PM -0800, Dave Hansen wrote: > Intel can obviously add or remove enumeration for a feature after > silicon ships. But, that eats up microcode "patch" space which is an > even more valuable resource than the microcode "ROM" space. That patch > space is a very constr

Re: [PATCH 3.18 00/31] 3.18.134-stable review

On Mon, Feb 04, 2019 at 11:36:15AM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.134 release. > There are 31 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me kno

[PATCH v13 00/15]tracing: Hist trigger snapshot and onchange additions

From: Tom Zanussi Hi, This is v13 of the hist trigger snapshot and onchange additions patchset. It addresses a bug Namhyung found where taking a snapshot from the command-line would cause an OOPs if there was a hist trigger snapshot action in effect at the same time. What should have happened

[PATCH v13 02/15] tracing: Make hist trigger Documentation better reflect actions/handlers

From: Tom Zanussi The action/handler code refactoring didn't change the action/handler syntax, but did generalize it - the Documentation should reflect that. Signed-off-by: Tom Zanussi --- Documentation/trace/histogram.rst | 56 ++- 1 file changed, 43 insert

[PATCH v13 03/15] tracing: Split up onmatch action data

From: Tom Zanussi Currently, the onmatch action data binds the onmatch action to data related to synthetic event generation. Since we want to allow the onmatch handler to potentially invoke a different action, and because we expect other handlers to generate synthetic events, we need to separate

[PATCH v13 12/15] tracing: Add hist trigger snapshot() action test case

From: Tom Zanussi Add a test case verifying the basic functionality of the hist:snapshot() action. Signed-off-by: Tom Zanussi Acked-by: Masami Hiramatsu --- .../inter-event/trigger-snapshot-action-hist.tc| 43 ++ 1 file changed, 43 insertions(+) create mode 100644 to

[PATCH v13 14/15] tracing: Add alternative synthetic event trace action test case

From: Tom Zanussi Add a test case for the alternative trace( --- .../inter-event/trigger-trace-action-hist.tc | 42 ++ 1 file changed, 42 insertions(+) create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-trace-action-hist.tc diff --gi

[PATCH v13 06/15] tracing: Add hist trigger snapshot() action

From: Tom Zanussi Add support for hist:handlerXXX($var).snapshot(), which will take a snapshot of the current trace buffer whenever handlerXXX is hit. As a first user, this also adds snapshot() action support for the onmax() handler i.e. hist:onmax($var).snapshot(). Also, the hist trigger key p

[PATCH v13 04/15] tracing: Generalize hist trigger onmax and save action

From: Tom Zanussi The action refactor code allowed actions and handlers to be separated, but the existing onmax handler and save action code is still not flexible enough to handle arbitrary coupling. This change generalizes them and in the process makes additional handlers and actions easier to

[PATCH v13 15/15] tracing: Add hist trigger action 'expected fail' test case

From: Tom Zanussi Add a test case verifying that basic action combinations fail as expected. Signed-off-by: Tom Zanussi --- .../inter-event/trigger-action-hist-xfail.tc | 30 ++ 1 file changed, 30 insertions(+) create mode 100644 tools/testing/selftests/ftrace/test.

[PATCH v13 09/15] tracing: Add hist trigger onchange() handler Documentation

From: Tom Zanussi Add Documentation for the hist:onchange($var) handler. Signed-off-by: Tom Zanussi --- Documentation/trace/histogram.rst | 98 +++ 1 file changed, 98 insertions(+) diff --git a/Documentation/trace/histogram.rst b/Documentation/trace/histog

[PATCH v13 11/15] tracing: Add SPDX license GPL-2.0 license identifier to inter-event testcases

From: Tom Zanussi Apparently this directory was missed in the license cleanup process - add the missing identifiers to the trigger/inter-event test cases. Signed-off-by: Tom Zanussi --- .../ftrace/test.d/trigger/inter-event/trigger-extended-error-support.tc | 1 + .../ftrace/test.d/trigger/in

[PATCH v13 13/15] tracing: Add hist trigger onchange() handler test case

From: Tom Zanussi Add a test case verifying the basic functionality of the hist:onchange($var) handler. Signed-off-by: Tom Zanussi Acked-by: Masami Hiramatsu --- .../inter-event/trigger-onchange-action-hist.tc| 28 ++ 1 file changed, 28 insertions(+) create mode 10064

[PATCH v13 10/15] tracing: Add alternative synthetic event trace action syntax

From: Tom Zanussi Add a 'trace(synthetic_event_name, params)' alternative to synthetic_event_name(params). Currently, the syntax used for generating synthetic events is to invoke synthetic_event_name(params) i.e. use the synthetic event name as a function call. Users requested a new form that m

[PATCH v13 07/15] tracing: Add hist trigger snapshot() action Documentation

From: Tom Zanussi Add Documentation for the hist:handlerXXX($var).snapshot() action. Signed-off-by: Tom Zanussi --- Documentation/trace/histogram.rst | 110 ++ 1 file changed, 110 insertions(+) diff --git a/Documentation/trace/histogram.rst b/Documentation

[PATCH v13 05/15] tracing: Add conditional snapshot

From: Tom Zanussi Currently, tracing snapshots are context-free - they capture the ring buffer contents at the time the tracing_snapshot() function was invoked, and nothing else. Additionally, they're always taken unconditionally - the calling code can decide whether or not to take a snapshot, b

[PATCH v13 08/15] tracing: Add hist trigger onchange() handler

From: Tom Zanussi Add support for a hist:onchange($var) handler, similar to the onmax() handler but triggering whenever there's any change in $var, not just a max. Signed-off-by: Tom Zanussi --- kernel/trace/trace.c | 3 ++- kernel/trace/trace_events_hist.c | 58 ++

[PATCH v13 01/15] tracing: Refactor hist trigger action code

From: Tom Zanussi The hist trigger action code currently implements two essentially hard-coded pairs of 'actions' - onmax(), which tracks a variable and saves some event fields when a max is hit, and onmatch(), which is hard-coded to generate a synthetic event. These hardcoded pairs (track max/s

Re: [PATCH 1/2] Revert "mm: don't reclaim inodes with many attached pages"

On Fri, Feb 01, 2019 at 09:19:04AM +1100, Dave Chinner wrote: > > So, assuming all this, can we, please, first check if Rik's patch is > > addressing > > the regression? > > Nope, it's broken and buggy, and reintroduces problems with racing > deferred counts that were fixed years ago when I origi

  1   2   3   4   5   6   7   8   9   10   >