[PATCH] Revert "pinctrl: amd: make it explicitly non-modular"

This reverts commit b8c2b10a9bc0272a20e096852f8fbbf361749dda. This patch was in my queue at the same time that a conversion of the same driver from bool --> tristate was pending and merged. That is commit 337ea0fb1535 ("pinctrl: Turn AMD support to tristate") Normally the conflict would show up

[PATCH] Revert "pinctrl: amd: make it explicitly non-modular"

This reverts commit b8c2b10a9bc0272a20e096852f8fbbf361749dda. This patch was in my queue at the same time that a conversion of the same driver from bool --> tristate was pending and merged. That is commit 337ea0fb1535 ("pinctrl: Turn AMD support to tristate") Normally the conflict would show up

[PATCH][RFC v5] PM / hibernate: Introduce test_resume mode for hibernation

test_resume mode is to verify if the snapshot data written to swap device can be successfully restored to memory. It is useful to ease the debugging process on hibernation, since this mode can not only bypass the BIOSes/bootloader, but also the system re-initialization. For example: echo

[PATCH][RFC v5] PM / hibernate: Introduce test_resume mode for hibernation

test_resume mode is to verify if the snapshot data written to swap device can be successfully restored to memory. It is useful to ease the debugging process on hibernation, since this mode can not only bypass the BIOSes/bootloader, but also the system re-initialization. For example: echo

[PATCH] f2fs: fix to report error number of f2fs_find_entry

This patch fixes to report the right error number of f2fs_find_entry to its caller. Signed-off-by: Chao Yu --- fs/f2fs/dir.c | 10 +- fs/f2fs/f2fs.h | 2 +- fs/f2fs/namei.c| 46 +++--- fs/f2fs/recovery.c | 7

[PATCH] f2fs: fix to report error number of f2fs_find_entry

This patch fixes to report the right error number of f2fs_find_entry to its caller. Signed-off-by: Chao Yu --- fs/f2fs/dir.c | 10 +- fs/f2fs/f2fs.h | 2 +- fs/f2fs/namei.c| 46 +++--- fs/f2fs/recovery.c | 7 +-- 4 files

Re: [PATCH/RFC] Re: linux-next: build failure after merge of the luto-misc tree

Hi Arnaldo, On Mon, 18 Jul 2016 20:41:32 -0300 Arnaldo Carvalho de Melo wrote: > > Ok, one of the possible reasons was for tools/{include,lib,perf,objtool} > code to be including code directly from the kernel, and that was still > the case for some headers, I fixed those and

Re: [PATCH/RFC] Re: linux-next: build failure after merge of the luto-misc tree

Hi Arnaldo, On Mon, 18 Jul 2016 20:41:32 -0300 Arnaldo Carvalho de Melo wrote: > > Ok, one of the possible reasons was for tools/{include,lib,perf,objtool} > code to be including code directly from the kernel, and that was still > the case for some headers, I fixed those and pushed to Ingo now,

Re: [PATCH V10 4/9] vfio: platform: add support for ACPI probe

On Mon, 18 Jul 2016 20:16:50 -0400 ok...@codeaurora.org wrote: > On 2016-07-18 20:00, Alex Williamson wrote: > > On Mon, 18 Jul 2016 19:09:22 -0400 > > Sinan Kaya wrote: > > > >> The code is using the compatible DT string to associate a reset driver > >> with the actual

Re: [PATCH V10 4/9] vfio: platform: add support for ACPI probe

On Mon, 18 Jul 2016 20:16:50 -0400 ok...@codeaurora.org wrote: > On 2016-07-18 20:00, Alex Williamson wrote: > > On Mon, 18 Jul 2016 19:09:22 -0400 > > Sinan Kaya wrote: > > > >> The code is using the compatible DT string to associate a reset driver > >> with the actual device itself. The

Re: [PATCH V10 4/9] vfio: platform: add support for ACPI probe

