[tip:sched/urgent] sched/core: Fix sched_rt_global_validate

Commit-ID: e9e7cb38c21c80c82af4b16608bb4c8c5ec6a28e Gitweb: http://git.kernel.org/tip/e9e7cb38c21c80c82af4b16608bb4c8c5ec6a28e Author: Juri Lelli AuthorDate: Tue, 11 Feb 2014 09:24:26 +0100 Committer: Thomas Gleixner CommitDate: Fri, 21 Feb 2014 21:27:10 +0100 sched/core: Fix sched_rt_

[tip:sched/urgent] sched/core: Make dl_b->lock IRQ safe

Commit-ID: 495163420ab5398c84af96ca3eae2c6aa4a140da Gitweb: http://git.kernel.org/tip/495163420ab5398c84af96ca3eae2c6aa4a140da Author: Juri Lelli AuthorDate: Tue, 11 Feb 2014 09:24:27 +0100 Committer: Thomas Gleixner CommitDate: Fri, 21 Feb 2014 21:27:10 +0100 sched/core: Make dl_b->lo

[tip:sched/urgent] sched/deadline: Fix bad accounting of nr_running

Commit-ID: 3d5f35bdfdef5fd627afe9b4bf9c4f32d17f4593 Gitweb: http://git.kernel.org/tip/3d5f35bdfdef5fd627afe9b4bf9c4f32d17f4593 Author: Juri Lelli AuthorDate: Thu, 20 Feb 2014 09:19:39 +0100 Committer: Thomas Gleixner CommitDate: Fri, 21 Feb 2014 21:27:09 +0100 sched/deadline: Fix bad a

Re: [PATCH] x86, kaslr: add missed "static" declarations

On Sun, Feb 9, 2014 at 1:56 PM, Kees Cook wrote: > This silences build warnings about unexported variables and functions. > > Signed-off-by: Kees Cook > --- > arch/x86/boot/compressed/aslr.c |9 + > 1 file changed, 5 insertions(+), 4 deletions(-) > > diff --git a/arch/x86/boot/compre

Re: [PATCH] Android / binder: Fix broken walk in binder_node_release()

On Thu, Feb 20, 2014 at 02:22:53PM +0100, Compostella, Jeremy wrote: > From: "Compostella, Jeremy" > > This bug can manifest itself in several situations, here is the one that made > me > hunt it last week: > > When an Android device is encrypted, Android starts all the init services of > core

Re: [PATCH] mtd: nand: MTD_NAND_SH_FLCTL should depend on HAS_DMA

Hi Geert, Thank you for the patch. On Friday 21 February 2014 20:54:34 Geert Uytterhoeven wrote: > If NO_DMA=y: > > drivers/built-in.o: In function `flctl_dma_fifo0_transfer': > sh_flctl.c:(.text+0x210398): undefined reference to `dma_map_single' > sh_flctl.c:(.text+0x2104b0): undefi

Re: + makefile-fix-build-with-make-380-again.patch added to -mm tree

On Fri, Feb 21, 2014 at 12:19 PM, Andrew Morton wrote: > On Fri, 21 Feb 2014 12:09:51 -0800 Kees Cook wrote: > >> >> This appears to be missing the: >> >> -else ifdef CONFIG_CC_STACKPROTECTOR_STRONG >> +else >> +ifdef CONFIG_CC_STACKPROTECTOR_STRONG >> >> chunk? > > Yup, already fixed after my ke

Re: [PATCH 1/2] mmc: host: MMC_SH_MMCIF should depend on HAS_DMA

Hi Geert, Thank you for the patches. On Friday 21 February 2014 20:52:50 Geert Uytterhoeven wrote: > If NO_DMA=y: > > drivers/built-in.o: In function `sh_mmcif_start_dma_tx': > sh_mmcif.c:(.text+0x5a3286): undefined reference to `dma_map_sg' > drivers/built-in.o: In function `sh_mmci

Re: [PATCH v2] x86, kaslr: export offset in VMCOREINFO ELF notes

On Thu, Jan 23, 2014 at 9:31 AM, Kees Cook wrote: > From: Eugene Surovegin > > Include kASLR offset in VMCOREINFO ELF notes to assist in debugging. > > Signed-off-by: Eugene Surovegin > Signed-off-by: Kees Cook > --- > v2: > - make sure "From:" got sent correctly > --- > arch/x86/kernel/machi

perf_fuzzer causes reboot

So I'm not sure who exactly to report this to. Some perf people CC'd as I trigger it while using the perf_fuzzer. This is with 3.14-rc3 on a core2 machine, although I've had the reboots happen throughout at least 3.14-rc* I'm having a hard time coming up with a reproducible test case. Using t

[PATCH 3.14] mwifiex: rename usb driver name registerring to usb core

Both libertas USB driver and mwifiex_usb driver are registerring with name 'usb8xxx'. The following conflict happens while trying to load both drivers. [6.211307] Error: Driver 'usb8xxx' is already registered... [6.217261] mwifiex_usb: Driver register failed! Fix it by renaming mwifiex_usb driver

Re: [RFC][PATCH 0/5] arch: atomic rework

