Re: [PATCH v4 2/2] x86/amd: Fixup cpu_core_id for family17h downcore configuration

On Tue, Jul 25, 2017 at 12:51:53PM +0700, Suravee Suthikulpanit wrote: > Ok. Sure, it doesn't need be contiguous. But at least the cpu_core_id should > represent an ID that make some sense since it is used in the > arch/x86/kernel/smpboot.c: match_smt() and some other places. So, if it's > invalid

[PATCH 1/2] remoteproc: qcom: Add support for SSR notifications

This adds the remoteproc part of subsystem restart, which is responsible for emitting notifications to other processors in the system about a dying remoteproc instance. These notifications are propagated to the various communication systems in the various remote processors to shut down

Re: [PATCH v4 2/2] x86/amd: Fixup cpu_core_id for family17h downcore configuration

On Tue, Jul 25, 2017 at 12:51:53PM +0700, Suravee Suthikulpanit wrote: > Ok. Sure, it doesn't need be contiguous. But at least the cpu_core_id should > represent an ID that make some sense since it is used in the > arch/x86/kernel/smpboot.c: match_smt() and some other places. So, if it's > invalid

[PATCH 1/2] remoteproc: qcom: Add support for SSR notifications

This adds the remoteproc part of subsystem restart, which is responsible for emitting notifications to other processors in the system about a dying remoteproc instance. These notifications are propagated to the various communication systems in the various remote processors to shut down

[PATCH 2/2] soc: qcom: GLINK SSR notifier

This driver register as a subsystem restart notifier and will send out notifications to remote processors that has opened the "glink_ssr" GLINK channel. This mechanism is used to signal any GLINK participants that a 3rd party is gone and that the communication state has to be reset; i.e. that

[PATCH 2/2] soc: qcom: GLINK SSR notifier

This driver register as a subsystem restart notifier and will send out notifications to remote processors that has opened the "glink_ssr" GLINK channel. This mechanism is used to signal any GLINK participants that a 3rd party is gone and that the communication state has to be reset; i.e. that

[PATCH 0/2] Qualcomm GLINK SSR support

This adds the common Qualcomm helpers to tie in subsystem restart notifications with the ADSP and Modem PILs and then adds a driver for the "glink_ssr" channel to propagate these notifications. This is needed on GLINK RPM enabled platforms to have the RPM reset the state of the communication

[PATCH 0/2] Qualcomm GLINK SSR support

This adds the common Qualcomm helpers to tie in subsystem restart notifications with the ADSP and Modem PILs and then adds a driver for the "glink_ssr" channel to propagate these notifications. This is needed on GLINK RPM enabled platforms to have the RPM reset the state of the communication

Re: [PATCH v2 1/2] ASoC: sun4i-i2s: Add more quirks for newer SoCs

Hi Markus, On Sat, Jul 22, 2017 at 08:53:51AM +0200, codekip...@gmail.com wrote: > From: Marcus Cooper > > In preparation for changing this driver to support newer SoC > implementations then where needed there has been a switch from > regmap_update_bits to regmap_field.

Re: [PATCH v2 1/2] ASoC: sun4i-i2s: Add more quirks for newer SoCs

Hi Markus, On Sat, Jul 22, 2017 at 08:53:51AM +0200, codekip...@gmail.com wrote: > From: Marcus Cooper > > In preparation for changing this driver to support newer SoC > implementations then where needed there has been a switch from > regmap_update_bits to regmap_field. Also included are

Re: [PATCH v4 2/2] x86/amd: Fixup cpu_core_id for family17h downcore configuration

Boris, On 7/24/17 21:44, Borislav Petkov wrote: On Mon, Jul 24, 2017 at 09:14:18PM +0700, Suravee Suthikulpanit wrote: Actually, this is not totally accurate. My apology. This patch is mainly fix to incorrect core ID in /proc/cpuinfo. So you're "fixing" only some numbering thing. Because

Re: [PATCH v4 2/2] x86/amd: Fixup cpu_core_id for family17h downcore configuration

Boris, On 7/24/17 21:44, Borislav Petkov wrote: On Mon, Jul 24, 2017 at 09:14:18PM +0700, Suravee Suthikulpanit wrote: Actually, this is not totally accurate. My apology. This patch is mainly fix to incorrect core ID in /proc/cpuinfo. So you're "fixing" only some numbering thing. Because

