Re: Build error for samples/bpf/ due to commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS")

On Fri, Apr 13, 2018 at 03:22:37PM +0200, Jesper Dangaard Brouer wrote: > Hi Peter, > > Your commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") broke build > for several samples/bpf programs. I'm unsure what the best way forward > is to unbreak these... > > The issue is that these samples

Re: Build error for samples/bpf/ due to commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS")

On Fri, Apr 13, 2018 at 03:22:37PM +0200, Jesper Dangaard Brouer wrote: > Hi Peter, > > Your commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") broke build > for several samples/bpf programs. I'm unsure what the best way forward > is to unbreak these... > > The issue is that these samples

Re: [PATCH v7 11/26] of: base: Add of_get_cpu_state_node() to get idle states for a CPU node

On Thu, Apr 12, 2018 at 6:14 AM, Ulf Hansson wrote: > The CPU's idle state nodes are currently parsed at the common cpuidle DT > library, but also when initializing back-end data for the arch specific CPU > operations, as in the PSCI driver case. > > To avoid open-coding,

Re: [PATCH v7 11/26] of: base: Add of_get_cpu_state_node() to get idle states for a CPU node

On Thu, Apr 12, 2018 at 6:14 AM, Ulf Hansson wrote: > The CPU's idle state nodes are currently parsed at the common cpuidle DT > library, but also when initializing back-end data for the arch specific CPU > operations, as in the PSCI driver case. > > To avoid open-coding, let's introduce

Re: [PATCH] mmap.2: MAP_FIXED is okay if the address range has been reserved

On Fri, Apr 13, 2018 at 8:49 AM, Michal Hocko wrote: > On Fri 13-04-18 08:43:27, Michael Kerrisk wrote: > [...] >> So, you mean remove this entire paragraph: >> >> For cases in which the specified memory region has not been >> reserved using an

Re: [PATCH] mmap.2: MAP_FIXED is okay if the address range has been reserved

On Fri, Apr 13, 2018 at 8:49 AM, Michal Hocko wrote: > On Fri 13-04-18 08:43:27, Michael Kerrisk wrote: > [...] >> So, you mean remove this entire paragraph: >> >> For cases in which the specified memory region has not been >> reserved using an existing mapping, newer

Re: [PATCH] iommu: amd: hide unused iommu_table_lock

On 2018-04-04 12:56:59 [+0200], Arnd Bergmann wrote: > The newly introduced lock is only used when CONFIG_IRQ_REMAP is enabled: > > drivers/iommu/amd_iommu.c:86:24: error: 'iommu_table_lock' defined but not > used [-Werror=unused-variable] > static DEFINE_SPINLOCK(iommu_table_lock); > > This

Re: [PATCH] iommu: amd: hide unused iommu_table_lock

On 2018-04-04 12:56:59 [+0200], Arnd Bergmann wrote: > The newly introduced lock is only used when CONFIG_IRQ_REMAP is enabled: > > drivers/iommu/amd_iommu.c:86:24: error: 'iommu_table_lock' defined but not > used [-Werror=unused-variable] > static DEFINE_SPINLOCK(iommu_table_lock); > > This

Re: [PATCH] tools build: Use -Xpreprocessor instead of -Wp and leave pathnames intact

On Fri, Apr 13, 2018 at 02:53:10PM +0100, Will Deacon wrote: > Build.include invokes the pre-processor via GCC in order to generate a > dependency list for the input file. Since these options are passed using > '-Wp,-M...,$(depfile)' it is important that $(depfile) does not contain > any commas,

Re: [PATCH] tools build: Use -Xpreprocessor instead of -Wp and leave pathnames intact

On Fri, Apr 13, 2018 at 02:53:10PM +0100, Will Deacon wrote: > Build.include invokes the pre-processor via GCC in order to generate a > dependency list for the input file. Since these options are passed using > '-Wp,-M...,$(depfile)' it is important that $(depfile) does not contain > any commas,

