drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 2a26d99b251b8625d27aed14e97fc10707a3a81f commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new lightweight SGL iterators date: 5

drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 2a26d99b251b8625d27aed14e97fc10707a3a81f commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new lightweight SGL iterators date: 5

fs/xfs/xfs_ondisk.h:96:2: error: call to '__compiletime_assert_96' declared with attribute error: XFS: sizeof(xfs_dir2_sf_entry_t) is wrong, expected 3

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 2a26d99b251b8625d27aed14e97fc10707a3a81f commit: ab9d1e4f7b0217948a3b35a64178602ab30ff45d Merge branch 'xfs-misc-fixes-4.6-3' into for-next date: 8 months

fs/xfs/xfs_ondisk.h:96:2: error: call to '__compiletime_assert_96' declared with attribute error: XFS: sizeof(xfs_dir2_sf_entry_t) is wrong, expected 3

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 2a26d99b251b8625d27aed14e97fc10707a3a81f commit: ab9d1e4f7b0217948a3b35a64178602ab30ff45d Merge branch 'xfs-misc-fixes-4.6-3' into for-next date: 8 months

arch/ia64/kernel/entry.S:621: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191)

Hi Will, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove HAVE_LATENCYTOP_SUPPORT date: 10 months ago

arch/ia64/kernel/entry.S:621: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191)

Hi Will, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove HAVE_LATENCYTOP_SUPPORT date: 10 months ago

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

Sorry, the warning is still there. I'm not sure adding sched_annotate_sleep() does anything, since it's defined as (in case CONFIG_DEBUG_ATOMIC_SLEEP is not set): # define sched_annotate_sleep() do { } while (0) On Sat, Oct 29, 2016 at 8:05 PM, Eric Dumazet wrote: > On

Re: net/dccp: warning in dccp_feat_clone_sp_val/__might_sleep

Sorry, the warning is still there. I'm not sure adding sched_annotate_sleep() does anything, since it's defined as (in case CONFIG_DEBUG_ATOMIC_SLEEP is not set): # define sched_annotate_sleep() do { } while (0) On Sat, Oct 29, 2016 at 8:05 PM, Eric Dumazet wrote: > On Sat, 2016-10-29 at 19:59

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

> I think we should do those two things completely independently. > We need to do something now to preserve the current interfaces > for the glibc changes that are coming soon [1], and Deepa's > patches do that (though I now realize the changelog doesn't > mention the requirement). I'll update

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

> I think we should do those two things completely independently. > We need to do something now to preserve the current interfaces > for the glibc changes that are coming soon [1], and Deepa's > patches do that (though I now realize the changelog doesn't > mention the requirement). I'll update

[PATCH] nbd: Fix error handling

'blk_mq_alloc_request()' returns an error pointer in case of error, not NULL. So test it with IS_ERR. Fixes: fd8383fd88a2 ("nbd: convert to blkmq") Signed-off-by: Christophe JAILLET --- drivers/block/nbd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] nbd: Fix error handling

'blk_mq_alloc_request()' returns an error pointer in case of error, not NULL. So test it with IS_ERR. Fixes: fd8383fd88a2 ("nbd: convert to blkmq") Signed-off-by: Christophe JAILLET --- drivers/block/nbd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/block/nbd.c

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

> btw, where did you post the libevdev patch? I haven't seen it anywhere I'm > subscribed to. The libevdev patch was posted to input-to...@lists.freedesktop.org : https://www.mail-archive.com/y2038@lists.linaro.org/msg01824.html -Deepa

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

> btw, where did you post the libevdev patch? I haven't seen it anywhere I'm > subscribed to. The libevdev patch was posted to input-to...@lists.freedesktop.org : https://www.mail-archive.com/y2038@lists.linaro.org/msg01824.html -Deepa

Re: [PATCH -next] brd: make symbol rd_size static

On 10/29/2016 10:10 AM, Wei Yongjun wrote: From: Wei Yongjun Fixes the following sparse warning: drivers/block/brd.c:411:15: warning: symbol 'rd_size' was not declared. Should it be static? We just tried this, it's used in arm: arch/arm/kernel/atags_parse.c static

Re: [PATCH -next] brd: make symbol rd_size static