Re: [PATCH v5 2/2] x86/mm: Improve TLB flush documentation

On Mon, Jul 24, 2017 at 9:47 PM, Nadav Amit wrote: > Andy Lutomirski wrote: > >> Improve comments as requested by PeterZ and also add some >> documentation at the top of the file. >> >> Signed-off-by: Andy Lutomirski >> --- >>

Re: [PATCH v5 2/2] x86/mm: Improve TLB flush documentation

On Mon, Jul 24, 2017 at 9:47 PM, Nadav Amit wrote: > Andy Lutomirski wrote: > >> Improve comments as requested by PeterZ and also add some >> documentation at the top of the file. >> >> Signed-off-by: Andy Lutomirski >> --- >> arch/x86/mm/tlb.c | 43 +--

[PATCH 1/5] arm64: dts: qcom: Add RPM glink nodes to msm8996

Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 78 +++ 1 file changed, 78 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi index

[PATCH 4/5] arm64: dts: qcom: msm8996: Specify smd-edge for ADSP

Add the smd-edge node for the adsp, to allow SMD communication with the ADSP. Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi

[PATCH 4/5] arm64: dts: qcom: msm8996: Specify smd-edge for ADSP

Add the smd-edge node for the adsp, to allow SMD communication with the ADSP. Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi

[PATCH 1/5] arm64: dts: qcom: Add RPM glink nodes to msm8996

Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 78 +++ 1 file changed, 78 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi index 8f085716e258..8ebef05e1750 100644 ---

[PATCH 0/5] DB820c DTS dump

A dump of DTS patches for MSM8996 and DB820c, found in the Linaro landing team tree. Bjorn Andersson (3): ARM64: dts: qcom: Add RPM glink nodes to msm8996 arm64: dts: msm8996: Add modem smp2p nodes arm64: dts: qcom: msm8996: Specify smd-edge for ADSP Rajendra Nayak (1): ARM64: dts: qcom:

[PATCH 3/5] arm64: dts: msm8996: Add modem smp2p nodes

Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 24 1 file changed, 24 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi index 8ebef05e1750..7d909546ca24

[PATCH 0/5] DB820c DTS dump

A dump of DTS patches for MSM8996 and DB820c, found in the Linaro landing team tree. Bjorn Andersson (3): ARM64: dts: qcom: Add RPM glink nodes to msm8996 arm64: dts: msm8996: Add modem smp2p nodes arm64: dts: qcom: msm8996: Specify smd-edge for ADSP Rajendra Nayak (1): ARM64: dts: qcom:

[PATCH 3/5] arm64: dts: msm8996: Add modem smp2p nodes

Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 24 1 file changed, 24 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi index 8ebef05e1750..7d909546ca24 100644 ---

[PATCH 5/5] arm64: dts: msm8996: Add QFPROM node

From: Vivek Gautam Signed-off-by: Vivek Gautam Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH 5/5] arm64: dts: msm8996: Add QFPROM node

From: Vivek Gautam Signed-off-by: Vivek Gautam Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi index

[PATCH 2/5] arm64: dts: qcom: db820c: Add pm8994 regulator node

From: Rajendra Nayak Add PM8994 RPM regulators with their min/max voltages to DB820c. Signed-off-by: Rajendra Nayak Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 148

[PATCH 2/5] arm64: dts: qcom: db820c: Add pm8994 regulator node

From: Rajendra Nayak Add PM8994 RPM regulators with their min/max voltages to DB820c. Signed-off-by: Rajendra Nayak Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 148 +++ 1 file changed, 148 insertions(+) diff --git

Re: [RFC Part1 PATCH v3 01/17] Documentation/x86: Add AMD Secure Encrypted Virtualization (SEV) descrption

On Mon, Jul 24, 2017 at 02:07:41PM -0500, Brijesh Singh wrote: Subject: Re: [RFC Part1 PATCH v3 01/17] Documentation/x86: Add AMD Secure Encrypted Virtualization (SEV) descrption ^^

Re: [RFC Part1 PATCH v3 01/17] Documentation/x86: Add AMD Secure Encrypted Virtualization (SEV) descrption

