Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM

Hi Vinod, On 2017-02-13 16:47, Vinod Koul wrote: On Mon, Feb 13, 2017 at 04:32:32PM +0100, Ulf Hansson wrote: [...] Although, I don't know of other examples, besides the runtime PM use case, where non-atomic channel prepare/unprepare would make sense. Do you? The primary ask for that has

Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM

Hi Vinod, On 2017-02-13 16:47, Vinod Koul wrote: On Mon, Feb 13, 2017 at 04:32:32PM +0100, Ulf Hansson wrote: [...] Although, I don't know of other examples, besides the runtime PM use case, where non-atomic channel prepare/unprepare would make sense. Do you? The primary ask for that has

Re: [PATCH v3 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > Sometimes we have to dereference next field of llist node before entering > loop becasue the node might be deleted or the next field might be > modified within the loop. So this adds the safe version of llist_for_each, > that is,

Re: [PATCH v3 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > Sometimes we have to dereference next field of llist node before entering > loop becasue the node might be deleted or the next field might be > modified within the loop. So this adds the safe version of llist_for_each, > that is, llist_for_each_safe. > > Signed-off-by:

Re: [PATCH v2] tags: honor COMPILED_SOURCE with apart output directory

Robert Jarzmik writes: > Robert Jarzmik writes: >> Signed-off-by: Robert Jarzmik >> --- >> Since v1: amended k expression, Marek's comments > Hi Marek, > > Is this version good for you ? Marek, could you take a look

Re: [PATCH v2] tags: honor COMPILED_SOURCE with apart output directory

Robert Jarzmik writes: > Robert Jarzmik writes: >> Signed-off-by: Robert Jarzmik >> --- >> Since v1: amended k expression, Marek's comments > Hi Marek, > > Is this version good for you ? Marek, could you take a look please ? -- Robert >> --- >> scripts/tags.sh | 3 ++- >> 1 file changed, 2

RE: [tip:locking/core] refcount_t: Introduce a special purpose refcount type

> Subject: refcount: Out-of-line everything > From: Peter Zijlstra > Date: Fri Feb 10 16:27:52 CET 2017 > > Linus asked to please make this real C code. Perhaps a completely stupid question, but I am going to ask anyway since only this way I can learn. What a real

RE: [tip:locking/core] refcount_t: Introduce a special purpose refcount type

> Subject: refcount: Out-of-line everything > From: Peter Zijlstra > Date: Fri Feb 10 16:27:52 CET 2017 > > Linus asked to please make this real C code. Perhaps a completely stupid question, but I am going to ask anyway since only this way I can learn. What a real difference it makes? Or are

[PATCH v3 8/9] sched: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/sched/core.c | 15 +++ 1 file changed, 3 insertions(+), 12 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index

[PATCH v3 7/9] irq_work: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/irq_work.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/kernel/irq_work.c b/kernel/irq_work.c index bcf107c..e2ebe8c 100644 ---

[PATCH v3 8/9] sched: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/sched/core.c | 15 +++ 1 file changed, 3 insertions(+), 12 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index d01f9d0..8938125 100644 ---

[PATCH v3 7/9] irq_work: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/irq_work.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/kernel/irq_work.c b/kernel/irq_work.c index bcf107c..e2ebe8c 100644 --- a/kernel/irq_work.c +++

[PATCH v3 5/9] fput: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/file_table.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/file_table.c b/fs/file_table.c index 6d982b5..3209da2 100644 ---

[PATCH v3 9/9] mm: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- mm/vmalloc.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 3ca82d4..8c0eb45 100644 ---

[PATCH v3 9/9] mm: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- mm/vmalloc.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 3ca82d4..8c0eb45 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c

[PATCH v3 5/9] fput: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/file_table.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/file_table.c b/fs/file_table.c index 6d982b5..3209da2 100644 --- a/fs/file_table.c +++

[PATCH v3 6/9] namespace.c: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/namespace.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index b5b1259..5cb2229 100644 ---

[PATCH v3 6/9] namespace.c: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/namespace.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index b5b1259..5cb2229 100644 --- a/fs/namespace.c +++

[PATCH v3 1/9] llist: Provide a safe version for llist_for_each

Sometimes we have to dereference next field of llist node before entering loop becasue the node might be deleted or the next field might be modified within the loop. So this adds the safe version of llist_for_each, that is, llist_for_each_safe. Signed-off-by: Byungchul Park

[PATCH v3 1/9] llist: Provide a safe version for llist_for_each

Sometimes we have to dereference next field of llist node before entering loop becasue the node might be deleted or the next field might be modified within the loop. So this adds the safe version of llist_for_each, that is, llist_for_each_safe. Signed-off-by: Byungchul Park ---

[PATCH v3 0/9] Don't reinvent the wheel but use existing llist API

Change from v2 - replace for_each(wake_list) with the safe version in scheduler. - fix a trivial comment in llist.h Change from v1 - split one patch to several ones, one for each subsystem. - replace for_each with the safe version where it's necessary. Byungchul Park (9): llist: Provide a safe

[PATCH v3 0/9] Don't reinvent the wheel but use existing llist API

Change from v2 - replace for_each(wake_list) with the safe version in scheduler. - fix a trivial comment in llist.h Change from v1 - split one patch to several ones, one for each subsystem. - replace for_each with the safe version where it's necessary. Byungchul Park (9): llist: Provide a safe

[PATCH v3 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/vhost/scsi.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c index

[PATCH v3 3/9] raid5: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/raid5.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 36c13e4..22a0326 100644

[PATCH v3 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/vhost/scsi.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c index 253310c..a4cb966 100644 ---

[PATCH v3 3/9] raid5: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/raid5.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 36c13e4..22a0326 100644 --- a/drivers/md/raid5.c

[PATCH v3 2/9] bcache: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/bcache/closure.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/md/bcache/closure.c

[PATCH v3 2/9] bcache: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/bcache/closure.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/md/bcache/closure.c b/drivers/md/bcache/closure.c index

Re: [PATCH] mm: free reserved area's memmap if possiable

if the reserved area by user were so big which caused the memmap big, and the reserved area's memamp did not be used by kernel, then user could free the the reserved area's memamp by memblock_mark_raw_pfn interface which is added by me. On 2017/2/14 14:53, zhouxianr...@huawei.com wrote: From:

Re: [PATCH] mm: free reserved area's memmap if possiable

if the reserved area by user were so big which caused the memmap big, and the reserved area's memamp did not be used by kernel, then user could free the the reserved area's memamp by memblock_mark_raw_pfn interface which is added by me. On 2017/2/14 14:53, zhouxianr...@huawei.com wrote: From:

Re: [PATCH v7 5/5] usb: doc: add document for USB3 debug port usage

Hi, On 02/14/2017 02:13 PM, Peter Chen wrote: > >> On 02/14/2017 11:45 AM, Peter Chen wrote: >>> On Tue, Feb 14, 2017 at 10:27 AM, Lu Baolu wrote: >>> Add Documentation/usb/usb3-debug-port.rst. This document includes the user guide for USB3 debug port.

Re: [PATCH v7 5/5] usb: doc: add document for USB3 debug port usage

Hi, On 02/14/2017 02:13 PM, Peter Chen wrote: > >> On 02/14/2017 11:45 AM, Peter Chen wrote: >>> On Tue, Feb 14, 2017 at 10:27 AM, Lu Baolu wrote: >>> Add Documentation/usb/usb3-debug-port.rst. This document includes the user guide for USB3 debug port. Cc:

Re: [PATCH BUGFIX] block: make elevator_get robust against cross blk/blk-mq choice

On 02/14/2017 08:07 AM, Omar Sandoval wrote: > On Tue, Feb 14, 2017 at 07:58:22AM +0100, Hannes Reinecke wrote: >> While we're at the topic: >> >> Can't we use the same names for legacy and mq scheduler? >> It's quite an unnecessary complication to have >> 'noop', 'deadline', and 'cfq' for legacy,

Re: [PATCH BUGFIX] block: make elevator_get robust against cross blk/blk-mq choice

On 02/14/2017 08:07 AM, Omar Sandoval wrote: > On Tue, Feb 14, 2017 at 07:58:22AM +0100, Hannes Reinecke wrote: >> While we're at the topic: >> >> Can't we use the same names for legacy and mq scheduler? >> It's quite an unnecessary complication to have >> 'noop', 'deadline', and 'cfq' for legacy,

linux-next: Tree for Feb 14

Hi all, Changes since 20170213: Removed trees: rdma-leon, rdma-leon-test (at owner's request) The net tree gained a build failure for which I applied a fix patch. The mfd tree gained a conflict against the input tree. The kvm tree gained conflicts against the powerpc tree. The akpm-current

linux-next: Tree for Feb 14

Hi all, Changes since 20170213: Removed trees: rdma-leon, rdma-leon-test (at owner's request) The net tree gained a build failure for which I applied a fix patch. The mfd tree gained a conflict against the input tree. The kvm tree gained conflicts against the powerpc tree. The akpm-current

Re: net/xfrm: stack out-of-bounds in xfrm_flowi_sport

On Mon, Feb 13, 2017 at 03:46:56PM +0100, Dmitry Vyukov wrote: > > On commit 7089db84e356562f8ba737c29e472cc42d530dbc. > > > struct flowi4 fl4_stack allocated on stack in udp_sendmsg is being > casted to larger struct flowi and then accessed. Looks like the problem is when using IPv4-mapped

Re: net/xfrm: stack out-of-bounds in xfrm_flowi_sport

On Mon, Feb 13, 2017 at 03:46:56PM +0100, Dmitry Vyukov wrote: > > On commit 7089db84e356562f8ba737c29e472cc42d530dbc. > > > struct flowi4 fl4_stack allocated on stack in udp_sendmsg is being > casted to larger struct flowi and then accessed. Looks like the problem is when using IPv4-mapped

Re: [PATCH BUGFIX] block: make elevator_get robust against cross blk/blk-mq choice

On Tue, Feb 14, 2017 at 07:58:22AM +0100, Hannes Reinecke wrote: > While we're at the topic: > > Can't we use the same names for legacy and mq scheduler? > It's quite an unnecessary complication to have > 'noop', 'deadline', and 'cfq' for legacy, but 'none' and 'mq-deadline' > for mq. If we could

Re: [PATCH BUGFIX] block: make elevator_get robust against cross blk/blk-mq choice

On Tue, Feb 14, 2017 at 07:58:22AM +0100, Hannes Reinecke wrote: > While we're at the topic: > > Can't we use the same names for legacy and mq scheduler? > It's quite an unnecessary complication to have > 'noop', 'deadline', and 'cfq' for legacy, but 'none' and 'mq-deadline' > for mq. If we could

[PATCH] mm: free reserved area's memmap if possiable

From: zhouxianrong just like freeing no-map area's memmap (gaps of memblock.memory) we could free reserved area's memmap (areas of memblock.reserved) as well only when user of reserved area indicate that we can do this in drivers. that is, user of reserved area know how

[PATCH] mm: free reserved area's memmap if possiable

From: zhouxianrong just like freeing no-map area's memmap (gaps of memblock.memory) we could free reserved area's memmap (areas of memblock.reserved) as well only when user of reserved area indicate that we can do this in drivers. that is, user of reserved area know how to use the reserved area

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > On Mon, Feb 13, 2017 at 04:58:05PM +0900, Byungchul Park wrote: >> On Mon, Feb 13, 2017 at 03:52:44PM +0800, Huang, Ying wrote: >> > Byungchul Park writes: >> > >> > > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > On Mon, Feb 13, 2017 at 04:58:05PM +0900, Byungchul Park wrote: >> On Mon, Feb 13, 2017 at 03:52:44PM +0800, Huang, Ying wrote: >> > Byungchul Park writes: >> > >> > > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: >> > >> Byungchul Park writes: >> > >>

Re: [PATCH BUGFIX] block: make elevator_get robust against cross blk/blk-mq choice

On 02/13/2017 11:28 PM, Jens Axboe wrote: > On 02/13/2017 03:09 PM, Omar Sandoval wrote: >> On Mon, Feb 13, 2017 at 10:01:07PM +0100, Paolo Valente wrote: >>> If, at boot, a legacy I/O scheduler is chosen for a device using blk-mq, >>> or, viceversa, a blk-mq scheduler is chosen for a device using

Re: [PATCH BUGFIX] block: make elevator_get robust against cross blk/blk-mq choice

On 02/13/2017 11:28 PM, Jens Axboe wrote: > On 02/13/2017 03:09 PM, Omar Sandoval wrote: >> On Mon, Feb 13, 2017 at 10:01:07PM +0100, Paolo Valente wrote: >>> If, at boot, a legacy I/O scheduler is chosen for a device using blk-mq, >>> or, viceversa, a blk-mq scheduler is chosen for a device using

Re: [PATCH V2 0/3] Define coherent device memory node

On 02/13/2017 09:04 PM, Vlastimil Babka wrote: > On 02/10/2017 11:06 AM, Anshuman Khandual wrote: >> This three patches define CDM node with HugeTLB & Buddy allocation >> isolation. Please refer to the last RFC posting mentioned here for details. >> The series has been split for easier review

Re: [PATCH V2 0/3] Define coherent device memory node

On 02/13/2017 09:04 PM, Vlastimil Babka wrote: > On 02/10/2017 11:06 AM, Anshuman Khandual wrote: >> This three patches define CDM node with HugeTLB & Buddy allocation >> isolation. Please refer to the last RFC posting mentioned here for details. >> The series has been split for easier review

[PATCH v4 3/4] dmaengine: Add Broadcom SBA RAID driver

The Broadcom stream buffer accelerator (SBA) provides offloading capabilities for RAID operations. This SBA offload engine is accessible via Broadcom SoC specific ring manager. This patch adds Broadcom SBA RAID driver which provides one DMA device with RAID capabilities using one or more Broadcom

[PATCH v4 4/4] dt-bindings: Add DT bindings document for Broadcom SBA RAID driver

This patch adds the DT bindings document for newly added Broadcom SBA RAID driver. Signed-off-by: Anup Patel Reviewed-by: Ray Jui Reviewed-by: Scott Branden --- .../devicetree/bindings/dma/brcm,iproc-sba.txt | 29

[PATCH v4 3/4] dmaengine: Add Broadcom SBA RAID driver

The Broadcom stream buffer accelerator (SBA) provides offloading capabilities for RAID operations. This SBA offload engine is accessible via Broadcom SoC specific ring manager. This patch adds Broadcom SBA RAID driver which provides one DMA device with RAID capabilities using one or more Broadcom

[PATCH v4 4/4] dt-bindings: Add DT bindings document for Broadcom SBA RAID driver

This patch adds the DT bindings document for newly added Broadcom SBA RAID driver. Signed-off-by: Anup Patel Reviewed-by: Ray Jui Reviewed-by: Scott Branden --- .../devicetree/bindings/dma/brcm,iproc-sba.txt | 29 ++ 1 file changed, 29 insertions(+) create mode 100644

[PATCH v4 0/4] Broadcom SBA RAID support

The Broadcom SBA RAID is a stream-based device which provides RAID5/6 offload. It requires a SoC specific ring manager (such as Broadcom FlexRM ring manager) to provide ring-based programming interface. Due to this, the Broadcom SBA RAID driver (mailbox client) implements DMA device having one

[PATCH v4 2/4] async_tx: Fix DMA_PREP_FENCE usage in do_async_gen_syndrome()

The DMA_PREP_FENCE is to be used when preparing Tx descriptor if output of Tx descriptor is to be used by next/dependent Tx descriptor. The DMA_PREP_FENSE will not be set correctly in do_async_gen_syndrome() when calling dma->device_prep_dma_pq() under following conditions: 1. ASYNC_TX_FENCE not

[PATCH v4 1/4] lib/raid6: Add log-of-2 table for RAID6 HW requiring disk position

The raid6_gfexp table represents {2}^n values for 0 <= n < 256. The Linux async_tx framework pass values from raid6_gfexp as coefficients for each source to prep_dma_pq() callback of DMA channel with PQ capability. This creates problem for RAID6 offload engines (such as Broadcom SBA) which take

[PATCH v4 0/4] Broadcom SBA RAID support

The Broadcom SBA RAID is a stream-based device which provides RAID5/6 offload. It requires a SoC specific ring manager (such as Broadcom FlexRM ring manager) to provide ring-based programming interface. Due to this, the Broadcom SBA RAID driver (mailbox client) implements DMA device having one

[PATCH v4 2/4] async_tx: Fix DMA_PREP_FENCE usage in do_async_gen_syndrome()

The DMA_PREP_FENCE is to be used when preparing Tx descriptor if output of Tx descriptor is to be used by next/dependent Tx descriptor. The DMA_PREP_FENSE will not be set correctly in do_async_gen_syndrome() when calling dma->device_prep_dma_pq() under following conditions: 1. ASYNC_TX_FENCE not

[PATCH v4 1/4] lib/raid6: Add log-of-2 table for RAID6 HW requiring disk position

The raid6_gfexp table represents {2}^n values for 0 <= n < 256. The Linux async_tx framework pass values from raid6_gfexp as coefficients for each source to prep_dma_pq() callback of DMA channel with PQ capability. This creates problem for RAID6 offload engines (such as Broadcom SBA) which take

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

On Mon, Feb 13, 2017 at 04:58:05PM +0900, Byungchul Park wrote: > On Mon, Feb 13, 2017 at 03:52:44PM +0800, Huang, Ying wrote: > > Byungchul Park writes: > > > > > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: > > >> Byungchul Park

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

On Mon, Feb 13, 2017 at 04:58:05PM +0900, Byungchul Park wrote: > On Mon, Feb 13, 2017 at 03:52:44PM +0800, Huang, Ying wrote: > > Byungchul Park writes: > > > > > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: > > >> Byungchul Park writes: > > >> > > >> > Sometimes we have to

[tip:perf/core] perf tests record: No need to test an array against NULL

Commit-ID: 9ef6839bcce7ca944c1ace4a7247cf13ca92a28f Gitweb: http://git.kernel.org/tip/9ef6839bcce7ca944c1ace4a7247cf13ca92a28f Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 17:04:05 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf tests record: No need to test an array against NULL

Commit-ID: 9ef6839bcce7ca944c1ace4a7247cf13ca92a28f Gitweb: http://git.kernel.org/tip/9ef6839bcce7ca944c1ace4a7247cf13ca92a28f Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 17:04:05 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 17:22:34 -0300

[tip:perf/core] perf symbols: dso->name is an array, no need to check it against NULL

Commit-ID: 5eae7d842510d33d4410c062280eda6c935403dd Gitweb: http://git.kernel.org/tip/5eae7d842510d33d4410c062280eda6c935403dd Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 17:11:03 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf symbols: dso->name is an array, no need to check it against NULL

Commit-ID: 5eae7d842510d33d4410c062280eda6c935403dd Gitweb: http://git.kernel.org/tip/5eae7d842510d33d4410c062280eda6c935403dd Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 17:11:03 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 17:22:35 -0300

[tip:perf/core] perf evsel: Inform how to make a sysctl setting permanent

Commit-ID: d6195a6a2c247515d5832debb51c03a74dc3f8f6 Gitweb: http://git.kernel.org/tip/d6195a6a2c247515d5832debb51c03a74dc3f8f6 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 16:45:24 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf evsel: Inform how to make a sysctl setting permanent

Commit-ID: d6195a6a2c247515d5832debb51c03a74dc3f8f6 Gitweb: http://git.kernel.org/tip/d6195a6a2c247515d5832debb51c03a74dc3f8f6 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 16:45:24 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 17:22:33 -0300

[tip:perf/core] perf symbols: No need to check if sym->name is NULL

Commit-ID: a7c3899c06865c75f8887f33d9043f6e8e780e71 Gitweb: http://git.kernel.org/tip/a7c3899c06865c75f8887f33d9043f6e8e780e71 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 16:52:15 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf symbols: No need to check if sym->name is NULL

Commit-ID: a7c3899c06865c75f8887f33d9043f6e8e780e71 Gitweb: http://git.kernel.org/tip/a7c3899c06865c75f8887f33d9043f6e8e780e71 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 16:52:15 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 17:22:34 -0300

Re: linux-next: build failure after merge of the net tree

* Stephen Rothwell wrote: > Hi all, > > After merging the net tree, today's linux-next build (powerpc64le perf) > failed like this: > > Warning: tools/include/uapi/linux/bpf.h differs from kernel > bpf.c: In function 'bpf_prog_attach': > bpf.c:180:6: error: 'union

Re: linux-next: build failure after merge of the net tree

* Stephen Rothwell wrote: > Hi all, > > After merging the net tree, today's linux-next build (powerpc64le perf) > failed like this: > > Warning: tools/include/uapi/linux/bpf.h differs from kernel > bpf.c: In function 'bpf_prog_attach': > bpf.c:180:6: error: 'union bpf_attr' has no member

[tip:perf/core] tools lib traceevent plugin function: Initialize 'index' variable

Commit-ID: e8c6f437fd12d39e462962eaed2315bac597d34c Gitweb: http://git.kernel.org/tip/e8c6f437fd12d39e462962eaed2315bac597d34c Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 13:33:57 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] tools lib traceevent plugin function: Initialize 'index' variable

Commit-ID: e8c6f437fd12d39e462962eaed2315bac597d34c Gitweb: http://git.kernel.org/tip/e8c6f437fd12d39e462962eaed2315bac597d34c Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Feb 2017 13:33:57 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 17:22:33 -0300

[tip:perf/core] tools lib traceevent: Initialize lenght on OLD_RING_BUFFER_TYPE_TIME_STAMP

Commit-ID: 14e4d7e0abfdefabea2b8796c5a8b2b9c77b5326 Gitweb: http://git.kernel.org/tip/14e4d7e0abfdefabea2b8796c5a8b2b9c77b5326 Author: Steven Rostedt (VMware) AuthorDate: Mon, 13 Feb 2017 12:11:44 -0500 Committer: Arnaldo Carvalho de Melo

[tip:perf/core] tools lib traceevent: Initialize lenght on OLD_RING_BUFFER_TYPE_TIME_STAMP

Commit-ID: 14e4d7e0abfdefabea2b8796c5a8b2b9c77b5326 Gitweb: http://git.kernel.org/tip/14e4d7e0abfdefabea2b8796c5a8b2b9c77b5326 Author: Steven Rostedt (VMware) AuthorDate: Mon, 13 Feb 2017 12:11:44 -0500 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 17:22:32 -0300

[tip:perf/core] perf diff: Change default setting to "delta-abs"

Commit-ID: be57b3fd218ad4a19725ac4bd53e67b2ede42a9d Gitweb: http://git.kernel.org/tip/be57b3fd218ad4a19725ac4bd53e67b2ede42a9d Author: Namhyung Kim AuthorDate: Sat, 11 Feb 2017 01:18:56 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13

[tip:perf/core] perf diff: Change default setting to "delta-abs"

Commit-ID: be57b3fd218ad4a19725ac4bd53e67b2ede42a9d Gitweb: http://git.kernel.org/tip/be57b3fd218ad4a19725ac4bd53e67b2ede42a9d Author: Namhyung Kim AuthorDate: Sat, 11 Feb 2017 01:18:56 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 14:29:38 -0300 perf diff:

[tip:perf/core] perf scripting perl: Fix compile error with some perl5 versions

Commit-ID: d7dd112ea5cacf91ae72c0714c3b911eb6016fea Gitweb: http://git.kernel.org/tip/d7dd112ea5cacf91ae72c0714c3b911eb6016fea Author: Wang YanQing AuthorDate: Sun, 12 Feb 2017 10:46:55 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13

[tip:perf/core] perf scripting perl: Fix compile error with some perl5 versions

Commit-ID: d7dd112ea5cacf91ae72c0714c3b911eb6016fea Gitweb: http://git.kernel.org/tip/d7dd112ea5cacf91ae72c0714c3b911eb6016fea Author: Wang YanQing AuthorDate: Sun, 12 Feb 2017 10:46:55 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 17:22:32 -0300 perf

[tip:perf/core] perf diff: Add diff.compute config option

Commit-ID: 4b35994abe459f08f58b4b3855abf4ba80308680 Gitweb: http://git.kernel.org/tip/4b35994abe459f08f58b4b3855abf4ba80308680 Author: Namhyung Kim AuthorDate: Fri, 10 Feb 2017 16:36:13 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13

[tip:perf/core] perf diff: Add diff.compute config option

Commit-ID: 4b35994abe459f08f58b4b3855abf4ba80308680 Gitweb: http://git.kernel.org/tip/4b35994abe459f08f58b4b3855abf4ba80308680 Author: Namhyung Kim AuthorDate: Fri, 10 Feb 2017 16:36:13 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 14:29:37 -0300 perf diff:

[tip:perf/core] tools include: Introduce linux/compiler-gcc.h

Commit-ID: 192614010a5052fe92611c7076ef664fd9bb60e8 Gitweb: http://git.kernel.org/tip/192614010a5052fe92611c7076ef664fd9bb60e8 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 10 Feb 2017 11:41:11 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] tools include: Introduce linux/compiler-gcc.h

Commit-ID: 192614010a5052fe92611c7076ef664fd9bb60e8 Gitweb: http://git.kernel.org/tip/192614010a5052fe92611c7076ef664fd9bb60e8 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 10 Feb 2017 11:41:11 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 14:29:29 -0300

[tip:perf/core] perf diff: Add diff.order config option

Commit-ID: d49dd15d69731589de4436a6dcfca59567320fdf Gitweb: http://git.kernel.org/tip/d49dd15d69731589de4436a6dcfca59567320fdf Author: Namhyung Kim AuthorDate: Fri, 10 Feb 2017 16:36:12 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13

[tip:perf/core] perf diff: Add diff.order config option

Commit-ID: d49dd15d69731589de4436a6dcfca59567320fdf Gitweb: http://git.kernel.org/tip/d49dd15d69731589de4436a6dcfca59567320fdf Author: Namhyung Kim AuthorDate: Fri, 10 Feb 2017 16:36:12 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 14:29:37 -0300 perf diff:

[tip:perf/core] perf diff: Add 'delta-abs' compute method

Commit-ID: a1668c25a8e1b53d00b2997ef5bc5e25c7a77235 Gitweb: http://git.kernel.org/tip/a1668c25a8e1b53d00b2997ef5bc5e25c7a77235 Author: Namhyung Kim AuthorDate: Fri, 10 Feb 2017 16:36:11 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13

[tip:perf/core] perf diff: Add 'delta-abs' compute method

Commit-ID: a1668c25a8e1b53d00b2997ef5bc5e25c7a77235 Gitweb: http://git.kernel.org/tip/a1668c25a8e1b53d00b2997ef5bc5e25c7a77235 Author: Namhyung Kim AuthorDate: Fri, 10 Feb 2017 16:36:11 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Feb 2017 14:29:36 -0300 perf diff:

Re: [PATCH] seccomp: Only dump core when single-threaded

On Tue, Feb 07, 2017 at 03:18:51PM -0800, Kees Cook wrote: > The SECCOMP_RET_KILL filter return code has always killed the current > thread, not the entire process. Changing this as a side-effect of dumping > core isn't a safe thing to do (a few test suites have already flagged this > behavioral

Re: [PATCH] seccomp: Only dump core when single-threaded

On Tue, Feb 07, 2017 at 03:18:51PM -0800, Kees Cook wrote: > The SECCOMP_RET_KILL filter return code has always killed the current > thread, not the entire process. Changing this as a side-effect of dumping > core isn't a safe thing to do (a few test suites have already flagged this > behavioral

Re: linux-next: build failure after merge of the net tree

* Stephen Rothwell wrote: > --- a/tools/include/uapi/linux/bpf.h > +++ b/tools/include/uapi/linux/bpf.h > @@ -116,6 +116,12 @@ enum bpf_attach_type { > > #define MAX_BPF_ATTACH_TYPE __MAX_BPF_ATTACH_TYPE > > +/* If BPF_F_ALLOW_OVERRIDE flag is used in BPF_PROG_ATTACH

Re: linux-next: build failure after merge of the net tree

* Stephen Rothwell wrote: > --- a/tools/include/uapi/linux/bpf.h > +++ b/tools/include/uapi/linux/bpf.h > @@ -116,6 +116,12 @@ enum bpf_attach_type { > > #define MAX_BPF_ATTACH_TYPE __MAX_BPF_ATTACH_TYPE > > +/* If BPF_F_ALLOW_OVERRIDE flag is used in BPF_PROG_ATTACH command > + * to the

Re: [PATCH 02/10] ARM: dts: da850-evm: fix whitespace errors

On Tuesday 14 February 2017 02:31 AM, Kevin Hilman wrote: > Kevin Hilman writes: > >> Bartosz Golaszewski writes: >> >>> Signed-off-by: Bartosz Golaszewski >> >> I'll fold this one into the original since it's not yet

[PATCH v5] drivers/misc: Add Aspeed LPC control driver

In order to manage server systems, there is typically another processor known as a BMC (Baseboard Management Controller) which is responsible for powering the server and other various elements, sometimes fans, often the system flash. The Aspeed BMC family which is what is used on OpenPOWER

Re: [PATCH 02/10] ARM: dts: da850-evm: fix whitespace errors

On Tuesday 14 February 2017 02:31 AM, Kevin Hilman wrote: > Kevin Hilman writes: > >> Bartosz Golaszewski writes: >> >>> Signed-off-by: Bartosz Golaszewski >> >> I'll fold this one into the original since it's not yet merged. > > Oops, Sekhar has already merged this one to his v4.11/dt

[PATCH v5] drivers/misc: Add Aspeed LPC control driver

In order to manage server systems, there is typically another processor known as a BMC (Baseboard Management Controller) which is responsible for powering the server and other various elements, sometimes fans, often the system flash. The Aspeed BMC family which is what is used on OpenPOWER

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

perf/x86/intel: Add Kaby Lake support (2017-02-11 21:28:23 +0100) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-core-for-mingo-4.11-20170213 > > for you to fetch changes up to a734fb5d60067a

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

Kaby Lake support (2017-02-11 21:28:23 +0100) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-core-for-mingo-4.11-20170213 > > for you to fetch changes up to a734fb5d60067a73dd7099a58756847c07f9cd68:

[PATCH v2] drm/amd/dc: resource: fix semicolon.cocci warnings (fwd)

Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry Wentland Signed-off-by: Julia Lawall Signed-off-by: Fengguang Wu --- v2: make subject line unique tree:

[PATCH v2] drm/amd/dc: resource: fix semicolon.cocci warnings (fwd)

Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry Wentland Signed-off-by: Julia Lawall Signed-off-by: Fengguang Wu --- v2: make subject line unique tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-4.9 head:

[PATCH v2] drm/amd/dc: dm_types: fix semicolon.cocci warnings

Remove unneeded semicolons. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry Wentland Signed-off-by: Julia Lawall Signed-off-by: Fengguang Wu --- v2: make subject line unique tree:

[PATCH v2] drm/amd/dc: dm_types: fix semicolon.cocci warnings

Remove unneeded semicolons. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry Wentland Signed-off-by: Julia Lawall Signed-off-by: Fengguang Wu --- v2: make subject line unique tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-4.9 head:

  1   2   3   4   5   6   7   8   9   10   >