Re: [tip:x86/boot] x86/KASLR: Fix boot crash with certain memory configurations

On 07/10/16 at 01:24pm, Ingo Molnar wrote: > > * Baoquan He wrote: > > > Hi Ingo, > > > > I am sorry the previous post didn't contain formal patch log. I made a new > > one > > as below. The boot crash could not only happen with certain memory. Because > > of > > this code

Re: [tip:x86/boot] x86/KASLR: Fix boot crash with certain memory configurations

On 07/10/16 at 01:24pm, Ingo Molnar wrote: > > * Baoquan He wrote: > > > Hi Ingo, > > > > I am sorry the previous post didn't contain formal patch log. I made a new > > one > > as below. The boot crash could not only happen with certain memory. Because > > of > > this code bug the regions

[tip:irq/core] irq/Documentation: Correct result of echnoing 5 to smp_affinity

Commit-ID: 99e9d958726c04cec3e36902d8583fdd8cb5b1bb Gitweb: http://git.kernel.org/tip/99e9d958726c04cec3e36902d8583fdd8cb5b1bb Author: John Kacur AuthorDate: Fri, 17 Jun 2016 15:05:15 +0200 Committer: Ingo Molnar CommitDate: Sun, 10 Jul 2016

[tip:irq/core] irq/Documentation: Correct result of echnoing 5 to smp_affinity

Commit-ID: 99e9d958726c04cec3e36902d8583fdd8cb5b1bb Gitweb: http://git.kernel.org/tip/99e9d958726c04cec3e36902d8583fdd8cb5b1bb Author: John Kacur AuthorDate: Fri, 17 Jun 2016 15:05:15 +0200 Committer: Ingo Molnar CommitDate: Sun, 10 Jul 2016 16:55:04 +0200 irq/Documentation: Correct

Re: [PATCH v2 2/2] input: add ADC resistor ladder driver

On 09/07/16 02:24, Alexandre Belloni wrote: > A common way of multiplexing buttons on a single input in cheap devices is > to use a resistor ladder on an ADC. This driver supports that configuration > by polling an ADC channel provided by IIO. > > Signed-off-by: Alexandre Belloni

Re: [PATCH v2 1/2] input: adc-keys: add DT binding documentation

On 09/07/16 02:24, Alexandre Belloni wrote: > Add documentation for ADC keys > > Signed-off-by: Alexandre Belloni I'm seeing a few more properties in the driver. They may be generic input ones, but should still be listed here... autorepeat for example. >

Re: [PATCH v2 2/2] input: add ADC resistor ladder driver

On 09/07/16 02:24, Alexandre Belloni wrote: > A common way of multiplexing buttons on a single input in cheap devices is > to use a resistor ladder on an ADC. This driver supports that configuration > by polling an ADC channel provided by IIO. > > Signed-off-by: Alexandre Belloni Acked-by:

Re: [PATCH v2 1/2] input: adc-keys: add DT binding documentation

On 09/07/16 02:24, Alexandre Belloni wrote: > Add documentation for ADC keys > > Signed-off-by: Alexandre Belloni I'm seeing a few more properties in the driver. They may be generic input ones, but should still be listed here... autorepeat for example. > --- > Changes in v2: > - fix title >

Re: Odd performance results

On Sun, Jul 10, 2016 at 07:17:19AM +0200, Peter Zijlstra wrote: > > > On 10 July 2016 06:26:39 CEST, "Paul E. McKenney" > wrote: > >Hello! > > > >So I ran a quick benchmark which showed stair-step results. I > >immediately > >thought "Ah, this is due to CPU 0 and

Re: Odd performance results

On Sun, Jul 10, 2016 at 07:17:19AM +0200, Peter Zijlstra wrote: > > > On 10 July 2016 06:26:39 CEST, "Paul E. McKenney" > wrote: > >Hello! > > > >So I ran a quick benchmark which showed stair-step results. I > >immediately > >thought "Ah, this is due to CPU 0 and 1, 2 and 3, 4 and 5, and 6

Re: How to set Current register in IIO driver from sysfs

