[PATCH v2 03/23] openrisc: tlb miss handler optimizations

2017-02-03 Thread Stafford Horne
From: Stefan Kristiansson By slightly reorganizing the code, the number of registers used in the tlb miss handlers can be reduced by two, thus removing the need to save them to memory. Also, some dead and commented out code is removed. No functional change. Signed-off-by: Stefan Kristiansson

[PATCH v2 04/23] openrisc: head: use THREAD_SIZE instead of magic constant

2017-02-03 Thread Stafford Horne
From: Stefan Kristiansson The stack size was hard coded to 0x2000, use the standard THREAD_SIZE definition loaded from thread_info.h. Signed-off-by: Stefan Kristiansson [sho...@gmail.com: Added body to the commit message] Signed-off-by: Stafford Horne --- arch/openrisc/kernel/head.S | 4 +++-

[PATCH v2 01/23] openrisc: use SPARSE_IRQ

2017-02-03 Thread Stafford Horne
From: Jonas Bonn The sparse IRQ framework is preferred nowadays so switch over to it. Signed-off-by: Jonas Bonn Signed-off-by: Stafford Horne --- arch/openrisc/Kconfig| 1 + arch/openrisc/include/asm/Kbuild | 1 + 2 files changed, 2 insertions(+) diff --git a/arch/openrisc/Kconfi

[PATCH] shm: Fix unlikely() test of info->seals to test only for WRITE and GROW

2017-02-03 Thread Steven Rostedt (VMware)
From: "Steven Rostedt (VMware)" Running my likely/unlikely profiler, I discovered that the test in shmem_write_begin() that tests for info->seals as unlikely, is always incorrect. This is because shmem_get_inode() sets info->seals to have F_SEAL_SEAL set by default, and it is unlikely to be clear

Re: [PATCH v8 00/15] ACPI platform MSI support and its example mbigen

2017-02-03 Thread Marc Zyngier
On 03/02/17 15:35, Sinan Kaya wrote: > On 2/3/2017 10:11 AM, Marc Zyngier wrote: >> On 03/02/17 14:50, Sinan Kaya wrote: >>> On 1/18/2017 7:54 AM, Hanjun Guo wrote: From: Hanjun Guo With platform msi support landed in the kernel, and the introduction of IORT for GICv3 ITS (PCI

Re: [PATCH v8 00/15] ACPI platform MSI support and its example mbigen

2017-02-03 Thread Sinan Kaya
On 2/3/2017 10:49 AM, Marc Zyngier wrote: >> Patches 13-15 are specific for MBIGEN. 00-12 are for the base functionality. > Is that to support SMMUv3's own MSI generation? It would be helpful if > you explained why you want this code to be merged beforehand, > potentially without any in-tree user.

Re: [PATCH 13/17] net: stmmac: Implement NAPI for TX

2017-02-03 Thread Corentin Labbe
On Fri, Feb 03, 2017 at 10:15:30AM -0500, David Miller wrote: > From: Corentin Labbe > Date: Fri, 3 Feb 2017 14:41:45 +0100 > > > On Tue, Jan 31, 2017 at 11:12:25PM -0500, David Miller wrote: > >> From: Corentin Labbe > >> Date: Tue, 31 Jan 2017 10:11:48 +0100 > >> > >> > The stmmac driver run

Fail git pull --rebase when local merges present? (was: [ANNOUNCE] Git v2.11.1)

2017-02-03 Thread Stephen Bash
On Thu, Feb 2, 2017 at 6:05 PM, Junio C Hamano wrote: > * "git pull --rebase", when there is no new commits on our side since >we forked from the upstream, should be able to fast-forward without >invoking "git rebase", but it didn't. As someone who has to mentor new developers to Git at

Re: [PATCH V8 04/10] arm64: exception: handle Synchronous External Abort

2017-02-03 Thread James Morse
Hi Tyler, On 01/02/17 17:16, Tyler Baicar wrote: > SEA exceptions are often caused by an uncorrected hardware > error, and are handled when data abort and instruction abort > exception classes have specific values for their Fault Status > Code. > When SEA occurs, before killing the process, report

Re: [PATCH V8 05/10] acpi: apei: handle SEA notification type for ARMv8

2017-02-03 Thread James Morse
Hi Tyler, On 01/02/17 17:16, Tyler Baicar wrote: > ARM APEI extension proposal added SEA (Synchronous External Abort) > notification type for ARMv8. > Add a new GHES error source handling function for SEA. If an error > source's notification type is SEA, then this function can be registered > into

Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family

2017-02-03 Thread Mathieu Poirier
On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote: > This patch adds watchdog controller driver for ZTE's zx2967 family. > > Signed-off-by: Baoyou Xie > --- > drivers/watchdog/Kconfig | 10 ++ > drivers/watchdog/Makefile | 1 + > drivers/watchdog/zx2967_wdt.c | 285 > ++

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread kbuild test robot
Hi Hoeun, [auto build test ERROR on next-20170203] [also build test ERROR on v4.10-rc6] [cannot apply to linus/master linux/master v4.9-rc8 v4.9-rc7 v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH v2 3/4] phy: Add USB3 PHY support for Broadcom NSP SoC

2017-02-03 Thread Jon Mason
On Thu, Feb 2, 2017 at 1:48 AM, Rafał Miłecki wrote: > [Resending with fixed/complete Cc-s] > > On Tue, 17 Jan 2017 11:14:29 -0500, Yendapally Reddy Dhananjaya Reddy > wrote:> This patch adds support for Broadcom > NSP USB3 PHY >> >> Signed-off-by: Yendapally Reddy Dhananjaya Reddy >> > > Seriou

Re: [PATCH v9 4/4] console: Make persistent scrollback a boot parameter

2017-02-03 Thread Manuel Schölling
Hi Paul, On Thu, 2017-02-02 at 15:07 -0500, Paul Gortmaker wrote: > On Tue, Jan 10, 2017 at 4:28 PM, Manuel Schölling > wrote: > > The impact of the persistent scrollback feature on the code size is > > rather small, so the config option is removed. The feature stays > > disabled by default and c

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread Ard Biesheuvel
On 31 January 2017 at 15:14, David Howells wrote: > Print the secure boot status in the x86 setup_arch() but otherwise do > nothing more for now. More functionality will be added later, but this at > least allows for testing. > > Signed-off-by: David Howells > --- > > arch/x86/kernel/setup.c |

Re: [PATCH 03/10] iommu: Introduce new 'struct iommu_device'

2017-02-03 Thread kbuild test robot
Hi Joerg, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc6] [cannot apply to iommu/next next-20170203] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Joerg-Roedel/Let

