Re: [PATCH] dt-bindings: misc: bk4: Add device tree binding for Liebherr's BK4 SPI bus

2018-10-15 Thread Rob Herring
On Fri, Sep 28, 2018 at 12:26:55AM +0200, Lukasz Majewski wrote: > Add Device Tree binding document for Liebherr's BK4 external SPI bus. > > Signed-off-by: Lukasz Majewski > --- > Documentation/devicetree/bindings/misc/lwn-bk4.txt | 26 > ++ > 1 file changed, 26 insertions(+

linux-next: Signed-off-by missing for commit in the fuse tree

2018-10-15 Thread Stephen Rothwell
Hi Miklos, Commit 5571f1e65486 ("fuse: enable caching of symlinks") is missing a Signed-off-by from its author. -- Cheers, Stephen Rothwell pgpv7Th7g5WNU.pgp Description: OpenPGP digital signature

Re: [PATCH v3 06/15] platform: goldfish: pipe: Move memory allocation from probe to init

2018-10-15 Thread Roman Kiryanov
> You should only allocate memory at probe time probe does not know what memory to allocate. We have several versions of the driver (with different init) and different versions allocate different state. >, not init time as what > happens if the hardware is not present yet your driver is loaded?

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Enke Chen
Hi, Greg: On 10/15/18 11:43 AM, Greg Kroah-Hartman wrote: > On Mon, Oct 15, 2018 at 11:16:36AM -0700, Enke Chen wrote: >> Hi, Greg: >> >>> Shouldn't there also be a manpage update, and a kselftest added for this >>> new user/kernel api that is being created? >>> >> >> I will submit a patch for man

Re: [PATCH v4 1/2] Bluetooth: Add device_get_bd_address()

2018-10-15 Thread Matthias Kaehlcke
On Mon, Oct 15, 2018 at 08:06:02PM +0200, Marcel Holtmann wrote: > Hi Matthias, > > void bt_sock_reclassify_lock(struct sock *sk, int proto); > > +int device_get_bd_address(struct device *dev, bdaddr_t *bd_addr); > >>> > >>> Maybe change the API name to start with bt_ and get rid

Re: [PATCH RFC 1/5] dt-bindings: power: supply: bq24190_charger: add bq24192 and usb-otg-vbus

2018-10-15 Thread Rob Herring
On Mon, Oct 01, 2018 at 01:30:01AM -0400, Brian Masney wrote: > Add support for the ti,bq24192 variant and a child node for the > usb-otg-vbus regulator. > > Signed-off-by: Brian Masney > --- > Documentation/devicetree/bindings/power/supply/bq24190.txt | 7 +++ > 1 file changed, 7 insertions

Re: [PATCH] Input: atmel_mxt_ts - mark expected switch fall-through

2018-10-15 Thread Gustavo A. R. Silva
On 10/15/18 8:21 PM, Dmitry Torokhov wrote: > On Mon, Oct 08, 2018 at 07:03:55PM +0200, Gustavo A. R. Silva wrote: >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases >> where we are expecting to fall through. >> >> Signed-off-by: Gustavo A. R. Silva > > Applied, thank you.

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Jann Horn
On Mon, Oct 15, 2018 at 8:36 PM Enke Chen wrote: > On 10/13/18 11:27 AM, Jann Horn wrote: > > On Sat, Oct 13, 2018 at 2:33 AM Enke Chen wrote: > >> For simplicity and consistency, this patch provides an implementation > >> for signal-based fault notification prior to the coredump of a child > >>

[PATCH v2] ARM: error out if compiling ARMv6 using Clang before 8.0

2018-10-15 Thread Stefan Agner
The kernel passes the ArmV6K architecture to the compiler when using the multi platform selection and enabling ARMv6. Clang older than version 8.0 emit assembly with an non-existing CPU, which then makes the GNU assembler fail. Warn users when compiling ARMv6 using Clang before 8.0. Suggested-by:

Re: [PATCH v3 09/15] platform: goldfish: pipe: Move goldfish_pipe to goldfish_pipe_v2

2018-10-15 Thread Roman Kiryanov
> > This is the v2 driver. v1 will be added later. > > If you want to add a new driver later, great, but don't change the name > of an existing driver for no good reason. I want our "v2" driver to be in a "v2" file and our "v1" driver in a "v1" file. I think this is reasonable.

Re: [PATCH v3 06/15] platform: goldfish: pipe: Move memory allocation from probe to init

2018-10-15 Thread Greg KH
On Mon, Oct 15, 2018 at 11:48:28AM -0700, Roman Kiryanov wrote: > > You should only allocate memory at probe time > > probe does not know what memory to allocate. We have several versions > of the driver (with different init) and different versions allocate > different state. I only see one drive

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Greg Kroah-Hartman
On Mon, Oct 15, 2018 at 11:49:11AM -0700, Enke Chen wrote: > Hi, Greg: > > On 10/15/18 11:43 AM, Greg Kroah-Hartman wrote: > > On Mon, Oct 15, 2018 at 11:16:36AM -0700, Enke Chen wrote: > >> Hi, Greg: > >> > >>> Shouldn't there also be a manpage update, and a kselftest added for this > >>> new use

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Enke Chen
Hi, Oleg: On 10/15/18 5:05 AM, Oleg Nesterov wrote: > On 10/12, Enke Chen wrote: >> >> For simplicity and consistency, this patch provides an implementation >> for signal-based fault notification prior to the coredump of a child >> process. A new prctl command, PR_SET_PREDUMP_SIG, is defined that