On 2016-07-18 20:00, Alex Williamson wrote: On Mon, 18 Jul 2016 19:09:22 -0400 Sinan Kaya wrote: The code is using the compatible DT string to associate a reset driver with the actual device itself. The compatible string does not exist on ACPI based systems. HID is the

Re: [PATCH V10 4/9] vfio: platform: add support for ACPI probe

On 2016-07-18 20:00, Alex Williamson wrote: On Mon, 18 Jul 2016 19:09:22 -0400 Sinan Kaya wrote: The code is using the compatible DT string to associate a reset driver with the actual device itself. The compatible string does not exist on ACPI based systems. HID is the unique identifier for a

Re: [PATCH 1/2] x86/dumpstack: Optimize save_stack_trace

On Mon, Jul 18, 2016 at 08:09:10AM -0500, Josh Poimboeuf wrote: > > > > There are several different users of save_stack_trace() in the kernel, > > > > we can't > > > > be sure that all of them are interested in dropping those guesses. > > > > > > > > So I'd rather advocate in favour of a new

Re: [PATCH 1/2] x86/dumpstack: Optimize save_stack_trace

On Mon, Jul 18, 2016 at 08:09:10AM -0500, Josh Poimboeuf wrote: > > > > There are several different users of save_stack_trace() in the kernel, > > > > we can't > > > > be sure that all of them are interested in dropping those guesses. > > > > > > > > So I'd rather advocate in favour of a new

Re: [STABLE] kernel oops which can be fixed by peterz's patches

On Mon, Jul 18, 2016 at 09:09:45PM +0900, Greg KH wrote: > > > All now applied to the 3.14-stable queue, thanks. > > > > Hello, > > > > I realized this was not applied to 3.18-stable yet. > > > > Is there any reason? > > I don't maintain the 3.18-stable tree, so there's nothing I can do >

Re: [STABLE] kernel oops which can be fixed by peterz's patches

On Mon, Jul 18, 2016 at 09:09:45PM +0900, Greg KH wrote: > > > All now applied to the 3.14-stable queue, thanks. > > > > Hello, > > > > I realized this was not applied to 3.18-stable yet. > > > > Is there any reason? > > I don't maintain the 3.18-stable tree, so there's nothing I can do >

Re: [PATCH V10 4/9] vfio: platform: add support for ACPI probe

On Mon, 18 Jul 2016 19:09:22 -0400 Sinan Kaya wrote: > The code is using the compatible DT string to associate a reset driver > with the actual device itself. The compatible string does not exist on > ACPI based systems. HID is the unique identifier for a device driver >

Re: [PATCH V10 4/9] vfio: platform: add support for ACPI probe

On Mon, 18 Jul 2016 19:09:22 -0400 Sinan Kaya wrote: > The code is using the compatible DT string to associate a reset driver > with the actual device itself. The compatible string does not exist on > ACPI based systems. HID is the unique identifier for a device driver > instead. > >

Re: [PATCH 3/3] mm, vmstat: remove zone and node double accounting by approximating retries -fix

On Mon, Jul 18, 2016 at 03:50:26PM +0100, Mel Gorman wrote: > As pointed out by Vlastimil, the atomic_add() functions are already assumed > to be able to handle negative numbers. The atomic_sub handling was wrong > anyway but this patch fixes it unconditionally. > > This is a fix to the mmotm

Re: [PATCH 3/3] mm, vmstat: remove zone and node double accounting by approximating retries -fix

On Mon, Jul 18, 2016 at 03:50:26PM +0100, Mel Gorman wrote: > As pointed out by Vlastimil, the atomic_add() functions are already assumed > to be able to handle negative numbers. The atomic_sub handling was wrong > anyway but this patch fixes it unconditionally. > > This is a fix to the mmotm