On Fri, Feb 21, 2014 at 11:43 AM, Peter Sewell wrote: > > You have to track dependencies through other assignments, e.g. simple x=y That is all visible in the SSA form. Variable assignment has been converted to some use of the SSA node that generated the value. The use might be a phi node or a ca

[PATCH] x86, kaslr: randomize module base load address

From: Andy Honig Randomize the load address of modules in the kernel to make kASLR effective for modules. Modules can only be loaded within a particular range of virtual address space. This patch adds 10 bits of entropy to the load address by adding 1-1024 * PAGE_SIZE to the beginning range whe

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

On Fri, Feb 21, 2014 at 09:48:46AM -0500, Josh Boyer wrote: > On Thu, Feb 20, 2014 at 6:52 PM, Greg Kroah-Hartman > wrote: > > 3.13-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Hannes Reinecke > > > > commit d8a5dc3033af2fd6d1603

Re: + makefile-fix-build-with-make-380-again.patch added to -mm tree

On Fri, 21 Feb 2014 12:09:51 -0800 Kees Cook wrote: > > This appears to be missing the: > > -else ifdef CONFIG_CC_STACKPROTECTOR_STRONG > +else > +ifdef CONFIG_CC_STACKPROTECTOR_STRONG > > chunk? Yup, already fixed after my kernel wouldn't compile ;) It conflicted with makefile-fix-extra-par

RE: [mwifiex/USB8897] Error: Driver 'usb8xxx' is already registered, aborting...