Re: [PATCH v3 09/15] platform: goldfish: pipe: Move goldfish_pipe to goldfish_pipe_v2

2018-10-15 Thread Greg KH
On Mon, Oct 15, 2018 at 11:55:26AM -0700, Roman Kiryanov wrote: > > > This is the v2 driver. v1 will be added later. > > > > If you want to add a new driver later, great, but don't change the name > > of an existing driver for no good reason. > > I want our "v2" driver to be in a "v2" file and our

Re: [PATCH v1 1/2] sysctl: cap to ULONG_MAX in proc_get_long()

2018-10-15 Thread Christian Brauner
On Mon, Oct 15, 2018 at 6:30 PM Christian Brauner wrote: > > On Mon, Oct 15, 2018 at 09:18:40AM -0700, Kees Cook wrote: > > On Mon, Oct 15, 2018 at 3:55 AM, Christian Brauner > > wrote: > > > proc_get_long() is a funny function. It uses simple_strtoul() and for a > > > good reason. proc_get_long

Re: [PATCH v3 06/15] platform: goldfish: pipe: Move memory allocation from probe to init

2018-10-15 Thread Roman Kiryanov
> > probe does not know what memory to allocate. We have several versions > > of the driver (with different init) and different versions allocate > > different state. > > I only see one driver here. It will be added in "PATCH v3 15/15". There will be two init functions allocating different states.

Re: [PATCH 1/2] dt-bindings: phy: Document cadence Sierra PHY bindings

2018-10-15 Thread Rob Herring
On Wed, Oct 03, 2018 at 05:02:25PM +0100, Alan Douglas wrote: > Add DT binding documentation for Sierra PHY. The PHY supports > a number of different protocols, including PCIe and USB. > > The PHY lanes may be configured as single or multi-lane links. > Each link is treated as a separate sub-node

Re: [PATCH 2/3] dt-bindings: cadence-quadspi: Add new compatible for AM654 SoC

2018-10-15 Thread Rob Herring
On Wed, 3 Oct 2018 22:26:02 +0530, Vignesh R wrote: > AM654 SoC has Cadence Octal SPI controller, which is similar to Cadence > QSPI controller but supports Octal IO(x8 data lines) and Double Data > Rate(DDR) mode. Add new compatible to support OSPI controller on TI's > AM654 SoCs. > > Signed-off-

Re: [PATCH 1/2] dt-bindings: pwm: tiecap: Add TI AM654 SoC specific compatible

2018-10-15 Thread Rob Herring
On Wed, 3 Oct 2018 22:36:57 +0530, Vignesh R wrote: > Add a new compatible string "ti,am654-ecap" to support PWM ECAP IP of > TI AM654 SoC. > > Signed-off-by: Vignesh R > Signed-off-by: Sekhar Nori > --- > Documentation/devicetree/bindings/pwm/pwm-tiecap.txt | 1 + > 1 file changed, 1 insertion

Re: [PATCH v3 2/9] dt-bindings: ti-lmu: Remove LM3697

2018-10-15 Thread Jacek Anaszewski
On 10/15/2018 02:56 AM, Rob Herring wrote: > On Sat, Oct 13, 2018 at 1:46 PM Jacek Anaszewski > wrote: >> >> On 10/12/2018 08:03 PM, Pavel Machek wrote: >>> Hi! >>> Signed-off-by: Dan Murphy >>> >>> NAK. >> >> Thanks for the NAK. >> >> This NAK was NAK'd by other

Re: [PATCH] ia64: disable SCHED_STACK_END_CHECK

2018-10-15 Thread Sergei Trofimovich
On Fri, 14 Sep 2018 08:06:17 +0100 Sergei Trofimovich wrote: > SCHED_STACK_END_CHECK assumes stack grows in one direction. > ia64 is a rare case where it is not. > > As a result kernel fails at startup as: > Kernel panic - not syncing: corrupted stack end detected inside scheduler > > The err

Re: [PATCH] perf tools: Store ids for events with their own cpus perf_event__synthesize_event_update_cpus

2018-10-15 Thread Arnaldo Carvalho de Melo
Em Fri, Oct 12, 2018 at 02:25:49PM +0100, John Garry escreveu: > On 09/10/2018 11:00, Jiri Olsa wrote: > > On Thu, Oct 04, 2018 at 10:20:39AM +0100, John Garry wrote: > > > > SNIP > > > > > > We synthesize an update event that needs to touch the evsel > > > > id array, which is not defined at tha

Re: [PATCH] ia64: enable GENERIC_HWEIGHT

2018-10-15 Thread Sergei Trofimovich
On Fri, 14 Sep 2018 08:06:46 +0100 Sergei Trofimovich wrote: > Noticed on a single driver failure: > ERROR: "__sw_hweight8" [drivers/net/wireless/mediatek/mt76/mt76.ko] > undefined! > > CC: Tony Luck > CC: Fenghua Yu > CC: linux-i...@vger.kernel.org > CC: Andrew Morton > CC: linux-kernel@v

Re: [PATCH v3 2/9] dt-bindings: ti-lmu: Remove LM3697

