Re: [PATCH] time: Avoid signed overflow in timekeeping_delta_to_ns()

On 14/11/2016 20:42, Chris Metcalf wrote: > This bugfix was originally made in commit 35a4933a8959 ("time: > Avoid signed overflow in timekeeping_get_ns()"). When the code was > refactored in commit 6bd58f09e1d8 ("time: Add cycles to nanoseconds > translation") the signed overflow fix was lost.

Re: [PATCH] time: Avoid signed overflow in timekeeping_delta_to_ns()

On 14/11/2016 20:42, Chris Metcalf wrote: > This bugfix was originally made in commit 35a4933a8959 ("time: > Avoid signed overflow in timekeeping_get_ns()"). When the code was > refactored in commit 6bd58f09e1d8 ("time: Add cycles to nanoseconds > translation") the signed overflow fix was lost.

Re: [PATCH 1/2] Staging: fsl-mc: include: mc: Kernel type 's16' preferred over 'int16_t'

-Original Message- From: Dan Carpenter [mailto:dan.carpen...@oracle.com] Sent: Monday, November 14, 2016 4:06 AM To: Stuart Yoder Cc: Shiva Kerdel ; de...@driverdev.osuosl.org; gre...@linuxfoundation.org; linux- ker...@vger.kernel.org; Nipun Gupta

Re: [PATCH 1/2] Staging: fsl-mc: include: mc: Kernel type 's16' preferred over 'int16_t'

-Original Message- From: Dan Carpenter [mailto:dan.carpen...@oracle.com] Sent: Monday, November 14, 2016 4:06 AM To: Stuart Yoder Cc: Shiva Kerdel ; de...@driverdev.osuosl.org; gre...@linuxfoundation.org; linux- ker...@vger.kernel.org; Nipun Gupta ; tred...@nvidia.com; Laurentiu

Re: [PATCH RFC tip/core/rcu] SRCU rewrite

On Mon, Nov 14, 2016 at 10:36:36AM -0800, Paul E. McKenney wrote: > SRCU uses two per-cpu counters: a nesting counter to count the number of > active critical sections, and a sequence counter to ensure that the nesting > counters don't change while they are being added together in >

Re: [PATCH RFC tip/core/rcu] SRCU rewrite

On Mon, Nov 14, 2016 at 10:36:36AM -0800, Paul E. McKenney wrote: > SRCU uses two per-cpu counters: a nesting counter to count the number of > active critical sections, and a sequence counter to ensure that the nesting > counters don't change while they are being added together in >

[PATCH] [media] ir-hix5hd2: make hisilicon,power-syscon property deprecated

From: Ruqiang Ju The clock of IR can be provided by the clock provider and controlled by common clock framework APIs. Signed-off-by: Ruqiang Ju Signed-off-by: Jiancheng Xue ---

[PATCH] [media] ir-hix5hd2: make hisilicon,power-syscon property deprecated

From: Ruqiang Ju The clock of IR can be provided by the clock provider and controlled by common clock framework APIs. Signed-off-by: Ruqiang Ju Signed-off-by: Jiancheng Xue --- .../devicetree/bindings/media/hix5hd2-ir.txt | 6 +++--- drivers/media/rc/ir-hix5hd2.c

Re: [RFC][PATCH 5/7] kref: Implement kref_put_lock()

On Mon, Nov 14, 2016 at 12:35:48PM -0800, Kees Cook wrote: > On Mon, Nov 14, 2016 at 9:39 AM, Peter Zijlstra wrote: > > Because home-rolling your own is _awesome_, stop doing it. Provide > > kref_put_lock(), just like kref_put_mutex() but for a spinlock. > > > >

Re: [RFC][PATCH 5/7] kref: Implement kref_put_lock()

On Mon, Nov 14, 2016 at 12:35:48PM -0800, Kees Cook wrote: > On Mon, Nov 14, 2016 at 9:39 AM, Peter Zijlstra wrote: > > Because home-rolling your own is _awesome_, stop doing it. Provide > > kref_put_lock(), just like kref_put_mutex() but for a spinlock. > > > > Signed-off-by: Peter Zijlstra

Re: [RFC][PATCH 0/7] kref improvements

On Tue, Nov 15, 2016 at 08:27:42AM +0100, Greg KH wrote: > On Mon, Nov 14, 2016 at 06:39:46PM +0100, Peter Zijlstra wrote: > > This series unfscks kref and then implements it in terms of refcount_t. > > > > x86_64-allyesconfig compile tested and boot tested with my regular config. > > > >

Re: [RFC][PATCH 0/7] kref improvements