On 10/29/2016 10:10 AM, Wei Yongjun wrote: From: Wei Yongjun Fixes the following sparse warning: drivers/block/brd.c:411:15: warning: symbol 'rd_size' was not declared. Should it be static? We just tried this, it's used in arm: arch/arm/kernel/atags_parse.c static int __init

Re: [PULL] bcache: multiple updates

On Sat, 29 Oct 2016, Eric Wheeler wrote: Kent, Davidlohr, does 3312845 need to land in 4.9 for some reason? No, not particularly. I can do my stuff whenever this is ends up being merged. Thanks, Davidlohr

Re: [PULL] bcache: multiple updates

On Sat, 29 Oct 2016, Eric Wheeler wrote: Kent, Davidlohr, does 3312845 need to land in 4.9 for some reason? No, not particularly. I can do my stuff whenever this is ends up being merged. Thanks, Davidlohr

make[2]: *** No rule to make target 'alchemy/'.

Hi Paul, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: cf2a5e0bb4c66e8c43caf9f1be93a1bd7fd07b17 MIPS: Support generating Flattened Image Trees (.itb) date: 3

make[2]: *** No rule to make target 'alchemy/'.

Hi Paul, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: cf2a5e0bb4c66e8c43caf9f1be93a1bd7fd07b17 MIPS: Support generating Flattened Image Trees (.itb) date: 3

Re: [PATCH 00/14] introduce the BFQ-v0 I/O scheduler as an extra scheduler

> Il giorno 29 ott 2016, alle ore 16:12, Jens Axboe ha > scritto: > > On 10/28/2016 11:38 PM, Paolo Valente wrote: >> >>> Il giorno 26 ott 2016, alle ore 18:12, Jens Axboe ha >>> scritto: >>> >>> On 10/26/2016 10:04 AM, Paolo Valente wrote: > Il

Re: [PATCH 00/14] introduce the BFQ-v0 I/O scheduler as an extra scheduler

> Il giorno 29 ott 2016, alle ore 16:12, Jens Axboe ha > scritto: > > On 10/28/2016 11:38 PM, Paolo Valente wrote: >> >>> Il giorno 26 ott 2016, alle ore 18:12, Jens Axboe ha >>> scritto: >>> >>> On 10/26/2016 10:04 AM, Paolo Valente wrote: > Il giorno 26 ott 2016, alle ore

include/linux/unaligned/access_ok.h:7:19: error: redefinition of 'get_unaligned_le16'

Hi Vincent, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: 3194c6870158e305dac2af52f83681e9cb67280f NFC: nfcmrvl: add firmware download support date: 1 year ago

include/linux/unaligned/access_ok.h:7:19: error: redefinition of 'get_unaligned_le16'

Hi Vincent, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: 3194c6870158e305dac2af52f83681e9cb67280f NFC: nfcmrvl: add firmware download support date: 1 year ago

Re: [PATCH net-next] firewire: net: really fix maximum possible MTU

From: Stefan Richter Date: Sat, 29 Oct 2016 22:16:58 +0200 > The maximum unicast datagram size /without/ link fragmentation is > 4096 - 4 = 4092 (max IEEE 1394 async payload size at >= S800 bus speed, > minus unfragmented encapssulation header). Max broadcast datagram

Re: [PATCH net-next] firewire: net: really fix maximum possible MTU

From: Stefan Richter Date: Sat, 29 Oct 2016 22:16:58 +0200 > The maximum unicast datagram size /without/ link fragmentation is > 4096 - 4 = 4092 (max IEEE 1394 async payload size at >= S800 bus speed, > minus unfragmented encapssulation header). Max broadcast datagram size > without

cris-linux-objcopy: error: the input file 'arch/cris/boot/rescue/rescue.o' has no sections

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: f9f3f864b5e8c09d7837d8980edba4ad52969819 cris: Fix section mismatches in architecture startup code

cris-linux-objcopy: error: the input file 'arch/cris/boot/rescue/rescue.o' has no sections

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a909d3e636995ba7c349e2ca5dbb528154d4ac30 commit: f9f3f864b5e8c09d7837d8980edba4ad52969819 cris: Fix section mismatches in architecture startup code

Re: [PATCH v4 2/2] fpga: Add support for Lattice iCE40 FPGAs