Re: [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C

On Fri, Apr 13, 2018 at 4:46 PM, Thomas Huth wrote: > On 13.04.2018 16:32, Daniel Vetter wrote: >> On Fri, Apr 13, 2018 at 11:40 AM, Thomas Huth wrote: >>> By enabling the DRM code for virtio-gpu on S390, you currently also get >>> all the code that is enabled

Re: [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C

On Fri, Apr 13, 2018 at 4:46 PM, Thomas Huth wrote: > On 13.04.2018 16:32, Daniel Vetter wrote: >> On Fri, Apr 13, 2018 at 11:40 AM, Thomas Huth wrote: >>> By enabling the DRM code for virtio-gpu on S390, you currently also get >>> all the code that is enabled by CONFIG_HDMI and CONFIG_I2C

Re: [PATCH] netfilter: fix CONFIG_NF_REJECT_IPV6=m link error

On Fri, Apr 13, 2018 at 3:15 PM, Pablo Neira Ayuso wrote: > On Mon, Apr 09, 2018 at 04:43:40PM +0200, Arnd Bergmann wrote: >> On Mon, Apr 9, 2018 at 4:37 PM, Pablo Neira Ayuso >> wrote: >> > Hi Arnd, >> > >> > On Mon, Apr 09, 2018 at 12:53:12PM +0200,

Re: [PATCH] netfilter: fix CONFIG_NF_REJECT_IPV6=m link error

On Fri, Apr 13, 2018 at 3:15 PM, Pablo Neira Ayuso wrote: > On Mon, Apr 09, 2018 at 04:43:40PM +0200, Arnd Bergmann wrote: >> On Mon, Apr 9, 2018 at 4:37 PM, Pablo Neira Ayuso >> wrote: >> > Hi Arnd, >> > >> > On Mon, Apr 09, 2018 at 12:53:12PM +0200, Arnd Bergmann wrote: >> >> We get a new

Re: [RFC PATCH 16/35] ovl: readd lsattr/chattr support

On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote: > Implement FS_IOC_GETFLAGS and FS_IOC_SETFLAGS. > > Needs vfs_ioctl() exported to modules. > > Signed-off-by: Miklos Szeredi > --- > fs/internal.h | 1 - > fs/ioctl.c | 1 + >

Re: [RFC PATCH 16/35] ovl: readd lsattr/chattr support

On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote: > Implement FS_IOC_GETFLAGS and FS_IOC_SETFLAGS. > > Needs vfs_ioctl() exported to modules. > > Signed-off-by: Miklos Szeredi > --- > fs/internal.h | 1 - > fs/ioctl.c | 1 + > fs/overlayfs/file.c | 59 >

Re: [PATCH 2/2] iio: afe: unit-converter: add support for adi,lt6106

On 04/12/2018 05:31 PM, Peter Rosin wrote: > On 2018-04-12 17:35, Andrew F. Davis wrote: >> On 04/12/2018 09:29 AM, Peter Rosin wrote: >>> On 2018-04-11 18:13, Andrew F. Davis wrote: On 04/11/2018 10:51 AM, Lars-Peter Clausen wrote: > On 04/11/2018 05:43 PM, Andrew F. Davis wrote: >>

Re: [PATCH 2/2] iio: afe: unit-converter: add support for adi,lt6106

On 04/12/2018 05:31 PM, Peter Rosin wrote: > On 2018-04-12 17:35, Andrew F. Davis wrote: >> On 04/12/2018 09:29 AM, Peter Rosin wrote: >>> On 2018-04-11 18:13, Andrew F. Davis wrote: On 04/11/2018 10:51 AM, Lars-Peter Clausen wrote: > On 04/11/2018 05:43 PM, Andrew F. Davis wrote: >>

Re: [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C

On 13.04.2018 16:32, Daniel Vetter wrote: > On Fri, Apr 13, 2018 at 11:40 AM, Thomas Huth wrote: >> By enabling the DRM code for virtio-gpu on S390, you currently also get >> all the code that is enabled by CONFIG_HDMI and CONFIG_I2C automatically. >> This is quite ugly, since

Re: [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C

On 13.04.2018 16:32, Daniel Vetter wrote: > On Fri, Apr 13, 2018 at 11:40 AM, Thomas Huth wrote: >> By enabling the DRM code for virtio-gpu on S390, you currently also get >> all the code that is enabled by CONFIG_HDMI and CONFIG_I2C automatically. >> This is quite ugly, since on S390, there is

Re: [PATCH 2/6] tracing: Add trace event error log

On Fri, 13 Apr 2018 09:24:34 -0500 Tom Zanussi wrote: > Yeah, I agree - I'd rather get it right than get it in now. I thought > this made sense, and was based on input from Masami, which I may have > misinterpreted, but I'll wait for some more ideas about the best

Re: [PATCH 2/6] tracing: Add trace event error log

On Fri, 13 Apr 2018 09:24:34 -0500 Tom Zanussi wrote: > Yeah, I agree - I'd rather get it right than get it in now. I thought > this made sense, and was based on input from Masami, which I may have > misinterpreted, but I'll wait for some more ideas about the best way to > do this. Too bad we

Re: [PATCH] ath10k: search all IEs for variant before falling back

Kalle Valo writes: > Thomas Hebb writes: > >> commit f2593cb1b291 ("ath10k: Search SMBIOS for OEM board file >> extension") added a feature to ath10k that allows Board Data File >> (BDF) conflicts between multiple devices that use the same device IDs

Re: [PATCH] ath10k: search all IEs for variant before falling back

Kalle Valo writes: > Thomas Hebb writes: > >> commit f2593cb1b291 ("ath10k: Search SMBIOS for OEM board file >> extension") added a feature to ath10k that allows Board Data File >> (BDF) conflicts between multiple devices that use the same device IDs >> but have different calibration

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On Fri, Apr 13, 2018 at 04:28:21PM +0200, Michal Hocko wrote: > On Fri 13-04-18 16:20:00, Vlastimil Babka wrote: > > We would need kmalloc-reclaimable-X variants. It could be worth it, > > especially if we find more similar usages. I suspect they would be more > > useful than the existing

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On Fri, Apr 13, 2018 at 04:28:21PM +0200, Michal Hocko wrote: > On Fri 13-04-18 16:20:00, Vlastimil Babka wrote: > > We would need kmalloc-reclaimable-X variants. It could be worth it, > > especially if we find more similar usages. I suspect they would be more > > useful than the existing

Re: Some minor fixes for perf user tools

Em Fri, Apr 13, 2018 at 03:13:09PM +0200, Jiri Olsa escreveu: > On Fri, Apr 06, 2018 at 01:38:08PM -0700, Andi Kleen wrote: > > This patchkit fixes some random minor issues in the perf user tools > > Acked-by: Jiri Olsa Thanks, applied. - Arnaldo

Re: Some minor fixes for perf user tools

Em Fri, Apr 13, 2018 at 03:13:09PM +0200, Jiri Olsa escreveu: > On Fri, Apr 06, 2018 at 01:38:08PM -0700, Andi Kleen wrote: > > This patchkit fixes some random minor issues in the perf user tools > > Acked-by: Jiri Olsa Thanks, applied. - Arnaldo

Re: [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C

On Fri, Apr 13, 2018 at 11:40 AM, Thomas Huth wrote: > By enabling the DRM code for virtio-gpu on S390, you currently also get > all the code that is enabled by CONFIG_HDMI and CONFIG_I2C automatically. > This is quite ugly, since on S390, there is no HDMI and no I2C. Thus it >

Re: [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C

On Fri, Apr 13, 2018 at 11:40 AM, Thomas Huth wrote: > By enabling the DRM code for virtio-gpu on S390, you currently also get > all the code that is enabled by CONFIG_HDMI and CONFIG_I2C automatically. > This is quite ugly, since on S390, there is no HDMI and no I2C. Thus it > would be great if

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On Fri 13-04-18 16:20:00, Vlastimil Babka wrote: > On 04/13/2018 03:59 PM, Michal Hocko wrote: > > On Fri 13-04-18 22:35:19, Minchan Kim wrote: > >> On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote: > > [...] > >>> @@ -1614,9 +1623,11 @@ struct dentry *__d_alloc(struct super_block

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On Fri 13-04-18 16:20:00, Vlastimil Babka wrote: > On 04/13/2018 03:59 PM, Michal Hocko wrote: > > On Fri 13-04-18 22:35:19, Minchan Kim wrote: > >> On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote: > > [...] > >>> @@ -1614,9 +1623,11 @@ struct dentry *__d_alloc(struct super_block

Re: [PATCH 2/6] tracing: Add trace event error log

Hi Steve, On Fri, 2018-04-13 at 09:45 -0400, Steven Rostedt wrote: > On Thu, 12 Apr 2018 18:52:13 -0500 > Tom Zanussi wrote: > > > Hi Steve, > > > > On Thu, 2018-04-12 at 18:20 -0400, Steven Rostedt wrote: > > > On Thu, 12 Apr 2018 10:13:17 -0500 > > > Tom Zanussi

Re: [PATCH 2/6] tracing: Add trace event error log

Hi Steve, On Fri, 2018-04-13 at 09:45 -0400, Steven Rostedt wrote: > On Thu, 12 Apr 2018 18:52:13 -0500 > Tom Zanussi wrote: > > > Hi Steve, > > > > On Thu, 2018-04-12 at 18:20 -0400, Steven Rostedt wrote: > > > On Thu, 12 Apr 2018 10:13:17 -0500 > > > Tom Zanussi wrote: > > > > > > > diff

Re: [PATCH] KVM: x86: VMX: hyper-v: Enlightened MSR-Bitmap support

Paolo Bonzini writes: > On 12/04/2018 17:25, Vitaly Kuznetsov wrote: >> @@ -5335,6 +5353,9 @@ static void __always_inline >> vmx_disable_intercept_for_msr(unsigned long *msr_bit >> if (!cpu_has_vmx_msr_bitmap()) >> return; >> >> +if

Re: [PATCH] KVM: x86: VMX: hyper-v: Enlightened MSR-Bitmap support

Paolo Bonzini writes: > On 12/04/2018 17:25, Vitaly Kuznetsov wrote: >> @@ -5335,6 +5353,9 @@ static void __always_inline >> vmx_disable_intercept_for_msr(unsigned long *msr_bit >> if (!cpu_has_vmx_msr_bitmap()) >> return; >> >> +if (static_branch_unlikely(_emsr_bitmap))

Re: [PATCH] kbuild: rpm-pkg: use kernel-install as a fallback for new-kernel-pkg

2018-04-12 3:15 GMT+09:00 Javier Martinez Canillas : > The new-kernel-pkg script is only present when grubby is installed, but it > may not always be the case. So if the script isn't present, attempt to use > the kernel-install script as a fallback instead. > > Signed-off-by:

Re: [PATCH] kbuild: rpm-pkg: use kernel-install as a fallback for new-kernel-pkg

2018-04-12 3:15 GMT+09:00 Javier Martinez Canillas : > The new-kernel-pkg script is only present when grubby is installed, but it > may not always be the case. So if the script isn't present, attempt to use > the kernel-install script as a fallback instead. > > Signed-off-by: Javier Martinez

Re: [RFC PATCH 04/35] ovl: copy up times

On Thu, Apr 12, 2018 at 05:07:55PM +0200, Miklos Szeredi wrote: > Copy up mtime and ctime to overlay inode after times in real object are > modified. Be careful not to dirty cachelines when not necessary. > > This is in preparation for moving overlay functionality out of the VFS. > > This patch

Re: [RFC PATCH 04/35] ovl: copy up times

On Thu, Apr 12, 2018 at 05:07:55PM +0200, Miklos Szeredi wrote: > Copy up mtime and ctime to overlay inode after times in real object are > modified. Be careful not to dirty cachelines when not necessary. > > This is in preparation for moving overlay functionality out of the VFS. > > This patch

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On 04/13/2018 03:59 PM, Michal Hocko wrote: > On Fri 13-04-18 22:35:19, Minchan Kim wrote: >> On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote: > [...] >>> @@ -1614,9 +1623,11 @@ struct dentry *__d_alloc(struct super_block *sb, >>> const struct qstr *name) >>> name =

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On 04/13/2018 03:59 PM, Michal Hocko wrote: > On Fri 13-04-18 22:35:19, Minchan Kim wrote: >> On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote: > [...] >>> @@ -1614,9 +1623,11 @@ struct dentry *__d_alloc(struct super_block *sb, >>> const struct qstr *name) >>> name =

[PATCH] sparc: fix compat siginfo ABI regression

Starting with commit v4.14-rc1~60^2^2~1, a SIGFPE signal sent via kill results to wrong values in si_pid and si_uid fields of compat siginfo_t. This happens due to FPE_FIXME being defined to 0 for sparc, and at the same time siginfo_layout() introduced by the same commit returns SIL_FAULT for

[PATCH] sparc: fix compat siginfo ABI regression

Starting with commit v4.14-rc1~60^2^2~1, a SIGFPE signal sent via kill results to wrong values in si_pid and si_uid fields of compat siginfo_t. This happens due to FPE_FIXME being defined to 0 for sparc, and at the same time siginfo_layout() introduced by the same commit returns SIL_FAULT for

Re: [PATCH 1/2] tracing/events: block: track and print if unplug was explicit or schedule

On Fri, 13 Apr 2018 15:07:17 +0200 Steffen Maier wrote: > Just like blktrace distinguishes explicit and schedule by means of > BLK_TA_UNPLUG_IO and BLK_TA_UNPLUG_TIMER, actually make use of the > existing argument "explicit" to distinguish the two cases in the one > common

Re: [PATCH 1/2] tracing/events: block: track and print if unplug was explicit or schedule

On Fri, 13 Apr 2018 15:07:17 +0200 Steffen Maier wrote: > Just like blktrace distinguishes explicit and schedule by means of > BLK_TA_UNPLUG_IO and BLK_TA_UNPLUG_TIMER, actually make use of the > existing argument "explicit" to distinguish the two cases in the one > common tracepoint

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On Fri, 13 Apr 2018 14:47:04 +0200 Petr Mladek wrote: > The interval is set to one hour. It is rather arbitrary selected time. > It is supposed to be a compromise between never print these messages, > do not lockup the machine, do not fill the entire buffer too quickly, > and

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On Fri, 13 Apr 2018 14:47:04 +0200 Petr Mladek wrote: > The interval is set to one hour. It is rather arbitrary selected time. > It is supposed to be a compromise between never print these messages, > do not lockup the machine, do not fill the entire buffer too quickly, > and get information if

Re: [PATCH v2 2/3] microblaze: remove redundant early_printk support

On Tue, Apr 10, 2018 at 8:44 AM, Michal Simek wrote: > Hi Rob, > > On 28.3.2018 04:06, Rob Herring wrote: >> With earlycon support now enabled, the arch specific early_printk support >> can be removed. > > earlycon is not the full replacement of early_printk support as is

Re: [PATCH v2 2/3] microblaze: remove redundant early_printk support

On Tue, Apr 10, 2018 at 8:44 AM, Michal Simek wrote: > Hi Rob, > > On 28.3.2018 04:06, Rob Herring wrote: >> With earlycon support now enabled, the arch specific early_printk support >> can be removed. > > earlycon is not the full replacement of early_printk support as is > designed right now. >

[GIT PULL] arm64: Late updates for 4.17

Hi Linus, As I mentioned in the previous pull request, we had some nasty conflicts with the KVM tree that resulted in us dropping some spectre-related work shortly before the merge window opened. Now that the KVM tree has been merged, we've put together an updated version of the patches based on

Re: [PATCH ipmi/kcs_bmc v1] ipmi: kcs_bmc: optimize the data buffers allocation

On 2018-04-13 21:50, Corey Minyard wrote: On 04/07/2018 02:54 AM, Wang, Haiyue wrote: Hi Corey, Since IPMI 2.0 just defined minimum, no maximum: KCS/SMIC Input : Required: 40 bytes IPMI Message, minimum KCS/SMIC Output : Required: 38 bytes IPMI Message, minimum Yes, though there

[GIT PULL] arm64: Late updates for 4.17

Hi Linus, As I mentioned in the previous pull request, we had some nasty conflicts with the KVM tree that resulted in us dropping some spectre-related work shortly before the merge window opened. Now that the KVM tree has been merged, we've put together an updated version of the patches based on

Re: [PATCH ipmi/kcs_bmc v1] ipmi: kcs_bmc: optimize the data buffers allocation

On 2018-04-13 21:50, Corey Minyard wrote: On 04/07/2018 02:54 AM, Wang, Haiyue wrote: Hi Corey, Since IPMI 2.0 just defined minimum, no maximum: KCS/SMIC Input : Required: 40 bytes IPMI Message, minimum KCS/SMIC Output : Required: 38 bytes IPMI Message, minimum Yes, though there

Re: [PATCH] ARM: omap2: Fix build when using split object directories

Tony, On 04/12/2018 04:08 AM, Masahiro Yamada wrote: > 2018-04-12 17:21 GMT+09:00 Anders Roxell : >> On 2018-04-11 16:15, Dave Gerlach wrote: >>> The sleep33xx and sleep43xx files should not depend on a header file >>> generated in drivers/memory. Remove this dependency

Re: [PATCH] ARM: omap2: Fix build when using split object directories

Tony, On 04/12/2018 04:08 AM, Masahiro Yamada wrote: > 2018-04-12 17:21 GMT+09:00 Anders Roxell : >> On 2018-04-11 16:15, Dave Gerlach wrote: >>> The sleep33xx and sleep43xx files should not depend on a header file >>> generated in drivers/memory. Remove this dependency and instead allow >>> both

Re: [PATCH v2] ARM: omap2: Fix build when using split object directories

On 04/12/2018 10:24 PM, Masahiro Yamada wrote: > 2018-04-13 11:58 GMT+09:00 Dave Gerlach : >> The sleep33xx and sleep43xx files should not depend on a header file >> generated in drivers/memory. Remove this dependency and instead allow >> both drivers/memory and

Re: [PATCH v2] ARM: omap2: Fix build when using split object directories

On 04/12/2018 10:24 PM, Masahiro Yamada wrote: > 2018-04-13 11:58 GMT+09:00 Dave Gerlach : >> The sleep33xx and sleep43xx files should not depend on a header file >> generated in drivers/memory. Remove this dependency and instead allow >> both drivers/memory and arch/arm/mach-omap2 to generate all

Re: [PATCH v5 05/14] PCI: Add pcie_print_link_status() to log link speed and whether it's limited

On Thu, Apr 12, 2018 at 09:32:49PM -0700, Jakub Kicinski wrote: > On Fri, 30 Mar 2018 16:05:18 -0500, Bjorn Helgaas wrote: > > + if (bw_avail >= bw_cap) > > + pci_info(dev, "%d Mb/s available bandwidth (%s x%d link)\n", > > +bw_cap, PCIE_SPEED2STR(speed_cap),

Re: [PATCH v5 05/14] PCI: Add pcie_print_link_status() to log link speed and whether it's limited

On Thu, Apr 12, 2018 at 09:32:49PM -0700, Jakub Kicinski wrote: > On Fri, 30 Mar 2018 16:05:18 -0500, Bjorn Helgaas wrote: > > + if (bw_avail >= bw_cap) > > + pci_info(dev, "%d Mb/s available bandwidth (%s x%d link)\n", > > +bw_cap, PCIE_SPEED2STR(speed_cap),

[PATCH 01/17] perf stat: Enable 1ms interval for printing event counters values

From: Alexey Budankov Currently print count interval for performance counters values is limited by 10ms so reading the values at frequencies higher than 100Hz is restricted by the tool. This change makes perf stat -I possible on frequencies up to 1KHz and, to

[PATCH 01/17] perf stat: Enable 1ms interval for printing event counters values

From: Alexey Budankov Currently print count interval for performance counters values is limited by 10ms so reading the values at frequencies higher than 100Hz is restricted by the tool. This change makes perf stat -I possible on frequencies up to 1KHz and, to some extent, makes perf stat -I to

[PATCH 02/17] tools headers: Restore READ_ONCE() C++ compatibility

From: Mark Rutland Our userspace defines READ_ONCE() in a way that clang doesn't like, as we have an anonymous union in which neither field is initialized. WRITE_ONCE() is fine since it initializes the __val field. For READ_ONCE() we can keep clang and GCC happy with a

[PATCH 02/17] tools headers: Restore READ_ONCE() C++ compatibility

From: Mark Rutland Our userspace defines READ_ONCE() in a way that clang doesn't like, as we have an anonymous union in which neither field is initialized. WRITE_ONCE() is fine since it initializes the __val field. For READ_ONCE() we can keep clang and GCC happy with a dummy initialization of

[PATCH] vfio-ccw: process ssch with interrupts disabled

When we call ssch, an interrupt might already be pending once we return from the START SUBCHANNEL instruction. Therefore we need to make sure interrupts are disabled until after we're done with our processing. Note that the subchannel lock is the same as the ccwdevice lock that is mentioned in

[PATCH] vfio-ccw: process ssch with interrupts disabled

When we call ssch, an interrupt might already be pending once we return from the START SUBCHANNEL instruction. Therefore we need to make sure interrupts are disabled until after we're done with our processing. Note that the subchannel lock is the same as the ccwdevice lock that is mentioned in

[PATCH 03/17] perf tests: Run dwarf unwind test on arm32

From: Kim Phillips Enable the unwind test on arm32: $ perf test unwind 58: DWARF unwind : Ok Signed-off-by: Kim Phillips Cc: Alexander Shishkin Cc: Brian Robbins

[PATCH 03/17] perf tests: Run dwarf unwind test on arm32

From: Kim Phillips Enable the unwind test on arm32: $ perf test unwind 58: DWARF unwind : Ok Signed-off-by: Kim Phillips Cc: Alexander Shishkin Cc: Brian Robbins Cc: Jiri Olsa Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 06/17] perf jvmti: Give hints about package names needed to build

From: Arnaldo Carvalho de Melo Give as examples of package names to install to have this built for fedora and debian, to help the user a bit. The part from 'e.g.:' onwards: No openjdk development package found, please install JDK package, e.g. openjdk-8-jdk,

[PATCH 06/17] perf jvmti: Give hints about package names needed to build

From: Arnaldo Carvalho de Melo Give as examples of package names to install to have this built for fedora and debian, to help the user a bit. The part from 'e.g.:' onwards: No openjdk development package found, please install JDK package, e.g. openjdk-8-jdk, java-1.8.0-openjdk-devel Cc:

[GIT PULL V2] Thermal management updates for v4.17-rc1

Hi, Linus, Please pull from   git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next to receive the latest Thermal Management updates for v4.17-rc1 with top-most commit b907b408ca64482989cd95dacef804ce509a3673:   Merge branches 'thermal-core' and 'thermal-soc' into next (2018-04-13

[GIT PULL V2] Thermal management updates for v4.17-rc1

Hi, Linus, Please pull from   git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next to receive the latest Thermal Management updates for v4.17-rc1 with top-most commit b907b408ca64482989cd95dacef804ce509a3673:   Merge branches 'thermal-core' and 'thermal-soc' into next (2018-04-13

[PATCH 08/17] Revert "x86/asm: Allow again using asm.h when building for the 'bpf' clang target"

From: Arnaldo Carvalho de Melo This reverts commit ca26cffa4e4aaeb09bb9e308f95c7835cb149248. Newer clang versions accept that asm(_ASM_SP) construct, and now that the bpf-script-test-kbuild.c script, used in one of the 'perf test LLVM' subtests doesn't include ptrace.h, which

[PATCH 08/17] Revert "x86/asm: Allow again using asm.h when building for the 'bpf' clang target"

From: Arnaldo Carvalho de Melo This reverts commit ca26cffa4e4aaeb09bb9e308f95c7835cb149248. Newer clang versions accept that asm(_ASM_SP) construct, and now that the bpf-script-test-kbuild.c script, used in one of the 'perf test LLVM' subtests doesn't include ptrace.h, which ended up including

Re: [RFC PATCH 24/35] Revert "ovl: fix relatime for directories"

On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote: > This reverts commit cd91304e7190b4c4802f8e413ab2214b233e0260. > > Overlayfs no longer relies on the vfs correct atime handling. > > Signed-off-by: Miklos Szeredi > --- > fs/inode.c |

Re: [RFC PATCH 24/35] Revert "ovl: fix relatime for directories"

On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote: > This reverts commit cd91304e7190b4c4802f8e413ab2214b233e0260. > > Overlayfs no longer relies on the vfs correct atime handling. > > Signed-off-by: Miklos Szeredi > --- > fs/inode.c | 21 - >

[PATCH 14/17] perf record: Change warning for missing sysfs entry to debug

From: Thomas Richter Using perf on 4.16.0 kernel on s390 shows this warning: failed: can't open node sysfs data each time I run command perf record ... for example: [root@s35lp76 perf]# ./perf record -e rB -- sleep 1 [ perf record: Woken up 1 times to write

[PATCH 12/17] perf sched: Fix documentation for timehist

From: Takuya Yamamoto Fixed a incorrect option and usage to those shown by "perf sched timehist -h", i.e. the default is really --call-graph, which is equivalent to -g. Signed-off-by: Takuya Yamamoto Cc: Peter Zijlstra Link:

[PATCH 14/17] perf record: Change warning for missing sysfs entry to debug

From: Thomas Richter Using perf on 4.16.0 kernel on s390 shows this warning: failed: can't open node sysfs data each time I run command perf record ... for example: [root@s35lp76 perf]# ./perf record -e rB -- sleep 1 [ perf record: Woken up 1 times to write data ] failed: can't

[PATCH 12/17] perf sched: Fix documentation for timehist

From: Takuya Yamamoto Fixed a incorrect option and usage to those shown by "perf sched timehist -h", i.e. the default is really --call-graph, which is equivalent to -g. Signed-off-by: Takuya Yamamoto Cc: Peter Zijlstra Link:

[PATCH 13/17] perf tests: Disable breakpoint accounting test for powerpc

From: Sandipan Das We disable this test as instruction breakpoints (HW_BREAKPOINT_X) are not available for powerpc. Before applying patch: 21: Breakpoint accounting : --- start --- test child forked, pid 3635 failed opening

[PATCH 15/17] perf report: Fix switching to another perf.data file

From: Arnaldo Carvalho de Melo In the TUI the 's' hotkey can be used to switch to another perf.data file in the current directory, but that got broken in Fixes: b01141f4f59c ("perf annotate: Initialize the priv are in symbol__new()"), that would show this once another file was

[PATCH 13/17] perf tests: Disable breakpoint accounting test for powerpc

From: Sandipan Das We disable this test as instruction breakpoints (HW_BREAKPOINT_X) are not available for powerpc. Before applying patch: 21: Breakpoint accounting : --- start --- test child forked, pid 3635 failed opening event 0 failed opening event

[PATCH 15/17] perf report: Fix switching to another perf.data file

From: Arnaldo Carvalho de Melo In the TUI the 's' hotkey can be used to switch to another perf.data file in the current directory, but that got broken in Fixes: b01141f4f59c ("perf annotate: Initialize the priv are in symbol__new()"), that would show this once another file was chosen:

[PATCH 16/17] perf annotate: Allow setting the offset level in .perfconfig

From: Arnaldo Carvalho de Melo The default is 1 (jump_target): # perf annotate --ignore-vmlinux --stdio2 _raw_spin_lock_irqsave Samples: 3K of event 'cycles:ppp', 3000 Hz, Event count (approx.): 2766398574 _raw_spin_lock_irqsave() /proc/kcore 0.26nop 4.61

[PATCH 17/17] perf annotate: Handle variables in 'sub', 'or' and many other instructions

From: Arnaldo Carvalho de Melo Just like is done for 'mov' and others that can have as source or targets variables resolved by objdump, to make them more compact: - orb$0x4,0x224d71(%rip)# 226ca4 <_rtld_global+0xca4> + orb

[PATCH 16/17] perf annotate: Allow setting the offset level in .perfconfig

From: Arnaldo Carvalho de Melo The default is 1 (jump_target): # perf annotate --ignore-vmlinux --stdio2 _raw_spin_lock_irqsave Samples: 3K of event 'cycles:ppp', 3000 Hz, Event count (approx.): 2766398574 _raw_spin_lock_irqsave() /proc/kcore 0.26nop 4.61push

[PATCH 17/17] perf annotate: Handle variables in 'sub', 'or' and many other instructions

From: Arnaldo Carvalho de Melo Just like is done for 'mov' and others that can have as source or targets variables resolved by objdump, to make them more compact: - orb$0x4,0x224d71(%rip)# 226ca4 <_rtld_global+0xca4> + orb$0x4,_rtld_global+0xca4 Cc:

[PATCH 11/17] perf version: Print status for syscall_table

From: Jin Yao This patch doesn't print "libaudit" line if HAVE_SYSCALL_TABLE_SUPPORT is available and add a line for HAVE_SYSCALL_TABLE_SUPPORT. For example, $ ./perf -vv perf version 4.13.rc5.gc2f8af9 dwarf: [ on ] # HAVE_DWARF_SUPPORT

[PATCH 11/17] perf version: Print status for syscall_table

From: Jin Yao This patch doesn't print "libaudit" line if HAVE_SYSCALL_TABLE_SUPPORT is available and add a line for HAVE_SYSCALL_TABLE_SUPPORT. For example, $ ./perf -vv perf version 4.13.rc5.gc2f8af9 dwarf: [ on ] # HAVE_DWARF_SUPPORT dwarf_getlocations: [ on ] #

[PATCH 10/17] perf tools: Rename HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT

From: Jin Yao To be consistent with other HAVE_XXX_SUPPORT uses in Makefile.config, this patch renames HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT and updates the C code accordingly. Signed-off-by: Jin Yao Suggested-by: Arnaldo Carvalho de

[PATCH 10/17] perf tools: Rename HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT

From: Jin Yao To be consistent with other HAVE_XXX_SUPPORT uses in Makefile.config, this patch renames HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT and updates the C code accordingly. Signed-off-by: Jin Yao Suggested-by: Arnaldo Carvalho de Melo Cc: Alexander Shishkin Cc: Andi Kleen Cc:

[PATCH 07/17] perf tests bpf: Remove unused ptrace.h include from LLVM test

From: Arnaldo Carvalho de Melo The bpf-script-test-kbuild.c script, used in one of the LLVM subtests, includes ptrace.h unnecessarily, and that ends up making it include a header that uses asm(_ASM_SP), a feature that is not supported by clang <= 4.0, breaking that 'perf test'

[PATCH 05/17] perf annotate browser: Allow showing offsets in more than just jump targets

From: Arnaldo Carvalho de Melo Jesper wanted to see offsets at callq sites when doing some performance investigation related to retpolines, so save him some time by providing a 'O' hotkey to allow showing offsets from function start at call instructions or in all instructions,

[PATCH 04/17] perf annotate: Allow showing offsets in more than just jump targets

From: Arnaldo Carvalho de Melo Jesper wanted to see offsets at callq sites when doing some performance investigation related to retpolines, so save him some time by providing an 'struct annotation_options' to control where offsets should appear: just on jump targets? That + call

[PATCH 07/17] perf tests bpf: Remove unused ptrace.h include from LLVM test

From: Arnaldo Carvalho de Melo The bpf-script-test-kbuild.c script, used in one of the LLVM subtests, includes ptrace.h unnecessarily, and that ends up making it include a header that uses asm(_ASM_SP), a feature that is not supported by clang <= 4.0, breaking that 'perf test' entry. This ended

[PATCH 05/17] perf annotate browser: Allow showing offsets in more than just jump targets

From: Arnaldo Carvalho de Melo Jesper wanted to see offsets at callq sites when doing some performance investigation related to retpolines, so save him some time by providing a 'O' hotkey to allow showing offsets from function start at call instructions or in all instructions, just go on

[PATCH 04/17] perf annotate: Allow showing offsets in more than just jump targets

From: Arnaldo Carvalho de Melo Jesper wanted to see offsets at callq sites when doing some performance investigation related to retpolines, so save him some time by providing an 'struct annotation_options' to control where offsets should appear: just on jump targets? That + call instructions?

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On Fri 13-04-18 22:35:19, Minchan Kim wrote: > On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote: [...] > > @@ -1614,9 +1623,11 @@ struct dentry *__d_alloc(struct super_block *sb, > > const struct qstr *name) > > name = _name; > > dname = dentry->d_iname; > >

Re: [PATCH 3/3] dcache: account external names as indirectly reclaimable memory

On Fri 13-04-18 22:35:19, Minchan Kim wrote: > On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote: [...] > > @@ -1614,9 +1623,11 @@ struct dentry *__d_alloc(struct super_block *sb, > > const struct qstr *name) > > name = _name; > > dname = dentry->d_iname; > >

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