On Tue, Nov 15, 2016 at 08:27:42AM +0100, Greg KH wrote: > On Mon, Nov 14, 2016 at 06:39:46PM +0100, Peter Zijlstra wrote: > > This series unfscks kref and then implements it in terms of refcount_t. > > > > x86_64-allyesconfig compile tested and boot tested with my regular config. > > > >

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Tue, Nov 15, 2016 at 08:28:55AM +0100, Greg KH wrote: > On Mon, Nov 14, 2016 at 10:16:55AM -0800, Christoph Hellwig wrote: > > On Mon, Nov 14, 2016 at 06:39:48PM +0100, Peter Zijlstra wrote: > > > Since we need to change the implementation, stop exposing internals. > > > > > > Provide

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Tue, Nov 15, 2016 at 08:28:55AM +0100, Greg KH wrote: > On Mon, Nov 14, 2016 at 10:16:55AM -0800, Christoph Hellwig wrote: > > On Mon, Nov 14, 2016 at 06:39:48PM +0100, Peter Zijlstra wrote: > > > Since we need to change the implementation, stop exposing internals. > > > > > > Provide

Re: [RFC][PATCH 0/7] kref improvements

* Greg KH wrote: > On Mon, Nov 14, 2016 at 06:39:46PM +0100, Peter Zijlstra wrote: > > This series unfscks kref and then implements it in terms of refcount_t. > > > > x86_64-allyesconfig compile tested and boot tested with my regular config. > > > > refcount_t is

Re: [RFC][PATCH 0/7] kref improvements

* Greg KH wrote: > On Mon, Nov 14, 2016 at 06:39:46PM +0100, Peter Zijlstra wrote: > > This series unfscks kref and then implements it in terms of refcount_t. > > > > x86_64-allyesconfig compile tested and boot tested with my regular config. > > > > refcount_t is as per the previous thread,

Re: [PATCH v2] tile: handle __ro_after_init like parisc does

On Mon, Nov 14, 2016 at 01:12:05PM -0800, Kees Cook wrote: > At some point here, I want to collect all the arch maintainers and > discuss the options for correctly reflecting the three data > memory-protection needs we have: > > - always read-only > - read-only after init > - read-only except

Re: [PATCH v2] tile: handle __ro_after_init like parisc does

On Mon, Nov 14, 2016 at 01:12:05PM -0800, Kees Cook wrote: > At some point here, I want to collect all the arch maintainers and > discuss the options for correctly reflecting the three data > memory-protection needs we have: > > - always read-only > - read-only after init > - read-only except

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 15/11/16 08:15, Jan Beulich wrote: On 15.11.16 at 07:33, wrote: >> On 15/11/16 01:11, Alex Thorlton wrote: >>> Hey everyone, >>> >>> We're having problems with large systems hitting a BUG in >>> xen_memory_setup, due to extra e820 entries created in the >>>

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 15/11/16 08:15, Jan Beulich wrote: On 15.11.16 at 07:33, wrote: >> On 15/11/16 01:11, Alex Thorlton wrote: >>> Hey everyone, >>> >>> We're having problems with large systems hitting a BUG in >>> xen_memory_setup, due to extra e820 entries created in the >>> XENMEM_machine_memory_map

Re: Linux 4.4.32

diff --git a/Makefile b/Makefile index 7c6f28e7a2f6..fba9b09a1330 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 31 +SUBLEVEL = 32 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/mips/kvm/emulate.c b/arch/mips/kvm/emulate.c index

Re: Linux 4.4.32

diff --git a/Makefile b/Makefile index 7c6f28e7a2f6..fba9b09a1330 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 31 +SUBLEVEL = 32 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/mips/kvm/emulate.c b/arch/mips/kvm/emulate.c index

Linux 4.8.8

I'm announcing the release of the 4.8.8 kernel. All users of the 4.8 kernel series must upgrade. The updated 4.8.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.8.y and can be browsed at the normal kernel.org git web browser:

Linux 4.8.8

I'm announcing the release of the 4.8.8 kernel. All users of the 4.8 kernel series must upgrade. The updated 4.8.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.8.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.32

I'm announcing the release of the 4.4.32 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.8.8

diff --git a/Makefile b/Makefile index 4d0f28cb481d..8f18daa2c76a 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 8 -SUBLEVEL = 7 +SUBLEVEL = 8 EXTRAVERSION = NAME = Psychotic Stoned Sheep diff --git a/arch/powerpc/include/asm/checksum.h

Linux 4.4.32

I'm announcing the release of the 4.4.32 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.8.8

diff --git a/Makefile b/Makefile index 4d0f28cb481d..8f18daa2c76a 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 8 -SUBLEVEL = 7 +SUBLEVEL = 8 EXTRAVERSION = NAME = Psychotic Stoned Sheep diff --git a/arch/powerpc/include/asm/checksum.h

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1)