On Mon, Jul 24, 2017 at 02:07:41PM -0500, Brijesh Singh wrote: Subject: Re: [RFC Part1 PATCH v3 01/17] Documentation/x86: Add AMD Secure Encrypted Virtualization (SEV) descrption ^^

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar wrote: > On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel wrote: >> Hi Jassi, >> >> Sorry for the delayed response... >> >> On Fri, Jul 21, 2017 at 9:16 PM, Jassi Brar wrote: >>>

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar wrote: > On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel wrote: >> Hi Jassi, >> >> Sorry for the delayed response... >> >> On Fri, Jul 21, 2017 at 9:16 PM, Jassi Brar wrote: >>> Hi Anup, >>> >>> On Fri, Jul 21, 2017 at 12:25 PM, Anup Patel >>> wrote:

[GIT PULL] s390 fixes for 4.13-rc3

Hi Linus, please pull from the 'for-linus' branch of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus to receive the following updates: Three bug fixes. Christian Borntraeger (2): s390/perf: fix problem state detection s390/mm: set change and

[GIT PULL] s390 fixes for 4.13-rc3

Hi Linus, please pull from the 'for-linus' branch of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus to receive the following updates: Three bug fixes. Christian Borntraeger (2): s390/perf: fix problem state detection s390/mm: set change and

Re: [PATCH v4 0/8] Multibyte memset variations

Matthew Wilcox writes: > From: Matthew Wilcox > > A relatively common idiom we're missing is a function to fill an area > of memory with a pattern which is larger than a single byte. I first > noticed this with a zram patch which wanted to fill a

Re: [PATCH v4 0/8] Multibyte memset variations

Matthew Wilcox writes: > From: Matthew Wilcox > > A relatively common idiom we're missing is a function to fill an area > of memory with a pattern which is larger than a single byte. I first > noticed this with a zram patch which wanted to fill a page with an > 'unsigned long' value. There

Re: [PATCH v2 00/13] mpt3sas driver NVMe support:

Is there any update on these patches ? Thanks, Suganath Prabu S On Fri, Jul 14, 2017 at 6:52 PM, Suganath Prabu S wrote: > Ventura Series controller are Tri-mode. The controller and > firmware are capable of supporting NVMe devices and > PCIe switches to

Re: [linux-next] cpus stalls detected few hours after booting next kernel

On Fri, 2017-06-30 at 17:28 +1000, Nicholas Piggin wrote: > On Fri, 30 Jun 2017 10:52:18 +0530 > Abdul Haleem wrote: > > > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote: > > > On Thu, 29 Jun 2017 20:23:05 +1000 > > > Nicholas Piggin

Re: [PATCH v2 00/13] mpt3sas driver NVMe support:

Is there any update on these patches ? Thanks, Suganath Prabu S On Fri, Jul 14, 2017 at 6:52 PM, Suganath Prabu S wrote: > Ventura Series controller are Tri-mode. The controller and > firmware are capable of supporting NVMe devices and > PCIe switches to be connected with the controller. This >

Re: [linux-next] cpus stalls detected few hours after booting next kernel

On Fri, 2017-06-30 at 17:28 +1000, Nicholas Piggin wrote: > On Fri, 30 Jun 2017 10:52:18 +0530 > Abdul Haleem wrote: > > > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote: > > > On Thu, 29 Jun 2017 20:23:05 +1000 > > > Nicholas Piggin wrote: > > > > > > > On Thu, 29 Jun 2017 19:36:14

Re: [Patch v5 12/12] Documention: v4l: Documentation for HEVC CIDs

On Thu, 2017-07-20 at 18:46 +0300, Stanimir Varbanov wrote: > Hi, > > >>> + > >>> +* - ``V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN`` > >>> + - Main profile. > >> > >> MAIN10? > >> > > No just MAIN. > > I haven't because the MFC does not supported it? > > If so, I think we have to add MAIN10

Re: [Patch v5 12/12] Documention: v4l: Documentation for HEVC CIDs

On Thu, 2017-07-20 at 18:46 +0300, Stanimir Varbanov wrote: > Hi, > > >>> + > >>> +* - ``V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN`` > >>> + - Main profile. > >> > >> MAIN10? > >> > > No just MAIN. > > I haven't because the MFC does not supported it? > > If so, I think we have to add MAIN10

[PATCH 0/4] ARM: sun9i: SMP bring-up with Multi-Cluster Power Management

