[PATCH] ima: namespacing IMA (PoC) - experimental

This IMA namespacing patch set was initially implemented by Yuqiong Sun, while at IBM Research as a summer intern working with David Safford. It was subsequently modified and rebased by Stefan Berger and Mehmet Kayaalp. The resulting patches are being made available from the

[PATCH] f2fs: remove extra inode_unlock() in error path

This commit removes an extra inode_unlock() that is being done in function f2fs_ioc_setflags error path. While there, get rid of a useless 'out' label as well. Fixes: 0abd675e97e6 ("f2fs: support plain user/group quota") Signed-off-by: Luis Henriques --- fs/f2fs/file.c | 5 + 1 file

Re: [RFC][PATCH] drm: kirin: Restrict modes to known good mode clocks

On Tue, Jul 11, 2017 at 5:44 PM, John Stultz wrote: > On Tue, Jul 11, 2017 at 8:12 AM, Daniel Vetter wrote: >> On Tue, Jul 11, 2017 at 5:05 PM, John Stultz wrote: > > be even better if you could calculate whether the mode is

Re: [RFC][PATCH] drm: kirin: Restrict modes to known good mode clocks

On Tue, Jul 11, 2017 at 5:44 PM, John Stultz wrote: > On Tue, Jul 11, 2017 at 8:12 AM, Daniel Vetter wrote: >> On Tue, Jul 11, 2017 at 5:05 PM, John Stultz wrote: > > be even better if you could calculate whether the mode is valid, but I > > didn't > > spend enough time to figure

Re: [PATCH 0/7] Constify platform/x86 attribute_group structures.

On Tue, Jul 11, 2017 at 04:18:13PM +0530, Arvind Yadav wrote: > attribute_groups are not supposed to change at runtime. All functions > working with attribute_groups provided by work > with const attribute_group. So mark the non-const structs as const. Build tested, no warnings/errors found.

Re: [PATCH 0/7] Constify platform/x86 attribute_group structures.

On Tue, Jul 11, 2017 at 04:18:13PM +0530, Arvind Yadav wrote: > attribute_groups are not supposed to change at runtime. All functions > working with attribute_groups provided by work > with const attribute_group. So mark the non-const structs as const. Build tested, no warnings/errors found.

Re: [PATCH 08/17] tty: New RISC-V SBI console driver

On Mon, 10 Jul 2017 23:21:07 PDT (-0700), m...@ellerman.id.au wrote: > Palmer Dabbelt writes: >> > ... >> +#ifdef CONFIG_EARLY_PRINTK >> +static void sbi_console_write(struct console *co, const char *buf, >> + unsigned int n) >> +{ >> +int i; >> +

Re: [PATCH 17/17] RISC-V: Build Infastructure

On Mon, 10 Jul 2017 23:31:18 PDT (-0700), m...@ellerman.id.au wrote: > Palmer Dabbelt writes: > >> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig >> new file mode 100644 >> index ..366f5f2cf106 >> --- /dev/null >> +++ b/arch/riscv/Kconfig >> @@ -0,0 +1,294 @@

Re: [PATCH 08/17] tty: New RISC-V SBI console driver

On Mon, 10 Jul 2017 23:21:07 PDT (-0700), m...@ellerman.id.au wrote: > Palmer Dabbelt writes: >> > ... >> +#ifdef CONFIG_EARLY_PRINTK >> +static void sbi_console_write(struct console *co, const char *buf, >> + unsigned int n) >> +{ >> +int i; >> + >> +for (i = 0;

Re: [PATCH 17/17] RISC-V: Build Infastructure

On Mon, 10 Jul 2017 23:31:18 PDT (-0700), m...@ellerman.id.au wrote: > Palmer Dabbelt writes: > >> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig >> new file mode 100644 >> index ..366f5f2cf106 >> --- /dev/null >> +++ b/arch/riscv/Kconfig >> @@ -0,0 +1,294 @@ > ... >> + >>

Re: [GIT pull] irq updates for 4.13

* Sebastian Reichel [170711 07:41]: > Ack, that also works for me. The strange thing is, that I added the > following before and it did not print anything. > > if (!pm_runtime_enabled(bank->chip.parent)) > dev_err(bank->chip.parent, "runtime pm issue!\n");

Re: [GIT pull] irq updates for 4.13

* Sebastian Reichel [170711 07:41]: > Ack, that also works for me. The strange thing is, that I added the > following before and it did not print anything. > > if (!pm_runtime_enabled(bank->chip.parent)) > dev_err(bank->chip.parent, "runtime pm issue!\n"); Enabled but not active, you should

Re: [GIT pull] irq updates for 4.13

On Tue, 11 Jul 2017, Linus Torvalds wrote: > On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > > > Ah. Now that makes sense. > > > > Unpatched the ordering is: > > > > chip_bus_lock(desc); > > irq_request_resources(desc); > > I *looked* at that