* Namhyung Kim wrote: > > > By default it shows the individual schedule events, including the time > > > between > > > sched-in events for the task, the task scheduling delay (time between > > > wakeup > > > and actually running) and run time for the task: > > > > > >

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1)

* Namhyung Kim wrote: > > > By default it shows the individual schedule events, including the time > > > between > > > sched-in events for the task, the task scheduling delay (time between > > > wakeup > > > and actually running) and run time for the task: > > > > > >time cpu

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Mon, Nov 14, 2016 at 06:39:48PM +0100, Peter Zijlstra wrote: > Since we need to change the implementation, stop exposing internals. > > Provide kref_read() to read the current reference count; typically > used for debug messages. > > Kills two anti-patterns: > > atomic_read(>refcount)

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Mon, Nov 14, 2016 at 06:39:48PM +0100, Peter Zijlstra wrote: > Since we need to change the implementation, stop exposing internals. > > Provide kref_read() to read the current reference count; typically > used for debug messages. > > Kills two anti-patterns: > > atomic_read(>refcount)

[PATCH] reset: hisilicon: add a polarity cell for reset line specifier

Add a polarity cell for reset line specifier. If the reset line is asserted when the register bit is 1, the polarity is normal. Otherwise, it is inverted. Signed-off-by: Jiancheng Xue --- .../devicetree/bindings/clock/hisi-crg.txt | 11 ---

Re: [RFC][PATCH 0/7] kref improvements

On Mon, Nov 14, 2016 at 06:39:46PM +0100, Peter Zijlstra wrote: > This series unfscks kref and then implements it in terms of refcount_t. > > x86_64-allyesconfig compile tested and boot tested with my regular config. > > refcount_t is as per the previous thread, it BUGs on over-/underflow and >

Re: [RFC][PATCH 0/7] kref improvements

On Mon, Nov 14, 2016 at 06:39:46PM +0100, Peter Zijlstra wrote: > This series unfscks kref and then implements it in terms of refcount_t. > > x86_64-allyesconfig compile tested and boot tested with my regular config. > > refcount_t is as per the previous thread, it BUGs on over-/underflow and >

[PATCH] reset: hisilicon: add a polarity cell for reset line specifier

Add a polarity cell for reset line specifier. If the reset line is asserted when the register bit is 1, the polarity is normal. Otherwise, it is inverted. Signed-off-by: Jiancheng Xue --- .../devicetree/bindings/clock/hisi-crg.txt | 11 --- arch/arm/boot/dts/hi3519.dtsi

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Mon, Nov 14, 2016 at 10:16:55AM -0800, Christoph Hellwig wrote: > On Mon, Nov 14, 2016 at 06:39:48PM +0100, Peter Zijlstra wrote: > > Since we need to change the implementation, stop exposing internals. > > > > Provide kref_read() to read the current reference count; typically > > used for

Re: [PATCH v3] mmc: sdhci-of-esdhc: fixup PRESENT_STATE read

On Monday 14 November 2016 16:12:27, Michael Walle wrote: > Since commit 87a18a6a5652 ("mmc: mmc: Use ->card_busy() to detect busy > cards in __mmc_switch()") the ESDHC driver is broken: > mmc0: Card stuck in programming state! __mmc_switch > mmc0: error -110 whilst initialising MMC card > >

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Mon, Nov 14, 2016 at 10:16:55AM -0800, Christoph Hellwig wrote: > On Mon, Nov 14, 2016 at 06:39:48PM +0100, Peter Zijlstra wrote: > > Since we need to change the implementation, stop exposing internals. > > > > Provide kref_read() to read the current reference count; typically > > used for

Re: [PATCH v3] mmc: sdhci-of-esdhc: fixup PRESENT_STATE read

On Monday 14 November 2016 16:12:27, Michael Walle wrote: > Since commit 87a18a6a5652 ("mmc: mmc: Use ->card_busy() to detect busy > cards in __mmc_switch()") the ESDHC driver is broken: > mmc0: Card stuck in programming state! __mmc_switch > mmc0: error -110 whilst initialising MMC card > >

[PATCH] perf/ring_buffer: Fix invalid page order

In rb_alloc_aux_page(), a page order is set to MAX_ORDER when order is greater than MAX_ORDER, but page order should be less than MAX_ORDER, therefore alloc_pages_node fails at least once. This patch fixes page order so that it can be always less than MAX_ORDER. Signed-off-by: Takao Indoh

[PATCH] perf/ring_buffer: Fix invalid page order