Hi everyone, This is a partial resend of my sun9i SMP support with MCPM series from over two years ago [1]. Not much has changed since then. We've tried to implement PSCI for both the A80 and A83T. Results were not promising. The issue is that these two chips have a broken security extensions

[PATCH 0/4] ARM: sun9i: SMP bring-up with Multi-Cluster Power Management

Hi everyone, This is a partial resend of my sun9i SMP support with MCPM series from over two years ago [1]. Not much has changed since then. We've tried to implement PSCI for both the A80 and A83T. Results were not promising. The issue is that these two chips have a broken security extensions

[PATCH 4/4] ARM: dts: sun9i: Add PRCM device node for the A80 dtsi

The PRCM is a collection of clock controls, reset controls, and various power switches/gates. Some of these can be independently listed and supported, while a number of CPU related ones are used in tandem with CPUCFG for SMP bringup and CPU hotplugging. Signed-off-by: Chen-Yu Tsai

[PATCH 4/4] ARM: dts: sun9i: Add PRCM device node for the A80 dtsi

The PRCM is a collection of clock controls, reset controls, and various power switches/gates. Some of these can be independently listed and supported, while a number of CPU related ones are used in tandem with CPUCFG for SMP bringup and CPU hotplugging. Signed-off-by: Chen-Yu Tsai ---

[PATCH 3/4] ARM: dts: sun9i: Add CPUCFG device node for A80 dtsi

CPUCFG is a collection of registers that are mapped to the SoC's signals from each individual processor core and associated peripherals, such as resets for processors, L1/L2 cache and other things. These registers are used for SMP bringup and CPU hotplugging. Signed-off-by: Chen-Yu Tsai

[PATCH 1/4] ARM: sun9i: Support SMP on A80 with Multi-Cluster Power Management (MCPM)

The A80 is a big.LITTLE SoC with 1 cluster of 4 Cortex-A7s and 1 cluster of 4 Cortex-A15s. This patch adds support to bring up the second cluster and thus all cores using the common MCPM code. Core/cluster power down has not been implemented, thus CPU hotplugging and big.LITTLE switcher is not

[PATCH 3/4] ARM: dts: sun9i: Add CPUCFG device node for A80 dtsi

CPUCFG is a collection of registers that are mapped to the SoC's signals from each individual processor core and associated peripherals, such as resets for processors, L1/L2 cache and other things. These registers are used for SMP bringup and CPU hotplugging. Signed-off-by: Chen-Yu Tsai ---

[PATCH 1/4] ARM: sun9i: Support SMP on A80 with Multi-Cluster Power Management (MCPM)

The A80 is a big.LITTLE SoC with 1 cluster of 4 Cortex-A7s and 1 cluster of 4 Cortex-A15s. This patch adds support to bring up the second cluster and thus all cores using the common MCPM code. Core/cluster power down has not been implemented, thus CPU hotplugging and big.LITTLE switcher is not

[PATCH 2/4] ARM: dts: sun9i: Add CCI-400 device nodes for A80

The A80 includes an ARM CCI-400 interconnect to support multi-cluster CPU caches. Also add the maximum clock frequency for the CPUs, as listed in the A80 Optimus Board FEX file. Signed-off-by: Chen-Yu Tsai --- arch/arm/boot/dts/sun9i-a80.dtsi | 46

[PATCH 2/4] ARM: dts: sun9i: Add CCI-400 device nodes for A80

The A80 includes an ARM CCI-400 interconnect to support multi-cluster CPU caches. Also add the maximum clock frequency for the CPUs, as listed in the A80 Optimus Board FEX file. Signed-off-by: Chen-Yu Tsai --- arch/arm/boot/dts/sun9i-a80.dtsi | 46 1

Re: [Patch v5 12/12] Documention: v4l: Documentation for HEVC CIDs

On Thu, 2017-07-20 at 16:50 +0200, Hans Verkuil wrote: > On 19/06/17 07:10, Smitha T Murthy wrote: > > Added V4l2 controls for HEVC encoder > > > > Signed-off-by: Smitha T Murthy > > --- > > Documentation/media/uapi/v4l/extended-controls.rst | 364 > >

[PATCH 1/1] usb: xhci: Handle USB transaction error on address command

Xhci driver handles USB transaction errors on transfer events, but transaction errors are possible on address device command completion events as well. The xHCI specification (section 4.6.5) says: A USB Transaction Error Completion Code for an Address Device Command may be due to a Stall response