Hi Joel, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

Re: [PATCH v4 2/2] fpga: Add support for Lattice iCE40 FPGAs

Hi Joel, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

Fw: [GIT] Networking

Sorry, forgot to CC: the lists on this one, doh! --- Begin Message --- Lots of fixes, mostly drivers as is usually the case. 1) Don't treat zero DMA address as invalid in vmxnet3, from Alexey Khoroshilov. 2) Fix element timeouts in netfilter's nft_dynset, from Anders K. Pedersen. 3)

Fw: [GIT] Networking

Sorry, forgot to CC: the lists on this one, doh! --- Begin Message --- Lots of fixes, mostly drivers as is usually the case. 1) Don't treat zero DMA address as invalid in vmxnet3, from Alexey Khoroshilov. 2) Fix element timeouts in netfilter's nft_dynset, from Anders K. Pedersen. 3)

Re: [PATCH v4 2/2] fpga: Add support for Lattice iCE40 FPGAs

Hi Joel, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

Re: [PATCH v4 2/2] fpga: Add support for Lattice iCE40 FPGAs

Hi Joel, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

Re: [PATCH 01/14] dma: sun6i-dma: Add burst case of 4

Hi, On Fri, Oct 28, 2016 at 1:51 AM, Maxime Ripard wrote: > On Sun, Oct 23, 2016 at 06:31:07PM +0200, Jean-Francois Moine wrote: >> On Tue, 4 Oct 2016 18:55:54 +0200 >> Maxime Ripard wrote: >> >> > On Tue, Oct 04, 2016 at

Re: [PATCH 01/14] dma: sun6i-dma: Add burst case of 4

Hi, On Fri, Oct 28, 2016 at 1:51 AM, Maxime Ripard wrote: > On Sun, Oct 23, 2016 at 06:31:07PM +0200, Jean-Francois Moine wrote: >> On Tue, 4 Oct 2016 18:55:54 +0200 >> Maxime Ripard wrote: >> >> > On Tue, Oct 04, 2016 at 12:40:11PM +0200, Jean-Francois Moine wrote: >> > > On Tue, 4 Oct 2016

Re: [PULL] bcache: multiple updates

On Thu, 27 Oct 2016, Jens Axboe wrote: > On 10/27/2016 05:27 PM, Eric Wheeler wrote: > > Hi Jens, > > > > Please pull this v4.9-rc2 based series of bcache updates for v4.9-rc3: > > (You may disregard the previous -rc1-based request.) > > > > git pull https://bitbucket.org/ewheelerinc/linux.git

Re: [PULL] bcache: multiple updates

On Thu, 27 Oct 2016, Jens Axboe wrote: > On 10/27/2016 05:27 PM, Eric Wheeler wrote: > > Hi Jens, > > > > Please pull this v4.9-rc2 based series of bcache updates for v4.9-rc3: > > (You may disregard the previous -rc1-based request.) > > > > git pull https://bitbucket.org/ewheelerinc/linux.git

[PATCH 4/6] mfd: ab8500-gpadc: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_GPADC drivers/mfd/Kconfig:bool "ST-Ericsson AB8500 GPADC driver" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned,

[PATCH 3/6] mfd: ab8500-debugfs: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_DEBUG drivers/mfd/Kconfig: bool "Enable debug info via debugfs" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 1/6] mfd: ab3100-core: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB3100_CORE drivers/mfd/Kconfig:bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that

[PATCH 4/6] mfd: ab8500-gpadc: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_GPADC drivers/mfd/Kconfig:bool "ST-Ericsson AB8500 GPADC driver" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned,

[PATCH 3/6] mfd: ab8500-debugfs: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_DEBUG drivers/mfd/Kconfig: bool "Enable debug info via debugfs" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 1/6] mfd: ab3100-core: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB3100_CORE drivers/mfd/Kconfig:bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that

[PATCH 6/6] mfd: abx500-core: drop unused MODULE_ tags from non-modular code

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config ABX500_CORE drivers/mfd/Kconfig:bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces

[PATCH 0/6] mfd: audit and demodule drivers/mfd/ab* drivers