Re: [PATCH v2] [media] ad9389b: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 04:34:41PM +0530, Bhaktipriya Shridhar wrote: > The workqueue work_queue is involved in EDID (Extended Display > Identification Data) handling. > > It has a single work item(>edid_handler) and hence > doesn't require ordering. It is not being used on a memory reclaim path.

Re: [PATCH v2] [media] ad9389b: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 04:34:41PM +0530, Bhaktipriya Shridhar wrote: > The workqueue work_queue is involved in EDID (Extended Display > Identification Data) handling. > > It has a single work item(>edid_handler) and hence > doesn't require ordering. It is not being used on a memory reclaim path.

Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change

On Mon, Jul 18, 2016 at 03:50:25PM +0100, Mel Gorman wrote: > With node-lru, the locking is based on the pgdat. As Minchan pointed > out, there is an opportunity to reduce LRU lock release/acquire in > check_move_unevictable_pages by only changing lock on a pgdat change. > > Signed-off-by: Mel

Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change

On Mon, Jul 18, 2016 at 03:50:25PM +0100, Mel Gorman wrote: > With node-lru, the locking is based on the pgdat. As Minchan pointed > out, there is an opportunity to reduce LRU lock release/acquire in > check_move_unevictable_pages by only changing lock on a pgdat change. > > Signed-off-by: Mel

Re: [PATCH 2/2] [media] cx25821: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:43:20PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "_irq_audio_queues" runs the audio upstream handler. > It has a single work item(>_audio_work_entry) and hence doesn't > require ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH 2/2] [media] cx25821: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:43:20PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "_irq_audio_queues" runs the audio upstream handler. > It has a single work item(>_audio_work_entry) and hence doesn't > require ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH 1/2] [media] cx25821: Drop Freeing of Workqueue

On Sat, Jul 16, 2016 at 02:41:49PM +0530, Bhaktipriya Shridhar wrote: > Workqueues shouldn't be freed. destroy_workqueue should be used instead. > destroy_workqueue safely destroys a workqueue and ensures that all pending > work items are done before destroying the workqueue. > > Signed-off-by:

Re: [PATCH 1/2] [media] cx25821: Drop Freeing of Workqueue

On Sat, Jul 16, 2016 at 02:41:49PM +0530, Bhaktipriya Shridhar wrote: > Workqueues shouldn't be freed. destroy_workqueue should be used instead. > destroy_workqueue safely destroys a workqueue and ensures that all pending > work items are done before destroying the workqueue. > > Signed-off-by:

Re: [PATCH 1/3] mm, vmscan: Remove redundant check in shrink_zones()

On Mon, Jul 18, 2016 at 03:50:24PM +0100, Mel Gorman wrote: > As pointed out by Minchan Kim, shrink_zones() checks for populated > zones in a zonelist but a zonelist can never contain unpopulated > zones. While it's not related to the node-lru series, it can be > cleaned up now. > > Suggested-by:

Re: [PATCH 1/3] mm, vmscan: Remove redundant check in shrink_zones()

On Mon, Jul 18, 2016 at 03:50:24PM +0100, Mel Gorman wrote: > As pointed out by Minchan Kim, shrink_zones() checks for populated > zones in a zonelist but a zonelist can never contain unpopulated > zones. While it's not related to the node-lru series, it can be > cleaned up now. > > Suggested-by:

Re: [PATCH] [media] gspca: finepix: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:25:56PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in streaming the camera data. > It has a single work item(>work_struct) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] gspca: finepix: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:25:56PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in streaming the camera data. > It has a single work item(>work_struct) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] gspca: jl2005bcd: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:23:48PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in streaming the camera data. > It has a single work item(>work_struct) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] gspca: vicam: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:22:19PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in streaming the camera data. > It has a single work item(>work_struct) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] gspca: jl2005bcd: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:23:48PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in streaming the camera data. > It has a single work item(>work_struct) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] gspca: vicam: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:22:19PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in streaming the camera data. > It has a single work item(>work_struct) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] gspca: sonixj: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:20:28PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in updating the JPEG quality > of the gspca_dev. It has a single work item(>work) and hence doesn't > require ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] gspca: sonixj: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:20:28PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in updating the JPEG quality > of the gspca_dev. It has a single work item(>work) and hence doesn't > require ordering. Also, it is not being used on a memory reclaim path. > Hence, the