2018-10-15 Thread Dan Murphy
Jacek On 10/15/2018 02:13 PM, Jacek Anaszewski wrote: > On 10/15/2018 02:56 AM, Rob Herring wrote: >> On Sat, Oct 13, 2018 at 1:46 PM Jacek Anaszewski >> wrote: >>> >>> On 10/12/2018 08:03 PM, Pavel Machek wrote: Hi! > Signed-off-by: Dan Murphy NAK. >>> >>

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Enke Chen
Hi, Oleg: I missed some of your comments in my previous reply. On 10/15/18 5:05 AM, Oleg Nesterov wrote: > On 10/12, Enke Chen wrote: >> >> For simplicity and consistency, this patch provides an implementation >> for signal-based fault notification prior to the coredump of a child >> process. A n

[GIT PULL] cpupower update for Linux 4.20-rc1

2018-10-15 Thread Shuah Khan
Hi Rafael, Please pull the following cpupower update for Linux 4.20-rc1 This cpupower update for Linux 4.20-rc1 consists of fixes for bugs and compile warnings from Prarit Bhargava and Anders Roxell. diff is attached. thanks, -- Shuah ---

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Enke Chen
Hi, Jann: Thanks for your detail explanation. Will take care of it. -- Enke On 10/15/18 11:54 AM, Jann Horn wrote: > On Mon, Oct 15, 2018 at 8:36 PM Enke Chen wrote: >> On 10/13/18 11:27 AM, Jann Horn wrote: >>> On Sat, Oct 13, 2018 at 2:33 AM Enke Chen wrote: For simplicity and consisten

Dear,

2018-10-15 Thread Mohammed Rouhani
Dear, Please accept my apologies I do not intend to invade your privacy, I wrote to you earlier, but no answer, in my first post I told you about my late client who bears the same surname with you, I received several letters from the bank, where he made a deposit of 7.2 million Euros before his

Re: Re: [PATCH v1 1/2] sysctl: cap to ULONG_MAX in proc_get_long()

2018-10-15 Thread Alexey Dobriyan
> int kstrtoul_bounded(const char *s, unsigned int base, > char **trailing, unsigned long long *res) NO! The whole point is not have million variants of slightly different integer parsing functions. Cap it in the sysctl -- noone would care.

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Enke Chen
Hi, Olge: >> probably ->predump_signal should be cleared on exec? As I replied to Jann, will do. Thanks. -- Enke On 10/15/18 12:17 PM, Enke Chen wrote: > Hi, Oleg: > > I missed some of your comments in my previous reply. > > On 10/15/18 5:05 AM, Oleg Nesterov wrote: >> On 10/12, Enke Chen wro

Re: Re: [PATCH v1 1/2] sysctl: cap to ULONG_MAX in proc_get_long()

2018-10-15 Thread Christian Brauner
On Mon, Oct 15, 2018 at 9:27 PM Alexey Dobriyan wrote: > > > int kstrtoul_bounded(const char *s, unsigned int base, > > char **trailing, unsigned long long *res) > > NO! The whole point is not have million variants of slightly different > integer parsing functions. > Cap it in the sysctl -- noone

Re: linux-next: Tree for Oct 15

2018-10-15 Thread Guenter Roeck
On Mon, Oct 15, 2018 at 07:25:46PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20181012: > > My qemu boots of a powerpc pseries_le_defconfig kernel failed today. > Bisect log: # bad: [774ea0551a2966c8fc29a6f675c3e28c5c6fa586] Add linux-next specific files for 20181012 # good: [

[PATCH v3 1/3] mtd: rawnand: Provide helper for polling GPIO R/B pin

2018-10-15 Thread Janusz Krzysztofik
Each controller driver having access to NAND R/B pin over GPIO would have to reimplement the polling loop otherwise. Suggested-by: Boris Brezillon Signed-off-by: Janusz Krzysztofik Reviewed-by: Boris Brezillon --- Changelog: v3: - don't surround added code with #ifdef CONFIG_GPIOLIB - sugeested

[PATCH v3 3/3] mtd: rawnand: ams-delta: Convert the driver to ->exec_op()

2018-10-15 Thread Janusz Krzysztofik
Replace legacy callbacks with ->select_chip() and ->exec_op(). Suggested-by: Boris Brezillon Signed-off-by: Janusz Krzysztofik Reviewed-by: Boris Brezillon --- Changelog: v3: - former PATCH 2/2 from which PATCH v3 2/3 has been split out, - added missing return on check_only - requested by Boris

[PATCH v3 2/3] mtd: rawnand: ams-delta: Stop using legacy .IOADDR_R/W

2018-10-15 Thread Janusz Krzysztofik
Replace use of legacy .IOADDR_R/W with runtime calculations based on priv->io_base. Suggested-by: Boris Brezillon Signed-off-by: Janusz Krzysztofik Reviewed-by: Boris Brezillon --- Changelog: v3: New patch, split out from former PATCH 2/2 on Boris request - thanks drivers/mtd/nand/raw/ams-del

[PATCH v2] slimbus: ngd: QCOM_QMI_HELPERS has to be selected

2018-10-15 Thread Niklas Cassel
QCOM_QMI_HELPERS is a hidden kconfig, so the proper usage is to select it, not depend upon it. Because of this change, we now also need to depend on the same Kconfigs as QCOM_QMI_HELPERS depends on. Signed-off-by: Niklas Cassel --- Hello Greg, Srini, I'm sorry for this. (Although I'm a bit curi

Re: [PATCH v13 12/12] selftests/livepatch: introduce tests