Nothing new here ; just another instance where we had modular remove and exit functions -- but the Makefile/Kconfig limited the use case to being always built-in; hence the code is useless and needs removing. So we remove the dead code and the misleading hints of modularity from these drivers,

[PATCH 2/6] mfd: ab8500-core: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_CORE drivers/mfd/Kconfig:bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is

[PATCH 5/6] mfd: ab8500: make sysctrl explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_CORE drivers/mfd/Kconfig:bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of

[PATCH 6/6] mfd: abx500-core: drop unused MODULE_ tags from non-modular code

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config ABX500_CORE drivers/mfd/Kconfig:bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces

[PATCH 0/6] mfd: audit and demodule drivers/mfd/ab* drivers

Nothing new here ; just another instance where we had modular remove and exit functions -- but the Makefile/Kconfig limited the use case to being always built-in; hence the code is useless and needs removing. So we remove the dead code and the misleading hints of modularity from these drivers,

[PATCH 2/6] mfd: ab8500-core: Make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_CORE drivers/mfd/Kconfig:bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is

[PATCH 5/6] mfd: ab8500: make sysctrl explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/mfd/Kconfig:config AB8500_CORE drivers/mfd/Kconfig:bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of

Re: [PATCH 2/3] blackfin: make-bf561/coreb.c explicitly non-modular

Hi Paul, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

Re: [PATCH 2/3] blackfin: make-bf561/coreb.c explicitly non-modular

Hi Paul, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

[PATCH v3 02/46] perf/x86/intel: rename CQM cpufeatures to CMT

CMT name has superseded CQM in Intel's documentation. Rename cpufeatures. Next patches in this series will use the CMT name. Signed-off-by: David Carrillo-Cisneros --- arch/x86/include/asm/cpufeatures.h | 14 +++--- arch/x86/kernel/cpu/common.c | 10 +-

[PATCH v3 01/46] perf/x86/intel/cqm: remove previous version of CQM and MBM

Completely remove previous version of CQM + MBM driver to ease review of new version (this patch series). Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/Makefile |2 +- arch/x86/events/intel/cqm.c| 1766

[PATCH v3 03/46] x86/intel: add CONFIG_INTEL_RDT_M configuration flag

New flag for building drivers for Intel RDT Monitoring (currently CMT, future: MBM). This driver may be converted to module once the hooks in perf cgroup are discussed. Signed-off-by: David Carrillo-Cisneros --- arch/x86/Kconfig | 12 1 file changed, 12

[PATCH v3 02/46] perf/x86/intel: rename CQM cpufeatures to CMT

CMT name has superseded CQM in Intel's documentation. Rename cpufeatures. Next patches in this series will use the CMT name. Signed-off-by: David Carrillo-Cisneros --- arch/x86/include/asm/cpufeatures.h | 14 +++--- arch/x86/kernel/cpu/common.c | 10 +- 2 files changed,

[PATCH v3 01/46] perf/x86/intel/cqm: remove previous version of CQM and MBM

Completely remove previous version of CQM + MBM driver to ease review of new version (this patch series). Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/Makefile |2 +- arch/x86/events/intel/cqm.c| 1766

[PATCH v3 03/46] x86/intel: add CONFIG_INTEL_RDT_M configuration flag

New flag for building drivers for Intel RDT Monitoring (currently CMT, future: MBM). This driver may be converted to module once the hooks in perf cgroup are discussed. Signed-off-by: David Carrillo-Cisneros --- arch/x86/Kconfig | 12 1 file changed, 12 insertions(+) diff --git

[PATCH v3 04/46] perf/x86/intel/cmt: add device initialization and CPU hotplug support

Introduce struct pkg_data to store per CPU package locks and data for new CMT driver. Each pkg_data is initialiazed/terminated on demand when the first/last CPU in its package goes online/offline. More details in code's comments. Signed-off-by: David Carrillo-Cisneros ---

[PATCH v3 10/46] perf/x86/intel/cmt: add Package MONitored Resource (pmonr) initialization

A pmonr is the per-package component of a monr. This patch only adds initialization/destruction of pmonrs. Future patches explain their usage and add functionality. CPU hotplug is supported by initializing/terminating all pmonrs in monr hierarchy when first/last CPU in package goes

[PATCH v3 11/46] perf/x86/intel/cmt: add cmt_user_flags (uflags) to monr

