intel_idle and turbostat patches for Linux-4.3

Hi Rafael, The following patches are available on my "intel_idle" and "turbostat" branches, as usual, plus here for review. [PATCH 1/4] intel_idle: Skylake Client Support - updated Initial SKL intel_idle support went into 4.3-rc1. That patch works, but this patch makes it more

[PATCH 1/4] intel_idle: Skylake Client Support - updated

From: Len Brown Addition of PC9 state, and minor tweaks to existing PC6 and PC8 states. Signed-off-by: Len Brown --- drivers/idle/intel_idle.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/idle/intel_idle.c

[PATCH 3/4] tools/power turbostat: KNL workaround for %Busy and Avg_MHz

From: Hubert Chrzaniuk KNL increments APERF and MPERF every 1024 clocks. This is compliant with the architecture specification, which requires that only the ratio of APERF/MPERF need be valid. However, turbostat takes advantage of the fact that these two MSRs

[PATCH 2/4] tools/power turbostat: IVB Xeon: fix --debug regression

From: Len Brown Staring in Linux-4.3-rc1, commit 6fb3143b561c ("tools/power turbostat: dump CONFIG_TDP") touches MSR 0x648, which is not supported on IVB-Xeon. This results in "turbostat --debug" exiting on those systems: turbostat: /dev/cpu/2/msr offset 0x648 read failed:

iwlwifi: Error sending REPLY_ADD_STA

Hello, sometimes the Wifi adapter (Wireless-N 2230) in this Lenovo Thinkpad E431 "disappears" and cannot be fixed by re-loading the iwlwifi kernel module either. Only a reboot will do. When I was running 3.16.0-4-amd64 from Debian/stable, I noticed the following message, but only _once_ and

Re: [RFC] PCI: Unassigned Expansion ROM BARs

On Thu, Sep 24, 2015 at 09:35:20PM -0700, Yinghai Lu wrote: > On Thu, Sep 24, 2015 at 12:01 PM, Yinghai Lu wrote: > > > Or do we want to keep a white list to say which device should have > > ROM bar as mush have, and other is optional to have ? > > Subject: [RFC PATCH] PCI:

Re: [PATCH v3 1/5] Input: goodix - reset device at init

On Thu, 2015-09-10 at 14:04 +, Tirdea, Irina wrote: > > > -Original Message- > > From: Bastien Nocera [mailto:had...@hadess.net] > > Sent: 09 September, 2015 20:03 > > To: Tirdea, Irina; linux-in...@vger.kernel.org > > Cc: linux-kernel@vger.kernel.org; Rob Herring; Pawel Moll; Ian > >

Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags

On 09/24/2015 10:54 AM, Murali Karicheri wrote: [...] > ti,omap3 is the family of omap3 devices similar to keystone. ti,omap3450 > is required if there is an exceptional treatment required for ti,omap3450. > > In keystone case so far there is no case of exceptional treatment > required in the

Re: netlink: Add barrier to netlink_connect for theoretical case

Hello, Herbert. On Fri, Sep 25, 2015 at 09:43:27AM +0800, Herbert Xu wrote: > Well had you said this in the first place I would've fixed it a > long time ago. There aren't any in-kernel users right now and > even if there were they'd have to do a connect/bind/sendmsg on > the same socket in two

Re: netlink: Add barrier to netlink_connect for theoretical case