On 10/07/16 14:11, Pratik Prajapati wrote: > Including more members. > > On Sat, Jul 9, 2016 at 5:22 PM, Pratik Prajapati > wrote: >> Hi, hi Pratik, >> >> I am trying to add support of adjusting IR led current in vcnl4000 >> driver (has IR led current register for

Re: How to set Current register in IIO driver from sysfs

On 10/07/16 14:11, Pratik Prajapati wrote: > Including more members. > > On Sat, Jul 9, 2016 at 5:22 PM, Pratik Prajapati > wrote: >> Hi, hi Pratik, >> >> I am trying to add support of adjusting IR led current in vcnl4000 >> driver (has IR led current register for doing the same). This is always

[PATCH v2] spi: spi-sh: Remove deprecated create_singlethread_workqueue

The workqueue has a single workitem(>ws) and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, the singlethreaded workqueue has been replaced with the use of system_wq. System workqueues have been able to handle high level of concurrency for a long time

[PATCH v2] spi: spi-sh: Remove deprecated create_singlethread_workqueue

The workqueue has a single workitem(>ws) and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, the singlethreaded workqueue has been replaced with the use of system_wq. System workqueues have been able to handle high level of concurrency for a long time

Re: [PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: frv-defconfig (attached as .config) compiler: frv-linux-gcc (GCC) 4.9.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin

Re: [PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: frv-defconfig (attached as .config) compiler: frv-linux-gcc (GCC) 4.9.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin

[PATCH v2] spi: spi-topcliff-pch: Remove deprecated create_singlethread_workqueue

The workqueue "wk" serves as a queue for carrying out execution of requests. It has a single work item(_data->work) and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, the singlethreaded workqueue has been replaced with the use of system_wq. System

[PATCH v2] spi: spi-topcliff-pch: Remove deprecated create_singlethread_workqueue

The workqueue "wk" serves as a queue for carrying out execution of requests. It has a single work item(_data->work) and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, the singlethreaded workqueue has been replaced with the use of system_wq. System

[PATCH] sched/core: add doc for cookie argument

Add documentation for the cookie argument in try_to_wake_up_local() This caused the following warning when building documentation: kernel/sched/core.c:2088: warning: No description found for parameter 'cookie' Fixes: e7904a28f533 ("ilocking/lockdep, sched/core: Implement a better lock pinning

[PATCH] sched/core: add doc for cookie argument

Add documentation for the cookie argument in try_to_wake_up_local() This caused the following warning when building documentation: kernel/sched/core.c:2088: warning: No description found for parameter 'cookie' Fixes: e7904a28f533 ("ilocking/lockdep, sched/core: Implement a better lock pinning

Re: [PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: sh-sh7785lcr_32bit_defconfig (attached as .config) compiler: sh4-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O

Re: [PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: sh-sh7785lcr_32bit_defconfig (attached as .config) compiler: sh4-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O

Re: Missing include file in include/uapi/linux/errqueue.h?

On Sun, Jul 10, 2016 at 1:43 AM, Brooks Moses wrote: > On Sat, Jul 9, 2016 at 10:36 AM, Brooks Moses wrote: >> I've been attempting to qualify the Linux 4.5.2 user-space headers for >> a toolchain release, and ran into what looks like a missing include >>

Re: Missing include file in include/uapi/linux/errqueue.h?

On Sun, Jul 10, 2016 at 1:43 AM, Brooks Moses wrote: > On Sat, Jul 9, 2016 at 10:36 AM, Brooks Moses wrote: >> I've been attempting to qualify the Linux 4.5.2 user-space headers for >> a toolchain release, and ran into what looks like a missing include >> file in include/uapi/linux/errqueue.h.

Re: [PATCH] iio: temperature: mcp9808: add Microchip MCP9808 temperature sensor

On 03/07/16 22:04, Alison Schofield wrote: > IIO driver, perhaps a reference driver, since this sensor is already > supported in hwmon/jc42 driver. > > Driver supports continuous conversion, resolution changes and > suspend/resume power ops. > > Signed-off-by: Alison Schofield

Re: [PATCH] iio: temperature: mcp9808: add Microchip MCP9808 temperature sensor

On 03/07/16 22:04, Alison Schofield wrote: > IIO driver, perhaps a reference driver, since this sensor is already > supported in hwmon/jc42 driver. > > Driver supports continuous conversion, resolution changes and > suspend/resume power ops. > > Signed-off-by: Alison Schofield > Cc: Daniel

Re: [PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: i386-randconfig-s1-201628 (attached as .config) compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed

Re: [PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: i386-randconfig-s1-201628 (attached as .config) compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed

Re: How to set Current register in IIO driver from sysfs

Including more members. On Sat, Jul 9, 2016 at 5:22 PM, Pratik Prajapati wrote: > Hi, > > I am trying to add support of adjusting IR led current in vcnl4000 > driver (has IR led current register for doing the same). > > Below is what I have done till now: > > 1)

Re: How to set Current register in IIO driver from sysfs

Including more members. On Sat, Jul 9, 2016 at 5:22 PM, Pratik Prajapati wrote: > Hi, > > I am trying to add support of adjusting IR led current in vcnl4000 > driver (has IR led current register for doing the same). > > Below is what I have done till now: > > 1) Added Current channel in the

Re: [PATCH v4 3/5]nbd: make nbd device wait for its users

On 2016 M06 30, Thu 14:02:03 CEST Pranay Kr. Srivastava wrote: > When a timeout occurs or a recv fails, then > instead of abruplty killing nbd block device > wait for its users to finish. > > This is more required when filesystem(s) like > ext2 or ext3 don't expect their buffer heads to >

Re: [PATCH v4 3/5]nbd: make nbd device wait for its users

On 2016 M06 30, Thu 14:02:03 CEST Pranay Kr. Srivastava wrote: > When a timeout occurs or a recv fails, then > instead of abruplty killing nbd block device > wait for its users to finish. > > This is more required when filesystem(s) like > ext2 or ext3 don't expect their buffer heads to >

KASAN vs vmapped stacks

Hi all- I found two nasty issues with virtually mapped stacks if KASAN is enabled. The first issue is a crash: the first non-init stack is allocated and accessed before KASAN initializes its zero shadow AFAICT, which means that we switch to that stack and then blow up when we start recursively

KASAN vs vmapped stacks

Hi all- I found two nasty issues with virtually mapped stacks if KASAN is enabled. The first issue is a crash: the first non-init stack is allocated and accessed before KASAN initializes its zero shadow AFAICT, which means that we switch to that stack and then blow up when we start recursively

Re: [PATCH 3/4] arch, x86, tsc: inform TSC deadline clockevent device about recalibration

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: i386-tinyconfig (attached as .config) compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed by >>):

Re: [PATCH 3/4] arch, x86, tsc: inform TSC deadline clockevent device about recalibration

/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914 config: i386-tinyconfig (attached as .config) compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed by >>):

Re: [PATCHv2 3/6] x86/arch_prctl/vdso: add ARCH_MAP_VDSO_*

On Thu, Jul 7, 2016 at 4:11 AM, Dmitry Safonov wrote: > On 07/06/2016 05:30 PM, Andy Lutomirski wrote: >> >> On Wed, Jun 29, 2016 at 3:57 AM, Dmitry Safonov >> wrote: >>> >>> Add API to change vdso blob type with arch_prctl. >>> As this is usefull

Re: [PATCHv2 3/6] x86/arch_prctl/vdso: add ARCH_MAP_VDSO_*

On Thu, Jul 7, 2016 at 4:11 AM, Dmitry Safonov wrote: > On 07/06/2016 05:30 PM, Andy Lutomirski wrote: >> >> On Wed, Jun 29, 2016 at 3:57 AM, Dmitry Safonov >> wrote: >>> >>> Add API to change vdso blob type with arch_prctl. >>> As this is usefull only by needs of CRIU, expose >>> this interface

Re: [PATCH 0/9] mm: Hardened usercopy

On Sun, Jul 10, 2016 at 5:03 AM, PaX Team wrote: > On 10 Jul 2016 at 11:16, Ingo Molnar wrote: > >> * PaX Team wrote: >> >> > On 9 Jul 2016 at 14:27, Andy Lutomirski wrote: >> > >> > > I like the series, but I have one minor nit to pick. The effect of

Re: [PATCH 0/9] mm: Hardened usercopy

On Sun, Jul 10, 2016 at 5:03 AM, PaX Team wrote: > On 10 Jul 2016 at 11:16, Ingo Molnar wrote: > >> * PaX Team wrote: >> >> > On 9 Jul 2016 at 14:27, Andy Lutomirski wrote: >> > >> > > I like the series, but I have one minor nit to pick. The effect of this >> > > series is to harden usercopy,

Re: [tip:x86/debug] printk: Make the printk*once() variants return a value

On Sun, 2016-07-10 at 14:06 +0200, Borislav Petkov wrote: > On Sun, Jul 10, 2016 at 01:23:51AM -0700, Joe Perches wrote: > > > > Assuming tip is included in linux-next as of july 8, yes. > Try one which has http://git.kernel.org/tip/81c2949f7fdcf8ff681326669a > fde24962232670 That commit isn't

Re: [tip:x86/debug] printk: Make the printk*once() variants return a value

On Sun, 2016-07-10 at 14:06 +0200, Borislav Petkov wrote: > On Sun, Jul 10, 2016 at 01:23:51AM -0700, Joe Perches wrote: > > > > Assuming tip is included in linux-next as of july 8, yes. > Try one which has http://git.kernel.org/tip/81c2949f7fdcf8ff681326669a > fde24962232670 That commit isn't

Re: [PATCH v4 2/5]nbd: fix might_sleep warning on socket shutdown

Hi, On 2016 M06 30, Thu 14:02:02 CEST Pranay Kr. Srivastava wrote: > spinlocked ranges should be small and not contain calls into huge > subfunctions. Fix my mistake and just get the pointer to the socket > instead of doing everything with spinlock held. > > Reported-by: Mikulas Patocka

Re: [PATCH v4 2/5]nbd: fix might_sleep warning on socket shutdown

Hi, On 2016 M06 30, Thu 14:02:02 CEST Pranay Kr. Srivastava wrote: > spinlocked ranges should be small and not contain calls into huge > subfunctions. Fix my mistake and just get the pointer to the socket > instead of doing everything with spinlock held. > > Reported-by: Mikulas Patocka >

[PATCH 2/4] arch, x86, tsc deadline clockevent dev: reduce TSC_DIVISOR to 2

In order to avoid overflowing an u32, the TSC deadline clockevent device's frequency is divided by TSC_DIVISOR at registration. The TSC_DIVISOR is currently defined as equaling 32 which allows for a TSC frequency as high as 2^32 / 10^9ns * 32 = 137 GHz. OTOH, larger values of TSC_DIVISOR

[PATCH 2/4] arch, x86, tsc deadline clockevent dev: reduce TSC_DIVISOR to 2

In order to avoid overflowing an u32, the TSC deadline clockevent device's frequency is divided by TSC_DIVISOR at registration. The TSC_DIVISOR is currently defined as equaling 32 which allows for a TSC frequency as high as 2^32 / 10^9ns * 32 = 137 GHz. OTOH, larger values of TSC_DIVISOR

[PATCH 3/4] arch, x86, tsc: inform TSC deadline clockevent device about recalibration

The TSC deadline clockevent devices' configuration and registration happens before the TSC frequency calibration is refined in tsc_refine_calibration_work(). This results in the TSC clocksource and the TSC deadline clockevent devices being configured with slightly different frequencies: the

[PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

With NOHZ_FULL and one single well-isolated, CPU consumptive task, one would expect approximately one clockevent interrupt per second. However, on my Intel Haswell where the monotonic clock is the TSC monotonic clock and the clockevent device is the TSC deadline device, it turns out that every

[PATCH 1/4] arch, x86, tsc deadline clockevent dev: reduce frequency roundoff error

In setup_APIC_timer(), the registered clockevent device's frequency is calculated by first dividing tsc_khz by TSC_DIVISOR and multiplying it with 1000 afterwards. The multiplication with 1000 is done for converting from kHz to Hz and the division by TSC_DIVISOR is carried out in order to make

[PATCH 0/4] avoid double timer interrupt with nohz and Intel TSC

With a single task running on a NOHZ CPU on an Intel Haswell, I recognized that I did not only get the one expected local_timer APIC interrupt, but two per second at minimum. Further tracing showed that the first one preceedes the programmed deadline by up to ~50us and hence, it did nothing

[PATCH 3/4] arch, x86, tsc: inform TSC deadline clockevent device about recalibration

The TSC deadline clockevent devices' configuration and registration happens before the TSC frequency calibration is refined in tsc_refine_calibration_work(). This results in the TSC clocksource and the TSC deadline clockevent devices being configured with slightly different frequencies: the

[PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency

With NOHZ_FULL and one single well-isolated, CPU consumptive task, one would expect approximately one clockevent interrupt per second. However, on my Intel Haswell where the monotonic clock is the TSC monotonic clock and the clockevent device is the TSC deadline device, it turns out that every

[PATCH 1/4] arch, x86, tsc deadline clockevent dev: reduce frequency roundoff error

In setup_APIC_timer(), the registered clockevent device's frequency is calculated by first dividing tsc_khz by TSC_DIVISOR and multiplying it with 1000 afterwards. The multiplication with 1000 is done for converting from kHz to Hz and the division by TSC_DIVISOR is carried out in order to make

[PATCH 0/4] avoid double timer interrupt with nohz and Intel TSC

With a single task running on a NOHZ CPU on an Intel Haswell, I recognized that I did not only get the one expected local_timer APIC interrupt, but two per second at minimum. Further tracing showed that the first one preceedes the programmed deadline by up to ~50us and hence, it did nothing

Re: [PATCH] nvme-loop: add configfs dependency

On Thu, Jul 07, 2016 at 08:35:17AM -0600, Jens Axboe wrote: > Thanks Arnd, applied. Actually I think we should replace the select with the depends. In fact I though I had done that a while ago, but I must have messed it up. Btw - do you plan to grab patches directly from the list now or do you

Re: [PATCH] nvme-loop: add configfs dependency

On Thu, Jul 07, 2016 at 08:35:17AM -0600, Jens Axboe wrote: > Thanks Arnd, applied. Actually I think we should replace the select with the depends. In fact I though I had done that a while ago, but I must have messed it up. Btw - do you plan to grab patches directly from the list now or do you

Re: [tip:x86/debug] printk: Make the printk*once() variants return a value

On Sun, Jul 10, 2016 at 01:23:51AM -0700, Joe Perches wrote: > Assuming tip is included in linux-next as of july 8, yes. Try one which has http://git.kernel.org/tip/81c2949f7fdcf8ff681326669afde24962232670 -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --

Re: [tip:x86/debug] printk: Make the printk*once() variants return a value

On Sun, Jul 10, 2016 at 01:23:51AM -0700, Joe Perches wrote: > Assuming tip is included in linux-next as of july 8, yes. Try one which has http://git.kernel.org/tip/81c2949f7fdcf8ff681326669afde24962232670 -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --

Re: [PATCH 0/9] mm: Hardened usercopy

On 10 Jul 2016 at 11:16, Ingo Molnar wrote: > * PaX Team wrote: > > > On 9 Jul 2016 at 14:27, Andy Lutomirski wrote: > > > > > I like the series, but I have one minor nit to pick. The effect of this > > > series is to harden usercopy, but most of the code is really

Re: [PATCH 0/9] mm: Hardened usercopy

On 10 Jul 2016 at 11:16, Ingo Molnar wrote: > * PaX Team wrote: > > > On 9 Jul 2016 at 14:27, Andy Lutomirski wrote: > > > > > I like the series, but I have one minor nit to pick. The effect of this > > > series is to harden usercopy, but most of the code is really about > > >

Re: [PATCH] iommu/amd: Fix unity mapping initialization race

On 2016年07月07日 00:00, Joerg Roedel wrote: From: Joerg Roedel There is a race condition in the AMD IOMMU init code that causes requested unity mappings to be blocked by the IOMMU for a short period of time. This results on boot failures and IO_PAGE_FAULTs on some machines.

Re: [PATCH] iommu/amd: Fix unity mapping initialization race

On 2016年07月07日 00:00, Joerg Roedel wrote: From: Joerg Roedel There is a race condition in the AMD IOMMU init code that causes requested unity mappings to be blocked by the IOMMU for a short period of time. This results on boot failures and IO_PAGE_FAULTs on some machines. Fix this by making

[tip:x86/asm] x86/entry: Inline enter_from_user_mode()

Commit-ID: be8a18e2e98e04a5def5887d913b267865562448 Gitweb: http://git.kernel.org/tip/be8a18e2e98e04a5def5887d913b267865562448 Author: Paolo Bonzini AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200 Committer: Ingo Molnar CommitDate: Sun, 10 Jul 2016

[tip:x86/asm] x86/entry: Inline enter_from_user_mode()

Commit-ID: be8a18e2e98e04a5def5887d913b267865562448 Gitweb: http://git.kernel.org/tip/be8a18e2e98e04a5def5887d913b267865562448 Author: Paolo Bonzini AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200 Committer: Ingo Molnar CommitDate: Sun, 10 Jul 2016 13:33:02 +0200 x86/entry: Inline

[tip:x86/asm] x86/entry: Avoid interrupt flag save and restore

Commit-ID: 2e9d1e150abf88cb63e5d34ca286edbb95b4c53d Gitweb: http://git.kernel.org/tip/2e9d1e150abf88cb63e5d34ca286edbb95b4c53d Author: Paolo Bonzini AuthorDate: Mon, 20 Jun 2016 16:58:29 +0200 Committer: Ingo Molnar CommitDate: Sun, 10 Jul 2016

[tip:x86/asm] x86/entry: Avoid interrupt flag save and restore

Commit-ID: 2e9d1e150abf88cb63e5d34ca286edbb95b4c53d Gitweb: http://git.kernel.org/tip/2e9d1e150abf88cb63e5d34ca286edbb95b4c53d Author: Paolo Bonzini AuthorDate: Mon, 20 Jun 2016 16:58:29 +0200 Committer: Ingo Molnar CommitDate: Sun, 10 Jul 2016 13:33:02 +0200 x86/entry: Avoid

Re: [tip:x86/asm] x86/entry: Inline enter_from_user_mode()

* Borislav Petkov wrote: > tip-bot for Paolo Bonzini wrote: > > >Commit-ID: eec4b1227db153ca16f8f5f285d01fefdce05438 > >Gitweb: > >http://git.kernel.org/tip/eec4b1227db153ca16f8f5f285d01fefdce05438 > >Author: Paolo Bonzini >

Re: [tip:x86/asm] x86/entry: Inline enter_from_user_mode()

* Borislav Petkov wrote: > tip-bot for Paolo Bonzini wrote: > > >Commit-ID: eec4b1227db153ca16f8f5f285d01fefdce05438 > >Gitweb: > >http://git.kernel.org/tip/eec4b1227db153ca16f8f5f285d01fefdce05438 > >Author: Paolo Bonzini > >AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200 > >Committer:

[tip:x86/platform] x86/platform/intel-mid: Mark regulators explicitly defined

Commit-ID: a11836fa5a67ba56d8338138e37b42384af73e5e Gitweb: http://git.kernel.org/tip/a11836fa5a67ba56d8338138e37b42384af73e5e Author: Andy Shevchenko AuthorDate: Sat, 9 Jul 2016 16:45:29 +0300 Committer: Ingo Molnar CommitDate: Sun,

[tip:x86/platform] x86/platform/intel-mid: Mark regulators explicitly defined

Commit-ID: a11836fa5a67ba56d8338138e37b42384af73e5e Gitweb: http://git.kernel.org/tip/a11836fa5a67ba56d8338138e37b42384af73e5e Author: Andy Shevchenko AuthorDate: Sat, 9 Jul 2016 16:45:29 +0300 Committer: Ingo Molnar CommitDate: Sun, 10 Jul 2016 10:33:41 +0200 x86/platform/intel-mid:

[PATCH v1] driver core: fix race between creating/querying glue dir and its cleanup

The global mutex of 'gdp_mutex' is used to serialize creating/querying glue dir and its cleanup. Turns out it isn't a perfect way because part(kobj_kset_leave()) of the actual cleanup action() is done inside the release handler of the glue dir kobject. That means gdp_mutex has to be held before

[PATCH v1] driver core: fix race between creating/querying glue dir and its cleanup

The global mutex of 'gdp_mutex' is used to serialize creating/querying glue dir and its cleanup. Turns out it isn't a perfect way because part(kobj_kset_leave()) of the actual cleanup action() is done inside the release handler of the glue dir kobject. That means gdp_mutex has to be held before

Re: [tip:x86/boot] x86/KASLR: Fix boot crash with certain memory configurations

* Baoquan He wrote: > Hi Ingo, > > I am sorry the previous post didn't contain formal patch log. I made a new > one > as below. The boot crash could not only happen with certain memory. Because > of > this code bug the regions which need be avoided like the zipped kernel

Re: [tip:x86/boot] x86/KASLR: Fix boot crash with certain memory configurations

* Baoquan He wrote: > Hi Ingo, > > I am sorry the previous post didn't contain formal patch log. I made a new > one > as below. The boot crash could not only happen with certain memory. Because > of > this code bug the regions which need be avoided like the zipped kernel with > its >

[PATCH 02/10] perf tools: Introduce trace_event__tp_format_id function

To get struct event_format object from tracepoint ID. It will be used in following patches. Link: http://lkml.kernel.org/n/tip-0omstcxuxa8npi3otondl...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/trace-event.c | 9 + tools/perf/util/trace-event.h | 2 ++

[PATCH 00/10] perf python: Add support to access tracepoint fields

hi, adding support to access tracepoint fields in python scripts. With this patchset it's possible to access tracepoint fields in event python object like: print "time %u prev_comm=%s prev_pid=%d prev_prio=%d prev_state=0x%x ==> next_comm=%s next_pid=%d next_prio=%d" % (

[PATCH 04/10] perf python: Fix pyrf_evlist__read_on_cpu event consuming

We can't consume the event before parsing it. Under heavy load we could get caught by kernel writer overwriting the event we're trying to parse. Link: http://lkml.kernel.org/n/tip-8dbalvrufeisa4cioyd9k...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/python.c | 6

[PATCH 02/10] perf tools: Introduce trace_event__tp_format_id function

To get struct event_format object from tracepoint ID. It will be used in following patches. Link: http://lkml.kernel.org/n/tip-0omstcxuxa8npi3otondl...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/trace-event.c | 9 + tools/perf/util/trace-event.h | 2 ++ 2 files changed,

[PATCH 00/10] perf python: Add support to access tracepoint fields

hi, adding support to access tracepoint fields in python scripts. With this patchset it's possible to access tracepoint fields in event python object like: print "time %u prev_comm=%s prev_pid=%d prev_prio=%d prev_state=0x%x ==> next_comm=%s next_pid=%d next_prio=%d" % (

[PATCH 04/10] perf python: Fix pyrf_evlist__read_on_cpu event consuming

We can't consume the event before parsing it. Under heavy load we could get caught by kernel writer overwriting the event we're trying to parse. Link: http://lkml.kernel.org/n/tip-8dbalvrufeisa4cioyd9k...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/python.c | 6 -- 1 file

[PATCH 05/10] perf python: Put perf.event objects into dictionary

Make perf.event object parts of the perf module dictionary so we can address them by name. Following objects/names are added: mmap_event lost_event comm_event task_event throttle_event task_event read_event sample_event switch_event We can now use it in python script like:

[PATCH 05/10] perf python: Put perf.event objects into dictionary

Make perf.event object parts of the perf module dictionary so we can address them by name. Following objects/names are added: mmap_event lost_event comm_event task_event throttle_event task_event read_event sample_event switch_event We can now use it in python script like:

[PATCH 10/10] perf script python: Fix string vs byte array resolving

Jirka reported that python code returns all arrays as strings. This makes impossible to get all items for byte array tracepoint field containing 0x00 value item. Fixing this by scanning full length of the array and returning it as PyByteArray object in case non printable byte is found. Cc:

[PATCH 10/10] perf script python: Fix string vs byte array resolving

Jirka reported that python code returns all arrays as strings. This makes impossible to get all items for byte array tracepoint field containing 0x00 value item. Fixing this by scanning full length of the array and returning it as PyByteArray object in case non printable byte is found. Cc:

[PATCH 09/10] perf python: Add tracepoint example

To show how to open tracepoint and access its fields. Reported-and-tested-by: Jiri Pirko Link: http://lkml.kernel.org/n/tip-7xt9nvyl45qwbg9237f46...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/python/tracepoint.py | 47

[PATCH 08/10] perf python: Add support to resolve tracepoint fields

Adding tp_getattro callback for sample event. It resolves tracepoint fields in runtime. It's now possible to access tracepoint fields in normal fashion like hardcoded ones (see the example in the next patch). Reported-and-tested-by: Jiri Pirko Link:

[PATCH 09/10] perf python: Add tracepoint example

To show how to open tracepoint and access its fields. Reported-and-tested-by: Jiri Pirko Link: http://lkml.kernel.org/n/tip-7xt9nvyl45qwbg9237f46...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/python/tracepoint.py | 47 + 1 file changed, 47

[PATCH 08/10] perf python: Add support to resolve tracepoint fields

Adding tp_getattro callback for sample event. It resolves tracepoint fields in runtime. It's now possible to access tracepoint fields in normal fashion like hardcoded ones (see the example in the next patch). Reported-and-tested-by: Jiri Pirko Link:

[PATCH 07/10] perf python: Add struct evsel into struct pyrf_event

To be able to find out event configuration info during sample parsing. Link: http://lkml.kernel.org/n/tip-b63rh6l44ort2t76etobv...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/python.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git

[PATCH 06/10] perf python: Add perf.tracepoint method

To get id of the tracepoint from subsystem and name strings. The interface is: id = perf.tracepoint(sys, name) In case of error -1 is returned. It will be used to get python tracepoint event's config value for tracepoint event. Link:

[PATCH 07/10] perf python: Add struct evsel into struct pyrf_event

To be able to find out event configuration info during sample parsing. Link: http://lkml.kernel.org/n/tip-b63rh6l44ort2t76etobv...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/python.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git

[PATCH 06/10] perf python: Add perf.tracepoint method

To get id of the tracepoint from subsystem and name strings. The interface is: id = perf.tracepoint(sys, name) In case of error -1 is returned. It will be used to get python tracepoint event's config value for tracepoint event. Link:

[PATCH 01/10] perf tools: Make perf_evlist__event2evsel public

It will be used outside of evlist.c object in folowing patches. Link: http://lkml.kernel.org/n/tip-m4jswtxn3ff3jn5qoo5h6...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/evlist.c | 4 ++-- tools/perf/util/evlist.h | 3 +++ 2 files changed, 5 insertions(+), 2

[PATCH 03/10] perf python: Init perf_event_attr::size in perf.evsel constructor

Currently 0 is passed as perf_event_attr::size, which could block usage of new features. Link: http://lkml.kernel.org/n/tip-kyzkn52sg75mcqrhsjbfe...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/python.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 01/10] perf tools: Make perf_evlist__event2evsel public

It will be used outside of evlist.c object in folowing patches. Link: http://lkml.kernel.org/n/tip-m4jswtxn3ff3jn5qoo5h6...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/evlist.c | 4 ++-- tools/perf/util/evlist.h | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-) diff

[PATCH 03/10] perf python: Init perf_event_attr::size in perf.evsel constructor

Currently 0 is passed as perf_event_attr::size, which could block usage of new features. Link: http://lkml.kernel.org/n/tip-kyzkn52sg75mcqrhsjbfe...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/python.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/util/python.c

Re: [GIT PULL] ACPI fixes for v4.7-rc7

Hi Rafael! On 08.07.2016 01:43, Rafael J. Wysocki wrote: > > Please pull from > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ > acpi-4.7-rc7 > > to receive ACPI fixes for v4.7-rc7 with top-most commit > […] > All of these fix recent regressions in ACPICA, in the ACPI

Re: [GIT PULL] ACPI fixes for v4.7-rc7

Hi Rafael! On 08.07.2016 01:43, Rafael J. Wysocki wrote: > > Please pull from > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ > acpi-4.7-rc7 > > to receive ACPI fixes for v4.7-rc7 with top-most commit > […] > All of these fix recent regressions in ACPICA, in the ACPI

Re: [RFC PATCH 0/3] doc-rst: customize HTML (RTD) theme

Em Sat, 9 Jul 2016 23:22:22 -0600 Jonathan Corbet escreveu: > On Tue, 5 Jul 2016 14:55:09 -0300 > Mauro Carvalho Chehab wrote: > > > I hope you don't mind. I'm merging those three patches on my tree > > (for now, they're on an experimental tree that I

Re: [RFC PATCH 0/3] doc-rst: customize HTML (RTD) theme

Em Sat, 9 Jul 2016 23:22:22 -0600 Jonathan Corbet escreveu: > On Tue, 5 Jul 2016 14:55:09 -0300 > Mauro Carvalho Chehab wrote: > > > I hope you don't mind. I'm merging those three patches on my tree > > (for now, they're on an experimental tree that I can easily rebase, if > > needed). If OK

<    1   2   3   4   5   >