In rb_alloc_aux_page(), a page order is set to MAX_ORDER when order is greater than MAX_ORDER, but page order should be less than MAX_ORDER, therefore alloc_pages_node fails at least once. This patch fixes page order so that it can be always less than MAX_ORDER. Signed-off-by: Takao Indoh ---

Re: [PATCH v11 10/22] vfio iommu type1: Add support for mediated devices

On 15/11/16 17:33, Kirti Wankhede wrote: > > > On 11/15/2016 10:47 AM, Alexey Kardashevskiy wrote: >> On 08/11/16 17:52, Alexey Kardashevskiy wrote: >>> On 05/11/16 08:10, Kirti Wankhede wrote: VFIO IOMMU drivers are designed for the devices which are IOMMU capable. Mediated device

Re: [PATCH v11 10/22] vfio iommu type1: Add support for mediated devices

On 15/11/16 17:33, Kirti Wankhede wrote: > > > On 11/15/2016 10:47 AM, Alexey Kardashevskiy wrote: >> On 08/11/16 17:52, Alexey Kardashevskiy wrote: >>> On 05/11/16 08:10, Kirti Wankhede wrote: VFIO IOMMU drivers are designed for the devices which are IOMMU capable. Mediated device

Re: Patch procedure

On Mon, Nov 14, 2016 at 12:16:08PM -0500, feas wrote: > Here is how I am going about making the patches. It is basically > what I have picked up from kernel newbies among other sites > and videos on making patches. I would be greatful for any > pointers on what seems to be the problem(s) with why

Re: Patch procedure

On Mon, Nov 14, 2016 at 12:16:08PM -0500, feas wrote: > Here is how I am going about making the patches. It is basically > what I have picked up from kernel newbies among other sites > and videos on making patches. I would be greatful for any > pointers on what seems to be the problem(s) with why

Re: [PATCH v3] mmc: sdhci-of-esdhc: fixup PRESENT_STATE read

On 14/11/16 17:12, Michael Walle wrote: > Since commit 87a18a6a5652 ("mmc: mmc: Use ->card_busy() to detect busy > cards in __mmc_switch()") the ESDHC driver is broken: > mmc0: Card stuck in programming state! __mmc_switch > mmc0: error -110 whilst initialising MMC card > > Since this commit

Re: [PATCH v3] mmc: sdhci-of-esdhc: fixup PRESENT_STATE read

On 14/11/16 17:12, Michael Walle wrote: > Since commit 87a18a6a5652 ("mmc: mmc: Use ->card_busy() to detect busy > cards in __mmc_switch()") the ESDHC driver is broken: > mmc0: Card stuck in programming state! __mmc_switch > mmc0: error -110 whilst initialising MMC card > > Since this commit

Re: [Intel-gfx] [PATCH v11 3/4] drm/i915: Use new CRC debugfs API

On Mon, Nov 14, 2016 at 12:44:25PM +0200, Jani Nikula wrote: > On Thu, 06 Oct 2016, Tomeu Vizoso wrote: > > diff --git a/drivers/gpu/drm/i915/intel_display.c > > b/drivers/gpu/drm/i915/intel_display.c > > index 23a6c7213eca..7412a05fa5d9 100644 > > ---

Re: [Intel-gfx] [PATCH v11 3/4] drm/i915: Use new CRC debugfs API

On Mon, Nov 14, 2016 at 12:44:25PM +0200, Jani Nikula wrote: > On Thu, 06 Oct 2016, Tomeu Vizoso wrote: > > diff --git a/drivers/gpu/drm/i915/intel_display.c > > b/drivers/gpu/drm/i915/intel_display.c > > index 23a6c7213eca..7412a05fa5d9 100644 > > --- a/drivers/gpu/drm/i915/intel_display.c > >

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

>>> On 15.11.16 at 07:33, wrote: > On 15/11/16 01:11, Alex Thorlton wrote: >> Hey everyone, >> >> We're having problems with large systems hitting a BUG in >> xen_memory_setup, due to extra e820 entries created in the >> XENMEM_machine_memory_map callback. The change in the

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

>>> On 15.11.16 at 07:33, wrote: > On 15/11/16 01:11, Alex Thorlton wrote: >> Hey everyone, >> >> We're having problems with large systems hitting a BUG in >> xen_memory_setup, due to extra e820 entries created in the >> XENMEM_machine_memory_map callback. The change in the patch gets things >>

Re: [PATHCv10 1/2] usb: USB Type-C connector class

On Mon, Nov 14, 2016 at 12:46:50PM -0800, Guenter Roeck wrote: > On Mon, Nov 14, 2016 at 02:32:35PM +0200, Heikki Krogerus wrote: > > Hi Greg, > > > > On Mon, Nov 14, 2016 at 10:51:48AM +0100, Greg KH wrote: > > > On Mon, Sep 19, 2016 at 02:16:56PM +0300, Heikki Krogerus wrote: > > > > The