Hello, Herbert. On Fri, Sep 25, 2015 at 11:39:57AM +0800, Herbert Xu wrote: > +static inline bool netlink_bound(struct netlink_sock *nlk) > +{ > + bool bound = READ_ONCE(nlk->bound); > + > + /* Ensure nlk is hashed and visible. */ > + if (bound) > + smp_rmb(); > + > +

Re: [PATCH v3 0/4] scsi: cleanup ioctl headers and provide UAPI versions

The whole series looks good to me. Thanks for picking this work up! Reviewed-by: Christoph Hellwig -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: Problems with printk logs and my driver

On 2015-09-25 08:02, Jiri Kosina wrote: On Fri, 25 Sep 2015, Felipe Tonello wrote: Maybe a better description on Kconfig and/or comments on source code it's enough. I personally find the current Kconfig description: === config USB_KBD tristate "USB HIDBP Keyboard (simple Boot)

x86_64: MAX_LOCAL_APIC way too big?

For 64-bit kernels, MAX_LOCAL_APIC is 32k: #ifdef CONFIG_X86_32 ... #else # define MAX_IO_APICS 128 # define MAX_LOCAL_APIC 32768 #endif (It seems to be a bit of a misnomer, it's not a maximum number of APICs we support, it's the highest APIC _id_ we support.) 32 thousand APICs? That's a lot.

Re: Glibc recvmsg from kernel netlink socket hangs forever

On 09/25/2015 08:55 AM, Herbert Xu wrote: On Thu, Sep 24, 2015 at 10:34:10PM -0700, Guenter Roeck wrote: Any idea what may be needed for 4.1 ? I am currently trying https://patchwork.ozlabs.org/patch/473041/, This patch should not make any difference on 4.1 and later because 4.1 is where I

Re: [PATCH] gpio: msm: Remove unused driver

On Fri, Aug 28, 2015 at 2:48 PM, Stephen Boyd wrote: > Remove this driver now that Bjorn has introduced a pinctrl driver > for msm8660 and the dts files have been updated with the pinctrl > compatibles. > > Cc: Bjorn Andersson > Cc: Andy

[PATCH v1 0/8] xen/arm: vgic: Support 32-bit access for 64-bit register

Hi all, This series aims to fix the 32-bit access on 64-bit register. Some guest OS such as FreeBSD and Linux (only in the ITS) use 32-bit access and will crash at boot time. I took the opportunity to go further and optimize the way Xen is storing registers such as GICD_IPRIORITYR, GICD_ITARGETR

[PATCH v1 7/8] xen/arm: vgic: Introduce helpers to read/write/clear/set vGIC register ...

and use them in the vGIC emulation. The GIC registers may support different access sizes. Rather than open coding the access for every registers, provide a set of helpers to access them. The caller will have to call vgic_regN_* where N is the size of the emulated registers. The new helpers

[PATCH v1 4/8] xen/arm: vgic: ctlr stores a 32-bit hardware register so use uint32_t

Signed-off-by: Julien Grall --- Changes in v2: - Patch added --- xen/include/asm-arm/domain.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xen/include/asm-arm/domain.h b/xen/include/asm-arm/domain.h index c3f5a95..1a5bfd7 100644 ---

[PATCH] mm, fs: Obey gfp_mapping for add_to_page_cache

From: Michal Hocko 6afdb859b710 ("mm: do not ignore mapping_gfp_mask in page cache allocation paths) has caught some users of hardcoded GFP_KERNEL used in the page cache allocation paths. This, however, wasn't complete and there were others which went unnoticed. Dave Chinner

Re: [PATCH 1/6] driver-core: platform: Provide helpers for multi-driver modules

On Fri, Sep 25, 2015 at 01:27:28PM +0300, Jani Nikula wrote: > On Thu, 24 Sep 2015, Thierry Reding wrote: [...] > > diff --git a/drivers/base/platform.c b/drivers/base/platform.c [...] > > +/** > > + * platform_register_drivers - register an array of platform drivers > >

Re: [PATCH] memcg: make mem_cgroup_read_stat() unsigned

On Tue 22-09-15 15:16:32, Greg Thelen wrote: > mem_cgroup_read_stat() returns a page count by summing per cpu page > counters. The summing is racy wrt. updates, so a transient negative sum > is possible. Callers don't want negative values: > - mem_cgroup_wb_stats() doesn't want negative nr_dirty

Re: [PATCH 1/3] blk-cgroup: Declare local symbols static

Acked-by: Tejun Heo Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

Re: PIDs Controller Limit

Hello, Aleksa. On Thu, Sep 24, 2015 at 09:42:38AM +1000, Aleksa Sarai wrote: > Does it make sense for the PIDs controller to allow a user to set a > limit of 0? Since we don't cancel attaches, a limit of 0 doesn't > affect anything (nothing stops attaches, and you need to have a > process in the

Re: [PATCH] kselftest: using built-in rule when delete file

On Thu, Sep 24, 2015 at 12:07:47PM +1000, Michael Ellerman wrote: > On Thu, 2015-09-24 at 10:05 +0800, long.wanglong wrote: > > On 2015/9/24 9:46, Michael Ellerman wrote: > > > On Wed, 2015-09-23 at 09:40 +, Wang Long wrote: > > >> Use make's built-in rules to when delete a file > > >> or

Re: [PATCH cgroup/for-4.3-fixes] cgroup, writeback: don't enable cgroup writeback on traditional hierarchies

Hello, Artem. On Fri, Sep 25, 2015 at 01:50:22PM +0300, Artem Bityutskiy wrote: > > Does not compile with multiple errors like > > > > linux/fs/fs-writeback.c:799:10: error: ‘struct bdi_writeback’ has no > > member named ‘last_comp_gen’ > >bdi->wb.last_comp_gen = bdi->wb.comp_gen; > > I

Re: [PATCH 05/11] x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory

On Fri, Sep 25, 2015 at 05:02:09PM +0100, Tomasz Nowicki wrote: [...] > > My concerns/ideas related to raw accessors for ARM64, please correct me > > at any point. > > > > ACPI spec - chapter: 19.5.96 OperationRegion (Declare Operation Region) > > defines PCI_Config as one of region types. Every

Re: [PATCH] memcg: make mem_cgroup_read_stat() unsigned

On Wed 23-09-15 00:21:33, Greg Thelen wrote: > > Andrew Morton wrote: > > > On Tue, 22 Sep 2015 17:42:13 -0700 Greg Thelen wrote: [...] > >> I assume it's pretty straightforward to create generic > >> percpu_counter_array routines which memcg could use. Possibly something >

[PATCH 2/3] perf intel-pt: Remove no_force_psb from documentation

From: Adrian Hunter no_force_psb was dropped as a late change to the kernel driver. Consequently, remove it from the documentation. Signed-off-by: Adrian Hunter Cc: Jiri Olsa Link:

[PATCH 1/3] perf probe: Use existing routine to look for a kernel module by dso->short_name

From: Arnaldo Carvalho de Melo We have map_groups__find_by_name() to look at the list of modules that are in place for a given machine, so use it instead of traversing the machine dso list, which also includes DSOs for userspace. When merging the user and kernel DSO lists a bug

[PATCH 3/3] perf tools: Fix copying of /proc/kcore

From: Adrian Hunter A copy of /proc/kcore containing the kernel text can be made to the buildid cache. e.g. perf buildid-cache -v -k /proc/kcore To workaround objdump limitations, a copy is also made when annotating against /proc/kcore. The copying process

[PATCH v2] driver-core: platform: Provide helpers for multi-driver modules

From: Thierry Reding Some modules register several sub-drivers. Provide a helper that makes it easy to register and unregister a list of sub-drivers, as well as unwind properly on error. Cc: Greg Kroah-Hartman Signed-off-by: Thierry Reding

[GIT PULL] Miscellaneous keyrings and modsign fixes

in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-fixes-20150925 for you to fetch changes up to 283e8ba2dfde54f8f27d7d0f459a07de79a39d55: MODSIGN: Change from CMS to PKCS#7 signing if the openssl is too old (2015-09-25 16:31:46 +0100

[PATCH v2 1/7] genirq: Fix the documentation of request_percpu_irq

From: Maxime Ripard The documentation of request_percpu_irq is confusing and suggest that the interrupt is not enabled at all, while it is actually enabled on the local CPU. Clarify that. Signed-off-by: Maxime Ripard

[PATCH v2 5/7] net: mvneta: Handle per-cpu interrupts

From: Maxime Ripard Now that our interrupt controller is allowing us to use per-CPU interrupts, actually use it in the mvneta driver. This involves obviously reworking the driver to have a CPU-local NAPI structure, and report for incoming packet using that

[PATCH v2 3/7] irqchip: armada-370-xp: Rework per-cpu interrupts handling

From: Maxime Ripard The MPIC driver currently has a list of interrupts to handle as per-cpu. Since the timer, fabric and neta interrupts were the only per-cpu interrupts in the system, we can now remove the switch and just check for the hardware irq number to

Re: can't oom-kill zap the victim's memory?

Michal Hocko wrote: > On Thu 24-09-15 14:15:34, David Rientjes wrote: > > > > Finally. Whatever we do, we need to change oom_kill_process() first, > > > > and I think we should do this regardless. The "Kill all user processes > > > > sharing victim->mm" logic looks wrong and

Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags

9/25/2015 9:01 AM, Nishanth Menon wrote: On 09/25/2015 10:18 AM, santosh shilimkar wrote: On 9/25/2015 7:50 AM, Nishanth Menon wrote: [...] But, how about userspace needing to know which SoC they are on, without needing to depend on board->soc mapping? How do we help resolve that? Why the

[PATCH v1 2/8] xen/arm: io: Extend write/read handler to pass the register in parameter

From: Julien Grall Rather than letting each handler to retrieve the register used by the I/O access, add a new parameter to pass the register in parameter. This will help to implement generic register manipulation on I/O access such as sign-extension and endianess.

[PATCH v1 6/8] xen/arm: vgic: Optimize the way to store the target vCPU in the rank

Xen is currently directly storing the value of register GICD_ITARGETSR (for GICv2) and GICD_IROUTER (for GICv3) in the rank. This makes the emulation of the registers access very simple but makes the code to get the target vCPU for a given IRQ more complex. While the target vCPU of an IRQ is

[PATCH v1 1/8] xen/arm: io: remove mmio_check_t typedef

From: Julien Grall This typedef is a left-over of the previous MMIO emulation implementation. Signed-off-by: Julien Grall --- Changes in v2: - Patch added --- xen/include/asm-arm/mmio.h | 1 - 1 file changed, 1 deletion(-) diff

[PATCH v1 3/8] xen/arm: Support sign-extension for every read access

The guest may try to load data from the emulated MMIO region using instruction with Sign-Extension (i.e ldrs*). This can happen for any access smaller than the register size (byte/half-word for aarch32, byte/half-word/word for aarch64). The support of sign-extension was limited for byte access in

Re: [PATCH v1 0/8] xen/arm: vgic: Support 32-bit access for 64-bit register

Please ignore this version, I've sent it to the wrong mailing list. Sorry for the noise. On 25/09/15 15:50, Julien Grall wrote: > Hi all, > > This series aims to fix the 32-bit access on 64-bit register. Some guest > OS such as FreeBSD and Linux (only in the ITS) use 32-bit access and will >

[PATCH v1 8/8] xen/arm: vgic-v3: Support 32-bit access for 64-bit registers

Based on 8.1.3 (IHI 0069A), unless stated otherwise, the 64-bit registers supports both 32-bit and 64-bits access. All the registers we properly emulate (i.e not RAZ/WI) supports 32-bit access. For RAZ/WI, it's also seems to be the case but I'm not 100% sure. Anyway, emulating 32-bit access for

[PATCH v1 5/8] xen/arm: vgic: Optimize the way to store GICD_IPRIORITYR in the rank

Xen is currently directly storing the value of register GICD_IPRIORITYR in the rank. This makes emulation of the register access very simple but makes the code to get the priority for a given IRQ more complex. While the priority of an IRQ is retrieved everytime an IRQ is injected to the guest,

Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags

On 9/25/2015 7:50 AM, Nishanth Menon wrote: On 09/24/2015 10:54 AM, Murali Karicheri wrote: [...] ti,omap3 is the family of omap3 devices similar to keystone. ti,omap3450 is required if there is an exceptional treatment required for ti,omap3450. In keystone case so far there is no case of

Re: [PATCH v3 4/4] scsi: provide UAPI version of scsi/sg.h and scsi/scsi_ioctl.h

On 09/25/2015 02:28 AM, Paolo Bonzini wrote: Provide a UAPI version of the header in the kernel, making it easier for interested projects to use an up-to-date version of the header. The new headers are placed under uapi/linux/ so as not to conflict with the glibc-provided headers in

Re: [PATCH 1/6] driver-core: platform: Provide helpers for multi-driver modules

On Thu, Sep 24, 2015 at 07:02:36PM +0200, Thierry Reding wrote: > From: Thierry Reding > > Some modules register several sub-drivers. Provide a helper that makes > it easy to register and unregister a list of sub-drivers, as well as > unwind properly on error. > > Cc: Greg

Re: [PATCH v2 03/19] libata: samsung_cf: fix handling platform_get_irq result

On Fri, Sep 25, 2015 at 08:43:31AM +0200, Andrzej Hajda wrote: > The function can return negative value. > > The problem has been detected using proposed semantic patch > scripts/coccinelle/tests/assign_signed_to_unsigned.cocci [1]. > > [1]: http://permalink.gmane.org/gmane.linux.kernel/2046107

Re: [PATCH] xen/pvhvm: add soft reset on kexec/kdump support

On 09/25/2015 09:59 AM, Konrad Rzeszutek Wilk wrote: On Fri, Sep 25, 2015 at 11:59:52AM +0200, Vitaly Kuznetsov wrote: Currently there is a number of issues preventing PVHVM Xen guests from doing successful kexec/kdump: - Bound event channels. - Registered vcpu_info. - PIRQ/emuirq mappings. -

Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags

On 09/25/2015 10:18 AM, santosh shilimkar wrote: > On 9/25/2015 7:50 AM, Nishanth Menon wrote: [...] >> But, how about userspace >> needing to know which SoC they are on, without needing to depend on >> board->soc mapping? How do we help resolve that? >> > Why the user space should care about

Re: [PATCH 07/17][UPDATE] mfd: qcom_rpm: Drop use of IRQF_NO_SUSPEND flag

On Fri, 25 Sep 2015, Sudeep Holla wrote: > The driver handles wakeup irq correctly using irq_set_irq_wake. There's > no need to use IRQF_NO_SUSPEND while registering the interrupt. > > This patch removes the use of IRQF_NO_SUSPEND flag. > > Cc: Samuel Ortiz > Acked-by:

Re: [PATCH] watchdog: perform all-CPU backtrace in case of hard lockup

On Fri, Sep 25, 2015 at 01:15:56PM +0200, Jiri Kosina wrote: > From: Jiri Kosina > > In many cases of hardlockup reports, it's actually not possible to know > why it triggered, because the CPU that got stuck is usually waiting on a > resource (with IRQs disabled) in posession

RE: [PATCH RFC 00/10] counter read during perf sampling

> On Thu, Sep 24, 2015 at 07:47:40PM +, Liang, Kan wrote: > > > > > > > On Tue, Sep 22, 2015 at 10:13:33AM -0400, kan.li...@intel.com wrote: > > > > From: Kan Liang > > > > > > > > The patch series intends to read counter statistics with fixed > > > > frequency during

[3.19.y-ckt stable] Linux 3.19.8-ckt7

I am announcing the release of the Linux 3.19.8-ckt7 kernel. The updated 3.19.y-ckt tree can be found at: git://kernel.ubuntu.com/ubuntu/linux.git linux-3.19.y and can be browsed at: http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.19.y The diff from v3.19.8-ckt6 is posted as

[PATCH 0/5] mtd: nand/UBI: add power-cut emulation

Hello, This series aims at adding a power-cut emulation layer at the nandsim level. The final goal is to support MLC NAND emulation in nandsim in order to validate the work done in the NAND, UBI and UBIFS layers to reliably support those chips. Even though the UBI layer already provides a

[PATCH 1/5] mtd: nand: add basic stuff to support power-cut emulation

Add a new status flag to support power-cut emulation. Since real NAND status is limited to 8bits, we can safely use higher bits for something else. The NAND_STATUS_POWER_CUT is assigned bit 30 to avoid integer overflow (not sure this is necessary). The NAND status is currently retrieved using

Re: [PATCH v2] ARM: dts: sunxi: Add regulators for LeMaker BananaPi

Hi Kevin, Kevin Hilman schrieb am 25. Sept 2015 01:57: > On Tue, Aug 18, 2015 at 8:36 AM, Maxime Ripard > wrote: >> On Sun, Aug 02, 2015 at 06:18:25PM +0200, Timo Sigurdsson wrote: >>> sun7i-a20-bananapi.dts doesn't contain regulator nodes for the AXP209 >>>

[PATCH v2 1/3] MIPS: mm: compile maar_init unconditionally

maar_init was previously only compiled when CONFIG_NEED_MULTIPLE_NODES was not set, which has been fine since it is only called from the standard implementation of mem_init which has the same condition. In preparation for calling it from the SMP startup code on secondary CPUs, move maar_init

[PATCH v2 0/3] MAAR SMP fix

This series improves support for Memory Accessibility Attribute Registers (MAARs) by printing their configuration during boot and by applying the configuration to secondary CPUs, which have their own independent MAAR state. Paul Burton (3): MIPS: mm: compile maar_init unconditionally MIPS:

[PATCH v2 2/3] MIPS: print MAAR configuration during boot

Verifying that the MAAR configuration is as expected is useful when debugging the performance of a system. Print out the memory regions configured via MAAR along with their attributes. Signed-off-by: Paul Burton --- Changes in v2: None arch/mips/mm/init.c | 29

[PATCH v2 3/3] MIPS: initialise MAARs on secondary CPUs

MAARs should be initialised on each CPU (or rather, core) in the system in order to achieve consistent behaviour & performance. Previously they have only been initialised on the boot CPU which leads to performance problems if tasks are later scheduled on a secondary CPU, particularly if those

Re: [RFC] PCI: Unassigned Expansion ROM BARs

On Fri, 2015-09-25 at 09:35 -0500, Bjorn Helgaas wrote: > On Thu, Sep 24, 2015 at 09:35:20PM -0700, Yinghai Lu wrote: > > On Thu, Sep 24, 2015 at 12:01 PM, Yinghai Lu wrote: > > > > > Or do we want to keep a white list to say which device should have > > > ROM bar as mush

Re: [PATCH v4] mfd: tps6105x: Fix possible NULL pointer access.

On Fri, 25 Sep 2015, Grigoryev Denis wrote: > tps6105x driver provides two cells. One is for GPIO and another one is > for selected mode depending on platform data. When tps6105x is used in > GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell > .name == NULL. This value causes an

Re: [Patch V1 1/3] x86, mce: MCE log size not enough for high core parts

On Fri, Sep 25, 2015 at 10:29:01AM +0200, Borislav Petkov wrote: > > > > > > > The last patch of that series had 2 changes. > > > > 1. Allow offline cpu's to participate in the rendezvous. Since in the odd > > chance the offline cpus have any errors collected we can still report them. > > (we

Re: [PATCH v6 4/9] Input: goodix - write configuration data to device

On Tue, 2015-09-15 at 17:31 +0300, Irina Tirdea wrote: > Goodix devices can be configured by writing custom data to the device > at > init. The configuration data is read with request_firmware from > "goodix__cfg.bin", where is the product id read from the > device > (e.g.: goodix_911_cfg.bin for

Re: [PATCH] KVM: nVMX: emulate the INVVPID instruction

Paolo Bonzini writes: > On 24/09/2015 17:45, Bandan Das wrote: >> > However, I have applied the patch to kvm/queue. Please send the changes >> > separately, and I will squash them in the existing VPID patch. >> >> Please don't do this. It's making it really difficult to

Re: [3.13.y-ckt stable] Linux 3.13.11-ckt27

diff --git a/Makefile b/Makefile index aa8e2b6..2e4c860 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ VERSION = 3 PATCHLEVEL = 13 SUBLEVEL = 11 -EXTRAVERSION = -ckt26 +EXTRAVERSION = -ckt27 NAME = King of Alienated Frog Porn # *DOCUMENTATION* diff --git

Re: [PATCH] arm64: Increase the max granular size

Will, On 22.09.15 19:29:02, Will Deacon wrote: > On Tue, Sep 22, 2015 at 06:59:48PM +0100, Robert Richter wrote: > > From: Tirumalesh Chalamarla > > > > Increase the standard cacheline size to avoid having locks in the same > > cacheline. > > > > Cavium's ThunderX core

[3.13.y-ckt stable] Linux 3.13.11-ckt27

I am announcing the release of the Linux 3.13.11-ckt27 kernel. The updated 3.13.y-ckt tree can be found at: git://kernel.ubuntu.com/ubuntu/linux.git linux-3.13.y and can be browsed at: http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.13.y The diff from v3.13.11-ckt26 is posted

[GIT PULL 0/3] perf/urgent fixes

Hi Ingo, Please consider pulling, - Arnaldo The following changes since commit d0d0313c2ae4bc220c4ed96ce340860a4e74a2e9: Merge tag 'perf-urgent-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent (2015-09-23 09:41:09 +0200) are available in the

Re: [PATCH v2] toshiba_acpi: Remove unneeded u32 variables from *setup_keyboard

On Fri, Sep 18, 2015 at 10:45:34PM -0600, Azael Avalos wrote: > The function toshiba_acpi_setup_keyboard currently has two u32 variables > used to store the Hotkey Event Type and the result of the HCI_SYSTEM_EVENT > query. > > This patch removes those two variables, as we already have a global >

Re: [PATCH] coccinelle: assign signed result to unsigned variable

>>> +@rs@ >>> +position p; >>> +typedef bool, u8, u16, u32, u64, s8, s16, s32, s64; >>> +{char, short int, int, long, long long, s8, s16, s32, s64} vs; >> Can it matter to specify also the type modifier "signed" in this SmPL >> approach? >>

Re: Glibc recvmsg from kernel netlink socket hangs forever

On Thu, Sep 24, 2015 at 10:34:10PM -0700, Guenter Roeck wrote: > > Any idea what may be needed for 4.1 ? > I am currently trying https://patchwork.ozlabs.org/patch/473041/, This patch should not make any difference on 4.1 and later because 4.1 is where I rewrote rhashtable resizing and it should

Re: [PATCH 05/11] x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory

Hi Lorenzo, On 09/14/2015 04:55 PM, Tomasz Nowicki wrote: On 11.09.2015 13:20, Lorenzo Pieralisi wrote: On Wed, Sep 09, 2015 at 02:47:55PM +0100, Tomasz Nowicki wrote: [...] I think (but I am happy to be corrected) that the map_bus() hook (ie that's why struct pci_bus is required in eg

[PATCH v2 2/7] irq: Export per-cpu irq allocation and de-allocation functions

From: Maxime Ripard Some drivers might use the per-cpu interrupts and still might be built as a module. Export request_percpu_irq an free_percpu_irq to these user, which also make it consistent with enable/disable_percpu_irq that were exported. Reported-by:

[PATCH v2 4/7] net: mvneta: Fix CPU_MAP registers initialisation

From: Maxime Ripard The CPU_MAP register is duplicated for each CPUs at different addresses, each instance being at a different address. However, the code so far was using CONFIG_NR_CPUS to initialise the CPU_MAP registers for each registers, while the SoCs

[PATCH v2 7/7] net: mvneta: Statically assign queues to CPUs

From: Maxime Ripard Since the switch to per-CPU interrupts, we lost the ability to set which CPU was going to receive our RX interrupt, which was now only the CPU on which the mvneta_open function was run. We can now assign our queues to their respective CPUs,

[PATCH v2 6/7] net: mvneta: Allow different queues

From: Maxime Ripard The mvneta driver allows to change the default RX queue trough the rxq_def kernel parameter. However, the current code doesn't allow to have any value but 0. It is actively checked for in the driver's probe because the drivers makes a number

Re: [PATCH v4 5/5] arm64: dts: Add sensor node to Juno dt

Liviu Dudau writes: > On Tue, Sep 15, 2015 at 05:51:01PM +0100, Punit Agrawal wrote: >> The SCP firmware on Juno provides access to SoC sensors via the >> SCPI. Add the sensor nodes to the device tree to enable this support. >> >> Signed-off-by: Punit Agrawal

RE: [PATCH v2 08/25] powerpc/8xx: Map IMMR area with 512k page at a fixed address

From: Scott Wood > Sent: 24 September 2015 21:14 > > Isn't this a more general problem? > > > > If there are multiple remap requests for the same physical page > > shouldn't the kernel be just increasing a reference count somewhere > > and returning address in the same virtual page? > > This

Re: [3.19.y-ckt stable] Linux 3.19.8-ckt7

diff --git a/Makefile b/Makefile index 535f2bd..57fe105 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ VERSION = 3 PATCHLEVEL = 19 SUBLEVEL = 8 -EXTRAVERSION = -ckt6 +EXTRAVERSION = -ckt7 NAME = Sedated Swine # *DOCUMENTATION* diff --git a/arch/arm64/kvm/inject_fault.c

[PATCH 3/5] UBI: switch the UBI device in read-only mode when mtd returns -EROFS

The NAND layer is now able to forward power-cut emulation errors from a NAND driver to the MTD user. Check for this kind of errors in UBI and switch the UBI device in read-only mode if such an error occurs. The error will also be forwarded to the UBI user requesting the operation if any, thus

[PATCH 4/5] mtd: nand: nandsim: implement ->get_status()

We need to implement a specific ->get_status() function to support power-cut emulation. Signed-off-by: Boris Brezillon --- drivers/mtd/nand/nandsim.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/nand/nandsim.c

[GIT PULL] Please pull NFS client bugfixes

Hi Linus, The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f: Linux 4.3-rc1 (2015-09-12 16:35:56 -0700) are available in the git repository at: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.3-2 for you to fetch changes up to

[PATCH 5/5] mtd: nand: nandsim: add support for power-cut emulation

Add support for power-cut emulation on program and erase operations. This power-cut emulation is configurable through the nandsim/powercut file exposed in debugfs and can be triggered on erase or program operations. The user can also specify a specific block and/or page (relative to a block) at

[PATCH 2/5] mtd: nand: return -EROFS in case of power-cut emulation

Now that we are able to emulate power-cuts, we should differentiate the power-cut emulation and input/output error cases to let the MTD user decide what it should do. EROFS was chosen to mimic what's done in UBI when a power-cut emulation occurs. Signed-off-by: Boris Brezillon

[PATCH v2 0/7] net: mvneta: Switch to per-CPU irq and make rxq_def useful

Hi, As stated in the first version: "this patchset reworks the Marvell neta driver in order to really support its per-CPU interrupts, instead of faking them as SPI, and allow the use of any RX queue instead of the hardcoded RX queue 0 that we have currently." Following the review which has been

Re: [PATCH] memcg: make mem_cgroup_read_stat() unsigned

Michal Hocko wrote: > On Tue 22-09-15 15:16:32, Greg Thelen wrote: >> mem_cgroup_read_stat() returns a page count by summing per cpu page >> counters. The summing is racy wrt. updates, so a transient negative sum >> is possible. Callers don't want negative values: >> - mem_cgroup_wb_stats()

Re: [PATCH v1 2/3] pinctrl: rockchip: add support for the rk3036

On Thu, Aug 27, 2015 at 10:46 PM, Xing Zheng wrote: > Many parts of pinctrl rk3036 are similar to rk2928's. > > Signed-off-by: Xing Zheng Patch applied with Heiko's ACK, and THANKS to Rockchip and Xing for working in the open community with

Re: No more new fbdev drivers, please

On Friday 25 September 2015, Aaro Koskinen wrote: > Hi, > > On Thu, Sep 24, 2015 at 03:27:01PM +0300, Tomi Valkeinen wrote: > > fbdev is (more or less) maintained, but it's a deprecated framework. All > > new Linux display drivers should be done on DRM. > > > > So let's not add any more new fbdev

[PATCH] drm/i915: fix task reference leak in i915_debugfs.c

Leak a task reference in i915_ppgtt_info(), add put_task_struct() to fix it. Signed-off-by: Geliang Tang --- drivers/gpu/drm/i915/i915_debugfs.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_debugfs.c

[GIT PULL] KVM fixes for 4.3-rc3

Linus, The following changes since commit 00cc1633816de8c95f337608a1ea64e228faf771: sched: access local runqueue directly in single_task_running (2015-09-18 13:47:59 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus for you to

Re: [PATCH 1/2] audit: stop an old auditd being starved out by a new auditd

On 15/09/24, Paul Moore wrote: > On Friday, September 18, 2015 03:59:58 AM Richard Guy Briggs wrote: > > Nothing prevents a new auditd starting up and replacing a valid > > audit_pid when an old auditd is still running, effectively starving out > > the old auditd since audit_pid no longer points

[PATCH v2 1/4] perf tools: Adds the config_term callback for different type events

Currently, function config_term() is used for checking config terms of all types of events, while unknown terms is not reported as an error because pmu events have valid terms in sysfs. But this is wrong when unknown terms are specificed to hw/sw events. This patch Adds the config_term callback so

[PATCH v2 2/4] perf tools: Prompt error message for wrong terms of hw/sw events

Prompt proper error message when wrong config terms is specificed for hw/sw type perf events. This patch makes the original error prompt function formats_error_string() more generic, which only outputs the static config terms for hw/sw perf events, and prepends pmu formats for pmu events. Before

[PATCH v2 4/4] perf tools: Enable event_config terms to tracepoint events

This patch enable config terms for tracepoint perf events. Valid terms for tracepoint events are call-graph and stack-size, so we can use different callgraph settings for each event and eliminate unnecessary overhead. Here is an example for using different call-graph config for each tracepoint.

[PATCH v2 3/4] perf tools: Adds the tracepoint name parsing support

Adds rules for parsing tracepoint names. Change rules of tracepoint which derives of PE_NAMEs into tracepoint names directly, so adding more rules based on tracepoint names will be easier. Signed-off-by: He Kuang --- tools/perf/util/parse-events.y | 38

Re: [PATCH] drm/i915: fix task reference leak in i915_debugfs.c

On Fri, 25 Sep 2015, Geliang Tang wrote: > Leak a task reference in i915_ppgtt_info(), add put_task_struct() > to fix it. Introduced by commit 1c60fef535d143860d5bf6593e24ab6417f5227c Author: Ben Widawsky Date: Fri Dec 6 14:11:30 2013 -0800

Re: [PATCH v9 00/18] Add VT-d Posted-Interrupts support - including prerequisite series

On 25/09/2015 03:49, Wu, Feng wrote: > Hi Paolo, > > Thanks for your review on this series! I'd like to confirm this series (plus > the patch fixing the compilation error) is okay to you and I don't need to > do extra things for it, right? Yes, can you check if branch vtd-pi of

[PATCH] watchdog: perform all-CPU backtrace in case of hard lockup

From: Jiri Kosina In many cases of hardlockup reports, it's actually not possible to know why it triggered, because the CPU that got stuck is usually waiting on a resource (with IRQs disabled) in posession of some other CPU is holding. IOW, we are often looking at the

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