Re: [PATCH 1/5] w83627ehf: Use hwmon_device_register_with_info and sensor groups

On Thu, Mar 23, 2017 at 02:03:04PM +0100, Peter Huewe wrote: > This patch replaces the old, deprecated call to hwmon_device_register > with the new hwmon_device_register_with_info and converts the whole > driver to the new hwmon interface using the hwmon_chip_info methods > and the attribute_group

Re: [PATCH 1/5] w83627ehf: Use hwmon_device_register_with_info and sensor groups

On Thu, Mar 23, 2017 at 02:03:04PM +0100, Peter Huewe wrote: > This patch replaces the old, deprecated call to hwmon_device_register > with the new hwmon_device_register_with_info and converts the whole > driver to the new hwmon interface using the hwmon_chip_info methods > and the attribute_group

Re: [PATCH v6 0/7] Xen transport for 9pfs frontend driver

9pfs maintainers, The patch series is fully acked, except for the header import from Xen (http://marc.info/?l=linux-kernel=149020945130417=2) which needs to be acked in Xen first (this is corresponding Xen series: http://marc.info/?l=xen-devel=149013482308654). Once that happens, the series is

Re: [PATCH v6 0/7] Xen transport for 9pfs frontend driver

9pfs maintainers, The patch series is fully acked, except for the header import from Xen (http://marc.info/?l=linux-kernel=149020945130417=2) which needs to be acked in Xen first (this is corresponding Xen series: http://marc.info/?l=xen-devel=149013482308654). Once that happens, the series is

[PATCH v4 2/2] iio: Aspeed ADC

Aspeed BMC SoCs include a 16 channel, 10-bit ADC. Low and high threshold interrupts are supported by the hardware but are not currently implemented. Signed-off-by: Rick Altherr --- Changes in v4: - Avoid copying per-model data to per-instance data Changes in v3: - Drop

[PATCH v4 2/2] iio: Aspeed ADC

Aspeed BMC SoCs include a 16 channel, 10-bit ADC. Low and high threshold interrupts are supported by the hardware but are not currently implemented. Signed-off-by: Rick Altherr --- Changes in v4: - Avoid copying per-model data to per-instance data Changes in v3: - Drop model numbers from

[PATCH v4 1/2] Documentation: dt-bindings: Document bindings for Aspeed ADC

Signed-off-by: Rick Altherr --- Changes in v4: None Changes in v3: - Consistently write hex contstants with lowercase letters - Drop model numbers from description as same IP is used in every generation Changes in v2: - Rewritten as an IIO ADC device

[PATCH v4 1/2] Documentation: dt-bindings: Document bindings for Aspeed ADC

Signed-off-by: Rick Altherr --- Changes in v4: None Changes in v3: - Consistently write hex contstants with lowercase letters - Drop model numbers from description as same IP is used in every generation Changes in v2: - Rewritten as an IIO ADC device

Re: [v1 0/9] Early boot time stamps for x86

On Thu, 23 Mar 2017, Pasha Tatashin wrote: > I will add a condition to tsc_early_init() to check for TSC_ADJUST if it is > not 0, disable early TSC feature. Does this sound OK? Not really. I have strong objections against how this is crammed into the early boot process along with the code

Re: [v1 0/9] Early boot time stamps for x86

On Thu, 23 Mar 2017, Pasha Tatashin wrote: > I will add a condition to tsc_early_init() to check for TSC_ADJUST if it is > not 0, disable early TSC feature. Does this sound OK? Not really. I have strong objections against how this is crammed into the early boot process along with the code

Re: [PATCH V4] perf: qcom: Add L3 cache PMU driver

On 2017-03-23 11:33, Mark Rutland wrote: Hi Agustin, Structurally, this looks good to me. I have a few minor comments below; with those fixed up I think this is ready to merge. Thanks Mark, I'll spin V5 ASAP. Agustin -- Qualcomm Datacenter Technologies, Inc. on behalf of the Qualcomm

Re: [PATCH V4] perf: qcom: Add L3 cache PMU driver

On 2017-03-23 11:33, Mark Rutland wrote: Hi Agustin, Structurally, this looks good to me. I have a few minor comments below; with those fixed up I think this is ready to merge. Thanks Mark, I'll spin V5 ASAP. Agustin -- Qualcomm Datacenter Technologies, Inc. on behalf of the Qualcomm

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller

Hello, Patrick. On Thu, Mar 23, 2017 at 06:15:33PM +, Patrick Bellasi wrote: > What is important to notice is that there is a middleware, in between > the kernel and the applications. This is a special kind of user-space > where it is still safe for the kernel to delegate some "decisions". >

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller

Hello, Patrick. On Thu, Mar 23, 2017 at 06:15:33PM +, Patrick Bellasi wrote: > What is important to notice is that there is a middleware, in between > the kernel and the applications. This is a special kind of user-space > where it is still safe for the kernel to delegate some "decisions". >

[PATCH 1/3] perf/x86: add sysfs entry to freeze counter on SMI

From: Kan Liang When setting FREEZE_WHILE_SMM bit in IA32_DEBUGCTL, all performance counters will be effected. There is no way to do per-counter freeze on smi. So it should not use the per-event interface (e.g. ioctl or event attribute) to set FREEZE_WHILE_SMM bit. Adds

[PATCH 1/3] perf/x86: add sysfs entry to freeze counter on SMI

From: Kan Liang When setting FREEZE_WHILE_SMM bit in IA32_DEBUGCTL, all performance counters will be effected. There is no way to do per-counter freeze on smi. So it should not use the per-event interface (e.g. ioctl or event attribute) to set FREEZE_WHILE_SMM bit. Adds sysfs entry

[PATCH 3/3] perf stat: Add support to measure SMI cost

From: Kan Liang Implementing a new --smi-cost mode in perf stat to measure SMI cost. During the measurement, the /sys/device/cpu/freeze_on_smi will be set. The measurement can be done with one counter and two free running MSR counters (IA32_APERF and SMI_COUNT). The formula

[PATCH 3/3] perf stat: Add support to measure SMI cost

From: Kan Liang Implementing a new --smi-cost mode in perf stat to measure SMI cost. During the measurement, the /sys/device/cpu/freeze_on_smi will be set. The measurement can be done with one counter and two free running MSR counters (IA32_APERF and SMI_COUNT). The formula to caculate SMI cost

[PATCH 2/3] tools lib api fs: Add sysfs__write_int function

From: Kan Liang Adding sysfs__write_int function to ease up writing int to sysfs. New interface is: int sysfs__write_int(const char *entry, int value); Also, introducing filename__write_int which is useful for new helpers to write sysctl values. Signed-off-by: Kan Liang

[PATCH 2/3] tools lib api fs: Add sysfs__write_int function

From: Kan Liang Adding sysfs__write_int function to ease up writing int to sysfs. New interface is: int sysfs__write_int(const char *entry, int value); Also, introducing filename__write_int which is useful for new helpers to write sysctl values. Signed-off-by: Kan Liang ---

[PATCH 0/3]measure SMI cost

From: Kan Liang Currently, there is no way to measure the time cost in System management mode (SMM) by perf. Intel perfmon supports FREEZE_WHILE_SMM bit in IA32_DEBUGCTL. Once it sets, the PMU core counters will freeze on SMI handler. But it will not have an effect on free

[PATCH 0/3]measure SMI cost

From: Kan Liang Currently, there is no way to measure the time cost in System management mode (SMM) by perf. Intel perfmon supports FREEZE_WHILE_SMM bit in IA32_DEBUGCTL. Once it sets, the PMU core counters will freeze on SMI handler. But it will not have an effect on free running counters.

Re: [PATCH V8 2/3] irq: Track the interrupt timings

On Thu, Mar 23, 2017 at 06:42:02PM +0100, Daniel Lezcano wrote: > +/* > + * The function record_irq_time is only called in one place in the > + * interrupts handler. We want this function always inline so the code > + * inside is embedded in the function and the static key branching > + * code can

Re: [PATCH V8 2/3] irq: Track the interrupt timings

On Thu, Mar 23, 2017 at 06:42:02PM +0100, Daniel Lezcano wrote: > +/* > + * The function record_irq_time is only called in one place in the > + * interrupts handler. We want this function always inline so the code > + * inside is embedded in the function and the static key branching > + * code can

[PATCH v4] staging: iio: ade7753: Replace mlock with driver private lock

The IIO subsystem is redefining iio_dev->mlock to be used by the IIO core only for protecting device operating mode changes. ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. In this driver, mlock was being used to protect hardware state changes. Replace it with a lock in the devices

[PATCH v4] staging: iio: ade7753: Replace mlock with driver private lock

The IIO subsystem is redefining iio_dev->mlock to be used by the IIO core only for protecting device operating mode changes. ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. In this driver, mlock was being used to protect hardware state changes. Replace it with a lock in the devices

Re: [PATCH V8 1/3] irq: Add flags to request_percpu_irq function

On 03/23/2017 10:42 AM, Daniel Lezcano wrote: > In the next changes, we track the interrupts but we discard the timers as > that does not make sense. The next interrupt on a timer is predictable. > > But, the API request_percpu_irq does not allow to pass a flag, hence > specifying > if the

Re: [PATCH V8 1/3] irq: Add flags to request_percpu_irq function

On 03/23/2017 10:42 AM, Daniel Lezcano wrote: > In the next changes, we track the interrupts but we discard the timers as > that does not make sense. The next interrupt on a timer is predictable. > > But, the API request_percpu_irq does not allow to pass a flag, hence > specifying > if the

Re: Query on DT overlay support.

On Thu, Mar 23, 2017 at 8:22 AM, Nava kishore Manne wrote: > Hi, > > > > This mail is regarding the DT overlay support in the Linux > kernel > > I am able to make the device-tree overlay work out of box by > using my own dtc complier (I mean

Re: Query on DT overlay support.

On Thu, Mar 23, 2017 at 8:22 AM, Nava kishore Manne wrote: > Hi, > > > > This mail is regarding the DT overlay support in the Linux > kernel > > I am able to make the device-tree overlay work out of box by > using my own dtc complier (I mean I used the dtc compiler

Re: [PATCH] Input: synaptics - do not mix logical and bitwise operations

On Mar 23 2017 or thereabouts, Dmitry Torokhov wrote: > Let's stop using !!x to reduce value of trackstick button expression to 0/1 > and use shift instead. This removes the following sparse warning: > > CHECK drivers/input/mouse/synaptics.c > drivers/input/mouse/synaptics.c:943:79: warning:

Re: [PATCH] Input: synaptics - do not mix logical and bitwise operations

On Mar 23 2017 or thereabouts, Dmitry Torokhov wrote: > Let's stop using !!x to reduce value of trackstick button expression to 0/1 > and use shift instead. This removes the following sparse warning: > > CHECK drivers/input/mouse/synaptics.c > drivers/input/mouse/synaptics.c:943:79: warning:

Re: [PATCH] fpga: altera_freeze_bridge: Constify ops

On Fri, Mar 17, 2017 at 3:15 PM, Moritz Fischer wrote: > The ops are not changing, make them const. > > Signed-off-by: Moritz Fischer Acked-by: Alan Tull > Cc: Alan Tull > Cc: linux-kernel@vger.kernel.org > Cc:

Re: [PATCH] fpga: altera_freeze_bridge: Constify ops

On Fri, Mar 17, 2017 at 3:15 PM, Moritz Fischer wrote: > The ops are not changing, make them const. > > Signed-off-by: Moritz Fischer Acked-by: Alan Tull > Cc: Alan Tull > Cc: linux-kernel@vger.kernel.org > Cc: linux-f...@vger.kernel.org > --- > drivers/fpga/altera-freeze-bridge.c | 2 +- >

Re: [PATCH v4 1/4] pinctrl: rockchip: remove unnecessary locking

On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote: > Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping: > > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote: [..] > > > [..] > > > > > > > @@ -1185,17 +1177,14 @@ static int rockchip_set_drive_perpin(struct > > >

Re: [PATCH v4 1/4] pinctrl: rockchip: remove unnecessary locking

On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote: > Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping: > > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote: [..] > > > [..] > > > > > > > @@ -1185,17 +1177,14 @@ static int rockchip_set_drive_perpin(struct > > >

[tip:locking/core] futex: Drop hb->lock before enqueueing on the rtmutex

Commit-ID: 56222b212e8edb1cf51f5dd73ff645809b082b40 Gitweb: http://git.kernel.org/tip/56222b212e8edb1cf51f5dd73ff645809b082b40 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:36:00 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Drop hb->lock before enqueueing on the rtmutex

Commit-ID: 56222b212e8edb1cf51f5dd73ff645809b082b40 Gitweb: http://git.kernel.org/tip/56222b212e8edb1cf51f5dd73ff645809b082b40 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:36:00 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:14:59 +0100 futex: Drop hb->lock

[tip:locking/core] futex: Futex_unlock_pi() determinism

Commit-ID: bebe5b514345f09be2c15e414d076b02ecb9cce8 Gitweb: http://git.kernel.org/tip/bebe5b514345f09be2c15e414d076b02ecb9cce8 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:59 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Futex_unlock_pi() determinism

Commit-ID: bebe5b514345f09be2c15e414d076b02ecb9cce8 Gitweb: http://git.kernel.org/tip/bebe5b514345f09be2c15e414d076b02ecb9cce8 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:59 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:10 +0100 futex:

[tip:locking/core] futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()

Commit-ID: cfafcd117da0216520568c195cb2f6cd1980c4bb Gitweb: http://git.kernel.org/tip/cfafcd117da0216520568c195cb2f6cd1980c4bb Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:58 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()

Commit-ID: cfafcd117da0216520568c195cb2f6cd1980c4bb Gitweb: http://git.kernel.org/tip/cfafcd117da0216520568c195cb2f6cd1980c4bb Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:58 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:09 +0100 futex: Rework

[tip:locking/core] futex,rt_mutex: Restructure rt_mutex_finish_proxy_lock()

Commit-ID: 38d589f2fd08f1296aea3ce62bebd185125c6d81 Gitweb: http://git.kernel.org/tip/38d589f2fd08f1296aea3ce62bebd185125c6d81 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:57 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex,rt_mutex: Restructure rt_mutex_finish_proxy_lock()

Commit-ID: 38d589f2fd08f1296aea3ce62bebd185125c6d81 Gitweb: http://git.kernel.org/tip/38d589f2fd08f1296aea3ce62bebd185125c6d81 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:57 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:09 +0100 futex,rt_mutex:

Re: [PATCH] reiserfs: avoid a -Wmaybe-uninitialized warning

On Thu 23-03-17 16:06:13, Arnd Bergmann wrote: > The latest gcc-7.0.1 snapshot warns about an unintialized variable use: > > In file included from fs/reiserfs/lbalance.c:8:0: > fs/reiserfs/lbalance.c: In function 'leaf_item_bottle.isra.3': > fs/reiserfs/reiserfs.h:1279:13: error: '*((void

[tip:locking/core] futex,rt_mutex: Introduce rt_mutex_init_waiter()

Commit-ID: 50809358dd7199aa7ce232f6877dd09ec30ef374 Gitweb: http://git.kernel.org/tip/50809358dd7199aa7ce232f6877dd09ec30ef374 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:56 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

Re: [PATCH] reiserfs: avoid a -Wmaybe-uninitialized warning

On Thu 23-03-17 16:06:13, Arnd Bergmann wrote: > The latest gcc-7.0.1 snapshot warns about an unintialized variable use: > > In file included from fs/reiserfs/lbalance.c:8:0: > fs/reiserfs/lbalance.c: In function 'leaf_item_bottle.isra.3': > fs/reiserfs/reiserfs.h:1279:13: error: '*((void

[tip:locking/core] futex,rt_mutex: Introduce rt_mutex_init_waiter()

Commit-ID: 50809358dd7199aa7ce232f6877dd09ec30ef374 Gitweb: http://git.kernel.org/tip/50809358dd7199aa7ce232f6877dd09ec30ef374 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:56 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:09 +0100 futex,rt_mutex:

[tip:locking/core] futex: Pull rt_mutex_futex_unlock() out from under hb->lock

Commit-ID: 16ffa12d742534d4ff73e8b3a4e81c1de39196f0 Gitweb: http://git.kernel.org/tip/16ffa12d742534d4ff73e8b3a4e81c1de39196f0 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:55 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Pull rt_mutex_futex_unlock() out from under hb->lock

Commit-ID: 16ffa12d742534d4ff73e8b3a4e81c1de39196f0 Gitweb: http://git.kernel.org/tip/16ffa12d742534d4ff73e8b3a4e81c1de39196f0 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:55 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:08 +0100 futex: Pull

[tip:locking/core] futex: Cleanup refcounting

Commit-ID: bf92cf3a5100f5a0d5f9834787b130159397cb22 Gitweb: http://git.kernel.org/tip/bf92cf3a5100f5a0d5f9834787b130159397cb22 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:53 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Cleanup refcounting

Commit-ID: bf92cf3a5100f5a0d5f9834787b130159397cb22 Gitweb: http://git.kernel.org/tip/bf92cf3a5100f5a0d5f9834787b130159397cb22 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:53 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:08 +0100 futex: Cleanup

[tip:locking/core] futex: Rework inconsistent rt_mutex/futex_q state

Commit-ID: 73d786bd043ebc855f349c81ea805f6b11cbf2aa Gitweb: http://git.kernel.org/tip/73d786bd043ebc855f349c81ea805f6b11cbf2aa Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:54 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Rework inconsistent rt_mutex/futex_q state

Commit-ID: 73d786bd043ebc855f349c81ea805f6b11cbf2aa Gitweb: http://git.kernel.org/tip/73d786bd043ebc855f349c81ea805f6b11cbf2aa Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:54 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:08 +0100 futex: Rework

[tip:locking/core] futex: Change locking rules

Commit-ID: 734009e96d1983ad739e5b656e03430b3660c913 Gitweb: http://git.kernel.org/tip/734009e96d1983ad739e5b656e03430b3660c913 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:52 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Change locking rules

Commit-ID: 734009e96d1983ad739e5b656e03430b3660c913 Gitweb: http://git.kernel.org/tip/734009e96d1983ad739e5b656e03430b3660c913 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:52 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:07 +0100 futex: Change

[tip:locking/core] futex,rt_mutex: Provide futex specific rt_mutex API

Commit-ID: 5293c2efda37775346885c7e924d4ef7018ea60b Gitweb: http://git.kernel.org/tip/5293c2efda37775346885c7e924d4ef7018ea60b Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:51 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex,rt_mutex: Provide futex specific rt_mutex API

Commit-ID: 5293c2efda37775346885c7e924d4ef7018ea60b Gitweb: http://git.kernel.org/tip/5293c2efda37775346885c7e924d4ef7018ea60b Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:51 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:07 +0100 futex,rt_mutex:

[tip:locking/core] futex: Remove rt_mutex_deadlock_account_*()

Commit-ID: fffa954fb528963c2fb7b0c0084eb77e2be7ab52 Gitweb: http://git.kernel.org/tip/fffa954fb528963c2fb7b0c0084eb77e2be7ab52 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:50 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Remove rt_mutex_deadlock_account_*()

Commit-ID: fffa954fb528963c2fb7b0c0084eb77e2be7ab52 Gitweb: http://git.kernel.org/tip/fffa954fb528963c2fb7b0c0084eb77e2be7ab52 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:50 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:07 +0100 futex: Remove

[tip:locking/core] futex: Use smp_store_release() in mark_wake_futex()

Commit-ID: 1b367ece0d7e696cab1c8501bab282cc6a538b3f Gitweb: http://git.kernel.org/tip/1b367ece0d7e696cab1c8501bab282cc6a538b3f Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:49 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Use smp_store_release() in mark_wake_futex()

Commit-ID: 1b367ece0d7e696cab1c8501bab282cc6a538b3f Gitweb: http://git.kernel.org/tip/1b367ece0d7e696cab1c8501bab282cc6a538b3f Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:49 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:06 +0100 futex: Use

[tip:locking/core] futex: Cleanup variable names for futex_top_waiter()

Commit-ID: 499f5aca2cdd5e958b27e2655e7e7f82524f46b1 Gitweb: http://git.kernel.org/tip/499f5aca2cdd5e958b27e2655e7e7f82524f46b1 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:48 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar

[tip:locking/core] futex: Cleanup variable names for futex_top_waiter()

Commit-ID: 499f5aca2cdd5e958b27e2655e7e7f82524f46b1 Gitweb: http://git.kernel.org/tip/499f5aca2cdd5e958b27e2655e7e7f82524f46b1 Author: Peter Zijlstra AuthorDate: Wed, 22 Mar 2017 11:35:48 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Mar 2017 19:10:06 +0100 futex: Cleanup

Re: [PATCH -v3 4/8] rtmutex: Clean up

On Thu, 23 Mar 2017 15:56:10 +0100 Peter Zijlstra wrote: > Previous patches changed the meaning of the return value of > rt_mutex_slowunlock(); update comments and code to reflect this. > > Signed-off-by: Peter Zijlstra (Intel) > --- Acked-by:

Re: [PATCH -v3 4/8] rtmutex: Clean up

On Thu, 23 Mar 2017 15:56:10 +0100 Peter Zijlstra wrote: > Previous patches changed the meaning of the return value of > rt_mutex_slowunlock(); update comments and code to reflect this. > > Signed-off-by: Peter Zijlstra (Intel) > --- Acked-by: Steven Rostedt (VMware) -- Steve

Re: [PATCH 3/4] RAS: Add a Corrected Errors Collector

On Thu, Mar 23, 2017 at 06:28:39PM +0100, Borislav Petkov wrote: > Meh, I don't like the idea of keeping an evergrowing list of PFNs we > can't do anything about anyway. Keeping every PFN would be overkill (most of them should be taken offline with no issues). A fixed array of a few of them with

Re: [PATCH 3/4] RAS: Add a Corrected Errors Collector

On Thu, Mar 23, 2017 at 06:28:39PM +0100, Borislav Petkov wrote: > Meh, I don't like the idea of keeping an evergrowing list of PFNs we > can't do anything about anyway. Keeping every PFN would be overkill (most of them should be taken offline with no issues). A fixed array of a few of them with

Re: [PATCH 2/6 v5] ftrace/x86_32: Move the ftrace specific code out of entry_32.S

On Thu, 23 Mar 2017, Steven Rostedt wrote: > --- a/arch/x86/kernel/ftrace_64.S > +++ b/arch/x86/kernel/ftrace_64.S > @@ -1,5 +1,5 @@ > /* > - * linux/arch/x86_64/mcount_64.S > + * linux/arch/x86_64/ftrace_64.S Can we please get rid of that nonsense completely? > * > * Copyright (C) 2014

Regression in i915 for 4.11-rc1 - bisected to commit 69df05e11ab8

Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered intermittent hangs with the following information in the logs: linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in plasmashell [1283], reason: Hang on render ring, action: reset linux-4v1g.suse kernel: [drm] GPU hangs

Re: [PATCH 2/6 v5] ftrace/x86_32: Move the ftrace specific code out of entry_32.S

On Thu, 23 Mar 2017, Steven Rostedt wrote: > --- a/arch/x86/kernel/ftrace_64.S > +++ b/arch/x86/kernel/ftrace_64.S > @@ -1,5 +1,5 @@ > /* > - * linux/arch/x86_64/mcount_64.S > + * linux/arch/x86_64/ftrace_64.S Can we please get rid of that nonsense completely? > * > * Copyright (C) 2014

Regression in i915 for 4.11-rc1 - bisected to commit 69df05e11ab8

Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered intermittent hangs with the following information in the logs: linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in plasmashell [1283], reason: Hang on render ring, action: reset linux-4v1g.suse kernel: [drm] GPU hangs

Re: [PATCH v3 2/2] staging: iio: ade7753: Replace mlock with driver private lock

On 23 March 2017 18:12:33 GMT+00:00, SIMRAN SINGHAL wrote: >On Thu, Mar 23, 2017 at 1:55 AM, Jonathan Cameron >wrote: >> On 21/03/17 18:03, simran singhal wrote: >>> The IIO subsystem is redefining iio_dev->mlock to be used by >>> the IIO core only

Re: [PATCH v3 2/2] staging: iio: ade7753: Replace mlock with driver private lock

On 23 March 2017 18:12:33 GMT+00:00, SIMRAN SINGHAL wrote: >On Thu, Mar 23, 2017 at 1:55 AM, Jonathan Cameron >wrote: >> On 21/03/17 18:03, simran singhal wrote: >>> The IIO subsystem is redefining iio_dev->mlock to be used by >>> the IIO core only for protecting device operating mode

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller

On 23-Mar 12:01, Tejun Heo wrote: > Hello, Hi Tejun, > On Thu, Mar 23, 2017 at 10:32:54AM +, Patrick Bellasi wrote: > > > But then we would lose out on being able to attach capacity > > > constraints to specific tasks or groups of tasks? > > > > Yes, right. If CGroups are not available than

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller

On 23-Mar 12:01, Tejun Heo wrote: > Hello, Hi Tejun, > On Thu, Mar 23, 2017 at 10:32:54AM +, Patrick Bellasi wrote: > > > But then we would lose out on being able to attach capacity > > > constraints to specific tasks or groups of tasks? > > > > Yes, right. If CGroups are not available than

Re: [PATCH v3 2/2] staging: iio: ade7753: Replace mlock with driver private lock

On Thu, Mar 23, 2017 at 1:55 AM, Jonathan Cameron wrote: > On 21/03/17 18:03, simran singhal wrote: >> The IIO subsystem is redefining iio_dev->mlock to be used by >> the IIO core only for protecting device operating mode changes. >> ie. Changes between INDIO_DIRECT_MODE,

Re: [PATCH v3 2/2] staging: iio: ade7753: Replace mlock with driver private lock

On Thu, Mar 23, 2017 at 1:55 AM, Jonathan Cameron wrote: > On 21/03/17 18:03, simran singhal wrote: >> The IIO subsystem is redefining iio_dev->mlock to be used by >> the IIO core only for protecting device operating mode changes. >> ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. >>

Re: [PATCH] tpm2: fix off-by-one comparison and out-of-bounds read error

On Thu, Mar 23, 2017 at 07:42:09PM +0300, Dan Carpenter wrote: > On Thu, Mar 23, 2017 at 05:53:58PM +0200, Jarkko Sakkinen wrote: > > On Wed, Mar 22, 2017 at 04:12:49PM +0300, Dan Carpenter wrote: > > > On Wed, Mar 22, 2017 at 11:45:37AM +, Colin Ian King wrote: > > > > On 22/03/17 11:42,

Re: [PATCH] tpm2: fix off-by-one comparison and out-of-bounds read error

On Thu, Mar 23, 2017 at 07:42:09PM +0300, Dan Carpenter wrote: > On Thu, Mar 23, 2017 at 05:53:58PM +0200, Jarkko Sakkinen wrote: > > On Wed, Mar 22, 2017 at 04:12:49PM +0300, Dan Carpenter wrote: > > > On Wed, Mar 22, 2017 at 11:45:37AM +, Colin Ian King wrote: > > > > On 22/03/17 11:42,

Re: RAID array is gone, please help

Thank you very much or your reply. I naively thought that starting without partitions would be the best starting point, given 3 of the disks had been in a RAID5 array previously (possibly with partitions, not sure), but that looks like a bad choice, based on some other things I've googled.

Re: RAID array is gone, please help

Thank you very much or your reply. I naively thought that starting without partitions would be the best starting point, given 3 of the disks had been in a RAID5 array previously (possibly with partitions, not sure), but that looks like a bad choice, based on some other things I've googled.

Re: net/kcm: double free of kcm inode

On Thu, Mar 23, 2017 at 5:09 AM, Dmitry Vyukov wrote: > Hello, > > I've got the following report while running syzkaller fuzzer. Note the > preceding kmem_cache_alloc injected failure, it's most likely the root > cause. > > FAULT_INJECTION: forcing a failure. > name failslab,

Re: net/kcm: double free of kcm inode

On Thu, Mar 23, 2017 at 5:09 AM, Dmitry Vyukov wrote: > Hello, > > I've got the following report while running syzkaller fuzzer. Note the > preceding kmem_cache_alloc injected failure, it's most likely the root > cause. > > FAULT_INJECTION: forcing a failure. > name failslab, interval 1,

Re: mm: BUG in resv_map_release

On 03/23/2017 10:25 AM, Mike Kravetz wrote: > On 03/23/2017 03:19 AM, Dmitry Vyukov wrote: >> Hello, >> >> I've got the following BUG while running syzkaller fuzzer. >> Note the injected kmalloc failure, most likely it's the root cause. > > Thanks Dmitry, > > The BUG indicates someone called

Re: mm: BUG in resv_map_release

On 03/23/2017 10:25 AM, Mike Kravetz wrote: > On 03/23/2017 03:19 AM, Dmitry Vyukov wrote: >> Hello, >> >> I've got the following BUG while running syzkaller fuzzer. >> Note the injected kmalloc failure, most likely it's the root cause. > > Thanks Dmitry, > > The BUG indicates someone called

Re: [PATCH v5] KVM: VMX: Fix enable VPID conditions

On 23/03/2017 13:30, Wanpeng Li wrote: > From: Wanpeng Li > > This can be reproduced by running L2 on L1, and disable VPID on L0 > if w/o commit "KVM: nVMX: Fix nested VPID vmx exec control", the L2 > crash as below: > > KVM: entry failed, hardware error 0x7 >

Re: [PATCH v5] KVM: VMX: Fix enable VPID conditions

On 23/03/2017 13:30, Wanpeng Li wrote: > From: Wanpeng Li > > This can be reproduced by running L2 on L1, and disable VPID on L0 > if w/o commit "KVM: nVMX: Fix nested VPID vmx exec control", the L2 > crash as below: > > KVM: entry failed, hardware error 0x7 > EAX= EBX=

Re: [PATCH V13 10/10] arm/arm64: KVM: add guest SEA support

On Tue, Mar 21, 2017 at 04:47:05PM -0600, Tyler Baicar wrote: > Currently external aborts are unsupported by the guest abort > handling. Add handling for SEAs so that the host kernel reports > SEAs which occur in the guest kernel. > > Signed-off-by: Tyler Baicar > --- >

Re: [PATCH V13 10/10] arm/arm64: KVM: add guest SEA support

On Tue, Mar 21, 2017 at 04:47:05PM -0600, Tyler Baicar wrote: > Currently external aborts are unsupported by the guest abort > handling. Add handling for SEAs so that the host kernel reports > SEAs which occur in the guest kernel. > > Signed-off-by: Tyler Baicar > --- >

Re: [PATCH v4 1/4] pinctrl: rockchip: remove unnecessary locking

Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping: > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote: > > One quick question below. Apologies if this has been covered, but just > > want to be sure. > > > > On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote: > >

Re: [PATCH v4 1/4] pinctrl: rockchip: remove unnecessary locking

Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping: > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote: > > One quick question below. Apologies if this has been covered, but just > > want to be sure. > > > > On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote: > >

Re: [PATCH V13 05/10] acpi: apei: handle SEA notification type for ARMv8

On Tue, Mar 21, 2017 at 04:47:00PM -0600, Tyler Baicar wrote: > ARM APEI extension proposal added SEA (Synchronous External Abort) > notification type for ARMv8. > Add a new GHES error source handling function for SEA. If an error > source's notification type is SEA, then this function can be

Re: [PATCH V13 05/10] acpi: apei: handle SEA notification type for ARMv8

On Tue, Mar 21, 2017 at 04:47:00PM -0600, Tyler Baicar wrote: > ARM APEI extension proposal added SEA (Synchronous External Abort) > notification type for ARMv8. > Add a new GHES error source handling function for SEA. If an error > source's notification type is SEA, then this function can be

Re: [PATCH v4 1/4] pinctrl: rockchip: remove unnecessary locking

On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote: > One quick question below. Apologies if this has been covered, but just > want to be sure. > > On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote: > > regmap_update_bits does its own locking and everything else accessed > >

Re: [PATCH v4 1/4] pinctrl: rockchip: remove unnecessary locking

On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote: > One quick question below. Apologies if this has been covered, but just > want to be sure. > > On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote: > > regmap_update_bits does its own locking and everything else accessed > >

Re: [RFC PATCH 1/1] nbd: replace kill_bdev() with __invalidate_device()

Yeah I think this is ok, I’ll throw it on my queue for fixes for this cycle. Thanks, Josef On 3/20/17, 6:58 PM, "Ming Lin" wrote: From: Ratna Manoj Bolla When a filesystem is mounted on a nbd device and on a disconnect, because of kill_bdev(), and

Re: [RFC PATCH 1/1] nbd: replace kill_bdev() with __invalidate_device()

Yeah I think this is ok, I’ll throw it on my queue for fixes for this cycle. Thanks, Josef On 3/20/17, 6:58 PM, "Ming Lin" wrote: From: Ratna Manoj Bolla When a filesystem is mounted on a nbd device and on a disconnect, because of kill_bdev(), and resetting bdev size to zero, buffer_head

RE: [PATCH v2] HV: properly delay KVP packets when negotiation is in progress

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Thursday, March 23, 2017 9:04 AM > To: Long Li > Cc: KY Srinivasan ; Haiyang Zhang > ; Stephen Hemminger > ;

RE: [PATCH v2] HV: properly delay KVP packets when negotiation is in progress

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Thursday, March 23, 2017 9:04 AM > To: Long Li > Cc: KY Srinivasan ; Haiyang Zhang > ; Stephen Hemminger > ; de...@linuxdriverproject.org; linux- > ker...@vger.kernel.org; sta...@vger.kernel.org >

<    3   4   5   6   7   8   9   10   11   12   >