uflags allow users to signal special behavior for a pmonr. This patch series introduces two uflags that provide new behavior and are relevant to users: 1) CMT_UF_NOLAZY_RMID: signal that rmids must be reserved immediately. 2) CMT_UF_NOSTEAL_RMID: rmids cannot be stolen. A monr mantains one

[PATCH v3 05/46] perf/x86/intel/cmt: add per-package locks

Per-package locks potentially reduce the contention when compared to the system-wide approach of the previous CQM/CMT driver. Lockdep needs lock_class_key's to be statically initialized and/or use nesting, but nesting is currently hard-coded for up to 8 levels and it's fragile to depend on

[PATCH v3 29/46] perf/x86/intel/cmt: add error handling to intel_cmt_event_read

First part of intel_cmt_event_read. Error conditions and placeholder for oncoming chunks. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 25 + 1 file changed, 25 insertions(+) diff --git a/arch/x86/events/intel/cmt.c

[PATCH v3 09/46] perf/x86/intel/cmt: add basic monr hierarchy

Add root for monr hierarchy and auxiliary functions for locking. Also, add support for attaching CPU and tasks events to monr hierarchy. As of this patch, both types of events always use the root monr (this will change when cgroups are introduced later in this series). More details in code's

[PATCH v3 05/46] perf/x86/intel/cmt: add per-package locks

Per-package locks potentially reduce the contention when compared to the system-wide approach of the previous CQM/CMT driver. Lockdep needs lock_class_key's to be statically initialized and/or use nesting, but nesting is currently hard-coded for up to 8 levels and it's fragile to depend on

[PATCH v3 29/46] perf/x86/intel/cmt: add error handling to intel_cmt_event_read

First part of intel_cmt_event_read. Error conditions and placeholder for oncoming chunks. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 25 + 1 file changed, 25 insertions(+) diff --git a/arch/x86/events/intel/cmt.c

[PATCH v3 09/46] perf/x86/intel/cmt: add basic monr hierarchy

Add root for monr hierarchy and auxiliary functions for locking. Also, add support for attaching CPU and tasks events to monr hierarchy. As of this patch, both types of events always use the root monr (this will change when cgroups are introduced later in this series). More details in code's

[PATCH v3 04/46] perf/x86/intel/cmt: add device initialization and CPU hotplug support

Introduce struct pkg_data to store per CPU package locks and data for new CMT driver. Each pkg_data is initialiazed/terminated on demand when the first/last CPU in its package goes online/offline. More details in code's comments. Signed-off-by: David Carrillo-Cisneros ---

[PATCH v3 10/46] perf/x86/intel/cmt: add Package MONitored Resource (pmonr) initialization

A pmonr is the per-package component of a monr. This patch only adds initialization/destruction of pmonrs. Future patches explain their usage and add functionality. CPU hotplug is supported by initializing/terminating all pmonrs in monr hierarchy when first/last CPU in package goes

[PATCH v3 11/46] perf/x86/intel/cmt: add cmt_user_flags (uflags) to monr

uflags allow users to signal special behavior for a pmonr. This patch series introduces two uflags that provide new behavior and are relevant to users: 1) CMT_UF_NOLAZY_RMID: signal that rmids must be reserved immediately. 2) CMT_UF_NOSTEAL_RMID: rmids cannot be stolen. A monr mantains one

[PATCH v3 07/46] perf/core: add RDT Monitoring attributes to struct hw_perf_event

Add attributes in hw_perf_event that are required by CMT and, in the future, MBM. Signed-off-by: David Carrillo-Cisneros --- include/linux/perf_event.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h index

[PATCH v3 06/46] perf/x86/intel/cmt: add intel_cmt pmu

Add pmu, llc_occupancy event attributes, and functions for event initialization. Empty pmu functions will be filled in future patches in this series. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 106 1

[PATCH v3 08/46] perf/x86/intel/cmt: add MONitored Resource (monr) initialization

Events use monrs to monitor CMT events. Events that share their monitoring target (same thread or cgroup) share a monr. This patch introduces monrs and adds support for monr creation/destruction. An event's associated monr is referenced by event->cmt_monr (introduced in previous patch).

[PATCH v3 12/46] perf/x86/intel/cmt: add per-package rmid pools