Re: [RFC v4 00/10] Provide the EL1 physical timer to the VM

2017-02-03 Thread Marc Zyngier
On 03/02/17 15:19, Jintack Lim wrote: > The ARM architecture defines the EL1 physical timer and the virtual timer, > and it is reasonable for an OS to expect to be able to access both. > However, the current KVM implementation does not provide the EL1 physical > timer to VMs but terminates VMs on a

Re: [PATCH] [net-next] hns_enet: use cpumask_var_t for on-stack mask

2017-02-03 Thread David Miller
From: Arnd Bergmann Date: Thu, 2 Feb 2017 15:49:24 +0100 > On large SMP builds, we can run into a build warning: > > drivers/net/ethernet/hisilicon/hns/hns_enet.c: In function > 'hns_set_irq_affinity.isra.27': > drivers/net/ethernet/hisilicon/hns/hns_enet.c:1242:1: warning: the frame size > o

Re: [PATCH] arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling

2017-02-03 Thread Punit Agrawal
Tyler Baicar writes: > From: "Jonathan (Zhixiong) Zhang" > > Add VM_FAULT_HWPOISON[_LARGE] handling to the arm64 page fault > handler. Handling of VM_FAULT_HWPOISON[_LARGE] is very similar > to VM_FAULT_OOM, the only difference is that a different si_code > (BUS_MCEERR_AR) is passed to user spac

Re: [PATCH 3/6] genirq/affinity: update CPU affinity for CPU hotplug events

2017-02-03 Thread kbuild test robot
Hi Christoph, [auto build test ERROR on block/for-next] [also build test ERROR on v4.10-rc6] [cannot apply to next-20170203] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Christoph-Hellwig

Re: [PATCH v2 4/9] xen/pvh: Bootstrap PVH guest

2017-02-03 Thread Boris Ostrovsky
>> + >> +__HEAD >> + >> +/* Entry point for PVH guests. */ > Could you add some comments about register conetnts at entry? Reference to Xen's docs/misc/hvmlite.markdown would be sifficient? >> +gdt: >> +.word gdt_end - gdt >> +.long _pa(gdt) > This is a rather strange construc

[tip:WIP.sched/core 133/133] include/linux/wait.h:41:2: error: unknown type name 'spinlock_t'