Re: [PATHCv10 1/2] usb: USB Type-C connector class

On Mon, Nov 14, 2016 at 12:46:50PM -0800, Guenter Roeck wrote: > On Mon, Nov 14, 2016 at 02:32:35PM +0200, Heikki Krogerus wrote: > > Hi Greg, > > > > On Mon, Nov 14, 2016 at 10:51:48AM +0100, Greg KH wrote: > > > On Mon, Sep 19, 2016 at 02:16:56PM +0300, Heikki Krogerus wrote: > > > > The

RE: [PATCH net-next v5] cadence: Add LSO support.

> > > If UFO is in use it should not silently disable UDP checksums. > > > > > > If you cannot support UFO with proper checksumming, then you cannot > > > enable support for that feature. > > > > According Cadence Gigabit Ethernet MAC documentation: > > > > "Hardware will not calculate the UDP

RE: [PATCH net-next v5] cadence: Add LSO support.

> > > If UFO is in use it should not silently disable UDP checksums. > > > > > > If you cannot support UFO with proper checksumming, then you cannot > > > enable support for that feature. > > > > According Cadence Gigabit Ethernet MAC documentation: > > > > "Hardware will not calculate the UDP

Re: [PATCH v7 2/5] mm: remove x86-only restriction of movable_node

Reza Arbab writes: > In commit c5320926e370 ("mem-hotplug: introduce movable_node boot > option"), the memblock allocation direction is changed to bottom-up and > then back to top-down like this: > > 1. memblock_set_bottom_up(true), called by

Re: [PATCH v7 2/5] mm: remove x86-only restriction of movable_node

Reza Arbab writes: > In commit c5320926e370 ("mem-hotplug: introduce movable_node boot > option"), the memblock allocation direction is changed to bottom-up and > then back to top-down like this: > > 1. memblock_set_bottom_up(true), called by cmdline_parse_movable_node(). > 2.

[PATCH] lkdtm: Prevent the compiler from optimising lkdtm_CORRUPT_STACK()

At least on powerpc with GCC 6, the compiler is smart enough to optimise lkdtm_CORRUPT_STACK() into an empty function that just returns. If we print the buffer after we've written to it that prevents the compiler from optimising away data and the memset(). Signed-off-by: Michael Ellerman

Re: [PATCH] thermal/powerclamp: add back module device table

On Mon, Nov 14, 2016 at 11:08:45AM -0800, Jacob Pan wrote: > Commit 3105f234e0aba43e44e277c20f9b32ee8add43d4 replaced module > cpu id table with a cpu feature check, which is logically correct. > But we need the module device table to allow module auto loading. > > Fixes:3105f234

[PATCH] lkdtm: Prevent the compiler from optimising lkdtm_CORRUPT_STACK()

At least on powerpc with GCC 6, the compiler is smart enough to optimise lkdtm_CORRUPT_STACK() into an empty function that just returns. If we print the buffer after we've written to it that prevents the compiler from optimising away data and the memset(). Signed-off-by: Michael Ellerman ---

Re: [PATCH] thermal/powerclamp: add back module device table

On Mon, Nov 14, 2016 at 11:08:45AM -0800, Jacob Pan wrote: > Commit 3105f234e0aba43e44e277c20f9b32ee8add43d4 replaced module > cpu id table with a cpu feature check, which is logically correct. > But we need the module device table to allow module auto loading. > > Fixes:3105f234

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1)

Hi Ingo, On Tue, Nov 15, 2016 at 07:42:14AM +0100, Ingo Molnar wrote: > > * Namhyung Kim wrote: > > > Hello, > > > > This patchset is a rebased version of David's sched timehist work [1]. > > I plan to improve perf sched command more and think that having > > timehist

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1)

Hi Ingo, On Tue, Nov 15, 2016 at 07:42:14AM +0100, Ingo Molnar wrote: > > * Namhyung Kim wrote: > > > Hello, > > > > This patchset is a rebased version of David's sched timehist work [1]. > > I plan to improve perf sched command more and think that having > > timehist command before the work

[PATCH] clk: qcom: smd-rpm: Add msm8974 clocks

This adds all RPM based clocks for msm8974 except cxo and gfx3d_clk_src. Signed-off-by: Bjorn Andersson --- .../devicetree/bindings/clock/qcom,rpmcc.txt | 1 + drivers/clk/qcom/clk-smd-rpm.c | 71 ++

[PATCH] clk: qcom: smd-rpm: Add msm8974 clocks