Re: [Patch v5 12/12] Documention: v4l: Documentation for HEVC CIDs

On Thu, 2017-07-20 at 16:50 +0200, Hans Verkuil wrote: > On 19/06/17 07:10, Smitha T Murthy wrote: > > Added V4l2 controls for HEVC encoder > > > > Signed-off-by: Smitha T Murthy > > --- > > Documentation/media/uapi/v4l/extended-controls.rst | 364 > > + > > 1 file changed,

[PATCH 1/1] usb: xhci: Handle USB transaction error on address command

Xhci driver handles USB transaction errors on transfer events, but transaction errors are possible on address device command completion events as well. The xHCI specification (section 4.6.5) says: A USB Transaction Error Completion Code for an Address Device Command may be due to a Stall response

[PATCH v4] acpi/iort: numa: Add numa node mapping for smmuv3 devices

ARM IORT specification(rev. C) has added provision to define proximity domain in SMMUv3 IORT table. Adding required code to parse Proximity domain and set numa_node of smmv3 platform devices. Add code to parse proximity domain in SMMUv3 IORT table to set numa node mapping for smmuv3 devices.

[PATCH v4] acpi/iort: numa: Add numa node mapping for smmuv3 devices

ARM IORT specification(rev. C) has added provision to define proximity domain in SMMUv3 IORT table. Adding required code to parse Proximity domain and set numa_node of smmv3 platform devices. Add code to parse proximity domain in SMMUv3 IORT table to set numa node mapping for smmuv3 devices.

linux-next: Tree for Jul 25