2018-10-15 Thread Joe Lawrence
On 10/15/2018 08:37 AM, Petr Mladek wrote: > From: Joe Lawrence > > Add a few livepatch modules and simple target modules that the included > regression suite can run tests against: > > - basic livepatching (multiple patches, atomic replace) > - pre/post (un)patch callbacks > - shadow vari

Re: [PATCH v2 0/8] OLPC 1.75 Keyboard/Touchpad fixes

2018-10-15 Thread Pavel Machek
Hi! > This makes keyboard/touchpad work on a DT MMP2 platform. > > I believe that it would be a good idea if this, once reviewed, went in > via the input tree. The DT and CLK parts got reviews/acks. > > Changes from v1: > - Basically none, just re-send, including Ack and Review tags in patches >

Re: [PATCH 6/6] arm64: dts: xilinx: ultra96: Standardize LED labels and triggers

2018-10-15 Thread Pavel Machek
On Wed 2018-10-10 09:25:24, Michal Simek wrote: > On 9.10.2018 16:05, Manivannan Sadhasivam wrote: > > For all 96Boards, the following standard is used for onboard LEDs. > > > > device-name:green:user1 default-trigger: heartbeat > > device-name:green:user2 default-trigger: mmc0/disk-activity > >

Re: [PATCH] xtensa: remove ZONE_DMA

2018-10-15 Thread Max Filippov
On Sun, Oct 14, 2018 at 11:13 AM Christoph Hellwig wrote: > > ZONE_DMA is intended for magic < 32-bit pools (usually ISA DMA), which > isn't required on xtensa. Move all the non-highmem memory into > ZONE_NORMAL instead to match other architectures. > > Signed-off-by: Christoph Hellwig > --- >

Re: [PATCH] HID: steam: remove input device when a hid client is running.

2018-10-15 Thread Pierre-Loup A. Griffais
On 10/14/18 10:36 AM, Rodrigo Rivas Costa wrote: Previously, when a HID client such as the Steam Client was running, this driver disabled its input device to avoid doubling the input events. While it worked mostly fine, some games got confused by the idle gamepad, and switched to two player m

Re: [PATCH] compiler.h: update definition of unreachable()