This adds all RPM based clocks for msm8974 except cxo and gfx3d_clk_src. Signed-off-by: Bjorn Andersson --- .../devicetree/bindings/clock/qcom,rpmcc.txt | 1 + drivers/clk/qcom/clk-smd-rpm.c | 71 ++ include/dt-bindings/clock/qcom,rpmcc.h

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

On Tue, Nov 15, 2016 at 1:47 AM, Tony Lindgren wrote: > 8< > From tony Mon Sep 17 00:00:00 2001 > From: Tony Lindgren > Date: Tue, 25 Oct 2016 08:33:35 -0700 > Subject: [PATCH] pinctrl: core: Use delayed work for hogs > >

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

On Tue, Nov 15, 2016 at 1:47 AM, Tony Lindgren wrote: > 8< > From tony Mon Sep 17 00:00:00 2001 > From: Tony Lindgren > Date: Tue, 25 Oct 2016 08:33:35 -0700 > Subject: [PATCH] pinctrl: core: Use delayed work for hogs > > Having the pin control framework call

Re: [PATCH v12 12/22] vfio: Add notifier callback to parent's ops structure of mdev

On 11/14/2016 11:42 PM, Kirti Wankhede wrote: > Add a notifier calback to parent's ops structure of mdev device so that per > device notifer for vfio module is registered through vfio_mdev module. > > Signed-off-by: Kirti Wankhede > Signed-off-by: Neo Jia

Re: [PATCH v12 12/22] vfio: Add notifier callback to parent's ops structure of mdev

On 11/14/2016 11:42 PM, Kirti Wankhede wrote: > Add a notifier calback to parent's ops structure of mdev device so that per > device notifer for vfio module is registered through vfio_mdev module. > > Signed-off-by: Kirti Wankhede > Signed-off-by: Neo Jia > Change-Id:

Re: [kbuild-all] [Patch v6.1] x86/kvm: Add AVX512_4VNNIW and AVX512_4FMAPS support

Hi He Chen, On Tue, Nov 15, 2016 at 02:02:23PM +0800, He Chen wrote: On Tue, Nov 15, 2016 at 04:24:39AM +0800, kbuild test robot wrote: Hi He, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.9-rc5] [cannot apply to next-20161114] [if your patch is applied to the wrong

Re: [kbuild-all] [Patch v6.1] x86/kvm: Add AVX512_4VNNIW and AVX512_4FMAPS support

Hi He Chen, On Tue, Nov 15, 2016 at 02:02:23PM +0800, He Chen wrote: On Tue, Nov 15, 2016 at 04:24:39AM +0800, kbuild test robot wrote: Hi He, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.9-rc5] [cannot apply to next-20161114] [if your patch is applied to the wrong

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1)

* Namhyung Kim wrote: > Hello, > > This patchset is a rebased version of David's sched timehist work [1]. > I plan to improve perf sched command more and think that having > timehist command before the work looks good. It seems David is busy > these days, so I'm retrying

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1)

* Namhyung Kim wrote: > Hello, > > This patchset is a rebased version of David's sched timehist work [1]. > I plan to improve perf sched command more and think that having > timehist command before the work looks good. It seems David is busy > these days, so I'm retrying it by myself. > >

Re: [PATCH] xen-platform: use builtin_pci_driver

On 14/11/16 13:52, Geliang Tang wrote: > Use builtin_pci_driver() helper to simplify the code. > > Signed-off-by: Geliang Tang Reviewed-by: Juergen Gross > --- > drivers/xen/platform-pci.c | 6 +- > 1 file changed, 1 insertion(+), 5 deletions(-) >

Re: [PATCH] xen-platform: use builtin_pci_driver

On 14/11/16 13:52, Geliang Tang wrote: > Use builtin_pci_driver() helper to simplify the code. > > Signed-off-by: Geliang Tang Reviewed-by: Juergen Gross > --- > drivers/xen/platform-pci.c | 6 +- > 1 file changed, 1 insertion(+), 5 deletions(-) > > diff --git

Re: [PATCH v2] f2fs: don't wait writeback for datas during checkpoint

Hi Jaegeuk, On 2016/11/15 7:32, Jaegeuk Kim wrote: > Hi Chao, > > On Mon, Nov 14, 2016 at 07:04:12PM +0800, Chao Yu wrote: >> Normally, while committing checkpoint, we will wait on all pages to be >> writebacked no matter the page is data or metadata, so in scenario where >> there are lots of

Re: [PATCH v2] f2fs: don't wait writeback for datas during checkpoint

Hi Jaegeuk, On 2016/11/15 7:32, Jaegeuk Kim wrote: > Hi Chao, > > On Mon, Nov 14, 2016 at 07:04:12PM +0800, Chao Yu wrote: >> Normally, while committing checkpoint, we will wait on all pages to be >> writebacked no matter the page is data or metadata, so in scenario where >> there are lots of