Hi all, Changes since 20170724: New tree: wberr Non-merge commits (relative to Linus' tree): 2223 2355 files changed, 84862 insertions(+), 43462 deletions(-) I have created today's linux-next tree at git

linux-next: Tree for Jul 25

Hi all, Changes since 20170724: New tree: wberr Non-merge commits (relative to Linus' tree): 2223 2355 files changed, 84862 insertions(+), 43462 deletions(-) I have created today's linux-next tree at git

ERROR: "gen_pool_virt_to_phys" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9 commit: dd55d44f408419278c00887bfcb2261d0caae350 staging: vboxvideo: Add vboxvideo to drivers/staging date: 8 days ago config: i386-randconfig-x071-07241824

Re: bcache with existing ext4 filesystem

On Mon, Jul 24, 2017 at 10:04:51PM +0200, Pavel Machek wrote: > Question for you was... Is the first 1KiB of each ext4 filesystem still > free and "reserved for a bootloader"? Yes. > If I needed more for bcache superblock (8KiB, IIRC), would that be > easy to accomplish on existing filesystem?

ERROR: "gen_pool_virt_to_phys" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9 commit: dd55d44f408419278c00887bfcb2261d0caae350 staging: vboxvideo: Add vboxvideo to drivers/staging date: 8 days ago config: i386-randconfig-x071-07241824

Re: bcache with existing ext4 filesystem

On Mon, Jul 24, 2017 at 10:04:51PM +0200, Pavel Machek wrote: > Question for you was... Is the first 1KiB of each ext4 filesystem still > free and "reserved for a bootloader"? Yes. > If I needed more for bcache superblock (8KiB, IIRC), would that be > easy to accomplish on existing filesystem?

[RESEND PATCH 0/2] userfaultfd: Add feature to request for a signal delivery

Hi Andrea, Mike, Rsending - fixed email address. Here is the patch set for the proposed userfaultfd UFFD_FEATURE_SIGBUS feature, including tests in selftest/vm/userfaultfd.c Please review. See following for previous discussion. http://www.spinics.net/lists/linux-mm/msg129224.html

[RESEND PATCH 1/2] userfaultfd: Add feature to request for a signal delivery

In some cases, userfaultfd mechanism should just deliver a SIGBUS signal to the faulting process, instead of the page-fault event. Dealing with page-fault event using a monitor thread can be an overhead in these cases. For example applications like the database could use the signaling mechanism

[RESEND PATCH 0/2] userfaultfd: Add feature to request for a signal delivery

Hi Andrea, Mike, Rsending - fixed email address. Here is the patch set for the proposed userfaultfd UFFD_FEATURE_SIGBUS feature, including tests in selftest/vm/userfaultfd.c Please review. See following for previous discussion. http://www.spinics.net/lists/linux-mm/msg129224.html

[RESEND PATCH 1/2] userfaultfd: Add feature to request for a signal delivery

In some cases, userfaultfd mechanism should just deliver a SIGBUS signal to the faulting process, instead of the page-fault event. Dealing with page-fault event using a monitor thread can be an overhead in these cases. For example applications like the database could use the signaling mechanism

Re: [PATCH] powerpc/pseries: Fix of_node_put() underflow during pseries remove

Tyrel Datwyler writes: > On 07/24/2017 03:42 AM, Michael Ellerman wrote: >> Laurent Vivier writes: >> >>> As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put() >>> underflow during DLPAR remove"), the call to of_node_put() >>> must

Re: [PATCH] powerpc/pseries: Fix of_node_put() underflow during pseries remove

Tyrel Datwyler writes: > On 07/24/2017 03:42 AM, Michael Ellerman wrote: >> Laurent Vivier writes: >> >>> As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put() >>> underflow during DLPAR remove"), the call to of_node_put() >>> must be removed from pSeries_reconfig_remove_node(). >>>

[RESEND PATCH 2/2] userfaultfd: selftest: Add tests for UFFD_FREATURE_SIGBUS

Signed-off-by: Prakash Sangappa --- tools/testing/selftests/vm/userfaultfd.c | 121 +- 1 files changed, 118 insertions(+), 3 deletions(-) diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c

[RESEND PATCH 2/2] userfaultfd: selftest: Add tests for UFFD_FREATURE_SIGBUS

Signed-off-by: Prakash Sangappa --- tools/testing/selftests/vm/userfaultfd.c | 121 +- 1 files changed, 118 insertions(+), 3 deletions(-) diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c index 1eae79a..6a43e84 100644

Re: [PATCH v5 2/2] x86/mm: Improve TLB flush documentation

Andy Lutomirski wrote: > Improve comments as requested by PeterZ and also add some > documentation at the top of the file. > > Signed-off-by: Andy Lutomirski > --- > arch/x86/mm/tlb.c | 43 +-- > 1 file changed, 33

Re: [PATCH v5 2/2] x86/mm: Improve TLB flush documentation

Andy Lutomirski wrote: > Improve comments as requested by PeterZ and also add some > documentation at the top of the file. > > Signed-off-by: Andy Lutomirski > --- > arch/x86/mm/tlb.c | 43 +-- > 1 file changed, 33 insertions(+), 10 deletions(-) > > diff

[PATCH v5 2/2] x86/mm: Improve TLB flush documentation

Improve comments as requested by PeterZ and also add some documentation at the top of the file. Signed-off-by: Andy Lutomirski --- arch/x86/mm/tlb.c | 43 +-- 1 file changed, 33 insertions(+), 10 deletions(-) diff --git

[PATCH v5 2/2] x86/mm: Improve TLB flush documentation

Improve comments as requested by PeterZ and also add some documentation at the top of the file. Signed-off-by: Andy Lutomirski --- arch/x86/mm/tlb.c | 43 +-- 1 file changed, 33 insertions(+), 10 deletions(-) diff --git a/arch/x86/mm/tlb.c

[PATCH v5 1/2] x86/mm: Try to preserve old TLB entries using PCID

PCID is a "process context ID" -- it's what other architectures call an address space ID. Every non-global TLB entry is tagged with a PCID, only TLB entries that match the currently selected PCID are used, and we can switch PGDs without flushing the TLB. x86's PCID is 12 bits. This is an

[PATCH v5 1/2] x86/mm: Try to preserve old TLB entries using PCID

PCID is a "process context ID" -- it's what other architectures call an address space ID. Every non-global TLB entry is tagged with a PCID, only TLB entries that match the currently selected PCID are used, and we can switch PGDs without flushing the TLB. x86's PCID is 12 bits. This is an

[PATCH v5 0/2] x86/mm: PCID

Here's PCID v5. Changes from v4: - Remove smp_mb__after_atomic() (Peterz) - Rebase, which involved tiny fixups due to SME - Add the doc patch, as promised Andy Lutomirski (2): x86/mm: Try to preserve old TLB entries using PCID x86/mm: Improve TLB flush documentation

[PATCH v5 0/2] x86/mm: PCID

Here's PCID v5. Changes from v4: - Remove smp_mb__after_atomic() (Peterz) - Rebase, which involved tiny fixups due to SME - Add the doc patch, as promised Andy Lutomirski (2): x86/mm: Try to preserve old TLB entries using PCID x86/mm: Improve TLB flush documentation

Re: [PATCH 1/2] net: ethernet: ti: cpts: convert to use kthread_worker

On Mon, Jul 24, 2017 at 07:34:38PM -0500, Grygorii Strashko wrote: > Below if pure TBD/RFC version of patch which add kthread worker to PTP core. > I'm sending it to get you opinion about implementation in general, before > continue with more changes. Pls, take a look if you have time? > - are

Re: [PATCH 1/2] net: ethernet: ti: cpts: convert to use kthread_worker

On Mon, Jul 24, 2017 at 07:34:38PM -0500, Grygorii Strashko wrote: > Below if pure TBD/RFC version of patch which add kthread worker to PTP core. > I'm sending it to get you opinion about implementation in general, before > continue with more changes. Pls, take a look if you have time? > - are

Re: [PATCH -tip] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Hi Masami, [auto build test ERROR on tip/x86/core] [also build test ERROR on v4.13-rc2 next-20170724] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Masami-Hiramatsu/kprobes-x86-Do-not-jump

Re: [PATCH -tip] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Hi Masami, [auto build test ERROR on tip/x86/core] [also build test ERROR on v4.13-rc2 next-20170724] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Masami-Hiramatsu/kprobes-x86-Do-not-jump

Re: [PATCH tip/core/rcu 4/5] sys_membarrier: Add expedited option

On Mon, Jul 24, 2017 at 02:58:16PM -0700, Paul E. McKenney wrote: > The sys_membarrier() system call has proven too slow for some use > cases, which has prompted users to instead rely on TLB shootdown. > Although TLB shootdown is much faster, it has the slight disadvantage > of not working at all

Re: [PATCH tip/core/rcu 4/5] sys_membarrier: Add expedited option

On Mon, Jul 24, 2017 at 02:58:16PM -0700, Paul E. McKenney wrote: > The sys_membarrier() system call has proven too slow for some use > cases, which has prompted users to instead rely on TLB shootdown. > Although TLB shootdown is much faster, it has the slight disadvantage > of not working at all

Re: [PATCH] efifb: allow user to disable write combined mapping.

On 19 July 2017 at 00:34, Peter Jones wrote: > On Tue, Jul 18, 2017 at 04:09:09PM +1000, Dave Airlie wrote: >> This patch allows the user to disable write combined mapping >> of the efifb framebuffer console using an nowc option. >> >> A customer noticed major slowdowns while

Re: [PATCH] efifb: allow user to disable write combined mapping.

On 19 July 2017 at 00:34, Peter Jones wrote: > On Tue, Jul 18, 2017 at 04:09:09PM +1000, Dave Airlie wrote: >> This patch allows the user to disable write combined mapping >> of the efifb framebuffer console using an nowc option. >> >> A customer noticed major slowdowns while logging to the

Re: [PATCH] xen: allocate page for shared info page from low memory

On 07/23/2017 04:25 PM, Boris Ostrovsky wrote: On 06/14/2017 01:11 PM, Juergen Gross wrote: On 14/06/17 18:58, Boris Ostrovsky wrote: On 06/12/2017 07:53 AM, Juergen Gross wrote: In a HVM guest the kernel allocates the page for mapping the shared info structure via extend_brk() today.

Re: [PATCH] xen: allocate page for shared info page from low memory

On 07/23/2017 04:25 PM, Boris Ostrovsky wrote: On 06/14/2017 01:11 PM, Juergen Gross wrote: On 14/06/17 18:58, Boris Ostrovsky wrote: On 06/12/2017 07:53 AM, Juergen Gross wrote: In a HVM guest the kernel allocates the page for mapping the shared info structure via extend_brk() today.

Re: [PATCH] mm: Always flush VMA ranges affected by zap_page_range

Hi Mel, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.13-rc2 next-20170724] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Mel-Gorman/mm-Always-flush-VMA-ranges-affected

Re: [PATCH] mm: Always flush VMA ranges affected by zap_page_range

Hi Mel, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.13-rc2 next-20170724] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Mel-Gorman/mm-Always-flush-VMA-ranges-affected