2018-10-15 Thread Nick Desaulniers
On Mon, Oct 15, 2018 at 11:21 AM Miguel Ojeda wrote: > > On Mon, Oct 15, 2018 at 7:22 PM wrote: > > > > Fixes the objtool warning seen with Clang: > > arch/x86/mm/fault.o: warning: objtool: no_context()+0x220: unreachable > > instruction > > > > Fixes commit 815f0ddb346c ("include/linux/compiler*

Re: [PATCH v3 09/15] platform: goldfish: pipe: Move goldfish_pipe to goldfish_pipe_v2

2018-10-15 Thread Roman Kiryanov
> > I want our "v2" driver to be in a "v2" file and our "v1" driver in a > > "v1" file. I think this is reasonable. > > The in kernel driver is the "v1" one. I believe v2 (on our end) was upstream as goldfish_pipe.c instead of goldfish_pipe_v2.c. > Why do you need a totally new driver file at al

[mm PATCH v3 0/6] Deferred page init improvements

2018-10-15 Thread Alexander Duyck
This patchset is essentially a refactor of the page initialization logic that is meant to provide for better code reuse while providing a significant improvement in deferred page initialization performance. In my testing I have seen a 60% reduction in the time needed for deferred memory initializa

[mm PATCH v3 5/6] mm: Use common iterator for deferred_init_pages and deferred_free_pages

2018-10-15 Thread Alexander Duyck
This patch creates a common iterator to be used by both deferred_init_pages and deferred_free_pages. By doing this we can cut down a bit on code overhead as they will likely both be inlined into the same function anyway. This new approach allows deferred_init_pages to make use of __init_pageblock.

[mm PATCH v3 3/6] mm: Use memblock/zone specific iterator for handling deferred page init

2018-10-15 Thread Alexander Duyck
This patch introduces a new iterator for_each_free_mem_pfn_range_in_zone. This iterator will take care of making sure a given memory range provided is in fact contained within a zone. It takes are of all the bounds checking we were doing in deferred_grow_zone, and deferred_init_memmap. In addition

[mm PATCH v3 2/6] mm: Drop meminit_pfn_in_nid as it is redundant

2018-10-15 Thread Alexander Duyck
As best as I can tell the meminit_pfn_in_nid call is completely redundant. The deferred memory initialization is already making use of for_each_free_mem_range which in turn will call into __next_mem_range which will only return a memory range if it matches the node ID provided assuming it is not NU

[mm PATCH v3 4/6] mm: Move hot-plug specific memory init into separate functions and optimize

2018-10-15 Thread Alexander Duyck
This patch is going through and combining the bits in memmap_init_zone and memmap_init_zone_device that are related to hotplug into a single function called __memmap_init_hotplug. I also took the opportunity to integrate __init_single_page's functionality into this function. In doing so I can get

[mm PATCH v3 1/6] mm: Use mm_zero_struct_page from SPARC on all 64b architectures

2018-10-15 Thread Alexander Duyck
This change makes it so that we use the same approach that was already in use on Sparc on all the archtectures that support a 64b long. This is mostly motivated by the fact that 8 to 10 store/move instructions are likely always going to be faster than having to call into a function that is not spe

[mm PATCH v3 6/6] mm: Add reserved flag setting to set_page_links

2018-10-15 Thread Alexander Duyck
This patch modifies the set_page_links function to include the setting of the reserved flag via a simple AND and OR operation. The motivation for this is the fact that the existing __set_bit call still seems to have effects on performance as replacing the call with the AND and OR can reduce initial

Re: [PATCH 01/11] staging: gasket: core: debug log updates

2018-10-15 Thread Todd Poynor
On Mon, Oct 15, 2018 at 12:34 AM Greg Kroah-Hartman wrote: > > On Sun, Oct 14, 2018 at 09:59:17PM -0700, Todd Poynor wrote: > > From: Todd Poynor > > > > Add debug logs for device enable/disable events, > > Why? > > What is going to need this? As one of the few people actually developing for Ape

Re: [PATCH] of: overlay: user space synchronization

2018-10-15 Thread Alan Tull
On Mon, Oct 15, 2018 at 1:09 PM Frank Rowand wrote: > > On 10/15/18 01:24, Geert Uytterhoeven wrote: > > > > Please say explicitly that tree_version contains a 32-bit unsigned > > decimal number, which is incremented before and after every change. > > I had to deduce that from the code. > > Good p

[PATCH] tty: serial: qcom_geni_serial: Don't slow all ports just for kgdb

2018-10-15 Thread Douglas Anderson
If you turn on CONFIG_KGDB then you'll get CONFIG_CONSOLE_POLL selected. If you have CONFIG_CONSOLE_POLL selected then the GENI serial driver was setting RX_BYTES_PW to 1 for _all_ UART ports. This doesn't seem like such a good idea. Let's only set RX_BYTES_PW to 1 for the console port. Signed-

Re: [PATCH 3/3] perf report: don't crash on invalid inline debug information

2018-10-15 Thread Milian Wolff
On Donnerstag, 11. Oktober 2018 21:39:20 CEST Arnaldo Carvalho de Melo wrote: > Em Thu, Oct 11, 2018 at 08:23:31PM +0200, Milian Wolff escreveu: > > On Donnerstag, 27. September 2018 21:10:37 CEST Arnaldo Carvalho de Melo > > > > wrote: > > > Em Wed, Sep 26, 2018 at 03:52:07PM +0200, Milian Wolff

[PATCH v4 05/13] arch/x86: Introduce a new config parameter RESCTRL

2018-10-15 Thread Moger, Babu
Introduces a new config parameter RESCTRL. This will be used as a common config parameter for both Intel and AMD. Each vendor will have their own config parameter to enable RDT feature. One for Intel(INTEL_RDT) and one for AMD(AMD_QOS). It can be enabled or disabled separately. The new parameter R

[PATCH v4 06/13] arch/x86: Use new config parameter RESCTRL for compilation

2018-10-15 Thread Moger, Babu
Use newly added config parameter RESCTRL to compile sources. This is common parameter across both Intel and AMD. Signed-off-by: Babu Moger --- arch/x86/include/asm/resctrl_sched.h | 4 ++-- arch/x86/kernel/cpu/Makefile | 4 ++-- include/linux/sched.h| 2 +- 3 files change

[PATCH v4 08/13] arch/x86: Bring few more functions into the resource structure

2018-10-15 Thread Moger, Babu
Bring all resource functions that are different between the vendors into resource structure and initialize them dynamically. Add _intel suffix to Intel specific functions. Implement these functions separately for each vendors. update_mba_bw : Feedback loop bandwidth update functionality is not

[PATCH v4 01/13] arch/x86: Start renaming the rdt files to more generic names

2018-10-15 Thread Moger, Babu
New generation of AMD processors start supporting RDT(or QOS) features. With more than one vendors supporting these features, it seems more appropriate to rename these files. Changed intel_rdt to resctrl where applicable. Signed-off-by: Babu Moger --- arch/x86/include/asm/{intel_rdt_sched.h =>

[PATCH v4 04/13] arch/x86: Bring all the macros to resctrl.h

2018-10-15 Thread Moger, Babu
Bring all the macros to resctrl.h and rename for consistency. Signed-off-by: Babu Moger --- arch/x86/kernel/cpu/resctrl.c | 3 --- arch/x86/kernel/cpu/resctrl.h | 5 + arch/x86/kernel/cpu/resctrl_monitor.c | 7 ++- 3 files changed, 7 insertions(+), 8 deletions(-) diff --

[PATCH v4 12/13] Documentation/x86: Rename and update intel_rdt_ui.txt

2018-10-15 Thread Moger, Babu
Rename intel_rdt_ui.txt to generic resctrl_ui.txt and update the documentation for AMD. Signed-off-by: Babu Moger --- Documentation/x86/{intel_rdt_ui.txt => resctrl_ui.txt} | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) rename Documentation/x86/{intel_rdt_ui.txt => resctrl_ui.tx

[PATCH v4 02/13] arch/x86: Rename the RDT functions and definitions

2018-10-15 Thread Moger, Babu
As AMD is starting to support RDT(or QOS) features, rename the RDT functions and definitions to more generic names. Replace intel_rdt to resctrl where applicable. Signed-off-by: Babu Moger --- arch/x86/include/asm/resctrl_sched.h | 24 arch/x86/kernel/cpu/resctrl.c

[PATCH v4 09/13] arch/x86: Introduce new config parameter AMD_QOS

2018-10-15 Thread Moger, Babu
Introduces the new config parameter AMD_QOS. This parameter will be used to enable cache and memory bandwidth allocation and monitoring features on AMD processors. This will enable common config parameter RESCTRL if selected. Signed-off-by: Babu Moger --- arch/x86/Kconfig | 17 -

[PATCH v4 13/13] MAINTAINERS: Update the file and documentation names in arch/x86

2018-10-15 Thread Moger, Babu
Update the MAINTAINERS to reflect the changed file(and documentation) names in arch/x86/kernel/cpu. The file names have changed from intel_rdt* to resctrl*. Signed-off-by: Babu Moger --- MAINTAINERS | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/MAINTAINERS b/MAINTAINE

[PATCH v4 03/13] arch/x86: Re-arrange RDT init code

2018-10-15 Thread Moger, Babu
Separate the call sequence for rdt_quirks and MBA feature. This is in preparation to handle vendor differences in these call sequences. Signed-off-by: Babu Moger --- arch/x86/kernel/cpu/resctrl.c | 29 +++-- 1 file changed, 23 insertions(+), 6 deletions(-) diff --git a/a

[PATCH v4 10/13] arch/x86: Add AMD feature bit X86_FEATURE_MBA in cpuid bits array

2018-10-15 Thread Moger, Babu
From: Sherry Hurwitz The feature bit X86_FEATURE_MBA is detected via CPUID leaf 0x8008 EBX Bit 06. This bit indicates the support of AMD's MBA feature. This feature is supported by both Intel and AMD. But they are detected different CPUID leaves. Signed-off-by: Sherry Hurwitz Signed-off-by

[PATCH v4 07/13] arch/x86: Initialize the resource functions that are different

2018-10-15 Thread Moger, Babu
Initialize the resource functions that are different between the vendors. Some features are initialized differently between the vendors. Add _intel suffix to Intel specific functions. For example, MBA feature varies significantly between Intel and AMD. Separate the initialization of these resource

[PATCH v4 11/13] arch/x86: Introduce QOS feature for AMD

2018-10-15 Thread Moger, Babu
Enables QOS feature on AMD. Following QoS sub-features are supported in AMD if the underlying hardware supports it. - L3 Cache allocation enforcement - L3 Cache occupancy monitoring - L3 Code-Data Prioritization support - Memory Bandwidth Enforcement(Allocation) The specification for this feat

[PATCH v4 00/13] arch/x86: AMD QoS support

2018-10-15 Thread Moger, Babu
This series adds support for AMD64 architectural extensions for Platform Quality of Service. These extensions are intended to provide for the monitoring of the usage of certain system resources by one or more processors and for the separate allocation and enforcement of limits on the use of certain

Re: [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses

2018-10-15 Thread Kees Cook
On Wed, Oct 10, 2018 at 1:08 PM, James Bottomley wrote: > The current code of conduct has an ambiguity in the it considers publishing > private information such as email addresses unacceptable behaviour. Since > the Linux kernel collects and publishes email addresses as part of the patch > proces

Re: Fix 80d20d35af1e ("nohz: Fix local_timer_softirq_pending()") may have revealed another problem

2018-10-15 Thread Heiner Kallweit
On 28.09.2018 15:18, Frederic Weisbecker wrote: > On Thu, Sep 27, 2018 at 06:05:46PM +0200, Thomas Gleixner wrote: >> On Tue, 28 Aug 2018, Frederic Weisbecker wrote: >>> On Fri, Aug 24, 2018 at 07:06:32PM +0200, Heiner Kallweit wrote: I tested it and Frederic is right, it doesn't help. Can it

Re: [PATCH 1/2] splice: don't merge into linked buffers

2018-10-15 Thread Eric Biggers
On Mon, Oct 15, 2018 at 05:04:18PM +0200, Jann Horn wrote: > Before this patch, it was possible for two pipes to affect each other after > data had been transferred between them with tee(): > > > $ cat tee_test.c > > int main(void) { > int pipe_a[2]; > if (pipe(pipe_a)) err(1, "p

Re: [Ksummit-discuss] [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion

2018-10-15 Thread Kees Cook
On Wed, Oct 10, 2018 at 2:04 PM, Luck, Tony wrote: >> the enforcement clause of the new code of conduct. Since there is concern >> that this becomes binding on the release of the 4.19 kernel > > Is there some logic behind that concern? What's magic about the release > of 4.19? Greg KH said 4.19

Re: [PATCH] cpufreq: conservative: Fix requested_freq handling

2018-10-15 Thread Rafael J. Wysocki
On Mon, Oct 15, 2018 at 2:51 PM Waldemar Rymarkiewicz wrote: > > On Mon, 15 Oct 2018 at 13:34, Rafael J. Wysocki wrote: > > > > On Monday, October 15, 2018 11:34:33 AM CEST Waldemar Rymarkiewicz wrote: > > > On Thu, 11 Oct 2018 at 23:10, Rafael J. Wysocki > > > wrote: > > > > > > > > On Tuesday

[PATCH] staging: add nrf24 driver

2018-10-15 Thread Marcin Ciupak
This patch adds driver for Nordic Semiconductor nRF24L01+ radio module. Signed-off-by: Marcin Ciupak --- drivers/staging/Kconfig | 2 + drivers/staging/Makefile | 1 + drivers/staging/nrf24/Kconfig | 16 + drivers/staging/nrf24/Make

Re: [PATCH 1/2] splice: don't merge into linked buffers

2018-10-15 Thread Jann Horn
On Mon, Oct 15, 2018 at 11:00 PM Eric Biggers wrote: > On Mon, Oct 15, 2018 at 05:04:18PM +0200, Jann Horn wrote: > > Before this patch, it was possible for two pipes to affect each other after > > data had been transferred between them with tee(): > > > > > > $ cat tee_test.c > > > >

Re: [PATCH] compiler.h: update definition of unreachable()

2018-10-15 Thread Miguel Ojeda
On Mon, Oct 15, 2018 at 10:13 PM Nick Desaulniers wrote: > > Looking at commit cb984d101b30 ("compiler-gcc: integrate the various > compiler-gcc[345].h files") it seems that the comment is referring to > gcc 4.4 not supporting __builtin_unreachable(). Looks like it was > added in 4.5 timeframe: h

Re: Re: [PATCH v1 1/2] sysctl: cap to ULONG_MAX in proc_get_long()

2018-10-15 Thread Kees Cook
On Mon, Oct 15, 2018 at 12:32 PM, Christian Brauner wrote: > On Mon, Oct 15, 2018 at 9:27 PM Alexey Dobriyan wrote: >> >> > int kstrtoul_bounded(const char *s, unsigned int base, >> > char **trailing, unsigned long long *res) >> >> NO! The whole point is not have million variants of slightly diff

Re: [PATCH v1 2/2] sysctl: handle overflow for file-max

2018-10-15 Thread Kees Cook
On Mon, Oct 15, 2018 at 9:28 AM, Christian Brauner wrote: > On Mon, Oct 15, 2018 at 09:11:51AM -0700, Kees Cook wrote: >> On Mon, Oct 15, 2018 at 3:55 AM, Christian Brauner >> wrote: >> > Currently, when writing >> > >> > echo 18446744073709551616 > /proc/sys/fs/file-max >> > >> > /proc/sys/fs/f

Re: [GIT PULL] clk/samsung updates for 4.20-rc1

2018-10-15 Thread Stephen Boyd
Quoting Sylwester Nawrocki (2018-10-05 04:49:14) > Hi Stephen, Mike, > > The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3: > > Linux 4.19-rc1 (2018-08-26 14:11:59 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Alan Cox
> +/* > + * Returns true if current's euid is same as p's uid or euid, > + * or has CAP_SYS_ADMIN. > + * > + * Called with rcu_read_lock, creds are safe. > + * > + * Adapted from set_one_prio_perm(). > + */ > +static bool set_predump_signal_perm(struct task_struct *p) > +{ > + const struct cred

Re: [PATCH] dt-bindings: misc: bk4: Add device tree binding for Liebherr's BK4 SPI bus

2018-10-15 Thread Lukasz Majewski
Hi All, > On Fri, Sep 28, 2018 at 12:26:55AM +0200, Lukasz Majewski wrote: > > Add Device Tree binding document for Liebherr's BK4 external SPI > > bus. > > > > Signed-off-by: Lukasz Majewski > > --- > > Documentation/devicetree/bindings/misc/lwn-bk4.txt | 26 > > ++ 1 file c

[PATCH] cpufreq: conservative: Take limits changes into account properly

2018-10-15 Thread Rafael J. Wysocki
From: Rafael J. Wysocki If the policy limits change between invocations of cs_dbs_update(), the requested frequency value stored in dbs_info may not be updated and the function may use a stale value of it next time. Moreover, if idle periods are takem into account by cs_dbs_update(), the request

[PATCH] staging: iio: adc: Add comments to prevent checks corrections

2018-10-15 Thread Gabriel Capella
This patch adds 3 comments in 2 different files. These comments warn to don't correct the checks of type: "CHECK: spaces preferred around that '-'" Signed-off-by: Gabriel Capella --- drivers/staging/iio/adc/ad7192.c | 1 + drivers/staging/iio/adc/ad7280a.c | 2 ++ 2 files changed, 3 insertions(

[PATCH] compiler-gcc: remove comment about gcc 4.5 from unreachable()

2018-10-15 Thread ndesaulniers
Remove the comment about being unable to detect __builtin_unreachable. __builtin_unreachable was implemented in the GCC 4.5 timeframe. The kernel's minimum supported version of GCC is 4.6 since commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6"). Commit cb984d101b30 ("compiler-gcc

Re: [PATCH] signal: Mark expected switch fall-throughs

2018-10-15 Thread Kees Cook
On Sat, Oct 13, 2018 at 4:48 AM, Gustavo A. R. Silva wrote: > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > Signed-off-by: Gustavo A. R. Silva Yes, please. :) I love every step closer we get to being able to use -Wimplicit-fall

Re: [PATCH] compat: Mark expected switch fall-throughs

2018-10-15 Thread Kees Cook
On Sat, Oct 13, 2018 at 4:50 AM, Gustavo A. R. Silva wrote: > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > Signed-off-by: Gustavo A. R. Silva Acked-by: Kees Cook -Kees > --- > include/linux/compat.h | 3 +++ > 1 file chang

Re: [PATCH] skbuff: Mark expected switch fall-throughs

2018-10-15 Thread Kees Cook
On Sat, Oct 13, 2018 at 4:56 AM, Gustavo A. R. Silva wrote: > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > Signed-off-by: Gustavo A. R. Silva Acked-by: Kees Cook -Kees > --- > include/linux/skbuff.h | 6 ++ > 1 file ch

Re: [PATCH] kernel/signal: Signal-based pre-coredump notification

2018-10-15 Thread Enke Chen
Hi, Alan: As I replied earlier, I will remove the logic that allows setting on others. This function "set_predump_signal_perm()" will be gone too. Thanks. -- Enke On 10/15/18 2:21 PM, Alan Cox wrote: >> +/* >> + * Returns true if current's euid is same as p's uid or euid, >> + * or has CAP_SYS_

Re: [PATCH v3 2/9] dt-bindings: ti-lmu: Remove LM3697

2018-10-15 Thread Pavel Machek
Hi! > >> Given this one seems to have not really been finished, it's probably > >> okay to make changes in this case. Still, it would be good to see > >> patches structured so that it's obvious we're breaking things. But how > >> the patches are structured doesn't matter until there's some agreeme

Re: [PATCH v2 3/5] clk: lochnagar: Add support for the Cirrus Logic Lochnagar

2018-10-15 Thread Stephen Boyd
Quoting Mark Brown (2018-10-15 09:55:28) > On Mon, Oct 15, 2018 at 09:39:59AM -0700, Stephen Boyd wrote: > > > Ok if there's going to be read/volatile regs and defaults then it makes > > sense to leave the defines in some shared header file, which is > > unfortunate for the independent merge of dr

Re: [PATCH] KEYS: trusted: fix -Wvarags warning

2018-10-15 Thread Nick Desaulniers
On Mon, Oct 15, 2018 at 2:26 AM David Laight wrote: > > From: ndesaulni...@google.com > > Sent: 11 October 2018 21:31 > ... > > by swapping h2 and h3. > > > > security/keys/trusted.c:146:17: warning: passing an object that > > undergoes default > > argument promotion to 'va_start' has undefi

Re: [PATCH 00/14] serial: langtiq: Add CCF suppport

2018-10-15 Thread Paul Burton
Hi Songjun, On Mon, Sep 24, 2018 at 06:27:49PM +0800, Songjun Wu wrote: > This patch series is for adding common clock framework support > for langtiq serial driver, mainly includes: s/langtiq/lantiq/ ... > 1) Add common clock framework support. > 2) Modify the dts file according to the DT conve

Re: [PATCH v3 07/15] platform: goldfish: pipe: Return status from "deinit" since "remove" does not do much

2018-10-15 Thread Roman Kiryanov
> This function can not fail, why are you returning 0 always? That > doesn't make sense. remove in struct platform_driver requires returning something, we have to have "return" somewhere. I think we want to return closer to the place where we do something useful.

Re: [RFC][PATCH] perf: Rewrite core context handling

2018-10-15 Thread Song Liu
> On Oct 15, 2018, at 1:34 AM, Peter Zijlstra wrote: > > On Mon, Oct 15, 2018 at 10:26:06AM +0300, Alexey Budankov wrote: >> Hi, >> >> On 10.10.2018 13:45, Peter Zijlstra wrote: >>> Hi all, >>> >>> There have been various issues and limitations with the way perf uses >>> (task) contexts to t

Re: linux-next: Tree for Oct 15

2018-10-15 Thread Guenter Roeck
an pseries > > > > > boots; big endian works fine. I'll try to bisect later. > > > > > > > > > > ALl ppc qemu tests (including big endian pseries) also generate a > > > > > warning. > > > > > > > > > >

[PATCH 1/2] ARM: copypage-fa: add kto and kfrom to input operands list

2018-10-15 Thread Stefan Agner
When functions incoming parameters are not in input operands list gcc 4.5 does not load the parameters into registers before calling this function but the inline assembly assumes valid addresses inside this function. This breaks the code because r0 and r1 are invalid when execution enters v4wb_copy

[PATCH 0/4] fpga: add managed create functions

2018-10-15 Thread Alan Tull
Hi Greg, Please take these four patches that have been reviewed on the mailing list. They all apply and build cleanly on the current linux-next and char-misc-testing. The first 3 add managed create functions for the FPGA API. The fourth is documentation rework. Alan Alan Tull (4): fpga: mgr

[PATCH 2/4] fpga: bridge: add devm_fpga_bridge_create

2018-10-15 Thread Alan Tull
Add devm_fpga_bridge_create() which is the managed version of fpga_bridge_create(). Change current bridge drivers to use devm_fpga_bridge_create(). Signed-off-by: Alan Tull Suggested-by: Federico Vaga Acked-by: Moritz Fischer --- Documentation/driver-api/fpga/fpga-bridge.rst | 3 ++ drivers/

[PATCH 4/4] docs: fpga: document programming fpgas using regions

2018-10-15 Thread Alan Tull
Clarify the intention that interfaces and upper layers use regions rather than managers directly. Rearrange API documentation to better group the API functions used to create FPGA mgr/bridge/regions and the API used for programming FPGAs. Signed-off-by: Alan Tull Suggested-by: Federico Vaga Ack

[PATCH 3/4] fpga: add devm_fpga_region_create

2018-10-15 Thread Alan Tull
Add devm_fpga_region_create() which is the managed version of fpga_region_create(). Change current region drivers to use devm_fpga_region_create(). Signed-off-by: Alan Tull Suggested-by: Federico Vaga Acked-by: Moritz Fischer --- Documentation/driver-api/fpga/fpga-region.rst | 3 ++ drivers/

<    1   2   3   4   5   6   7   8   9   >