Re: [GIT pull] irq updates for 4.13

On Tue, 11 Jul 2017, Linus Torvalds wrote: > On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > > > Ah. Now that makes sense. > > > > Unpatched the ordering is: > > > > chip_bus_lock(desc); > > irq_request_resources(desc); > > I *looked* at that ordering and then

Re: [RFC PATCH v1 3/8] sched/cpufreq_schedutil: make worker kthread be SCHED_DEADLINE

On Wed, Jul 05, 2017 at 09:59:00AM +0100, Juri Lelli wrote: > @@ -4065,6 +4067,9 @@ static int __sched_setscheduler(struct task_struct *p, > } > > if (user) { > + if (attr->sched_flags & SCHED_FLAG_SPECIAL) > + return -EPERM; Should be -EINVAL I

Re: [RFC PATCH v1 3/8] sched/cpufreq_schedutil: make worker kthread be SCHED_DEADLINE

On Wed, Jul 05, 2017 at 09:59:00AM +0100, Juri Lelli wrote: > @@ -4065,6 +4067,9 @@ static int __sched_setscheduler(struct task_struct *p, > } > > if (user) { > + if (attr->sched_flags & SCHED_FLAG_SPECIAL) > + return -EPERM; Should be -EINVAL I

Re: [RFC PATCH v1 5/8] sched/cpufreq_schedutil: always consider all CPUs when deciding next freq

On Wed, Jul 05, 2017 at 09:59:02AM +0100, Juri Lelli wrote: > delta_ns = time - j_sg_cpu->last_update; > if (delta_ns > TICK_NSEC) { > j_sg_cpu->iowait_boost = 0; > - continue; > + j_sg_cpu->util_cfs = 0;

Re: [RFC PATCH v1 5/8] sched/cpufreq_schedutil: always consider all CPUs when deciding next freq

On Wed, Jul 05, 2017 at 09:59:02AM +0100, Juri Lelli wrote: > delta_ns = time - j_sg_cpu->last_update; > if (delta_ns > TICK_NSEC) { > j_sg_cpu->iowait_boost = 0; > - continue; > + j_sg_cpu->util_cfs = 0;

Re: [PATCH 02/13] mpt3sas: SGL to PRP Translation for I/Os to NVMe devices

On Tue, Jul 11, 2017 at 01:55:02AM -0700, Suganath Prabu S wrote: > diff --git a/drivers/scsi/mpt3sas/mpt3sas_base.h > b/drivers/scsi/mpt3sas/mpt3sas_base.h > index 60fa7b6..cebdd8e 100644 > --- a/drivers/scsi/mpt3sas/mpt3sas_base.h > +++ b/drivers/scsi/mpt3sas/mpt3sas_base.h > @@ -54,6 +54,7 @@

Re: [PATCH 02/13] mpt3sas: SGL to PRP Translation for I/Os to NVMe devices

On Tue, Jul 11, 2017 at 01:55:02AM -0700, Suganath Prabu S wrote: > diff --git a/drivers/scsi/mpt3sas/mpt3sas_base.h > b/drivers/scsi/mpt3sas/mpt3sas_base.h > index 60fa7b6..cebdd8e 100644 > --- a/drivers/scsi/mpt3sas/mpt3sas_base.h > +++ b/drivers/scsi/mpt3sas/mpt3sas_base.h > @@ -54,6 +54,7 @@

Re: [GIT pull] irq updates for 4.13

* Grygorii Strashko [170711 08:40]: > Tony, Potentially we can use pm_runtime_force_suspend()/resume() there, but > they are not compatible with > irqoff context (CPUIdle late stages). > > In other words, below patch should fix this issue, but will break CPUIdle on >

Re: [GIT pull] irq updates for 4.13

* Grygorii Strashko [170711 08:40]: > Tony, Potentially we can use pm_runtime_force_suspend()/resume() there, but > they are not compatible with > irqoff context (CPUIdle late stages). > > In other words, below patch should fix this issue, but will break CPUIdle on > OMAP :( Thanks, yea let's

Re: [PATCH] iscsi-target: Reject immediate data underflow larger than SCSI transfer length

On Tue, 2017-07-11 at 00:22 -0700, Nicholas A. Bellinger wrote: > So rejecting this case as already done in commit abb85a9b51 is the > correct approach for >= v4.3.y. Hello Nic, I hope that you agree that the current target_cmd_size_check() implementation is complicated and ugly. Patch 30/33 of

Re: [PATCH] iscsi-target: Reject immediate data underflow larger than SCSI transfer length

On Tue, 2017-07-11 at 00:22 -0700, Nicholas A. Bellinger wrote: > So rejecting this case as already done in commit abb85a9b51 is the > correct approach for >= v4.3.y. Hello Nic, I hope that you agree that the current target_cmd_size_check() implementation is complicated and ugly. Patch 30/33 of

[ANNOUNCE] v4.11.9-rt7

Dear RT folks! I'm pleased to announce the v4.11.9-rt7 patch set. Changes since v4.11.9-rt6: - Alex Shi fixed a "scheduling while atomic" bug on arm64 in the CPU idle code. - Vikram Mulukutla reported a problem where a parked CPU-hotplug thread was still on the runqueue. Patched

[ANNOUNCE] v4.11.9-rt7

Dear RT folks! I'm pleased to announce the v4.11.9-rt7 patch set. Changes since v4.11.9-rt6: - Alex Shi fixed a "scheduling while atomic" bug on arm64 in the CPU idle code. - Vikram Mulukutla reported a problem where a parked CPU-hotplug thread was still on the runqueue. Patched

Re: [GIT pull] irq updates for 4.13

Hi, On Tue, Jul 11, 2017 at 08:40:10AM -0700, Linus Torvalds wrote: > On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > > > Ah. Now that makes sense. > > > > Unpatched the ordering is: > > > > chip_bus_lock(desc); > > irq_request_resources(desc);

Re: [GIT pull] irq updates for 4.13

Hi, On Tue, Jul 11, 2017 at 08:40:10AM -0700, Linus Torvalds wrote: > On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > > > Ah. Now that makes sense. > > > > Unpatched the ordering is: > > > > chip_bus_lock(desc); > > irq_request_resources(desc); > > I *looked* at

Re: [GIT pull] irq updates for 4.13

* Linus Torvalds [170711 08:40]: > On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > > > Ah. Now that makes sense. > > > > Unpatched the ordering is: > > > > chip_bus_lock(desc); > > irq_request_resources(desc); >

Re: [GIT pull] irq updates for 4.13

* Linus Torvalds [170711 08:40]: > On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > > > Ah. Now that makes sense. > > > > Unpatched the ordering is: > > > > chip_bus_lock(desc); > > irq_request_resources(desc); > > I *looked* at that ordering and then went "Naah,

[PATCH 1/2] ARM: dts: stm32: add ADC support on stm32h7

Add support for ADC (Analog to Digital Converter) to STM32H7. It has 3 ADCs, distributed over two ADC blocks: - ADC1 and ADC2 @0x40022000 - ADC3 @0x58026000 (instantiated separately) Signed-off-by: Fabrice Gasnier --- arch/arm/boot/dts/stm32h743.dtsi | 53

[PATCH 1/2] ARM: dts: stm32: add ADC support on stm32h7

Add support for ADC (Analog to Digital Converter) to STM32H7. It has 3 ADCs, distributed over two ADC blocks: - ADC1 and ADC2 @0x40022000 - ADC3 @0x58026000 (instantiated separately) Signed-off-by: Fabrice Gasnier --- arch/arm/boot/dts/stm32h743.dtsi | 53

[PATCH 2/2] ARM: dts: stm32: enable ADC on stm32h743i-eval board

There's a potentiometer connected to ADC1 and ADC2 in0 on stm32h743i-eval board. - Add fixed-voltage 'vdda' regulator that supplies 'vref' pin. It's used as voltage reference for ADC and/or DAC. - Enable ADC1 in0 input (arbitrary choice: could be ADC2 as well). Note: No pinctrl is needed to use

Re: [PATCH] platform/x86: peaq-wmi: Fix peaq_ignore_events_counter handling off by 1

On Tue, Jul 11, 2017 at 01:41:34PM +0200, Hans de Goede wrote: > If peaq_ignore_events_counter gets set to 1 we should skip polling 1 > time, rather then ignoring it. > > Signed-off-by: Hans de Goede Thanks Hans, queued to testing. -- Darren Hart VMware Open Source

Re: [PATCH] platform/x86: peaq-wmi: Fix peaq_ignore_events_counter handling off by 1

On Tue, Jul 11, 2017 at 01:41:34PM +0200, Hans de Goede wrote: > If peaq_ignore_events_counter gets set to 1 we should skip polling 1 > time, rather then ignoring it. > > Signed-off-by: Hans de Goede Thanks Hans, queued to testing. -- Darren Hart VMware Open Source Technology Center

[PATCH 2/2] ARM: dts: stm32: enable ADC on stm32h743i-eval board

There's a potentiometer connected to ADC1 and ADC2 in0 on stm32h743i-eval board. - Add fixed-voltage 'vdda' regulator that supplies 'vref' pin. It's used as voltage reference for ADC and/or DAC. - Enable ADC1 in0 input (arbitrary choice: could be ADC2 as well). Note: No pinctrl is needed to use

[PATCH 0/2] Enable ADC support on STM32H7

This patchset adds ADC device-tree nodes to STM32H7 SoC and enables ADC1 by default on stm32h743i-eval board. Fabrice Gasnier (2): ARM: dts: stm32: add ADC support on stm32h7 ARM: dts: stm32: enable ADC on stm32h743i-eval board arch/arm/boot/dts/stm32h743.dtsi | 53

[PATCH 0/2] Enable ADC support on STM32H7

This patchset adds ADC device-tree nodes to STM32H7 SoC and enables ADC1 by default on stm32h743i-eval board. Fabrice Gasnier (2): ARM: dts: stm32: add ADC support on stm32h7 ARM: dts: stm32: enable ADC on stm32h743i-eval board arch/arm/boot/dts/stm32h743.dtsi | 53

Re: [PATCH v2] integrity: track mtime in addition to i_version for assessment

On Fri, Jul 07, 2017 at 10:05:30AM -0400, Jeff Layton wrote: > From: Jeff Layton > > The IMA assessment code tries to use the i_version counter to detect > when changes to a file have occurred. Many filesystems don't increment > it properly (or at all) so detecting changes

Re: [PATCH v2] integrity: track mtime in addition to i_version for assessment

On Fri, Jul 07, 2017 at 10:05:30AM -0400, Jeff Layton wrote: > From: Jeff Layton > > The IMA assessment code tries to use the i_version counter to detect > when changes to a file have occurred. Many filesystems don't increment > it properly (or at all) so detecting changes with that is not

Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite

ARGH!!! please, if there are known holes in patches, put a comment in. I now had to independently discover this problem during review of the last patch. On Wed, May 24, 2017 at 05:59:39PM +0900, Byungchul Park wrote: > The ring buffer can be overwritten by hardirq/softirq/work contexts. > That

Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite

ARGH!!! please, if there are known holes in patches, put a comment in. I now had to independently discover this problem during review of the last patch. On Wed, May 24, 2017 at 05:59:39PM +0900, Byungchul Park wrote: > The ring buffer can be overwritten by hardirq/softirq/work contexts. > That

Re: [PATCH v7 05/16] lockdep: Implement crossrelease feature

Sorry for the much delayed response; aside from the usual backlog I got unusually held up by family responsibilities. My comments in the form of a patch.. --- a/include/linux/lockdep.h +++ b/include/linux/lockdep.h @@ -542,10 +542,10 @@ extern void crossrelease_hardirq_start(v extern void

Re: [PATCH v7 05/16] lockdep: Implement crossrelease feature

Sorry for the much delayed response; aside from the usual backlog I got unusually held up by family responsibilities. My comments in the form of a patch.. --- a/include/linux/lockdep.h +++ b/include/linux/lockdep.h @@ -542,10 +542,10 @@ extern void crossrelease_hardirq_start(v extern void

Re: v4l2-fwnode: status, plans for merge, any branch to merge against?

Hi Pavel, On Thu, Jul 06, 2017 at 12:38:51PM +0200, Pavel Machek wrote: > Hi! > > > > > > > I expect to have most of them in during the next merge window. > > > > > > > > > > So git://linuxtv.org/media_tree.git branch master is the right one to > > > > > work one? > > > > > > > > I also pushed

Re: v4l2-fwnode: status, plans for merge, any branch to merge against?

Hi Pavel, On Thu, Jul 06, 2017 at 12:38:51PM +0200, Pavel Machek wrote: > Hi! > > > > > > > I expect to have most of them in during the next merge window. > > > > > > > > > > So git://linuxtv.org/media_tree.git branch master is the right one to > > > > > work one? > > > > > > > > I also pushed

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On Tue, Jul 11, 2017 at 11:41:57AM +0200, Peter Zijlstra wrote: > On Tue, Jul 11, 2017 at 12:40:06PM +0800, Li, Aubrey wrote: > > > On Mon, Jul 10, 2017 at 06:42:06PM +0200, Peter Zijlstra wrote: > > > >> Data to indicate what hurts how much would be a very good addition to > > >> the Changelogs.

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On Tue, Jul 11, 2017 at 11:41:57AM +0200, Peter Zijlstra wrote: > On Tue, Jul 11, 2017 at 12:40:06PM +0800, Li, Aubrey wrote: > > > On Mon, Jul 10, 2017 at 06:42:06PM +0200, Peter Zijlstra wrote: > > > >> Data to indicate what hurts how much would be a very good addition to > > >> the Changelogs.

Re: [PATCH] KVM: VMX: Fix invalid guest state detection after task-switch emulation

On 11/07/2017 17:54, Radim Krčmář wrote: > 2017-07-11 00:13-0700, Wanpeng Li: >> From: Wanpeng Li >> >> This can be reproduced by EPT=1, unrestricted_guest=N, >> emulate_invalid_state=Y >> or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it >> tries

Re: [PATCH] KVM: VMX: Fix invalid guest state detection after task-switch emulation

On 11/07/2017 17:54, Radim Krčmář wrote: > 2017-07-11 00:13-0700, Wanpeng Li: >> From: Wanpeng Li >> >> This can be reproduced by EPT=1, unrestricted_guest=N, >> emulate_invalid_state=Y >> or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it >> tries >> to emulate invalid

[PATCH v2] power: supply: ltc2941-battery-gauge: Add LTC2944 support

The only difference between the already supported LTC2943 and LTC2944 is the operating range (3.6V - 20V compared to 3.6V - 60V). Signed-off-by: Dragos Bogdan --- Changes in v2: - Fix the voltage and current conversion.

[PATCH v2] power: supply: ltc2941-battery-gauge: Add LTC2944 support

The only difference between the already supported LTC2943 and LTC2944 is the operating range (3.6V - 20V compared to 3.6V - 60V). Signed-off-by: Dragos Bogdan --- Changes in v2: - Fix the voltage and current conversion. .../devicetree/bindings/power/supply/ltc2941.txt | 10 ++---

Re: [RFC PATCH v1] irqchip: Add support for tango interrupt router

On 06/06/2017 17:52, Thomas Petazzoni wrote: > On Tue, 6 Jun 2017 15:42:36 +0200, Mason wrote: > >> +interrupt-controller@6f800 { >> +compatible = "sigma,smp8759-intc"; >> +reg = <0x6f800 0x430>; >> +interrupt-controller; >> +#interrupt-cells =

Re: [RFC PATCH v1] irqchip: Add support for tango interrupt router

On 06/06/2017 17:52, Thomas Petazzoni wrote: > On Tue, 6 Jun 2017 15:42:36 +0200, Mason wrote: > >> +interrupt-controller@6f800 { >> +compatible = "sigma,smp8759-intc"; >> +reg = <0x6f800 0x430>; >> +interrupt-controller; >> +#interrupt-cells =

[PATCH] MIPS: pistachio: Enable Root FS on NFS in defconfig

When the upstream kernel pistachio_defconfig is built & tested on the ci40 platform the current lack of these options leads to essentially false failures when the RFS fails to mount. Signed-off-by: Matt Redfearn --- arch/mips/configs/pistachio_defconfig | 5 - 1

[PATCH] MIPS: pistachio: Enable Root FS on NFS in defconfig

When the upstream kernel pistachio_defconfig is built & tested on the ci40 platform the current lack of these options leads to essentially false failures when the RFS fails to mount. Signed-off-by: Matt Redfearn --- arch/mips/configs/pistachio_defconfig | 5 - 1 file changed, 4

Re: [PATCH v3 2/7] libsas: remove unused port_gone_completion

On 10/07/2017 08:06, Yijing Wang wrote: No one uses the port_gone_completion in struct asd_sas_port, clean it out. This seems like a reasonable tidy-up patch which could be taken in isolation, having no dependency on the rest of the series. Signed-off-by: Yijing Wang

Re: [PATCH v3 2/7] libsas: remove unused port_gone_completion

On 10/07/2017 08:06, Yijing Wang wrote: No one uses the port_gone_completion in struct asd_sas_port, clean it out. This seems like a reasonable tidy-up patch which could be taken in isolation, having no dependency on the rest of the series. Signed-off-by: Yijing Wang ---

Re: [PATCH] KVM: VMX: Fix invalid guest state detection after task-switch emulation

2017-07-11 00:13-0700, Wanpeng Li: > From: Wanpeng Li > > This can be reproduced by EPT=1, unrestricted_guest=N, > emulate_invalid_state=Y > or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it > tries > to emulate invalid guest state task-switch:

Re: [PATCH] KVM: VMX: Fix invalid guest state detection after task-switch emulation

2017-07-11 00:13-0700, Wanpeng Li: > From: Wanpeng Li > > This can be reproduced by EPT=1, unrestricted_guest=N, > emulate_invalid_state=Y > or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it > tries > to emulate invalid guest state task-switch: > > kvm_exit: reason

Re: [v6,3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT

Hi Guenter, > > This allows setting a default value for the watchdog.open_timeout > > commandline parameter via Kconfig. > > > > Some BSPs allow remote updating of the kernel image and root file > > system, but updating the bootloader requires physical access. Hence, if > > one has a firmware

Re: [v6,3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT

Hi Guenter, > > This allows setting a default value for the watchdog.open_timeout > > commandline parameter via Kconfig. > > > > Some BSPs allow remote updating of the kernel image and root file > > system, but updating the bootloader requires physical access. Hence, if > > one has a firmware

Re: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)")

On Tue, 20 Jun 2017 01:20:26 +0200, Paul Donohue wrote: > > On Mon, Jun 19, 2017 at 01:02:18PM -0700, Laura Abbott wrote: > > On 06/19/2017 11:43 AM, Paul Donohue wrote: > > > I get the same results as you - x_max and y_max affect cursor speed, and > > > x_res and y_res seem to have no effect.

Re: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)")

On Tue, 20 Jun 2017 01:20:26 +0200, Paul Donohue wrote: > > On Mon, Jun 19, 2017 at 01:02:18PM -0700, Laura Abbott wrote: > > On 06/19/2017 11:43 AM, Paul Donohue wrote: > > > I get the same results as you - x_max and y_max affect cursor speed, and > > > x_res and y_res seem to have no effect.

Re: [PATCH v9 07/38] x86/mm: Remove phys_to_virt() usage in ioremap()

On 7/11/2017 10:38 AM, Brian Gerst wrote: On Tue, Jul 11, 2017 at 11:02 AM, Tom Lendacky wrote: On 7/10/2017 11:58 PM, Brian Gerst wrote: On Mon, Jul 10, 2017 at 3:50 PM, Tom Lendacky wrote: On 7/8/2017 7:57 AM, Brian Gerst wrote: On

Re: [PATCH v9 07/38] x86/mm: Remove phys_to_virt() usage in ioremap()

On 7/11/2017 10:38 AM, Brian Gerst wrote: On Tue, Jul 11, 2017 at 11:02 AM, Tom Lendacky wrote: On 7/10/2017 11:58 PM, Brian Gerst wrote: On Mon, Jul 10, 2017 at 3:50 PM, Tom Lendacky wrote: On 7/8/2017 7:57 AM, Brian Gerst wrote: On Fri, Jul 7, 2017 at 9:39 AM, Tom Lendacky wrote:

Re: [RFC v5 02/38] powerpc: Free up four 64K PTE bits in 64K backed HPTE pages

On Tue, Jul 11, 2017 at 03:59:59PM +1000, Balbir Singh wrote: > On Wed, 5 Jul 2017 14:21:39 -0700 > Ram Pai wrote: > > > Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 > > in the 64K backed HPTE pages. This along with the earlier > > patch will entirely free up

Re: [RFC v5 02/38] powerpc: Free up four 64K PTE bits in 64K backed HPTE pages

On Tue, Jul 11, 2017 at 03:59:59PM +1000, Balbir Singh wrote: > On Wed, 5 Jul 2017 14:21:39 -0700 > Ram Pai wrote: > > > Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 > > in the 64K backed HPTE pages. This along with the earlier > > patch will entirely free up the four bits from

Re: [RFC][PATCH] drm: kirin: Restrict modes to known good mode clocks

On Tue, Jul 11, 2017 at 8:12 AM, Daniel Vetter wrote: > On Tue, Jul 11, 2017 at 5:05 PM, John Stultz wrote: > be even better if you could calculate whether the mode is valid, but I > didn't > spend enough time to figure out if this is

Re: [RFC][PATCH] drm: kirin: Restrict modes to known good mode clocks

On Tue, Jul 11, 2017 at 8:12 AM, Daniel Vetter wrote: > On Tue, Jul 11, 2017 at 5:05 PM, John Stultz wrote: > be even better if you could calculate whether the mode is valid, but I > didn't > spend enough time to figure out if this is possible. Theoretically that might

Re: [PATCH v5 5/5] intel_idle: Add S0ix validation

I acknowledge the specific need for this check to assure a great user-experience on specific hardware. I also concur the motivation to make mechanisms general and generic so they can be re-used. However, it isn't clear to me that this check would be used outside of some very specific scenarios,

RE: [PATCH V3] perf/x86/intel/uncore: remove nonexistent clockticks event for client uncore

> > > User observable change with the patch. > > clockticks event is removed from CBOX. User may need to change their > > script to use uncore_clock/clockticks/ instead. > > I don't think we can do that and break everyone's scripts. Have to keep the > old behavior, even though it is not ideal. >

Re: [PATCH v5 5/5] intel_idle: Add S0ix validation

I acknowledge the specific need for this check to assure a great user-experience on specific hardware. I also concur the motivation to make mechanisms general and generic so they can be re-used. However, it isn't clear to me that this check would be used outside of some very specific scenarios,

RE: [PATCH V3] perf/x86/intel/uncore: remove nonexistent clockticks event for client uncore

> > > User observable change with the patch. > > clockticks event is removed from CBOX. User may need to change their > > script to use uncore_clock/clockticks/ instead. > > I don't think we can do that and break everyone's scripts. Have to keep the > old behavior, even though it is not ideal. >

Re: [GIT pull] irq updates for 4.13

* Thomas Gleixner [170711 08:07]: > On Tue, 11 Jul 2017, Thomas Gleixner wrote: > > On Tue, 11 Jul 2017, Tony Lindgren wrote: > > > * Thomas Gleixner [170711 02:48]: > > > And "external abort on non-linefetch" means something is not clocked > > > in this

Re: [GIT pull] irq updates for 4.13

* Thomas Gleixner [170711 08:07]: > On Tue, 11 Jul 2017, Thomas Gleixner wrote: > > On Tue, 11 Jul 2017, Tony Lindgren wrote: > > > * Thomas Gleixner [170711 02:48]: > > > And "external abort on non-linefetch" means something is not clocked > > > in this case. The following alone makes things

Re: [PATCH] leds: leds-aat1290.c: enclosed arithmetic expression macro

On Tue, 2017-07-11 at 23:23 +0800, Lynn Lei wrote: > Fixed the unenclosed complex values macro issue generated by > scripts/checkpatch.pl: > ERROR: Macros with complex values should be enclosed in parentheses [] > diff --git a/drivers/leds/leds-aat1290.c b/drivers/leds/leds-aat1290.c [] > @@

Re: [PATCH] leds: leds-aat1290.c: enclosed arithmetic expression macro

On Tue, 2017-07-11 at 23:23 +0800, Lynn Lei wrote: > Fixed the unenclosed complex values macro issue generated by > scripts/checkpatch.pl: > ERROR: Macros with complex values should be enclosed in parentheses [] > diff --git a/drivers/leds/leds-aat1290.c b/drivers/leds/leds-aat1290.c [] > @@

Re: [GIT pull] irq updates for 4.13

On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > Ah. Now that makes sense. > > Unpatched the ordering is: > > chip_bus_lock(desc); > irq_request_resources(desc); I *looked* at that ordering and then went "Naah, that makes no sense". But if

Re: [GIT pull] irq updates for 4.13

On Tue, Jul 11, 2017 at 7:41 AM, Thomas Gleixner wrote: > > Ah. Now that makes sense. > > Unpatched the ordering is: > > chip_bus_lock(desc); > irq_request_resources(desc); I *looked* at that ordering and then went "Naah, that makes no sense". But if that's the only issue,

Re: [GIT pull] irq updates for 4.13

On 07/11/2017 09:41 AM, Thomas Gleixner wrote: > On Tue, 11 Jul 2017, Tony Lindgren wrote: >> * Thomas Gleixner [170711 02:48]: >> And "external abort on non-linefetch" means something is not clocked >> in this case. The following alone makes things boot for me again, but I

Re: [GIT pull] irq updates for 4.13

On 07/11/2017 09:41 AM, Thomas Gleixner wrote: > On Tue, 11 Jul 2017, Tony Lindgren wrote: >> * Thomas Gleixner [170711 02:48]: >> And "external abort on non-linefetch" means something is not clocked >> in this case. The following alone makes things boot for me again, but I don't >> quite

Re: [PATCH v9 07/38] x86/mm: Remove phys_to_virt() usage in ioremap()

On Tue, Jul 11, 2017 at 11:02 AM, Tom Lendacky wrote: > On 7/10/2017 11:58 PM, Brian Gerst wrote: >> >> On Mon, Jul 10, 2017 at 3:50 PM, Tom Lendacky >> wrote: >>> >>> On 7/8/2017 7:57 AM, Brian Gerst wrote: On Fri, Jul 7, 2017 at

Re: [PATCH v9 07/38] x86/mm: Remove phys_to_virt() usage in ioremap()

On Tue, Jul 11, 2017 at 11:02 AM, Tom Lendacky wrote: > On 7/10/2017 11:58 PM, Brian Gerst wrote: >> >> On Mon, Jul 10, 2017 at 3:50 PM, Tom Lendacky >> wrote: >>> >>> On 7/8/2017 7:57 AM, Brian Gerst wrote: On Fri, Jul 7, 2017 at 9:39 AM, Tom Lendacky wrote: > >

Re: [PATCH v3 1/7] libsas: Use static sas event pool to appease sas event lost

On 10/07/2017 08:06, Yijing Wang wrote: Now libsas hotplug work is static, every sas event type has its own static work, LLDD driver queue the hotplug work into shost->work_q. If LLDD driver burst post lots hotplug events to libsas, the hotplug events may pending in the workqueue like

Re: [PATCH v3 1/7] libsas: Use static sas event pool to appease sas event lost

On 10/07/2017 08:06, Yijing Wang wrote: Now libsas hotplug work is static, every sas event type has its own static work, LLDD driver queue the hotplug work into shost->work_q. If LLDD driver burst post lots hotplug events to libsas, the hotplug events may pending in the workqueue like

[PATCH v3 01/10] x86/entry/64: Refactor IRQ stacks and make them NMI-safe

From: Andy Lutomirski This will allow IRQ stacks to nest inside NMIs or similar entries that can happen during IRQ stack setup or teardown. The new macros won't work correctly if they're invoked with IRQs on. Add a check under CONFIG_DEBUG_ENTRY to detect that. Signed-off-by:

[PATCH v3 01/10] x86/entry/64: Refactor IRQ stacks and make them NMI-safe

From: Andy Lutomirski This will allow IRQ stacks to nest inside NMIs or similar entries that can happen during IRQ stack setup or teardown. The new macros won't work correctly if they're invoked with IRQs on. Add a check under CONFIG_DEBUG_ENTRY to detect that. Signed-off-by: Andy Lutomirski

[PATCH v3 05/10] objtool: add ORC unwind table generation

Now that objtool knows the states of all registers on the stack for each instruction, it's straightforward to generate debuginfo for an unwinder to use. Instead of generating DWARF, generate a new format called ORC, which is more suitable for an in-kernel unwinder. See

[PATCH v3 05/10] objtool: add ORC unwind table generation

Now that objtool knows the states of all registers on the stack for each instruction, it's straightforward to generate debuginfo for an unwinder to use. Instead of generating DWARF, generate a new format called ORC, which is more suitable for an in-kernel unwinder. See

[PATCH v3 07/10] x86/entry/64: add unwind hint annotations

Add unwind hint annotations to entry_64.S. This will enable the ORC unwinder to unwind through any location in the entry code including syscalls, interrupts, and exceptions. Signed-off-by: Josh Poimboeuf --- arch/x86/entry/Makefile | 1 - arch/x86/entry/calling.h | 5

[PATCH v3 06/10] objtool, x86: add facility for asm code to provide unwind hints

Some asm (and inline asm) code does special things to the stack which objtool can't understand. (Nor can GCC or GNU assembler, for that matter.) In such cases we need a facility for the code to provide annotations, so the unwinder can unwind through it. This provides such a facility, in the

[PATCH v3 07/10] x86/entry/64: add unwind hint annotations

Add unwind hint annotations to entry_64.S. This will enable the ORC unwinder to unwind through any location in the entry code including syscalls, interrupts, and exceptions. Signed-off-by: Josh Poimboeuf --- arch/x86/entry/Makefile | 1 - arch/x86/entry/calling.h | 5

[PATCH v3 06/10] objtool, x86: add facility for asm code to provide unwind hints

Some asm (and inline asm) code does special things to the stack which objtool can't understand. (Nor can GCC or GNU assembler, for that matter.) In such cases we need a facility for the code to provide annotations, so the unwinder can unwind through it. This provides such a facility, in the

[PATCH v3 04/10] x86/dumpstack: fix interrupt and exception stack boundary checks

On x86_64, the double fault exception stack is located immediately after the interrupt stack in memory. This causes confusion in the unwinder when it tries to unwind through an empty interrupt stack, where the stack pointer points to the address bordering the two stacks. The unwinder incorrectly

[PATCH v3 04/10] x86/dumpstack: fix interrupt and exception stack boundary checks

On x86_64, the double fault exception stack is located immediately after the interrupt stack in memory. This causes confusion in the unwinder when it tries to unwind through an empty interrupt stack, where the stack pointer points to the address bordering the two stacks. The unwinder incorrectly

[PATCH v3 09/10] x86/unwind: add ORC unwinder

Add a new ORC unwinder which is enabled by CONFIG_ORC_UNWINDER. It plugs into the existing x86 unwinder framework. It relies on objtool to generate the needed .orc_unwind and .orc_unwind_ip sections. For more details on why ORC is used instead of DWARF, see Documentation/x86/orc-unwinder.txt.

[PATCH v3 09/10] x86/unwind: add ORC unwinder

Add a new ORC unwinder which is enabled by CONFIG_ORC_UNWINDER. It plugs into the existing x86 unwinder framework. It relies on objtool to generate the needed .orc_unwind and .orc_unwind_ip sections. For more details on why ORC is used instead of DWARF, see Documentation/x86/orc-unwinder.txt.

[PATCH v3 10/10] x86/kconfig: make it easier to switch to the new ORC unwinder

A couple of Kconfig changes which make it much easier to switch to the new CONFIG_ORC_UNWINDER: 1) Remove x86 dependencies on CONFIG_FRAME_POINTER for lockdep, latencytop, and fault injection. x86 has a 'guess' unwinder which just scans the stack for kernel text addresses. It's not 100%

[PATCH v3 10/10] x86/kconfig: make it easier to switch to the new ORC unwinder

A couple of Kconfig changes which make it much easier to switch to the new CONFIG_ORC_UNWINDER: 1) Remove x86 dependencies on CONFIG_FRAME_POINTER for lockdep, latencytop, and fault injection. x86 has a 'guess' unwinder which just scans the stack for kernel text addresses. It's not 100%

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