Re: [PATCH v2] ovl: drop CAP_SYS_RESOURCE from saved mounter's credentials

On Mon, Jul 24, 2017 at 10:15:22AM +0200, Miklos Szeredi wrote: > On Sat, Jul 22, 2017 at 11:30 AM, Amir Goldstein wrote: > > Bumped into this patch (Now upstream commit 51f8f3c4e225) and realized > > it is missing cc: stable # v4.8 > > > > At least this docker PR suggests

Re: [PATCH v2] ovl: drop CAP_SYS_RESOURCE from saved mounter's credentials

On Mon, Jul 24, 2017 at 10:15:22AM +0200, Miklos Szeredi wrote: > On Sat, Jul 22, 2017 at 11:30 AM, Amir Goldstein wrote: > > Bumped into this patch (Now upstream commit 51f8f3c4e225) and realized > > it is missing cc: stable # v4.8 > > > > At least this docker PR suggests that regression

Re: RCU stall warnings...

Hi Dave, On Mon, 24 Jul 2017 16:34:58 -0700 (PDT) David Miller wrote: > > Shoing my ignorance as well, after reading this, for some reason this > commit below sticks out to me. Maybe I should do a bisect and see if > it lands on this commit. > > That would take a while as

Re: RCU stall warnings...

Hi Dave, On Mon, 24 Jul 2017 16:34:58 -0700 (PDT) David Miller wrote: > > Shoing my ignorance as well, after reading this, for some reason this > commit below sticks out to me. Maybe I should do a bisect and see if > it lands on this commit. > > That would take a while as it's hard to