Re: [PATCH] [media] pvrusb2: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:02:34PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "workqueue" is involved in polling the pvrusb2 hardware > (pvr2_hdw). > > It has a single work item(>workpoll) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence,

Re: [PATCH] [media] pvrusb2: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:02:34PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "workqueue" is involved in polling the pvrusb2 hardware > (pvr2_hdw). > > It has a single work item(>workpoll) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. > Hence,

Re: [PATCH] [media] s5p-mfc: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:00:25PM +0530, Bhaktipriya Shridhar wrote: > alloc_workqueue replaces deprecated create_singlethread_workqueue(). > > The MFC device driver is a v4l2 driver which can encode/decode video > raw/elementary streams and has support for all popular video codecs. > > The

Re: [PATCH] [media] s5p-mfc: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:00:25PM +0530, Bhaktipriya Shridhar wrote: > alloc_workqueue replaces deprecated create_singlethread_workqueue(). > > The MFC device driver is a v4l2 driver which can encode/decode video > raw/elementary streams and has support for all popular video codecs. > > The

Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8?

Hi all- There are four core patches needed for the THREAD_INFO_IN_TASK thing, and they apply cleanly to -mm now. The x86 patch to flip the feature on does not apply cleanly anywhere because it depends on changes in -tip *and* in -mm. I'd like to get all of this as well as the rest of the

Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8?

Hi all- There are four core patches needed for the THREAD_INFO_IN_TASK thing, and they apply cleanly to -mm now. The x86 patch to flip the feature on does not apply cleanly anywhere because it depends on changes in -tip *and* in -mm. I'd like to get all of this as well as the rest of the

Re: [PATCH -next] module: use kmemdup rather than duplicating its implementation

weiyj...@163.com writes: > From: Wei Yongjun > > Use kmemdup rather than duplicating its implementation. > > Generated by: scripts/coccinelle/api/memdup.cocci > > Signed-off-by: Wei Yongjun Hi Wei! This code has been removed

Re: [PATCH -next] module: use kmemdup rather than duplicating its implementation

weiyj...@163.com writes: > From: Wei Yongjun > > Use kmemdup rather than duplicating its implementation. > > Generated by: scripts/coccinelle/api/memdup.cocci > > Signed-off-by: Wei Yongjun Hi Wei! This code has been removed by other changes in modules-next, so your very nice cleanup

Re: [PATCH] [media] s5p-mfc: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:00:25PM +0530, Bhaktipriya Shridhar wrote: > alloc_workqueue replaces deprecated create_singlethread_workqueue(). > > The MFC device driver is a v4l2 driver which can encode/decode video > raw/elementary streams and has support for all popular video codecs. > > The

Re: [PATCH] [media] s5p-mfc: Remove deprecated create_singlethread_workqueue

On Sat, Jul 16, 2016 at 02:00:25PM +0530, Bhaktipriya Shridhar wrote: > alloc_workqueue replaces deprecated create_singlethread_workqueue(). > > The MFC device driver is a v4l2 driver which can encode/decode video > raw/elementary streams and has support for all popular video codecs. > > The

mmotm 2016-07-18-16-40 uploaded

The mm-of-the-moment snapshot 2016-07-18-16-40 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH] drm/ttm: Remove create_singlethread_workqueue

On Sat, Jul 16, 2016 at 01:50:17PM +0530, Bhaktipriya Shridhar wrote: > swap_queue was created to handle shrinking in low memory situations. > A separate workqueue was used in order to avoid other workqueue tasks > from being blocked since work items on swap_queue spend a lot of time > waiting for

