Re: [PATCH] docs: add index entry for networking/msg_zerocopy

On Tue, Jan 09, 2018 at 10:58:23AM -0700, Jonathan Corbet wrote: > On Sat, 6 Jan 2018 12:30:37 +1100 > "Tobin C. Harding" wrote: > > > Currently msg_zerocopy is not included in any toctree. Sphinx emits a > > build warning to this effect. The other three rst files in > >

Re: [PATCH v3 6/6] coresight: etm4x: Support panic kdump

On Thu, Dec 21, 2017 at 04:20:15PM +0800, Leo Yan wrote: > ETMv4 hardware information and configuration needs to be saved as > metadata; these metadata should be compatible with tool 'perf' and > can be used for tracing data analysis. ETMv4 usually works as tracer > per CPU, we cannot wait to

Re: Documentation: infiniband: move sysfs interface to ABI

On Mon, Jan 08, 2018 at 02:23:42PM +0530, Aishwarya Pant wrote: > Hi > > In Documentation/infiniband/sysfs.txt, there is a description of the > infiniband > sysfs interface and there also exists > Documentation/ABI/testing/sysfs-class-infiniband which is out of date. > > Would it be useful to

Re: [PATCH] docs-rst: networking: wire up msg_zerocopy

From: Jonathan Corbet Date: Tue, 9 Jan 2018 09:55:27 -0700 > On Tue, 09 Jan 2018 11:50:49 -0500 (EST) > David Miller wrote: > >> From: Mike Rapoport >> Date: Mon, 8 Jan 2018 08:50:17 +0200 >> >> > Fix the following 'make

Re: [PATCH] docs-rst: networking: wire up msg_zerocopy

From: Mike Rapoport Date: Mon, 8 Jan 2018 08:50:17 +0200 > Fix the following 'make htmldocs' complaint: > > Documentation/networking/msg_zerocopy.rst:: WARNING: document isn't included > in any toctree. > > Signed-off-by: Mike Rapoport

Re: Documentation: infiniband: move sysfs interface to ABI

On Tue, Jan 09, 2018 at 10:28:20AM -0700, Jason Gunthorpe wrote: > On Mon, Jan 08, 2018 at 02:23:42PM +0530, Aishwarya Pant wrote: > > Hi > > > > In Documentation/infiniband/sysfs.txt, there is a description of the > > infiniband > > sysfs interface and there also exists > >

Re: [PATCH] docs: add index entry for networking/msg_zerocopy

On Sat, 6 Jan 2018 12:30:37 +1100 "Tobin C. Harding" wrote: > Currently msg_zerocopy is not included in any toctree. Sphinx emits a > build warning to this effect. The other three rst files in > Documentation/networking are all indexed. We can add msg_zerocopy to the > toctree to

Re: [PATCH RFC 6/7] serial: Add device tree bindings for GENI based UART Controller

On 1/2/2018 8:55 AM, Rob Herring wrote: On Wed, Dec 27, 2017 at 09:27:25AM -0700, Karthikeyan Ramasubramanian wrote: Add device tree binding support for GENI based UART Controller in the QUP Wrapper. Signed-off-by: Karthikeyan Ramasubramanian Signed-off-by: Girish

Re: [PATCH v3 3/6] coresight: Support panic kdump functionality

On Thu, Dec 21, 2017 at 04:20:12PM +0800, Leo Yan wrote: > After kernel panic happens, coresight has many useful info can be used > for analysis. For example, the trace info from ETB RAM can be used to > check the CPU execution flows before crash. So we can save the tracing > data from sink

Re: [PATCH] docs-rst: networking: wire up msg_zerocopy

From: Mike Rapoport Date: Mon, 8 Jan 2018 08:50:17 +0200 > Fix the following 'make htmldocs' complaint: > > Documentation/networking/msg_zerocopy.rst:: WARNING: document isn't included > in any toctree. > > Signed-off-by: Mike Rapoport Does

Re: [PATCH] docs-rst: networking: wire up msg_zerocopy