2017-02-03 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.sched/core head: 9a631ea4bdc4d7a7faabc4a98d632f39573a9a8d commit: 9a631ea4bdc4d7a7faabc4a98d632f39573a9a8d [133/133] sched/headers: Split out of config: mips-bigsur_defconfig (attached as .config) compiler: mips64-linux-g

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread David Howells
Ard Biesheuvel wrote: > > + if (IS_ENABLED(CONFIG_EFI)) { > > Shouldn't this be a runtime check? Interesting question. The original patch I was working from had a #ifdef here. Possibly it doesn't need to be there at all. We could rely entirely on the value of boot_params.secure_boot.

Re: [PATCH v4 13/15] livepatch: change to a per-task consistency model

2017-02-03 Thread Miroslav Benes
On Thu, 2 Feb 2017, Petr Mladek wrote: > > diff --git a/Documentation/livepatch/livepatch.txt > > b/Documentation/livepatch/livepatch.txt > > index 7f04e13..fb00d66 100644 > > --- a/Documentation/livepatch/livepatch.txt > > +++ b/Documentation/livepatch/livepatch.txt > > > + In that case, arche

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread Ard Biesheuvel
On 3 February 2017 at 16:21, David Howells wrote: > Ard Biesheuvel wrote: > >> > + if (IS_ENABLED(CONFIG_EFI)) { >> >> Shouldn't this be a runtime check? > > Interesting question. The original patch I was working from had a #ifdef > here. Possibly it doesn't need to be there at all. We c

[PATCH] staging: bcm2835-audio: fix spacing of macro

2017-02-03 Thread Hendrik v. Raven
removes the unwanted spaces inside of sizeof( ), removing a complaint of checkpatch.pl. Also removes the second space behind the macro name. Signed-off-by: Hendrik v. Raven --- drivers/staging/bcm2835-audio/vc_vchi_audioserv_defs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --gi

two small PCI MSI cleanups

2017-02-03 Thread Christoph Hellwig
Remove an entirely dead function, and two small wrappers that are not useful except for making the callchain in the MSI setup code even harder to follow.

[PATCH 2/2] PCI/msi: remove pci_msi_domain_{alloc,free}_irqs

2017-02-03 Thread Christoph Hellwig
Just call the msi_* version directly instead of having trivial wrappers for one or two callsites. Signed-off-by: Christoph Hellwig --- arch/x86/kernel/apic/msi.c | 2 +- drivers/pci/msi.c | 30 ++ include/linux/msi.h| 3 --- 3 files changed, 3 inser

[PATCH 1/2] PCI/msi: remove unused function pci_msi_create_default_irq_domain

2017-02-03 Thread Christoph Hellwig
Signed-off-by: Christoph Hellwig --- drivers/pci/msi.c | 27 --- include/linux/msi.h | 3 --- 2 files changed, 30 deletions(-) diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c index 50c5003295ca..4f2996bd5c6a 100644 --- a/drivers/pci/msi.c +++ b/drivers/pci/msi.c @@

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread David Howells
Ard Biesheuvel wrote: > Yes, but only if you are booting via UEFI, no? Why limit it so? Even if you don't boot via UEFI, the bootloader/kexec can always set the secure-boot state on. > So perhaps use efi_enabled(EFI_BOOT) instead? I've no objection to that, given it incorporates a test of CON

Re: [PATCH] arm64: kconfig: allow support for memory failure handling

2017-02-03 Thread Punit Agrawal
Tyler Baicar writes: > From: "Jonathan (Zhixiong) Zhang" > > If ACPI_APEI and MEMORY_FAILURE is configured, select > ACPI_APEI_MEMORY_FAILURE. This enables memory failure recovery > when such memory failure is reported through ACPI APEI. APEI > (ACPI Platform Error Interfaces) provides a means f

Issues with FW with Intel 720 wifi card

2017-02-03 Thread Bharat Kumar Gogada
Hi, Im using linux 4.6 kernel, I get following error when I do interface up. Here is the boot log. [4.407681] iwlwifi :01:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [4.407742] iwlwifi :01:00.0: Detected Intel(R) Wireless N 7260, REV=0x144 [4.407831] iwlwifi 000

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread David Howells
David Howells wrote: > Ard Biesheuvel wrote: > > > Yes, but only if you are booting via UEFI, no? > > Why limit it so? Even if you don't boot via UEFI, the bootloader/kexec can > always set the secure-boot state on. > > > So perhaps use efi_enabled(EFI_BOOT) instead? > > I've no objection t

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread Ard Biesheuvel
On 3 February 2017 at 16:29, David Howells wrote: > David Howells wrote: > >> Ard Biesheuvel wrote: >> >> > Yes, but only if you are booting via UEFI, no? >> >> Why limit it so? Even if you don't boot via UEFI, the bootloader/kexec can >> always set the secure-boot state on. >> >> > So perhaps

Re: [PATCH v5 0/3] modversions: redefine kcrctab entries as 32-bit values

2017-02-03 Thread Linus Torvalds
On Fri, Feb 3, 2017 at 1:54 AM, Ard Biesheuvel wrote: > This v4 is a followup to [0] 'modversions: redefine kcrctab entries as > relative CRC pointers' [...] ok, I have this in a local branch now, assuming it passes my (admittedly fairly superficial) testing I'll merge it so that we can put this

Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.

2017-02-03 Thread Tony Lindgren
* Pavel Machek [170203 00:00]: > Hi! > > > On Fri, Jan 27, 2017 at 10:55:12PM +0100, Pavel Machek wrote: > > > Ok, I can try. But so far even -rc1 is a lot of fun. But... I consider > > > phone calls core feature of a phone. I'd very much like to get that to > > > work. Unfortunately, that means

Re: [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode

2017-02-03 Thread Linus Torvalds
On Fri, Feb 3, 2017 at 6:16 AM, Joseph Salisbury wrote: > On 02/02/2017 03:36 PM, Laura Abbott wrote: >> >> You might try https://marc.info/?l=linux-kernel&m=148553171703761 >> which fixed https://bugzilla.redhat.com/show_bug.cgi?id=1384238 > > This patch resolves the bug for multiple users. Than

Re: [PATCH v7 3/3] thermal: zx2967: add thermal driver for ZTE's zx2967 family

2017-02-03 Thread Mathieu Poirier
On Fri, Feb 03, 2017 at 06:10:55PM +0800, Baoyou Xie wrote: > This patch adds thermal driver for ZTE's zx2967 family. > > Signed-off-by: Baoyou Xie > --- > drivers/thermal/Kconfig | 8 ++ > drivers/thermal/Makefile | 1 + > drivers/thermal/zx2967_thermal.c | 281 > +

[PATCH] [net-next?] hns: avoid stack overflow with CONFIG_KASAN

2017-02-03 Thread Arnd Bergmann
The use of ACCESS_ONCE() looks like a micro-optimization to force gcc to use an indexed load for the register address, but it has an absolutely detrimental effect on builds with gcc-5 and CONFIG_KASAN=y, leading to a very likely kernel stack overflow aside from very complex object code: hisilicon/

[PATCH] [net-next] net/mlx5e: fix another maybe-uninitialized false-positive

2017-02-03 Thread Arnd Bergmann
In commit abeffce ("net/mlx5e: Fix a -Wmaybe-uninitialized warning"), I fixed a gcc warning for the ipv4 offload handling. Now we get the same warning for the added ipv6 support: drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:815:40: warning: 'out_dev' may be used uninitialized in this function

Re: [PATCH v8 00/15] ACPI platform MSI support and its example mbigen

2017-02-03 Thread Lorenzo Pieralisi
On Fri, Feb 03, 2017 at 10:57:44AM -0500, Sinan Kaya wrote: > On 2/3/2017 10:49 AM, Marc Zyngier wrote: > >> Patches 13-15 are specific for MBIGEN. 00-12 are for the base > >> functionality. > > Is that to support SMMUv3's own MSI generation? It would be helpful if > > you explained why you want t

Re: [PATCH v2 4/9] xen/pvh: Bootstrap PVH guest

2017-02-03 Thread Juergen Gross
On 03/02/17 17:20, Boris Ostrovsky wrote: > >>> + >>> + __HEAD >>> + >>> +/* Entry point for PVH guests. */ >> Could you add some comments about register conetnts at entry? > > Reference to Xen's docs/misc/hvmlite.markdown would be sifficient? I think the corresponding lines should be copied t

[PATCH] media: uvcvideo: Add support for changing UVC_URBS/UVC_MAX_PACKETS from sysfs

2017-02-03 Thread Anurag Kumar Vulisha
The uvc_video.c driver currently has fixed the maximum UVC_URBS queued to 5 and max UVC_MAX_PACKETS per URB to 32K. This configuration works fine with USB 2.0 and some USB 3.0 cameras on embedded platforms(like Zynq Ultrascale). Since embedded platforms has slow processing speed as compared to ser

Re: [PATCH v4 13/15] livepatch: change to a per-task consistency model

2017-02-03 Thread Miroslav Benes
Petr has already mentioned majority of things I too found out, so only couple of nits... > diff --git a/Documentation/ABI/testing/sysfs-kernel-livepatch > b/Documentation/ABI/testing/sysfs-kernel-livepatch > index da87f43..24b6570 100644 > --- a/Documentation/ABI/testing/sysfs-kernel-livepatch

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Hoeun Ryu
On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: > On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: >> Using virtually mapped stack, kernel stacks are allocated via vmalloc. >> In the current implementation, two stacks per cpu can be cached when >> tasks are freed and the cached stacks are used aga

Re: Issues with FW with Intel 720 wifi card

2017-02-03 Thread Luca Coelho
Hi Bharat, On Fri, 2017-02-03 at 16:27 +, Bharat Kumar Gogada wrote: > Hi, > > Im using linux 4.6 kernel, I get following error when I do interface up. > > Here is the boot log. > [4.407681] iwlwifi :01:00.0: loaded firmware version 16.242414.0 > op_mode iwlmvm > [4.407742] iwl

[PATCH] MIPS: ip27: disable qlge driver in defconfig

2017-02-03 Thread Arnd Bergmann
One of the last remaining failures in kernelci.org is for a gcc bug: drivers/net/ethernet/qlogic/qlge/qlge_main.c:4819:1: error: insn does not satisfy its constraints: drivers/net/ethernet/qlogic/qlge/qlge_main.c:4819:1: internal compiler error: in extract_constrain_insn, at recog.c:2190 This i

Re: [patch 0/3] KVM CPU frequency change hypercalls

2017-02-03 Thread Radim Krcmar
2017-02-02 15:47-0200, Marcelo Tosatti: > Implement KVM hypercalls for the guest > to issue frequency changes. > > Current situation with DPDK and frequency changes is as follows: > An algorithm in the guest decides when to increase/decrease > frequency based on the queue length of the device. Do

Re: [PATCH v9 4/4] console: Make persistent scrollback a boot parameter

2017-02-03 Thread Adam Borowski
On Fri, Feb 03, 2017 at 05:04:15PM +0100, Manuel Schölling wrote: > On Thu, 2017-02-02 at 15:07 -0500, Paul Gortmaker wrote: > > On Tue, Jan 10, 2017 at 4:28 PM, Manuel Schölling > > wrote: > > > The impact of the persistent scrollback feature on the code size is > > > rather small, so the config

[PATCH] ARM: defconfigs: make NF_CT_PROTO_SCTP and NF_CT_PROTO_UDPLITE built-in

2017-02-03 Thread Arnd Bergmann
The symbols can no longer be used as loadable modules, leading to a harmless Kconfig warning: arch/arm/configs/imote2_defconfig:60:warning: symbol value 'm' invalid for NF_CT_PROTO_UDPLITE arch/arm/configs/imote2_defconfig:59:warning: symbol value 'm' invalid for NF_CT_PROTO_SCTP arch/arm/confi

[PATCH] drm/amdgpu: fix warning on older gcc releases

2017-02-03 Thread Arnd Bergmann
gcc-4.8 warns about '{0}' being used an an initializer for nested structures: drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c: In function ‘gfx_v8_0_ring_emit_ce_meta_init’: drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c:7263:2: warning: missing braces around initializer [-Wmissing-braces] } ce_payload = {0}; dr

Re: [PATCH 2/2] DTS: dra7: Add "opp_high" opp node to support 1.5 GHz SoC operation

2017-02-03 Thread Nishanth Menon
On 02/03/2017 09:24 AM, Lukasz Majewski wrote: The "opp_high" property brings support for 1.5 GHz CPU frequency for TI's am57xx line of processors. Signed-off-by: Lukasz Majewski --- arch/arm/boot/dts/dra7.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/dra7.dts

Re: [PATCH RT] Align rt_mutex inlining with upstream behavior

2017-02-03 Thread Andy Ritger
On Fri, Feb 03, 2017 at 04:54:34PM +0100, Sebastian Andrzej Siewior wrote: > On 2017-01-30 09:35:34 [-0800], Andy Ritger wrote: > > The problem is that various static inline functions such as > > reservation_object_fini() indirectly call mutex_destroy. On DEBUG_MUTEX > > kernels, mutex_destroy is

Re: [PATCH v4 15/15] livepatch: allow removal of a disabled patch

2017-02-03 Thread Miroslav Benes
On Thu, 19 Jan 2017, Josh Poimboeuf wrote: > From: Miroslav Benes > > Currently we do not allow patch module to unload since there is no > method to determine if a task is still running in the patched code. > > The consistency model gives us the way because when the unpatching > finishes we kno

Re: [RFC v4 00/10] Provide the EL1 physical timer to the VM

2017-02-03 Thread Jintack Lim
On Fri, Feb 3, 2017 at 11:14 AM, Marc Zyngier wrote: > On 03/02/17 15:19, Jintack Lim wrote: >> The ARM architecture defines the EL1 physical timer and the virtual timer, >> and it is reasonable for an OS to expect to be able to access both. >> However, the current KVM implementation does not prov

[PATCH] fixup! userfaultfd: non-cooperative: add event for memory unmaps

2017-02-03 Thread Arnd Bergmann
The prototypes for MMU-based machines and MMU-less builds have to be the same, this fixes the build errors I saw: mm/nommu.c:1201:15: error: conflicting types for 'do_mmap' mm/nommu.c:1580:5: error: conflicting types for 'do_munmap' Fixes: mmtom ("userfaultfd: non-cooperative: add event for memor

Re: [PATCH] pciehp: Fix race condition handling surprise link-down

2017-02-03 Thread Bjorn Helgaas
On Thu, Feb 02, 2017 at 10:00:53PM -0800, Raj, Ashok wrote: > Hi Bjorn > > On Thu, Feb 02, 2017 at 08:59:01PM -0600, Bjorn Helgaas wrote: > > Hi Ashok, > > > > Sorry it took me so long to review this. I never felt like I really > > understood it, and it took me a long time to try to figure out a

Re: [RFC v2] timers: Don't wake ktimersoftd on every tick

2017-02-03 Thread Sebastian Andrzej Siewior
On 2016-12-13 15:44:05 [-0600], Haris Okanovic wrote: > Changed the way timers are collected per Julia and Thomas' > recommendation: Expired timers are now collected in interrupt context > and fired in ktimersoftd to avoid double-walk of `pending_map`. … > Thanks, > Haris I've been staring at it f

Re: [PATCH v8 00/15] ACPI platform MSI support and its example mbigen

2017-02-03 Thread Sinan Kaya
On 2/3/2017 11:40 AM, Lorenzo Pieralisi wrote: > (2) Your HIDMA MSI does not depend on Agustin patch series to work I confirm that my driver doesn't depend on Agustin's patch. -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologi

Re: [PATCH v2 4/5] userfaultfd: mcopy_atomic: return -ENOENT when no compatible VMA found

2017-02-03 Thread Mike Rapoport
Hello Andrea, On Thu, Feb 02, 2017 at 07:02:47PM +0100, Andrea Arcangeli wrote: > On Fri, Jan 27, 2017 at 08:44:32PM +0200, Mike Rapoport wrote: > > - err = -EINVAL; > > + err = -ENOENT; > > dst_vma = find_vma(dst_mm, dst_start); > > if (!dst_vma || !is_

[PATCH] net: phy: dp83867: Fix for automatically detected PHYs

2017-02-03 Thread Alexey Brodkin
Current implemntation returns ENODEV if device tree node for phy is absent. But in reality there're many boards with the one and only PHY on board and MACs that may find a PHY by querying MDIO bus. One good example is STMMAC. So that's what I saw: --- Booing --->8--

Re: [RFC v4 00/10] Provide the EL1 physical timer to the VM

2017-02-03 Thread Marc Zyngier
On 03/02/17 16:51, Jintack Lim wrote: > On Fri, Feb 3, 2017 at 11:14 AM, Marc Zyngier wrote: >> On 03/02/17 15:19, Jintack Lim wrote: >>> The ARM architecture defines the EL1 physical timer and the virtual timer, >>> and it is reasonable for an OS to expect to be able to access both. >>> However,

Re: [PATCH 1/2] DTS: dra7: Replace obsolete "operating-points" property with "operating-points-v2"

2017-02-03 Thread Dave Gerlach
Hi, On 02/03/2017 09:24 AM, Lukasz Majewski wrote: The "operating-points" property have been replaced with "operating-points-v2". Only entries with the same frequencies have been added, so no reqression should be introduced. Signed-off-by: Lukasz Majewski --- arch/arm/boot/dts/dra7.dtsi | 22 +

Re: [PATCH 2/2] DTS: dra7: Add "opp_high" opp node to support 1.5 GHz SoC operation

2017-02-03 Thread Dave Gerlach
On 02/03/2017 09:24 AM, Lukasz Majewski wrote: The "opp_high" property brings support for 1.5 GHz CPU frequency for TI's am57xx line of processors. Signed-off-by: Lukasz Majewski --- arch/arm/boot/dts/dra7.dtsi | 5 + 1 file changed, 5 insertions(+) This can't be blindly enabled for all

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread Ard Biesheuvel
On 3 February 2017 at 16:29, Ard Biesheuvel wrote: > On 3 February 2017 at 16:29, David Howells wrote: >> David Howells wrote: >> >>> Ard Biesheuvel wrote: >>> >>> > Yes, but only if you are booting via UEFI, no? >>> >>> Why limit it so? Even if you don't boot via UEFI, the bootloader/kexec ca

Re: [PATCH v2 RESEND] xen/manage: correct return value check on xenbus_scanf()

2017-02-03 Thread Boris Ostrovsky
On 02/03/2017 03:54 AM, Jan Beulich wrote: > A negative return value indicates an error; in fact the function at > present won't ever return zero. > > Signed-off-by: Jan Beulich > Reviewed-by: Juergen Gross Applied to for-linus-4.11. -boris

Re: [patch 2/3] KVM: x86: introduce ioctl to allow frequency hypercalls

2017-02-03 Thread Radim Krcmar
2017-02-02 15:47-0200, Marcelo Tosatti: > For most VMs, modifying the host frequency is an undesired > operation. Introduce ioctl to enable the guest to > modify host CPU frequency. > > > Signed-off-by: Marcelo Tosatti > --- > arch/x86/include/asm/kvm_host.h |2 ++ > arch/x86/include/uapi

Re: [PATCH 3/6] genirq/affinity: update CPU affinity for CPU hotplug events

2017-02-03 Thread kbuild test robot
Hi Christoph, [auto build test ERROR on block/for-next] [also build test ERROR on v4.10-rc6] [cannot apply to next-20170203] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Christoph-Hellwig

Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family

2017-02-03 Thread Guenter Roeck
On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote: > On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote: > > This patch adds watchdog controller driver for ZTE's zx2967 family. > > > > Signed-off-by: Baoyou Xie > > --- > > drivers/watchdog/Kconfig | 10 ++ > > drivers

Re: [PATCH] net: phy: dp83867: Fix for automatically detected PHYs

2017-02-03 Thread Andrew Lunn
On Fri, Feb 03, 2017 at 07:52:37PM +0300, Alexey Brodkin wrote: > Current implemntation returns ENODEV if device tree node for > phy is absent. But in reality there're many boards with the one > and only PHY on board and MACs that may find a PHY by querying > MDIO bus. One good example is STMMAC.

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Michal Hocko
On Sat 04-02-17 01:42:56, Hoeun Ryu wrote: > On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: > > On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: > >> Using virtually mapped stack, kernel stacks are allocated via vmalloc. > >> In the current implementation, two stacks per cpu can be cached when >

Re: [PATCH 7/7] efi: Print the secure boot status in x86 setup_arch() [ver #7]

2017-02-03 Thread David Howells
Ard Biesheuvel wrote: > OK, I have queued these patches (minus the DeployedMode one) in the > next branch on efi.git. Please double check, I will send out a pull > request to tip shortly (once the autobuilder gives me the green light) Looks okay. Now if I can just squeeze a fixed grub2 out of P

Re: [PATCH v3] initramfs: finish fput() before accessing any binary from initramfs

2017-02-03 Thread Tero Kristo
On 02/02/17 00:12, Andrew Morton wrote: On Wed, 1 Feb 2017 19:35:40 +0530 Lokesh Vutla wrote: commit 4a9d4b024a31 ("switch fput to task_work_add") implements a schedule_work() for completing fput(), but did not guarantee calling __fput() after unpacking initramfs. Because of this, there is a p

[tip:WIP.sched/core 125/133] arch/s390/appldata/appldata_base.c:572:1: note: in expansion of macro 'EXPORT_SYMBOL_GPL'

2017-02-03 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.sched/core head: 9a631ea4bdc4d7a7faabc4a98d632f39573a9a8d commit: d05e7f397bbc869fbd04ca88cd3097b1c13b69d7 [125/133] sched/headers: Move task statistics from to config: s390-gcov_defconfig (attached as .config) compiler:

Re: [RFC PATCH 1/2] mm, vmscan: account the number of isolated pages per zone

2017-02-03 Thread Brian Foster
On Fri, Feb 03, 2017 at 03:50:09PM +0100, Michal Hocko wrote: > [Let's CC more xfs people] > > On Fri 03-02-17 19:57:39, Tetsuo Handa wrote: > [...] > > (1) I got an assertion failure. > > I suspect this is a result of > http://lkml.kernel.org/r/20170201092706.9966-2-mho...@kernel.org > I have no

Re: [PATCH v2 4/8] arm: set CONFIG_MMC_BCM2835=y in bcm2835_defconfig

2017-02-03 Thread Eric Anholt
Gerd Hoffmann writes: > --- > arch/arm/configs/bcm2835_defconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm/configs/bcm2835_defconfig > b/arch/arm/configs/bcm2835_defconfig > index 4b89f4e..3767c24 100644 > --- a/arch/arm/configs/bcm2835_defconfig > +++ b/arch/arm/configs

Re: [PATCH v3] ARM: dts: i.MX25: add AIPS control registers

2017-02-03 Thread Sascha Hauer
On Fri, Feb 03, 2017 at 01:59:52PM +0100, Martin Kaiser wrote: > The i.MX25 contains two AHB to IP bridges (AIPS), each of which has a set of > control registers. Add the memory regions for the control registers to > the Device Tree. > > Signed-off-by: Martin Kaiser Reviewed-by: Sascha Hauer S

Re: [PATCH] staging: bcm2835-audio: fix spacing of macro

2017-02-03 Thread Joe Perches
On Fri, 2017-02-03 at 17:17 +0100, Hendrik v. Raven wrote: > VC_AUDIO_MAX_MSG_LEN This macro seems unused and might as well be removed.

linux-next 20170130 - BUG mmc driver 'sleeping function called from invalid context'

2017-02-03 Thread valdis . kletnieks
Booted next-20170130 with a flash memory card forgotten in the reader slot, and it produced a truly impressive amount of splattage - managing to trigger both a BUG for sleeping in an invalid context *and* a lockdep whinge. I can't tell if it's 2 mmc bugs, or if lockdep got confused due to the BUG

Re: [PATCH] net: phy: dp83867: Fix for automatically detected PHYs

2017-02-03 Thread Alexey Brodkin
Hi Andrew, On Fri, 2017-02-03 at 18:10 +0100, Andrew Lunn wrote: > On Fri, Feb 03, 2017 at 07:52:37PM +0300, Alexey Brodkin wrote: > > > > Current implemntation returns ENODEV if device tree node for > > phy is absent. But in reality there're many boards with the one > > and only PHY on board and

Re: [PATCH v2 3/8] mmc: bcm2835: add sdhost controller to devicetree

2017-02-03 Thread Eric Anholt
Gerd Hoffmann writes: > Signed-off-by: Gerd Hoffmann Patches 3, 7, 8 are: Acked-by: Eric Anholt waiting on Ulf for merging the driver now. signature.asc Description: PGP signature

Re: [PATCH v5 0/3] Add Support for Cavium Cryptographic Acceleration Unit

2017-02-03 Thread Sasha Levin
On Mon, Jan 30, 2017 at 7:30 AM, George Cherian wrote: > This series adds the support for Cavium Cryptographic Accelerarion Unit (CPT) > CPT is available in Cavium's Octeon-Tx SoC series. > > The series was tested with ecryptfs and dm-crypt for in kernel cryptographic > offload operations. This dr

Re: [patch 3/3] KVM: x86: frequency change hypercalls

2017-02-03 Thread Radim Krcmar
2017-02-02 15:47-0200, Marcelo Tosatti: > Implement min/max/up/down frequency change > KVM hypercalls. To be used by DPDK implementation. > > Also allow such hypercalls from guest userspace. > > Signed-off-by: Marcelo Tosatti > > --- > Index: kvm-pvfreq/arch/x86/kvm/x86.c > ===

[PATCH net-next 5/9] sunvnet: add memory barrier before check for tx enable

2017-02-03 Thread Shannon Nelson
In order to allow the underlying LDC and outstanding memory operations to potentially catch up with the driver's Tx requests, add a memory barrier before checking again for available tx descriptors. Signed-off-by: Shannon Nelson --- drivers/net/ethernet/sun/sunvnet_common.c |1 + 1 files cha

[PATCH net-next 3/9] sunvnet: update version and version printing

2017-02-03 Thread Shannon Nelson
There have been several changes since the first version of this code, so we bump the version number. While we're at it, we can simplify the version printing a bit and drop a couple lines of code. Signed-off-by: Shannon Nelson --- drivers/net/ethernet/sun/sunvnet.c | 14 -- 1 files

[PATCH net-next 6/9] sunvnet: straighten up message event handling logic

2017-02-03 Thread Shannon Nelson
The use of gotos for handling the incoming events made this code harder to read and support than it should be. This patch straightens out and clears up the logic. Signed-off-by: Shannon Nelson --- drivers/net/ethernet/sun/sunvnet_common.c | 94 ++--- 1 files changed, 4

[PATCH net-next 2/9] sunvnet: remove unused variable in maybe_tx_wakeup

2017-02-03 Thread Shannon Nelson
From: Sowmini Varadhan The vio_dring_state *dr variable is unused in maybe_tx_wakeup(). As the comments indicate, we call maybe_tx_wakeup() whenever we get a STOPPED LDC message on the port. If the queue is stopped, we want to wake it up so that we will send another START message at the next TX a

[PATCH net-next 0/9] sunvnet driver updates

2017-02-03 Thread Shannon Nelson
The sunvnet ldom virtual network driver was due for some updates and a bugfix or two. These patches address a few items left over from last year's make-over. Shannon Nelson (8): sunvnet: make sunvnet common code dynamically loadable sunvnet: update version and version printing sunvnet: add

[PATCH net-next 4/9] sunvnet: add driver stats for ethtool support

2017-02-03 Thread Shannon Nelson
Since we're collecting some stats in the driver code, let's support use of the ethtool driver stats facility in both sunvnet and ldmvsw. Signed-off-by: Shannon Nelson --- drivers/net/ethernet/sun/ldmvsw.c | 63 + drivers/net/ethernet/sun/sunvnet.c|

[PATCH net-next 8/9] ldmvsw: update and simplify version string

2017-02-03 Thread Shannon Nelson
New version and simplify the print code. Signed-off-by: Shannon Nelson --- drivers/net/ethernet/sun/ldmvsw.c | 14 -- 1 files changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/net/ethernet/sun/ldmvsw.c b/drivers/net/ethernet/sun/ldmvsw.c index 7c5dab4..552c0a9 100644

Re: [PATCHSET v3] slab: make memcg slab destruction scalable

2017-02-03 Thread Tejun Heo
Hello, On Tue, Jan 17, 2017 at 03:54:01PM -0800, Tejun Heo wrote: > Changes from [V2] to V3. > > * 0002-slub-separate-out-sysfs_slab_release-from-sysfs_slab.patch > separated out from > 0002-slab-remove-synchronous-rcu_barrier-call-in-memcg-ca.patch. > > * 0002-slab-remove-synchronous-rcu_ba

[PATCH net-next 1/9] sunvnet: make sunvnet common code dynamically loadable

2017-02-03 Thread Shannon Nelson
When the sunvnet_common code was split out for use by both sunvnet and the newer ldmvsw, it was made into a static kernel library, which limits the usefulness of sunvnet and ldmvsw as loadables, since most of the real work is being done in the shared code. Also, this is simply dead code in kernels

[PATCH net-next 9/9] ldmvsw: disable tso and gso for bridge operations

2017-02-03 Thread Shannon Nelson
The ldmvsw driver is specifically for supporting the ldom virtual networking by running in the primary ldom and using the LDC to connect the remaining ldoms to the outside world via a bridge. With TSO and GSO supported while connected the bridge, things tend to misbehave as seen in our case by del

[PATCH net-next 7/9] sunvnet: remove extra rcu_read_unlocks

2017-02-03 Thread Shannon Nelson
The RCU read lock is grabbed first thing in sunvnet_start_xmit_common() so it always needs to be released. This removes the conditional release in the dropped packet error path and removes a couple of superfluous calls in the middle of the code. Reported-by: Bijan Mottahedeh Signed-off-by: Shann

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

2017-02-03 Thread Luck, Tony
On Thu, Feb 02, 2017 at 06:14:05PM -0800, David Carrillo-Cisneros wrote: > If we tie allocation groups and monitoring groups, we are tying the > meaning of CPUs and we'll have to choose between the CAT meaning or > the perf meaning. > > Let's allow semantics that will allow perf like monitoring to

[PATCHv2 2/2] arch: Rename CONFIG_DEBUG_RODATA and CONFIG_DEBUG_MODULE_RONX

2017-02-03 Thread Laura Abbott
Both of these options are poorly named. The features they provide are necessary for system security and should not be considered debug only. Change the name to something that accurately describes what these options do. Signed-off-by: Laura Abbott --- v2: This patch is now doing the renaming of C

[PATCHv2 0/2] Hardening configs refactor/rename

2017-02-03 Thread Laura Abbott
Hi, This is a follow up to my proposal to rename/refactor CONFIG_DEBUG_RODATA and CONFIG_DEBUG_SET_MODULE_RONX. Among other objections, there shouldn't be 'debug' in the name since these provide necessary kernel protection. v2 takes a slightly different approach to this per feedback. Patch #1 mov

[PATCHv2 1/2] arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to be common

2017-02-03 Thread Laura Abbott
There are multiple architectures that support CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX. These options also now have the ability to be turned off at runtime. Move these to an architecture independent location and make these options def_bool y for almost all of those arches. Signed-off-by: Lau

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Andy Lutomirski
On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu wrote: > On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: >> On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: >>> Using virtually mapped stack, kernel stacks are allocated via vmalloc. >>> In the current implementation, two stacks per cpu can be cached whe

Re: [PATCH] net: phy: dp83867: Fix for automatically detected PHYs

2017-02-03 Thread Andrew Lunn
> This is especially nice because we may change the base-board and use > there another PHY and as long we have drivers for all possible PHY built > in the kernel (or available via modules) proper driver will be instantiated > based on PHY ID read from MDIO. I.e. having no PHY node in DT adds > fle

<    1   2   3   4   5   6   7   8   >