Hi Fengguang, > Greetings, > > I got the below dmesg and the first bad commit is > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > commit 68458dede7e0055198318dcb0318df3b4f419507 > CommitDate: Mon Jan 13 14:46:59 2014 -0500 > > mwifiex: add USB8897 support > > [

Re: progress, marching to the rear

On 02/20/2014 08:13 PM, Gene Heskett wrote: > I finally found a keyboard I can use when the boots fails to the > initramfs: prompt. ps2 plug on it. > > From the messages it leaves on screen, it is NOT finding the drive plugged > into the mobo SATA1 connector when I try to boot to a 3.13.1-2-3 ke

Re: [PATCH] fs, kernel: Support disabling the uselib syscall

On Fri, 21 Feb 2014 10:11:06 -0800 Josh Triplett wrote: > uselib hasn't been used since libc5; glibc does not use it. Support > turning it off. > > When disabled, also omit the load_elf_library implementation from > binfmt_elf.c, which only uselib invokes. > > bloat-o-meter: > add/remove: 0/4

Re: x86_pmu_start WARN_ON.

On Fri, 21 Feb 2014, Peter Zijlstra wrote: > group_sched_in() that fails (for whatever reason), and without x86_pmu > TXN support (because the leader is !x86_pmu), will corrupt the n_added > state. > > If this all is correct; the below ought to cure things. I've applied the patch and have been u

Intel microcode extended signature table support in Linux/BITS

I am directing this question to you hoping one of you can either address it directly, or forward it internally at Intel. We have code in the Linux kernel to support microcode extended signature tables which has never been tested as far as I know, as there are no public test vectors of microcode up

[PATCH] kallsyms: fix absolute addresses for kASLR

From: Andy Honig Currently symbols that are absolute addresses are incorrectly displayed in /proc/kallsyms if the kernel is loaded with kASLR. The problem was that the scripts/kallsyms.c file which generates the array of symbol names and addresses uses an relocatable value for all symbols, even

Re: + makefile-fix-build-with-make-380-again.patch added to -mm tree

On Fri, Feb 21, 2014 at 12:07 PM, wrote: > Subject: + makefile-fix-build-with-make-380-again.patch added to -mm tree > To: > jbeul...@suse.com,jbeul...@suse.com,keesc...@chromium.org,mi...@kernel.org,mma...@suse.cz > From: a...@linux-foundation.org > Date: Fri, 21 Feb 2014 12:07:52 -0800 > > > T

Re: [PATCH 3.11 085/121] tty: Set correct tty name in 'active' sysfs attribute

Hi On Fri, Feb 21, 2014 at 3:46 PM, Josh Boyer wrote: > On Fri, Feb 21, 2014 at 9:37 AM, Ray Strode wrote: >> Hi, >> >> This broke plymouth, i think. Plymouth used the herustic: >> "/sys/class/tty/console/active contains something other than tty0" to >> mean "probably has serial consoles, force

Re: [BISECTED] Xen HVM guest hangs since 3.12-rc5

On Thu, Feb 20, 2014 at 12:44:15PM -0800, Steven Noonan wrote: > On Wed, Feb 19, 2014 at 1:01 PM, Steven Noonan wrote: > > On Wed, Feb 19, 2014 at 9:41 AM, Konrad Rzeszutek Wilk > > wrote: > >> On Tue, Feb 18, 2014 at 11:16:05PM -0800, Steven Noonan wrote: > >>> I've been running into problems on

Re: [PATCHv2 1/8] ARM: at91: Add at91sam9rl DT SoC support

Hi Mark, On 20/02/2014 at 10:12:32 +0100, Nicolas Ferre wrote : > NAK. Either this is a atmel,at91rm9200-pinctrl node or a simple-bus. Not > both; that doesn't make any sense. > > >>> Simply a copy paste, I'll fix that here and also the 6 other atmel > >>> dtsi includes. > >>> > >>>

[PATCH] [media] v4l: VIDEO_SH_VOU should depend on HAS_DMA

If NO_DMA=y: warning: (VIDEO_DM6446_CCDC && VIDEO_DM355_CCDC && VIDEO_DM365_ISIF && VIDEO_OMAP2_VOUT && VIDEO_SH_VOU && VIDEO_VIU && VIDEO_TIMBERDALE && VIDEO_MX1 && VIDEO_OMAP1) selects VIDEOBUF_DMA_CONTIG which has unmet direct dependencies (MEDIA_SUPPORT && HAS_DMA) drivers/built-in

[PATCH] fbdev: FB_OPENCORES should depend on HAS_DMA

If NO_DMA=y: drivers/built-in.o: In function `ocfb_remove': ocfb.c:(.text+0x27fee): undefined reference to `dma_free_coherent' drivers/built-in.o: In function `ocfb_probe': ocfb.c:(.text+0x28418): undefined reference to `dma_alloc_coherent' ocfb.c:(.text+0x284d2): undefined ref

[PATCH] mtd: nand: MTD_NAND_SH_FLCTL should depend on HAS_DMA

If NO_DMA=y: drivers/built-in.o: In function `flctl_dma_fifo0_transfer': sh_flctl.c:(.text+0x210398): undefined reference to `dma_map_single' sh_flctl.c:(.text+0x2104b0): undefined reference to `dma_unmap_single' Signed-off-by: Geert Uytterhoeven --- drivers/mtd/nand/Kconfig |1

[PATCH 2/2] mmc: host: MMC_OMAP_HS should depend on HAS_DMA

If NO_DMA=y: drivers/built-in.o: In function `omap_hsmmc_pre_dma_transfer': omap_hsmmc.c:(.text+0x5a0928): undefined reference to `dma_map_sg' drivers/built-in.o: In function `omap_hsmmc_dma_cleanup': omap_hsmmc.c:(.text+0x5a0e8e): undefined reference to `dma_unmap_sg' drivers/

[PATCH 1/2] mmc: host: MMC_SH_MMCIF should depend on HAS_DMA

If NO_DMA=y: drivers/built-in.o: In function `sh_mmcif_start_dma_tx': sh_mmcif.c:(.text+0x5a3286): undefined reference to `dma_map_sg' drivers/built-in.o: In function `sh_mmcif_start_dma_rx': sh_mmcif.c:(.text+0x5a33fc): undefined reference to `dma_map_sg' drivers/built-in.o: I

[PATCHv3 1/9] ARM: at91: prepare at91sam9rl DT transition

Add the new names, coming from DT, for the clock lookups. Signed-off-by: Alexandre Belloni --- arch/arm/mach-at91/at91sam9rl.c | 16 1 file changed, 16 insertions(+) diff --git a/arch/arm/mach-at91/at91sam9rl.c b/arch/arm/mach-at91/at91sam9rl.c index 3651517abedf..d6ee8bb47213

Re: [PATCH] rapidio/tsi721: fix tasklet termination in dma channel release

On Fri, 21 Feb 2014, Alexandre Bounine wrote: > This patch is a modification of the patch originally proposed > by Xiaotian Feng : https://lkml.org/lkml/2012/11/5/413 > This new version disables DMA channel interrupts and ensures that the tasklet > wil not be scheduled again before calling tasklet_

[PATCHv3 5/9] ARM: at91: prepare sam9 dt boards transition to common clk

From: Boris BREZILLON This patch prepare the transition to common clk for sam9 dt boards by replacing the timer init callback. Clocks registration cannot be done in early init callback (as formerly done by the old clk implementation) because it requires dynamic allocation which is not ready yet

[PATCHv3 6/9] ARM: at91: prepare common clk transition for sam9rl SoCs

This patch encloses sam9rl old clk registration in #if defined(CONFIG_OLD_CLK_AT91)/#endif sections. Signed-off-by: Alexandre Belloni --- arch/arm/mach-at91/at91sam9rl.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-at91/at91sam9rl.c b/arch/arm/mach-at91

[PATCHv3 4/9] ARM: at91: dt: sam9rl: Device Tree for the at91sam9rlek

Add a device tree for the at91sam9rl-ek. For now it supports: - MMC - dbgu - usart1 - watchdog - nand - leds - buttons Signed-off-by: Alexandre Belloni --- arch/arm/boot/dts/Makefile | 2 + arch/arm/boot/dts/at91sam9rlek.dts | 151 + 2 files c

[PATCHv3 9/9] ARM: at91: switch sam9rl to common clock framework

Signed-off-by: Alexandre Belloni --- arch/arm/mach-at91/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm/mach-at91/Kconfig b/arch/arm/mach-at91/Kconfig index 4f0e800e7e71..7013b7b66a1e 100644 --- a/arch/arm/mach-at91/Kconfig +++ b/arch/arm/mach-at91/Kconfig @@ -137,7 +137,6 @@

[PATCHv3 7/9] ARM: at91/dt: define at91sam9rl clocks

Define at91sam9rl clocks in at91sam9rl dtsi file. Signed-off-by: Alexandre Belloni --- arch/arm/boot/dts/at91sam9rl.dtsi | 231 +- 1 file changed, 229 insertions(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/at91sam9rl.dtsi b/arch/arm/boot/dts/at91sam9rl

[PATCH] usb: musb: USB_MUSB_DUAL_ROLE/USB_MUSB_GADGET should depend on HAS_DMA

If NO_DMA=y: drivers/built-in.o: In function `txstate': musb_gadget.c:(.text+0x35955a): undefined reference to `dma_unmap_single' musb_gadget.c:(.text+0x35957e): undefined reference to `dma_sync_single_for_cpu' drivers/built-in.o: In function `musb_g_giveback': (.text+0x359672

[PATCHv3 8/9] ARM: at91/dt: define main clk frequency of at91sam9rlek

Define the main clock frequency for the new main clock node in at91sam9rlek.dts Signed-off-by: Alexandre Belloni --- arch/arm/boot/dts/at91sam9rlek.dts | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/at91sam9rlek.dts b/arch/arm/boot/dts/at91sam9rlek.dts index 0451013

[PATCHv3 3/9] ARM: at91/defconfig: Add the sam9rl to the list of DT-enabled SOCs

at91sam9rl now has a device tree, add it to the at91_dt_defconfig. Signed-off-by: Alexandre Belloni --- arch/arm/configs/at91_dt_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/at91_dt_defconfig b/arch/arm/configs/at91_dt_defconfig index 0b4e9b5210d8..d0bddb699865

[PATCHv3 0/9] Device tree support for the at91sam9rlek

This series adds DT support for the at91sam9rl SoC, then the at91sam9rl-ek evaluation board. While the at91sam9rl dtsi should be almost complete (still missing LCD and touchscreen bits). The at91sam9rlek DT now support the following tested features: - MMC - dbgu - usart1 - watchdog - nand -

[PATCHv3 2/9] ARM: at91: Add at91sam9rl DT SoC support

This adds preliminary DT support for the at91sam9rl. Signed-off-by: Alexandre Belloni --- arch/arm/boot/dts/at91sam9rl.dtsi | 622 ++ 1 file changed, 622 insertions(+) create mode 100644 arch/arm/boot/dts/at91sam9rl.dtsi diff --git a/arch/arm/boot/dts/at91sa

Re: [RFC][PATCH 0/5] arch: atomic rework

On 21 February 2014 19:41, Linus Torvalds wrote: > On Fri, Feb 21, 2014 at 11:16 AM, Linus Torvalds > wrote: >> >> Why would this be any different, especially since it's easy to >> understand both for a human and a compiler? > > Btw, the actual data path may actually be semantically meaningful ev

[PATCH 2/3] regmap: Add API call apply but not register a patch file

This patch provides a new regmap API call that allows a patch to be applied but not registered with the regmap core. Common code between this and the existing regmap_register_patch function is factored out to reduce duplication. This can be helpful when devices have more complex boot proceedures a

[PATCH 3/3] mfd: arizona: Use new regmap features for manual register patch

On the wm5102 the register patches are applied manually, rather than by the regmap core. This application is wrapped in calls to regcache_cache_bypass. However, this is dangerous as other threads may be accessing the hardware at the same time as the pm_runtime operations and if they do so during th

[PATCH 1/3] regmap: Check stride of register patch as we register it

Currently, we check the registers in the patch are aligned to the register stride everytime we sync the cache and the first time the patch is written out is unchecked. This patch checks the register patch when we first register it so the first writes are no longer unchecked and then doesn't check

[GIT PULL REQUEST] watchdog - v3.14-rc4 Fixes

Hi Linus, Please pull from 'master' branch of git://www.linux-watchdog.org/linux-watchdog.git It corrects the error code when no device was found for w83697hf_wdt. This will update the following files: w83697hf_wdt.c |2 +- 1 files changed, 1 insertion(+), 1 deletion(-) with these

Re: [RFC][PATCH 0/5] arch: atomic rework

On Fri, Feb 21, 2014 at 11:16 AM, Linus Torvalds wrote: > > Why would this be any different, especially since it's easy to > understand both for a human and a compiler? Btw, the actual data path may actually be semantically meaningful even at a processor level. For example, let's look at that gc

[PATCH RFC 2/2] net: macb: DMA-unmap full rx-buffer

When allocating RX buffers a fixed size is used, while freeing is based on actually received bytes, resulting in the following kernel warning when CONFIG_DMA_API_DEBUG is enabled: WARNING: CPU: 0 PID: 0 at lib/dma-debug.c:1051 check_unmap+0x258/0x894() macb e000b000.ethernet: DMA-API: device driv

[PATCH RFC 1/2] net: macb: Check DMA mappings for error

With CONFIG_DMA_API_DEBUG enabled the following warning is printed: WARNING: CPU: 0 PID: 619 at lib/dma-debug.c:1101 check_unmap+0x758/0x894() macb e000b000.ethernet: DMA-API: device driver failed to check map error[device address=0x2d171c02] [size=322 bytes] [mapped as single] Modules

[PATCH RFC 0/2] net: macb: Fixing DMA usage

Hi, when I enabled CONFIG_DMA_API_DEBUG recently, I started seeing warnings caused by the macb's DMA usage. I read trough Documentation/DMA-API_HOWTO.txt and tried solving these to the best of my knowledge of the networking and DMA systems. But that knowledge is not very deep. So, there might be f

[PATCH] rapidio/tsi721: fix tasklet termination in dma channel release

This patch is a modification of the patch originally proposed by Xiaotian Feng : https://lkml.org/lkml/2012/11/5/413 This new version disables DMA channel interrupts and ensures that the tasklet wil not be scheduled again before calling tasklet_kill(). Unfortunately the updated patch was not rele

Re: [RFC][PATCH 0/5] arch: atomic rework

On Fri, Feb 21, 2014 at 06:28:05PM +, Peter Sewell wrote: > On 20 February 2014 17:01, Linus Torvalds >wrote: [ . . . ] > > > So, if you make one of two changes to your example, then I will agree > > > with you. > > > > No. We're not playing games here. I'm fed up with complex examples > > t

Re: [PATCH 1/3] x86/hash: fix build failure with older binutils

On 02/21/2014 06:16 AM, Jan Beulich wrote: On 21.02.14 at 13:51, "H. Peter Anvin" wrote: >> How old? > > 2.16.91.0.5 (SLE10) > I would *love* to kill off binutils 2.16. It was a horribly buggy version, and it has been hard to deal with keeping things alive with it. How important is this?

Re: [RFC][PATCH 0/5] arch: atomic rework

On Fri, Feb 21, 2014 at 10:25 AM, Peter Sewell wrote: > > If one thinks this is too fragile, then simply using memory_order_acquire > and paying the resulting barrier cost (and perhaps hoping that compilers > will eventually be able to optimise some cases of those barriers to > hardware-level depe

Re: [RFC][PATCH 0/5] arch: atomic rework

On Fri, Feb 21, 2014 at 07:35:37PM +0100, Michael Matz wrote: > Hi, > > On Thu, 20 Feb 2014, Linus Torvalds wrote: > > > But I'm pretty sure that any compiler guy must *hate* that current odd > > dependency-generation part, and if I was a gcc person, seeing that > > bugzilla entry Torvald pointed

Re: [tip:x86/asmlinkage] lto: Handle LTO common symbols in module loader

On 02/20/2014 03:11 PM, Rusty Russell wrote: > tip-bot for Joe Mario writes: >> Commit-ID: 80375980f1608f43b47abc2671456b23ec68c434 >> Gitweb: >> http://git.kernel.org/tip/80375980f1608f43b47abc2671456b23ec68c434 >> Author: Joe Mario >> AuthorDate: Sat, 8 Feb 2014 09:01:09 +0100 >> Comm

Re: [PATCH 4/4] hugetlb: add hugepages_node= command-line option

On Fri, Feb 21, 2014 at 02:07:08AM -0800, David Rientjes wrote: > On Thu, 20 Feb 2014, Marcelo Tosatti wrote: > > > > 1GB is of such granularity that you'd typically either be (a) oom so that > > > your userspace couldn't even start, or (b) have enough memory such that > > > userspace would be a

Re: [PATCH] phy: restrict Samsung S5P/Exynos drivers to the respective architectures

On Fri, Feb 21, 2014 at 04:55:51PM +0100, Sylwester Nawrocki wrote: > Hi, > > On 21/02/14 15:05, Uwe Kleine-König wrote: > > Enabling these drivers on platforms not created by Samsung is useless > > unless you're doing compile tests. So don't offer the users to enable > > them without COMPILE_TEST

Re: [PATCH v2] xen-pciback: Use pci_enable_msix_exact() instead of pci_enable_msix()

On 02/21/2014 01:58 PM, Alexander Gordeev wrote: On Fri, Feb 21, 2014 at 01:33:34PM -0500, Boris Ostrovsky wrote: Reviewed-by: Boris Ostrovsky Thank you, Boris! Whom should I ask this patch for inclusion? This should go into the Xen tree. Konrad is usually the one putting together pull req

Re: [Patch v6 1/2] dmaengine: qcom_bam_dma: Add device tree binding

On Fri, Feb 21, 2014 at 05:36:47PM +, Mark Rutland wrote: [snip] > > > > Yes only a single interrupt. I can remove the s. > > Please don't, the interrupts proeprty is standard and shouldn't change. > > I was only asking to ensure that all interrupts were described in the > binding, which th

Re: SPDX-License-Identifier

On Fri, Feb 21, 2014 at 09:57:20AM -0800, Greg Kroah-Hartman wrote: > > But shouldn't we at least write somewhere > > that it has connection to spdx.org where you can find out that licenses. > > Why? Are these licenses so unknown that no one knows what they are? > And, as part of the kernel-as-a-

Re: [PATCH 3.10 00/66] 3.10.32-stable review

On Thu, Feb 20, 2014 at 09:09:48PM -0800, Guenter Roeck wrote: > On 02/20/2014 03:50 PM, Greg Kroah-Hartman wrote: > >This is the start of the stable review cycle for the 3.10.32 release. > >There are 66 patches in this series, all will be posted as a response > >to this one. If anyone has any iss

Re: [PATCH v2] xen-pciback: Use pci_enable_msix_exact() instead of pci_enable_msix()

On Fri, Feb 21, 2014 at 01:33:34PM -0500, Boris Ostrovsky wrote: > Reviewed-by: Boris Ostrovsky Thank you, Boris! Whom should I ask this patch for inclusion? -- Regards, Alexander Gordeev agord...@redhat.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

Re: [PATCH v7 5/8] ARM: dts: sun7i: Add support for mmc

On Tue, Feb 18, 2014 at 04:10:38PM +0100, Hans de Goede wrote: > Hi, > > On 02/18/2014 03:22 PM, Maxime Ripard wrote: > >On Mon, Feb 17, 2014 at 11:02:41AM +0100, David Lanzendörfer wrote: > >>Signed-off-by: David Lanzendörfer > >>Signed-off-by: Hans de Goede > >>--- > >> arch/arm/boot/dts/sun7

Re: [PATCH v2] kvm: Use pci_enable_msix_exact() instead of pci_enable_msix()

On Fri, Feb 21, 2014 at 06:11:29PM +0100, Paolo Bonzini wrote: > It's okay, but it's not clear to me whether I should include this > patch or someone else will. :) Please, include it. Thanks! > Paolo -- Regards, Alexander Gordeev agord...@redhat.com -- To unsubscribe from this list: send the l

Re: [RFC][PATCH 4/4] perf/events: Use helper functions in event assignment to shrink macro size

On Wed, 12 Feb 2014 20:58:27 +0100 Peter Zijlstra wrote: > > +void *perf_trace_event_setup(struct ftrace_event_call *event_call, > > +struct perf_trace_event *pe) > > +{ > > + pe->head = this_cpu_ptr(event_call->perf_events); > > + if (pe->constant && hlist_empty(pe->

Re: [RFC][PATCH 0/5] arch: atomic rework

Hi, On Thu, 20 Feb 2014, Linus Torvalds wrote: > But I'm pretty sure that any compiler guy must *hate* that current odd > dependency-generation part, and if I was a gcc person, seeing that > bugzilla entry Torvald pointed at, I would personally want to > dismember somebody with a rusty spoon.. Y

Re: [PATCH v2] xen-pciback: Use pci_enable_msix_exact() instead of pci_enable_msix()

On 02/21/2014 11:53 AM, Alexander Gordeev wrote: As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_r

Re: [PATCH v5 2/5] ACPI / processor_core: Rework _PDC related stuff to make it more arch-independent

Hi Rafael, On Wed, Feb 19, 2014 at 01:50:22AM +0100, Rafael J. Wysocki wrote: > On Wednesday, February 19, 2014 12:23:55 AM Hanjun Guo wrote: > > _PDC related stuff in processor_core.c is little bit X86/IA64 dependent, > > rework the code to make it more arch-independent, no functional change > >

Re: [PATCH] mm: per-thread vma caching

On Thu, Feb 20, 2014 at 9:28 PM, Davidlohr Bueso wrote: > From: Davidlohr Bueso > > This patch is a continuation of efforts trying to optimize find_vma(), > avoiding potentially expensive rbtree walks to locate a vma upon faults. Ok, so I like this one much better than the previous version. How

[RFC 1/1] fs: Quota: Refresh Kconfig

Update Kconfig with a complete list of supported filesystems. (Other local filesystems concerned by quota and/or journaled quotas ?) --- fs/quota/Kconfig | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/fs/quota/Kconfig b/fs/quota/Kconfig index 880fd98..7339003 100644 -

Re: [PATCH 7/7] pid: get pid_t ppid of task in init_pid_ns

On 14/02/20, Oleg Nesterov wrote: > On 01/23, Richard Guy Briggs wrote: > > > > Added the functions task_ppid_nr_ns() and task_ppid_nr() to abstract the > > lookup > > of the PPID (real_parent's pid_t) of a process, including rcu locking, in > > the > > arbitrary and init_pid_ns. > > This provide

[PATCH] fs, kernel: Support disabling the uselib syscall

uselib hasn't been used since libc5; glibc does not use it. Support turning it off. When disabled, also omit the load_elf_library implementation from binfmt_elf.c, which only uselib invokes. bloat-o-meter: add/remove: 0/4 grow/shrink: 0/1 up/down: 0/-785 (-785) function

Re: [PATCH v4 3/3] KVM: x86: Enable Intel MPX for guest

Il 21/02/2014 18:57, Liu, Jinsong ha scritto: - F(BMI2) | F(ERMS) | f_invpcid | F(RTM) | F(RDSEED) | + F(BMI2) | F(ERMS) | f_invpcid | F(RTM) | F(MPX) | F(RDSEED) | F(ADX); MPX also needs to be conditional on mpx_supported here, like it is done with

[RFC patch 0/5] hrtimers: Add deferrable mode

Deferrable timers are beneficial for power saving. They behave like standard timers except that their expiry can be delayed up to the expiry of the next non deferred timer. That prevents them from waking up cpus from deep idle periods. Right now deferrable timers are only available in the timer wh

RE: [PATCH v3 0/4] X86/KVM: enable Intel MPX for KVM

Paolo Bonzini wrote: > Il 22/01/2014 13:03, Paolo Bonzini ha scritto: >> Il 22/01/2014 06:29, Liu, Jinsong ha scritto: >>> These patches are version 3 to enalbe Intel MPX for KVM. >>> >>> Version 1: >>> * Add some Intel MPX definiation >>> * Fix a cpuid(0x0d, 0) exposing bug, dynamic per XCR0

Re: [PATCH 0/4] x86: Fix ftrace recovery when code modification failed

On Fri, 21 Feb 2014 17:33:52 +0100 Petr Mládek wrote: > Yes, it works but I would still do few more changes: > > + run_sync() also in ftrace_modify_code() in the recovery >part; I would solve this by moving the "out" label. Sounds good. > > + print some warning in update_ft

Re: [PATCH v2 2/2] phy: Select PHY_EXYNOS_DP_VIDEO by default for ARCH_EXYNOS

On Friday 21 February 2014 17:50:44 Sylwester Nawrocki wrote: > On 21/02/14 17:41, Arnd Bergmann wrote: > > On Friday 21 February 2014 17:25:04 Sylwester Nawrocki wrote: > >> > > >> > Hmm, good point, I will modify it that way. > >> > > >> > For patch 1/2 I guess it should be: > >> > > >> > "def

[RFC patch 5/5] timerfd: Expose deferrable mode to user space

Expose the deferrable timer mode to user space by adding a new TDF_TIMER_DEFERRABLE flag. The deferrable mode is available through the syscall timerfd_settime() by handing in TDF_TIMER_IS_DEFERRABLE via the 'flags' argument. TFD_TIMER_IS_DEFERRABLE and the other TFD_TIMER_ flags can be ored togeth

[PATCH v4 2/3] KVM: x86: add MSR_IA32_BNDCFGS to msrs_to_save

>From 7d1b41c3fdf71e4c73280e117948102f54f74be7 Mon Sep 17 00:00:00 2001 From: Liu Jinsong Date: Sat, 22 Feb 2014 08:10:17 +0800 Subject: [PATCH v4 2/3] KVM: x86: add MSR_IA32_BNDCFGS to msrs_to_save Add MSR_IA32_BNDCFGS to msrs_to_save, and corresponding logic to kvm_get/set_msr(). Signed-off-by

[PATCH v4 3/3] KVM: x86: Enable Intel MPX for guest

>From 8b3a3b1f08c166e0c2cdc6162e6fa95d9c7ad2ec Mon Sep 17 00:00:00 2001 From: Liu Jinsong Date: Sat, 22 Feb 2014 08:53:27 +0800 Subject: [PATCH v4 3/3] KVM: x86: Enable Intel MPX for guest This patch enable Intel MPX feature to guest. Signed-off-by: Xudong Hao Signed-off-by: Liu Jinsong --- a

[RFC patch 2/5] hrtimer: Make use of the active bases bitfield

Instead of looping through all bases, find the active ones via the cpu_base->active_bases bit field. Signed-off-by: Thomas Gleixner --- kernel/hrtimer.c | 33 + 1 file changed, 21 insertions(+), 12 deletions(-) Index: tip/kernel/hrtimer.c ==

[RFC patch 1/5] hrtimer: Always check for HRTIMER_MODE_REL

We have not just HRTIMER_MODE_REL and HRTIMER_MODE_ABS, so a direct check for mode == HRTIMER_MODE_ABS is not sufficient. Always check for the HRTIMER_MODE_REL bit. Signed-off-by: Thomas Gleixner --- kernel/hrtimer.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Index: tip/kerne

[RFC patch 4/5] posix-timers: Expose deferrable mode to user space

Expose the deferrable timer mode to user space by adding a new TIMER_IS_DEFERRABLE flag. The deferrable mode is available for the syscalls clock_nanosleep() and timer_settime(). For both syscalls TIMER_IS_DEFERRABLE is handed in via the 'flags' argument. TIMER_ABSTIME and TIMER_IS_DEFERRABLE can b

Re: SPDX-License-Identifier

On Fri, Feb 21, 2014 at 06:26:08PM +0100, Michal Simek wrote: > On 02/21/2014 05:56 PM, Greg Kroah-Hartman wrote: > > On Fri, Feb 21, 2014 at 10:20:45AM -0600, Felipe Balbi wrote: > >> Hi, > >> > >> On Fri, Feb 21, 2014 at 05:18:39PM +0100, Michal Simek wrote: > >>> On 02/21/2014 05:12 PM, Felipe B

[RFC patch 3/5] hrtimer: Add support for deferrable hrtimers

Deferrable timers have a relaxed expiry mode. The timers are not guaranteed to expire at the programmed expiry time. They are always batched with the expiry of non deferrrable timers. If the system goes idle non deferrable timers are not taken into account for the calculation of the next timer expi

[PATCH v4 1/3] KVM: x86: Intel MPX vmx and msr handle

>From eb56f19c14d5603209b22b97cd53ef1716bf2804 Mon Sep 17 00:00:00 2001 From: Liu Jinsong Date: Sat, 22 Feb 2014 07:53:32 +0800 Subject: [PATCH v4 1/3] KVM: x86: Intel MPX vmx and msr handle This patch handle vmx and msr of Intel MPX feature. Signed-off-by: Xudong Hao Signed-off-by: Liu Jinsong

[PATCH v4 0/3] KVM: x86: enable Intel MPX for KVM

These patches are version 4 to enable Intel MPX for KVM. Version 1: * Add some Intel MPX definiation * Fix a cpuid(0x0d, 0) exposing bug, dynamic per XCR0 features enable/disable * vmx and msr handle for MPX support at KVM * enalbe MPX feature for guest Version 2: * remove generic MPX

Re: [PATCH] ARM: bcm2835: Move to mach-bcm directory

On Fri, Feb 21, 2014 at 09:41:53AM -0800, Markus Mayer wrote: > On 21 February 2014 06:09, Matt Porter wrote: > > On Thu, Feb 20, 2014 at 09:53:56PM -0700, Stephen Warren wrote: > >> On 02/20/2014 05:16 PM, Markus Mayer wrote: > >> > Move the bcm2835 board file into the mach-bcm directory. This al

Re: [PATCH] ARM: bcm2835: Move to mach-bcm directory

On 02/21/2014 10:41 AM, Markus Mayer wrote: > On 21 February 2014 06:09, Matt Porter wrote: >> On Thu, Feb 20, 2014 at 09:53:56PM -0700, Stephen Warren wrote: >>> On 02/20/2014 05:16 PM, Markus Mayer wrote: Move the bcm2835 board file into the mach-bcm directory. This allows us to get ri

[GIT] Sparc

Please pull to get these three minor fixes from David Howells and Paul Gortmaker. Thanks! The following changes since commit e95003c3f9ccbfa7ab9d265e6eb703ee2fa4cfe7: Merge tag 'nfs-for-3.14-4' of git://git.linux-nfs.org/projects/trondmy/linux-nfs (2014-02-19 12:13:02 -0800) are available i

Re: [PATCH] ARM: bcm2835: Move to mach-bcm directory

On 21 February 2014 06:09, Matt Porter wrote: > On Thu, Feb 20, 2014 at 09:53:56PM -0700, Stephen Warren wrote: >> On 02/20/2014 05:16 PM, Markus Mayer wrote: >> > Move the bcm2835 board file into the mach-bcm directory. This allows us >> > to get rid of the mach-bcm2835 directory with the associa

[PATCH] KVM: x86: Fix xsave cpuid exposing bug

>From 00c920c96127d20d4c3bb790082700ae375c39a0 Mon Sep 17 00:00:00 2001 From: Liu Jinsong Date: Fri, 21 Feb 2014 23:47:18 +0800 Subject: [PATCH] KVM: x86: Fix xsave cpuid exposing bug EBX of cpuid(0xD, 0) is dynamic per XCR0 features enable/disable. Bit 63 of XCR0 is reserved for future expansion

Re: [Patch v6 1/2] dmaengine: qcom_bam_dma: Add device tree binding

On Fri, Feb 21, 2014 at 04:30:53PM +, Andy Gross wrote: > On Fri, Feb 21, 2014 at 09:26:57AM +, Mark Rutland wrote: > > On Fri, Feb 21, 2014 at 06:43:04AM +, Andy Gross wrote: > > > Add device tree binding support for the QCOM BAM DMA driver. > > > > [snip] > > > +Required properties:

[PATCH] KVM: x86: expose ADX feature to guest

>From 0750e335eb5860b0b483e217e8a08bd743cbba16 Mon Sep 17 00:00:00 2001 From: Liu Jinsong Date: Thu, 20 Feb 2014 17:39:32 +0800 Subject: [PATCH] KVM: x86: expose ADX feature to guest ADCX and ADOX instructions perform an unsigned addition with Carry flag and Overflow flag respectively. Signed-of

Re: [PATCH] ARM: EDMA: Use platform_get_resource functions for DT

On 02/21/2014 06:15 AM, Mark Rutland wrote: >> Also, while at it get rid of the assumption in the code that "CC" is at reg >> index 0 in the DT and xbar is at offset 1. Instead use reg-names to get the >> memory resource in concern keeping things much cleaner and simpler. This also >> makes it poss

[PATCH] KVM: x86: expose new instruction RDSEED to guest

>From 24ffdce9efebf13c6ed4882f714b2b57ef1141eb Mon Sep 17 00:00:00 2001 From: Liu Jinsong Date: Thu, 20 Feb 2014 17:38:26 +0800 Subject: [PATCH] KVM: x86: expose new instruction RDSEED to guest RDSEED instruction return a random number, which supplied by a cryptographically secure, deterministic

put_page on transparent huge page leaks?

Hi, I'm tracking a possible memory leak in iommu/amd. The driver uses this logic to fault a page in response to a PRI from a device: npages = get_user_pages(fault->state->task, fault->state->mm, fault->address, 1, write, 0, &page, NULL); if (npages == 1) put_pa

Re: [PATCH v4 3/3] qspinlock, x86: Add x86 specific optimization for 2 contending tasks

On Mon, Feb 17, 2014 at 03:41:24PM -0500, Waiman Long wrote: > + struct { > + u8 lock; /* Lock bit */ > + u8 wait; /* Waiting bit */ > + u16 qcode; /* Queue code */ > + }; 16 bit code would result in 14 bits for the CPU number,

<    1   2   3   4   5   6   7   8   >