[PATCH v2] kvm: x86: don't print warning messages for unimplemented msrs

Change unimplemented msrs messages to use pr_debug. If CONFIG_DYNAMIC_DEBUG is set, then these messages can be enabled at run time or else -DDEBUG can be used at compile time to enable them. These messages will still be printed if ignore_msrs=1. Signed-off-by: Bandan Das ---

[PATCH v2] kvm: x86: don't print warning messages for unimplemented msrs

Change unimplemented msrs messages to use pr_debug. If CONFIG_DYNAMIC_DEBUG is set, then these messages can be enabled at run time or else -DDEBUG can be used at compile time to enable them. These messages will still be printed if ignore_msrs=1. Signed-off-by: Bandan Das --- v2: use

Re: [PATCH v11 10/22] vfio iommu type1: Add support for mediated devices

On 11/15/2016 10:47 AM, Alexey Kardashevskiy wrote: > On 08/11/16 17:52, Alexey Kardashevskiy wrote: >> On 05/11/16 08:10, Kirti Wankhede wrote: >>> VFIO IOMMU drivers are designed for the devices which are IOMMU capable. >>> Mediated device only uses IOMMU APIs, the underlying hardware can be

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 15/11/16 01:11, Alex Thorlton wrote: > Hey everyone, > > We're having problems with large systems hitting a BUG in > xen_memory_setup, due to extra e820 entries created in the > XENMEM_machine_memory_map callback. The change in the patch gets things > working, but Boris and I wanted to get

Re: [PATCH v11 10/22] vfio iommu type1: Add support for mediated devices

On 11/15/2016 10:47 AM, Alexey Kardashevskiy wrote: > On 08/11/16 17:52, Alexey Kardashevskiy wrote: >> On 05/11/16 08:10, Kirti Wankhede wrote: >>> VFIO IOMMU drivers are designed for the devices which are IOMMU capable. >>> Mediated device only uses IOMMU APIs, the underlying hardware can be

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 15/11/16 01:11, Alex Thorlton wrote: > Hey everyone, > > We're having problems with large systems hitting a BUG in > xen_memory_setup, due to extra e820 entries created in the > XENMEM_machine_memory_map callback. The change in the patch gets things > working, but Boris and I wanted to get

Re: [PATCH -tip v2 2/6] selftests: ftrace: Initialize ftrace before each test

On Mon, 14 Nov 2016 13:12:00 -0500 Steven Rostedt wrote: > On Sun, 30 Oct 2016 15:54:10 +0900 > Masami Hiramatsu wrote: > > > Reset ftrace to initial state before running each test. > > This fixes some test cases to enable tracing before starting > >

Re: [PATCH -tip v2 2/6] selftests: ftrace: Initialize ftrace before each test

On Mon, 14 Nov 2016 13:12:00 -0500 Steven Rostedt wrote: > On Sun, 30 Oct 2016 15:54:10 +0900 > Masami Hiramatsu wrote: > > > Reset ftrace to initial state before running each test. > > This fixes some test cases to enable tracing before starting > > trace test. This can avoid false-positive

Re: kvm: deadlock between kvm_vm_ioctl_get_dirty_log/kvm_hv_set_msr_common/kvm_create_pit

On Tue, Nov 15, 2016 at 7:27 AM, Dmitry Vyukov wrote: > Hello, > > The following program produces a deadlocked, unkillable process: > https://gist.githubusercontent.com/dvyukov/fb7e93f6618f4eccb84d419ea6cec491/raw/a14b60250e593eb1b61f50cead41059dc49ceff2/gistfile1.txt > > > #

Re: kvm: deadlock between kvm_vm_ioctl_get_dirty_log/kvm_hv_set_msr_common/kvm_create_pit

On Tue, Nov 15, 2016 at 7:27 AM, Dmitry Vyukov wrote: > Hello, > > The following program produces a deadlocked, unkillable process: > https://gist.githubusercontent.com/dvyukov/fb7e93f6618f4eccb84d419ea6cec491/raw/a14b60250e593eb1b61f50cead41059dc49ceff2/gistfile1.txt > > > # cat

kvm: deadlock between kvm_vm_ioctl_get_dirty_log/kvm_hv_set_msr_common/kvm_create_pit

Hello, The following program produces a deadlocked, unkillable process: https://gist.githubusercontent.com/dvyukov/fb7e93f6618f4eccb84d419ea6cec491/raw/a14b60250e593eb1b61f50cead41059dc49ceff2/gistfile1.txt # cat /proc/9362/task/*/stack [] __synchronize_srcu+0x2f8/0x4a0 kernel/rcu/srcu.c:448 []