Re: [PATCH 2/2] dma: Add Spreadtrum DMA controller driver

On Mon, Jul 24, 2017 at 02:46:00PM +0800, Baolin Wang wrote: > Hi, > > On 六, 7月 22, 2017 at 01:27:31下午 +0530, Vinod Koul wrote: > > On Tue, Jul 18, 2017 at 03:06:12PM +0800, Baolin Wang wrote: > > > +static void sprd_dma_set_uid(struct sprd_dma_chn *mchan) > > > +{ > > > + struct sprd_dma_dev

Re: [PATCH 2/2] dma: Add Spreadtrum DMA controller driver

On Mon, Jul 24, 2017 at 02:46:00PM +0800, Baolin Wang wrote: > Hi, > > On 六, 7月 22, 2017 at 01:27:31下午 +0530, Vinod Koul wrote: > > On Tue, Jul 18, 2017 at 03:06:12PM +0800, Baolin Wang wrote: > > > +static void sprd_dma_set_uid(struct sprd_dma_chn *mchan) > > > +{ > > > + struct sprd_dma_dev

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Monday 24 July 2017 11:54 PM, Rob Herring wrote: > On Tue, Jul 18, 2017 at 04:27:15PM +0530, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy >> --- >> Documentation/devicetree/bindings/gpio/gpio-davinci.txt | 3 ++- >>

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Monday 24 July 2017 11:54 PM, Rob Herring wrote: > On Tue, Jul 18, 2017 at 04:27:15PM +0530, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy >> --- >> Documentation/devicetree/bindings/gpio/gpio-davinci.txt | 3 ++- >>

Re: [lkp-robot] [x86/refcount] b631e535c6: WARNING:at_net/netlink/af_netlink.c:#netlink_sock_destruct

On Mon, Jul 24, 2017 at 6:03 AM, Hans Liljestrand wrote: > On Sun, Jul 23, 2017 at 08:52:53PM -0700, Kees Cook wrote: >> >> Is 14afee4b6092f ("net: convert sock.sk_wmem_alloc from atomic_t to >> refcount_t") correct? That looks like a statistics counter, not a >>

Re: [lkp-robot] [x86/refcount] b631e535c6: WARNING:at_net/netlink/af_netlink.c:#netlink_sock_destruct

On Mon, Jul 24, 2017 at 6:03 AM, Hans Liljestrand wrote: > On Sun, Jul 23, 2017 at 08:52:53PM -0700, Kees Cook wrote: >> >> Is 14afee4b6092f ("net: convert sock.sk_wmem_alloc from atomic_t to >> refcount_t") correct? That looks like a statistics counter, not a >> refcounter? I can't quite tell,

  1   2   3   4   5   6   7   8   9   10   >