On Tue, 09 Jan 2018 11:50:49 -0500 (EST) David Miller wrote: > From: Mike Rapoport > Date: Mon, 8 Jan 2018 08:50:17 +0200 > > > Fix the following 'make htmldocs' complaint: > > > > Documentation/networking/msg_zerocopy.rst:: WARNING: document

Re: [PATCH v6 00/11] Intel SGX Driver

On Thu, Jan 04, 2018 at 03:06:43AM -0600, Dr. Greg Wettstein wrote: > If we are talking about the issues motivating the KPTI work I don't > have any useful information beyond what is raging through the industry > right now. > > With respect to SGX, the issues giving rise to KPTI are

[RFC tip/locking/lockdep v4 16/17] lockdep: Documention for recursive read lock detection reasoning

As now we support recursive read lock deadlock detection, add related explanation in the Documentation/lockdep/lockdep-desgin.txt: * Definition of recursive read locks, non-recursive locks, strong dependency path and notions of -(**)->. * Lockdep's assumption. *

Re: [PATCH v6 00/11] Intel SGX Driver

On Thu, Jan 04, 2018 at 03:17:24PM +0100, Cedric Blancher wrote: > So how does this protect against the MELTDOWN attack (CVE-2017-5754) > and the MELTATOMBOMBA4 worm which uses this exploit? > > Ced Everything going out of L1 gets encrypted. This is done to defend against peripheral like

[RFC tip/locking/lockdep v4 03/17] lockdep: Redefine LOCK_*_STATE* bits

There are three types of lock acquisitions: write, non-recursive read and recursive read, among which write locks and non-recursive read locks have no difference from a viewpoint for deadlock detections, because a write acquisition of the corresponding lock on an independent CPU or task makes a

Re: [PATCH v6 00/11] Intel SGX Driver

On Jan 9, 4:25pm, Jarkko Sakkinen wrote: } Subject: Re: [PATCH v6 00/11] Intel SGX Driver Good afternoon I hope the week is going well for everyone. In order to minimize spamming mailboxes with two mails I'm incorporating a reply to Jarkko's second e-mail on the Memory Encryption Engine below

[PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers

From: Jae Hyun Yoo Hello, This patch set provides support for PECI of AST2400/2500 which can give us PECI functionalities such as temperature monitoring, platform manageability, processor diagnostics and failure analysis. Also provides generic peci.h and peci_ioctl.h

[PATCH linux dev-4.10 3/6] drivers/misc: Add driver for Aspeed PECI and generic PECI headers

This commit adds driver implementation for Aspeed PECI. Also adds generic peci.h and peci_ioctl.h files to provide compatibility to peci drivers that can be implemented later e.g. Nuvoton's BMC SoC family. Signed-off-by: Jae Hyun Yoo --- drivers/misc/Kconfig

[PATCH linux dev-4.10 6/6] drivers/hwmon: Add a driver for a generic PECI hwmon

This commit adds driver implementation for a generic PECI hwmon. Signed-off-by: Jae Hyun Yoo --- drivers/hwmon/Kconfig | 6 + drivers/hwmon/Makefile | 1 + drivers/hwmon/peci-hwmon.c | 953 + 3 files changed,

[PATCH linux dev-4.10 1/6] Documentation: dt-bindings: Add Aspeed PECI

This commit adds a dt-bindings document for Aspeed PECI. Signed-off-by: Jae Hyun Yoo --- .../devicetree/bindings/misc/aspeed-peci.txt | 55 ++ 1 file changed, 55 insertions(+) create mode 100644

[PATCH linux dev-4.10 5/6] Documentation: hwmon: Add a generic PECI hwmon

From: Jae Hyun Yoo This commit add a document for a generic PECI hwmon driver. Signed-off-by: Jae Hyun Yoo --- Documentation/hwmon/peci-hwmon | 74 ++ 1 file changed, 74 insertions(+) create mode 100644

[PATCH linux dev-4.10 4/6] Documentation: dt-bindings: Add a generic PECI hwmon

This commit add a dt-bindings document for a generic PECI hwmon driver. Signed-off-by: Jae Hyun Yoo --- .../devicetree/bindings/hwmon/peci-hwmon.txt | 33 ++ 1 file changed, 33 insertions(+) create mode 100644

Re: [PATCH v13 0/7] cgroup-aware OOM killer

On Thu, 30 Nov 2017, Andrew Morton wrote: > > This patchset makes the OOM killer cgroup-aware. > > Thanks, I'll grab these. > > There has been controversy over this patchset, to say the least. I > can't say that I followed it closely! Could those who still have > reservations please summarise

CRNG acronym

Hello, just curious, what's the official meaning of the "CRNG" acronym (e. g., in [1])? Some searching suggests that "C[S]RNG" means "cryptographic[-strength] random number generator". [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/char/random.c [2]

Protecting code integrity with PGP (kernel developer version)

Hi, all: I would like to adapt this document to be more specific to kernel development: https://github.com/lfit/itpol/blob/master/protecting-code-integrity.md This stems from many back-and-forth conversations with kernel devs, and I believe many would benefit from such guide, especially

[PATCH linux dev-4.10 2/6] ARM: dts: aspeed: peci: Add Aspeed PECI

This commit adds Aspeed PECI node into aspeed-g4 and aspeed-g5. Signed-off-by: Jae Hyun Yoo --- arch/arm/boot/dts/aspeed-g4.dtsi | 14 ++ arch/arm/boot/dts/aspeed-g5.dtsi | 14 ++ 2 files changed, 28 insertions(+) diff --git

Re: CRNG acronym

On Wed, Jan 10, 2018 at 02:47:19AM +0200, Bob Bib wrote: > Hello, > > just curious, > what's the official meaning of the "CRNG" acronym (e. g., in [1])? > > Some searching suggests that "C[S]RNG" > means "cryptographic[-strength] random number generator". > [1] >

[PATCH 1/5] Documentation/pktgen: Clearify how-to use pktgen samples

o Change process name in ps output: looks like, these days the process is named kpktgend_, rather than pktgen/. o Use pg_ctrl for start/stop as it can work well with pgset without changes to $(PGDEV) variable. o Clarify a bit needed $(PGDEV) definition for sample scripts and that one needs

[PATCH 0/5] pktgen: Behavior flags fixes

There are a bunch of fixes/cleanups/Documentations. Diffstat says for itself, regardless added docs and missed flag parameters. Cc: Arnd Bergmann Cc: "David S. Miller" Cc: David Windsor Cc: Eric Dumazet Cc: Ingo

[PATCH v5] MIPS: Add noexec=on|off kernel parameter

From: Miodrag Dinic Add a new kernel parameter to override the default behavior related to the decision whether to indicate stack as non-executable or executable (regardless of PT_GNU_STACK entry or CPU RIXI support) in function mips_elf_read_implies_exec(). Allowed

[RFC] doc: fix code snippet build warnings

Posting as RFC in the hope that someone knows how to massage sphinx correctly to fix this patch. Currently function kernel-doc contains a multi-line code snippet. This is causing sphinx to emit 5 build warnings WARNING: Unexpected indentation. WARNING: Unexpected indentation.

Re: [PATCH v3 6/6] coresight: etm4x: Support panic kdump

On Tue, Jan 09, 2018 at 01:21:28PM -0700, Mathieu Poirier wrote: > On Thu, Dec 21, 2017 at 04:20:15PM +0800, Leo Yan wrote: > > ETMv4 hardware information and configuration needs to be saved as > > metadata; these metadata should be compatible with tool 'perf' and > > can be used for tracing data

Re: [PATCH v3 3/6] coresight: Support panic kdump functionality

On Tue, Jan 09, 2018 at 11:41:26AM -0700, Mathieu Poirier wrote: > On Thu, Dec 21, 2017 at 04:20:12PM +0800, Leo Yan wrote: > > After kernel panic happens, coresight has many useful info can be used > > for analysis. For example, the trace info from ETB RAM can be used to > > check the CPU