[PATCH] kvm: x86: don't print warning messages for unimplemented msrs

Change unimplemented msrs messages to use pr_debug. If CONFIG_DYNAMIC_DEBUG is set, then these messages can be enabled at run time or else -DDEBUG can be used at compile time to enable them. These messages will still be printed if ignore_msrs=1. Signed-off-by: Bandan Das ---

kvm: deadlock between kvm_vm_ioctl_get_dirty_log/kvm_hv_set_msr_common/kvm_create_pit

Hello, The following program produces a deadlocked, unkillable process: https://gist.githubusercontent.com/dvyukov/fb7e93f6618f4eccb84d419ea6cec491/raw/a14b60250e593eb1b61f50cead41059dc49ceff2/gistfile1.txt # cat /proc/9362/task/*/stack [] __synchronize_srcu+0x2f8/0x4a0 kernel/rcu/srcu.c:448 []

[PATCH] kvm: x86: don't print warning messages for unimplemented msrs

Change unimplemented msrs messages to use pr_debug. If CONFIG_DYNAMIC_DEBUG is set, then these messages can be enabled at run time or else -DDEBUG can be used at compile time to enable them. These messages will still be printed if ignore_msrs=1. Signed-off-by: Bandan Das --- This is a follow up

[GIT PULL] arch/tile bugfix for 4.9-rc6

Linus, Please pull the following change for 4.9-rc6 from: git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git stable This just fixes an incompatibility with tile __ro_after_init. Chris Metcalf (1): tile: handle __ro_after_init like parisc does

[GIT PULL] arch/tile bugfix for 4.9-rc6

Linus, Please pull the following change for 4.9-rc6 from: git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git stable This just fixes an incompatibility with tile __ro_after_init. Chris Metcalf (1): tile: handle __ro_after_init like parisc does

Re: [PATCH 2/3] qemu: Implement virtio-pstore device

On Fri, Nov 11, 2016 at 12:50:03AM +0200, Michael S. Tsirkin wrote: > On Fri, Sep 16, 2016 at 07:05:47PM +0900, Namhyung Kim wrote: > > On Tue, Sep 13, 2016 at 06:57:10PM +0300, Michael S. Tsirkin wrote: > > > On Sat, Aug 20, 2016 at 05:07:43PM +0900, Namhyung Kim wrote: > > > > + > > > > +/* the

Re: [PATCH 2/3] qemu: Implement virtio-pstore device

On Fri, Nov 11, 2016 at 12:50:03AM +0200, Michael S. Tsirkin wrote: > On Fri, Sep 16, 2016 at 07:05:47PM +0900, Namhyung Kim wrote: > > On Tue, Sep 13, 2016 at 06:57:10PM +0300, Michael S. Tsirkin wrote: > > > On Sat, Aug 20, 2016 at 05:07:43PM +0900, Namhyung Kim wrote: > > > > + > > > > +/* the

Re: [RFC PATCH] x86/debug: Dump more detailed segfault info

* Borislav Petkov wrote: > On Sun, Nov 13, 2016 at 12:25:52PM +0100, Borislav Petkov wrote: > > Hmm, enabling all *PRINTK* options from your .config doesn't change > > anything for my qemu guest here. Lemme try with your full config. > > Same with your .config: > > [

Re: [RFC PATCH] x86/debug: Dump more detailed segfault info

* Borislav Petkov wrote: > On Sun, Nov 13, 2016 at 12:25:52PM +0100, Borislav Petkov wrote: > > Hmm, enabling all *PRINTK* options from your .config doesn't change > > anything for my qemu guest here. Lemme try with your full config. > > Same with your .config: > > [ 115.694717]

Re: perf: fuzzer KASAN slab-out-of-bounds in snb_uncore_imc_event_del

On Tue, Nov 15, 2016 at 6:57 AM, Vince Weaver wrote: > On Mon, 14 Nov 2016, Vince Weaver wrote: > >> Anyway as per the suggestion at Linux Plumbers I enabled KASAN and on my >> haswell machine it falls over in a few minutes of running the perf_fuzzer. >> >> [

Re: perf: fuzzer KASAN slab-out-of-bounds in snb_uncore_imc_event_del

On Tue, Nov 15, 2016 at 6:57 AM, Vince Weaver wrote: > On Mon, 14 Nov 2016, Vince Weaver wrote: > >> Anyway as per the suggestion at Linux Plumbers I enabled KASAN and on my >> haswell machine it falls over in a few minutes of running the perf_fuzzer. >> >> [ 205.740194] >>

  1   2   3   4   5   6   7   8   9   10   >