A Resource Monitoring ID (RMID) is a hardware ID used to track cache occupancy and memory bandwidth. The rmids are a per-package resource and only one can be programmed at a time per logical CPU. This patch series creates per-package rmids pools and (default) lazy allocation of rmids (only

[PATCH v3 06/46] perf/x86/intel/cmt: add intel_cmt pmu

Add pmu, llc_occupancy event attributes, and functions for event initialization. Empty pmu functions will be filled in future patches in this series. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 106 1 file changed, 106

[PATCH v3 08/46] perf/x86/intel/cmt: add MONitored Resource (monr) initialization

Events use monrs to monitor CMT events. Events that share their monitoring target (same thread or cgroup) share a monr. This patch introduces monrs and adds support for monr creation/destruction. An event's associated monr is referenced by event->cmt_monr (introduced in previous patch).

[PATCH v3 12/46] perf/x86/intel/cmt: add per-package rmid pools

A Resource Monitoring ID (RMID) is a hardware ID used to track cache occupancy and memory bandwidth. The rmids are a per-package resource and only one can be programmed at a time per logical CPU. This patch series creates per-package rmids pools and (default) lazy allocation of rmids (only

[PATCH v3 07/46] perf/core: add RDT Monitoring attributes to struct hw_perf_event

Add attributes in hw_perf_event that are required by CMT and, in the future, MBM. Signed-off-by: David Carrillo-Cisneros --- include/linux/perf_event.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h index 345ec20..0202b32 100644

[PATCH v3 17/46] perf/x86/intel/cmt: add uflag CMT_UF_NOLAZY_RMID

This uflag allows user to specify that a rmid must be allocated at monr's initialization or fail otherwise. For this to work we split __pmonr_apply_uflags into reserve and apply modes. The reserve mode will try to reserve a free rmid, and if successful, the apply mode can proceed using the rmid

[PATCH v3 15/46] perf/x86/intel: encapsulate rmid and closid updates in pqr cache

Encapsulate updates for PQR_ASSOC msr's RMID and CLOSID into intel_rdt_common. Use new interface in Intel CMT. Change RDT common code to build for both CONFIG_INTEL_RDT_A and CONFIG_INTEL_RDT_M. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c

[PATCH v3 19/46] perf/x86/intel/cmt: add support for cgroup events

First part of cgroup support for CMT. A monr's position in monrs hierarchy depends on the position of it's target cgroup or thread in the cgroup hierarchy. (See code comments for details). A monr that monitors a cgroup keeps a reference to in monr->monr_cgroup and its used in future patches to

[PATCH v3 13/46] perf/x86/intel/cmt: add pmonr's Off and Unused states

A pmonr uses a state machine to keep track of its rmids and their hierarchical dependency with other pmonrs in the same package. This patch introduces the first two states in such state machine. It also adds pmonr_rmids: a word-size container to atomically access a pmonr's sched and read rmids.

[PATCH v3 22/46] perf/x86/intel/cmt: sync cgroups and intel_cmt device start/stop

Start/stop cgroup monitoring for cgroups when intel_cmt device is started/stopped. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 99 + 1 file changed, 99 insertions(+) diff --git

[PATCH v3 30/46] perf/x86/intel/cmt: add asynchronous read for task events

Reading CMT/MBM task events in intel_cmt poses a challenge since it requires to read from multiple sockets (usually accomplished with an IPI) while called with interruptions disabled. The current usptream driver avoids the problematic read with interruptions disabled by not making a dummy

[PATCH v3 26/46] sched: introduce the finish_arch_pre_lock_switch() scheduler hook

This hook allows architecture specific code to be called right after perf_events' context switch but before the scheduler lock is released. It will serve two uses in this patch series: 1) Calls CMT's cgroup context switch code that update the current RMID when no perf event is active (in

[PATCH v3 18/46] perf/core: add arch_info field to struct perf_cgroup

This is the first patch for cgroup support in this series. Adds a new field to perf_cgroup that is used by intel_cmt pmu to associate a monr with a perf_cgroup instance. Signed-off-by: David Carrillo-Cisneros --- include/linux/perf_event.h | 4 +++- kernel/events/core.c

[PATCH v3 20/46] perf/core: add pmu::event_terminate

The new pmu::event_terminate allows a PMU to access an event's cgroup before the event is torn down. Used in CMT to dettach the cgroup from a monr before perf clears event->cgrp. Signed-off-by: David Carrillo-Cisneros --- include/linux/perf_event.h | 6 ++

[PATCH v3 17/46] perf/x86/intel/cmt: add uflag CMT_UF_NOLAZY_RMID

This uflag allows user to specify that a rmid must be allocated at monr's initialization or fail otherwise. For this to work we split __pmonr_apply_uflags into reserve and apply modes. The reserve mode will try to reserve a free rmid, and if successful, the apply mode can proceed using the rmid

[PATCH v3 15/46] perf/x86/intel: encapsulate rmid and closid updates in pqr cache

Encapsulate updates for PQR_ASSOC msr's RMID and CLOSID into intel_rdt_common. Use new interface in Intel CMT. Change RDT common code to build for both CONFIG_INTEL_RDT_A and CONFIG_INTEL_RDT_M. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 6 ++

[PATCH v3 19/46] perf/x86/intel/cmt: add support for cgroup events

First part of cgroup support for CMT. A monr's position in monrs hierarchy depends on the position of it's target cgroup or thread in the cgroup hierarchy. (See code comments for details). A monr that monitors a cgroup keeps a reference to in monr->monr_cgroup and its used in future patches to

[PATCH v3 13/46] perf/x86/intel/cmt: add pmonr's Off and Unused states

A pmonr uses a state machine to keep track of its rmids and their hierarchical dependency with other pmonrs in the same package. This patch introduces the first two states in such state machine. It also adds pmonr_rmids: a word-size container to atomically access a pmonr's sched and read rmids.

[PATCH v3 22/46] perf/x86/intel/cmt: sync cgroups and intel_cmt device start/stop

Start/stop cgroup monitoring for cgroups when intel_cmt device is started/stopped. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 99 + 1 file changed, 99 insertions(+) diff --git a/arch/x86/events/intel/cmt.c

[PATCH v3 30/46] perf/x86/intel/cmt: add asynchronous read for task events

Reading CMT/MBM task events in intel_cmt poses a challenge since it requires to read from multiple sockets (usually accomplished with an IPI) while called with interruptions disabled. The current usptream driver avoids the problematic read with interruptions disabled by not making a dummy

[PATCH v3 26/46] sched: introduce the finish_arch_pre_lock_switch() scheduler hook

This hook allows architecture specific code to be called right after perf_events' context switch but before the scheduler lock is released. It will serve two uses in this patch series: 1) Calls CMT's cgroup context switch code that update the current RMID when no perf event is active (in

[PATCH v3 18/46] perf/core: add arch_info field to struct perf_cgroup

This is the first patch for cgroup support in this series. Adds a new field to perf_cgroup that is used by intel_cmt pmu to associate a monr with a perf_cgroup instance. Signed-off-by: David Carrillo-Cisneros --- include/linux/perf_event.h | 4 +++- kernel/events/core.c | 2 ++ 2 files

[PATCH v3 20/46] perf/core: add pmu::event_terminate

The new pmu::event_terminate allows a PMU to access an event's cgroup before the event is torn down. Used in CMT to dettach the cgroup from a monr before perf clears event->cgrp. Signed-off-by: David Carrillo-Cisneros --- include/linux/perf_event.h | 6 ++ kernel/events/core.c | 4

[PATCH v3 21/46] perf/x86/intel/cmt: use newly introduced event_terminate

The change from event_destroy to event_terminate allows to check if the event is a event cgroup during event destuction, before generic code clears event->cgrp. Signed-off-by: David Carrillo-Cisneros --- arch/x86/events/intel/cmt.c | 5 ++--- 1 file changed, 2 insertions(+),

[PATCH v3 16/46] perf/x86/intel/cmt: set sched rmid and complete pmu start/stop/add/del

Now that the pmonr state machine and pqr_common are in place, add pmonr_update_sched_rmid to find the adequate rmid to use. With it, complete the body of PMUs functions that start/stop, add/del events. A pmonr in Unused state tries to allocate a free rmid the first time one of its monitored

  1   2   3   4   5   6   7   8   9   10   >