Re: [PATCH/RFC] Re: linux-next: build failure after merge of the luto-misc tree

Em Tue, Jul 19, 2016 at 08:22:35AM +1000, Stephen Rothwell escreveu: > Hi Arnaldo, > > On Mon, 18 Jul 2016 17:36:34 -0300 Arnaldo Carvalho de Melo > wrote: > > > > Em Mon, Jul 18, 2016 at 01:04:34PM -0700, Andy Lutomirski escreveu: > > > On Sun, Jul 17, 2016 at 10:18 PM,

mmotm 2016-07-18-16-40 uploaded

The mm-of-the-moment snapshot 2016-07-18-16-40 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH] drm/ttm: Remove create_singlethread_workqueue

On Sat, Jul 16, 2016 at 01:50:17PM +0530, Bhaktipriya Shridhar wrote: > swap_queue was created to handle shrinking in low memory situations. > A separate workqueue was used in order to avoid other workqueue tasks > from being blocked since work items on swap_queue spend a lot of time > waiting for

Re: [PATCH/RFC] Re: linux-next: build failure after merge of the luto-misc tree

Em Tue, Jul 19, 2016 at 08:22:35AM +1000, Stephen Rothwell escreveu: > Hi Arnaldo, > > On Mon, 18 Jul 2016 17:36:34 -0300 Arnaldo Carvalho de Melo > wrote: > > > > Em Mon, Jul 18, 2016 at 01:04:34PM -0700, Andy Lutomirski escreveu: > > > On Sun, Jul 17, 2016 at 10:18 PM, Stephen Rothwell > > >

[PATCH 07/15] tools: Copy the bitops files accessed from the kernel and check for drift

From: Arnaldo Carvalho de Melo copy some more kernel files accessed from tools/, check for drift. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan

[PATCH 07/15] tools: Copy the bitops files accessed from the kernel and check for drift

From: Arnaldo Carvalho de Melo copy some more kernel files accessed from tools/, check for drift. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: http://lkml.kernel.org/n/tip-omz8xdyvvxgjiuqzwj6ec...@git.kernel.org Signed-off-by: Arnaldo Carvalho de Melo

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

From: Jiri Olsa 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

[PATCH 12/15] perf probe: Warn unmatched function filter correctly

From: Masami Hiramatsu Warn unmatched function filter correctly instead of warning "symbol-loading error", since that can be a filter issue. >From the technical point of view, this adds a filter chech in map__load and if there is a filter, it returns -2 (filter-out),

Re: [PATCH v3 1/4] lib/dlock-list: Distributed and lock-protected lists

Hello, Waiman. On Fri, Jul 15, 2016 at 01:39:40PM -0400, Waiman Long wrote: > Suggested-by: Tejun Heo Not sure I should be on suggested-by given that this wasn't my idea at all. > +/* > + * include/linux/dlock-list.h > + * > + * A distributed (per-cpu) set of lists each of

[PATCH 04/15] perf tools: Remove tools/perf/util/include/asm/byteorder.h

From: Arnaldo Carvalho de Melo Not used anymore. This also stops include linux/swab.h directly from the kernel sources, remove that reference from the MANIFEST. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc:

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

From: Jiri Olsa 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

[PATCH 12/15] perf probe: Warn unmatched function filter correctly

From: Masami Hiramatsu Warn unmatched function filter correctly instead of warning "symbol-loading error", since that can be a filter issue. >From the technical point of view, this adds a filter chech in map__load and if there is a filter, it returns -2 (filter-out), instead of -1 (error), and

Re: [PATCH v3 1/4] lib/dlock-list: Distributed and lock-protected lists

Hello, Waiman. On Fri, Jul 15, 2016 at 01:39:40PM -0400, Waiman Long wrote: > Suggested-by: Tejun Heo Not sure I should be on suggested-by given that this wasn't my idea at all. > +/* > + * include/linux/dlock-list.h > + * > + * A distributed (per-cpu) set of lists each of which is protected

[PATCH 04/15] perf tools: Remove tools/perf/util/include/asm/byteorder.h

From: Arnaldo Carvalho de Melo Not used anymore. This also stops include linux/swab.h directly from the kernel sources, remove that reference from the MANIFEST. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Signed-off-by: Arnaldo Carvalho de Melo ---

[GIT PULL 00/15] perf/core improvements and fixes

+0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-20160718 for you to fetch changes up to 988dd774dcbd9151c2a643fc7284c5c3c4d0adb7: perf tests: Add is_printable_array test (2016-07-18 19:50:35

[PATCH 11/15] perf cpu_map: Add more helpers

From: Mark Rutland In some cases it's necessry to figure out the map-local index of a given Linux logical CPU ID. Add a new helper, cpu_map__idx, to acquire this. As the logic is largely the same as the existing cpu_map__has, this is rewritten in terms of the new helper.

[PATCH 10/15] perf stat: Balance opening and reading events

From: Mark Rutland In create_perf_stat_counter, when a target CPU has not been provided, we call __perf_evsel__open with empty_cpu_map, and open a single FD per thread. However, in read_counter we assume that we opened events for the product of threads and CPUs described in

[GIT PULL 00/15] perf/core improvements and fixes

repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-20160718 for you to fetch changes up to 988dd774dcbd9151c2a643fc7284c5c3c4d0adb7: perf tests: Add is_printable_array test (2016-07-18 19:50:35 -0300

[PATCH 11/15] perf cpu_map: Add more helpers

From: Mark Rutland In some cases it's necessry to figure out the map-local index of a given Linux logical CPU ID. Add a new helper, cpu_map__idx, to acquire this. As the logic is largely the same as the existing cpu_map__has, this is rewritten in terms of the new helper. At the same time, add

[PATCH 10/15] perf stat: Balance opening and reading events

From: Mark Rutland In create_perf_stat_counter, when a target CPU has not been provided, we call __perf_evsel__open with empty_cpu_map, and open a single FD per thread. However, in read_counter we assume that we opened events for the product of threads and CPUs described in the evsel's cpu_map.

RE: [PATCH] timekeeping: Fix memory overwrite of sleep_time_bin array

Hi Rafael, > -Original Message- > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Sent: Tuesday, July 19, 2016 6:02 AM > To: Chen, Yu C > Cc: John Stultz; Thomas Gleixner; linux-kernel@vger.kernel.org; Linux PM list > Subject: Re: [PATCH] timekeeping: Fix memory overwrite of

[PATCH 09/15] tools: Copy linux/{hash,poison}.h and check for drift

From: Arnaldo Carvalho de Melo We were also using this directly from the kernel sources, the two last cases, fix it. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang

[PATCH 06/15] Remove: kernel unistd*h files from perf's MANIFEST, not used

From: Arnaldo Carvalho de Melo No need to copy it to a detached tarball as they aren't used anymore Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan

[PATCH 15/15] perf tests: Add is_printable_array test

From: Jiri Olsa Add automated test for is_printable_array function. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Jiri Pirko Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Steven

[PATCH 14/15] perf tools: Make is_printable_array global

From: Jiri Olsa It's used from 2 objects in perf, so it's better to keep just one copy. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Jiri Pirko Cc: Namhyung Kim Cc: Peter Zijlstra

[PATCH 06/15] Remove: kernel unistd*h files from perf's MANIFEST, not used

From: Arnaldo Carvalho de Melo No need to copy it to a detached tarball as they aren't used anymore Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: http://lkml.kernel.org/n/tip-lopmaqi439ke10g1j9cxr...@git.kernel.org Signed-off-by: Arnaldo Carvalho de

[PATCH 15/15] perf tests: Add is_printable_array test

From: Jiri Olsa Add automated test for is_printable_array function. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Jiri Pirko Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Steven Rostedt Link: http://lkml.kernel.org/r/1468685480-18951-4-git-send-email-jo...@kernel.org Signed-off-by: Arnaldo

[PATCH 14/15] perf tools: Make is_printable_array global

From: Jiri Olsa It's used from 2 objects in perf, so it's better to keep just one copy. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Jiri Pirko Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Steven Rostedt Link: http://lkml.kernel.org/r/1468685480-18951-3-git-send-email-jo...@kernel.org

RE: [PATCH] timekeeping: Fix memory overwrite of sleep_time_bin array

Hi Rafael, > -Original Message- > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Sent: Tuesday, July 19, 2016 6:02 AM > To: Chen, Yu C > Cc: John Stultz; Thomas Gleixner; linux-kernel@vger.kernel.org; Linux PM list > Subject: Re: [PATCH] timekeeping: Fix memory overwrite of

[PATCH 09/15] tools: Copy linux/{hash,poison}.h and check for drift

From: Arnaldo Carvalho de Melo We were also using this directly from the kernel sources, the two last cases, fix it. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: http://lkml.kernel.org/n/tip-7o14xvacqcjc5llc7gvjj...@git.kernel.org Signed-off-by:

[PATCH 08/15] perf tools: Remove include/linux/list.h from perf's MANIFEST

From: Arnaldo Carvalho de Melo It hasn't been used since we made tools/ self sufficiente wrt list.h. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Josh Poimboeuf Cc: Namhyung Kim

[PATCH 08/15] perf tools: Remove include/linux/list.h from perf's MANIFEST

From: Arnaldo Carvalho de Melo It hasn't been used since we made tools/ self sufficiente wrt list.h. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Josh Poimboeuf Cc: Namhyung Kim Cc: Wang Nan Fixes: d1b39d41ebec ("tools: Make list.h self-sufficient") Link:

[PATCH 02/15] perf jit: Remove some no-op error handling

From: Dan Carpenter The 'info.e_machine' struct member is an uint16_t so 'm' is never less than zero. It looks like this was maybe left over code from earlier versions so I've just removed it. Signed-off-by: Dan Carpenter Cc: Adrian Hunter

[PATCH 01/15] perf jit: Add missing curly braces

From: Dan Carpenter It doesn't change the runtime behavior, but my static checker complains that curly braces were intended. Signed-off-by: Dan Carpenter Cc: Adrian Hunter Cc: Alexander Shishkin

[PATCH 05/15] perf tools: Remove tools/perf/util/include/linux/const.h

From: Arnaldo Carvalho de Melo Not used anymore, remove one more file referencing kernel sources, i.e. outside of tools/ Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc:

[PATCH 03/15] perf tools: Add missing linux/compiler.h include to perf-sys.h

From: Arnaldo Carvalho de Melo It uses the likely/unlikely macros, so need to include . Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan

[PATCH 03/15] perf tools: Add missing linux/compiler.h include to perf-sys.h

From: Arnaldo Carvalho de Melo It uses the likely/unlikely macros, so need to include . Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: http://lkml.kernel.org/n/tip-p0xrhgbkicsii9ohmhhpr...@git.kernel.org Signed-off-by: Arnaldo Carvalho de Melo ---

[PATCH 01/15] perf jit: Add missing curly braces

From: Dan Carpenter It doesn't change the runtime behavior, but my static checker complains that curly braces were intended. Signed-off-by: Dan Carpenter Cc: Adrian Hunter Cc: Alexander Shishkin Cc: Peter Zijlstra Cc: Stephane Eranian Cc: kernel-janit...@vger.kernel.org Link:

[PATCH 05/15] perf tools: Remove tools/perf/util/include/linux/const.h

From: Arnaldo Carvalho de Melo Not used anymore, remove one more file referencing kernel sources, i.e. outside of tools/ Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: http://lkml.kernel.org/n/tip-ykfjt3t8l0npxfwmekiww...@git.kernel.org Signed-off-by:

[PATCH 02/15] perf jit: Remove some no-op error handling

From: Dan Carpenter The 'info.e_machine' struct member is an uint16_t so 'm' is never less than zero. It looks like this was maybe left over code from earlier versions so I've just removed it. Signed-off-by: Dan Carpenter Cc: Adrian Hunter Cc: Alexander Shishkin Cc: Peter Zijlstra Cc:

4.7-rc7: use-after-free in proc_map_files_readdir

Just caught this spew during a fuzz-run. [ 4971.564511] == [ 4971.570505] BUG: KASAN: use-after-free in proc_map_files_readdir+0x2e3/0x5a0 at addr 88044feb2044 [ 4971.582570] Read of size 4 by task trinity-main/29845 [

4.7-rc7: use-after-free in proc_map_files_readdir

Just caught this spew during a fuzz-run. [ 4971.564511] == [ 4971.570505] BUG: KASAN: use-after-free in proc_map_files_readdir+0x2e3/0x5a0 at addr 88044feb2044 [ 4971.582570] Read of size 4 by task trinity-main/29845 [

[PATCH V10 9/9] vfio: platform: check reset call return code during release

Release call is ignoring the return code from reset call and can potentially continue even though reset call failed. If reset_required module parameter is set, this patch is going to validate the return code and will cause stack dump with WARN_ON and warn the user of failure. Signed-off-by:

[PATCH V10 9/9] vfio: platform: check reset call return code during release

Release call is ignoring the return code from reset call and can potentially continue even though reset call failed. If reset_required module parameter is set, this patch is going to validate the return code and will cause stack dump with WARN_ON and warn the user of failure. Signed-off-by:

Re: [PATCH] radix-tree: fix radix_tree_iter_retry() for tagged iterators.

On Fri, Jul 15, 2016 at 01:57:33PM -0700, Andrew Morton wrote: > On Fri, 15 Jul 2016 13:00:40 -0600 Ross Zwisler > wrote: > > > > > ... > > > > In looking at this more, I agree that your patch fixes this particular bug, > > but I think that ultimately we might

[PATCH V10 2/9] vfio: platform: move reset call to a common function

The reset call sequence seems to replicate itself multiple times across the file. Grouping them together for maintenance reasons. Signed-off-by: Sinan Kaya Reviewed-by: Eric Auger Reviewed-by: Baptiste Reynal ---

Re: [PATCH V2 01/10] Documentation: dt-bindings: mailbox: tegra: Add binding for HSP mailbox

On 07/11/2016 10:08 AM, Stephen Warren wrote: On 07/11/2016 08:14 AM, Rob Herring wrote: On Thu, Jul 07, 2016 at 12:35:02PM -0600, Stephen Warren wrote: On 07/07/2016 12:13 PM, Sivaram Nair wrote: On Tue, Jul 05, 2016 at 05:04:22PM +0800, Joseph Lo wrote: Add DT binding for the Hardware

[PATCH V10 1/9] vfio: platform: rename reset function

Renaming the reset function to of_reset as it is only used by the device tree based platforms. Signed-off-by: Sinan Kaya Reviewed-by: Eric Auger Reviewed-by: Baptiste Reynal ---

[PATCH V10 7/9] vfio, platform: make reset driver a requirement by default

The code was allowing platform devices to be used without a supporting VFIO reset driver. The hardware can be left in some inconsistent state after a guest machine abort. The reset driver will put the hardware back to safe state and disable interrupts before returning the control back to the host

[PATCH V10 3/9] vfio: platform: determine reset capability

Creating a new function to determine if this driver supports reset function or not. This is an attempt to abstract device tree calls from the rest of the code. Signed-off-by: Sinan Kaya Reviewed-by: Eric Auger Reviewed-by: Baptiste Reynal

<    1   2   3   4   5   6   7   8   9   10   >