Re: Tearing down DMA transfer setup after DMA client has finished

Vinod Koul writes: > To make it efficient, disregarding your Sbox HW issue, the solution is > virtual channels. You can delink physical channels and virtual channels. If > one has SW controlled MUX then a channel can service any client. For few > controllers request lines

[PATCH v18 13/15] acpi/arm64: Add memory-mapped timer support in GTDT driver

From: Fu Wei On platforms booting with ACPI, architected memory-mapped timers' configuration data is provided by firmware through the ACPI GTDT static table. The clocksource architected timer kernel driver requires a firmware interface to collect timer configuration and

[PATCH v18 11/15] acpi/arm64: Add GTDT table parse driver

From: Fu Wei This patch adds support for parsing arch timer info in GTDT, provides some kernel APIs to parse all the PPIs and always-on info in GTDT and export them. By this driver, we can simplify arm_arch_timer drivers, and separate the ACPI GTDT knowledge from it.

[PATCH v18 15/15] acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver

From: Fu Wei This driver adds support for parsing SBSA Generic Watchdog timer in GTDT, parse all info in SBSA Generic Watchdog Structure in GTDT, and creating a platform device with that information. This allows the operating system to obtain device data from the resource of

[PATCH v18 14/15] clocksource/drivers/arm_arch_timer: Add GTDT support for memory-mapped timer

From: Fu Wei The patch add memory-mapped timer register support by using the information provided by the new GTDT driver of ACPI. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 35 --- 1 file changed, 32

[PATCH v18 12/15] clocksource/drivers/arm_arch_timer: Simplify ACPI support code.

From: Fu Wei The patch update arm_arch_timer driver to use the function provided by the new GTDT driver of ACPI. By this way, arm_arch_timer.c can be simplified, and separate all the ACPI GTDT knowledge from this timer driver. Signed-off-by: Fu Wei

Re: [PATCH v2 4/5] arm64: dts: exynos5433: Add bus dt node using VDD_INT for Exynos5433

On Thu, Dec 08, 2016 at 01:58:10PM +0900, Chanwoo Choi wrote: > This patch adds the bus nodes using VDD_INT for Exynos5433 SoC. > Exynos5433 has the following AMBA AXI buses to translate data > between DRAM and sub-blocks. > > Following list specify the detailed correlation between sub-block and

Re: [PATCH 3/3] powerpc: enable support for GCC plugins

On Thu, Dec 8, 2016 at 6:42 AM, PaX Team wrote: > On 6 Dec 2016 at 17:28, Andrew Donnellan wrote: > >> Enable support for GCC plugins on powerpc. >> >> Add an additional version check in gcc-plugins-check to advise users to >> upgrade to gcc 5.2+ on powerpc to avoid issues

Re: ATH9 driver issues on ARM64

On 08/12/16 15:29, Bharat Kumar Gogada wrote: Two things: > Here is the cat /proc/interrupts (after we do interface up): > > root@:~# ifconfig wlan0 up > [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > root@Xilinx-ZCU102-2016_3:~# cat /proc/interrupts >CPU0

[PATCH v3 14/15] livepatch: add /proc//patch_state

Expose the per-task patch state value so users can determine which tasks are holding up completion of a patching operation. Signed-off-by: Josh Poimboeuf --- Documentation/filesystems/proc.txt | 18 ++ fs/proc/base.c | 15 +++

[PATCH v3 12/15] livepatch: store function sizes

For the consistency model we'll need to know the sizes of the old and new functions to determine if they're on the stacks of any tasks. Signed-off-by: Josh Poimboeuf --- include/linux/livepatch.h | 3 +++ kernel/livepatch/core.c | 16 2 files changed, 19

[PATCH v3 05/15] livepatch/powerpc: add TIF_PATCH_PENDING thread flag

Add the TIF_PATCH_PENDING thread flag to enable the new livepatch per-task consistency model for powerpc. The bit getting set indicates the thread has a pending patch which needs to be applied when the thread exits the kernel. The bit is included in the _TIF_USER_WORK_MASK macro so that

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

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 know that all tasks were marked as safe to

[PATCH v3 07/15] livepatch/s390: add TIF_PATCH_PENDING thread flag

From: Miroslav Benes Update a task's patch state when returning from a system call or user space interrupt, or after handling a signal. This greatly increases the chances of a patch operation succeeding. If a task is I/O bound, it can be patched when returning from a system

[PATCH v3 00/15] livepatch: hybrid consistency model

Dusting the cobwebs off the consistency model again. This is based on linux-next/master. v1 was posted on 2015-02-09: https://lkml.kernel.org/r/cover.1423499826.git.jpoim...@redhat.com v2 was posted on 2016-04-28: https://lkml.kernel.org/r/cover.1461875890.git.jpoim...@redhat.com The

[PATCH v3 04/15] livepatch/x86: add TIF_PATCH_PENDING thread flag

Add the TIF_PATCH_PENDING thread flag to enable the new livepatch per-task consistency model for x86_64. The bit getting set indicates the thread has a pending patch which needs to be applied when the thread exits the kernel. The bit is placed in the _TIF_ALLWORK_MASK macro, which results in

[PATCH v3 08/15] livepatch: separate enabled and patched states

Once we have a consistency model, patches and their objects will be enabled and disabled at different times. For example, when a patch is disabled, its loaded objects' funcs can remain registered with ftrace indefinitely until the unpatching operation is complete and they're no longer in use.

[PATCH v3 01/15] stacktrace/x86: add function for detecting reliable stack traces

For live patching and possibly other use cases, a stack trace is only useful if it can be assured that it's completely reliable. Add a new save_stack_trace_tsk_reliable() function to achieve that. Scenarios which indicate that a stack trace may be unreliable: - running task - interrupt stack -

Re: [PATCH v3 04/15] livepatch/x86: add TIF_PATCH_PENDING thread flag

On Thu, Dec 8, 2016 at 10:08 AM, Josh Poimboeuf wrote: > Add the TIF_PATCH_PENDING thread flag to enable the new livepatch > per-task consistency model for x86_64. The bit getting set indicates > the thread has a pending patch which needs to be applied when the thread >

Re: [RFC, PATCHv1 24/28] x86/mm: add sync_global_pgds() for configuration with 5-level paging

On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov wrote: > This basically restores slightly modified version of original > sync_global_pgds() which we had before foldedl p4d was introduced. > > The only modification is protection against 'address' overflow. > >

Re: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

On 08/12/16 17:01, Alex Williamson wrote: > On Thu, 8 Dec 2016 13:14:04 + > Robin Murphy wrote: >> On 08/12/16 09:36, Auger Eric wrote: >>> 3) RMRR reporting in the iommu group sysfs? Joerg: yes; Don: no >>>My current series does not expose them in iommu group sysfs.

[PATCH v18 00/15] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

From: Fu Wei This patchset: (1)Preparation for adding GTDT support in arm_arch_timer: 1. Move some enums and marcos to header file; 2. Add a new enum for spi type; 3. Improve printk relevant code; 4. Rename some enums and defines; 5.

[PATCH v18 01/15] clocksource/drivers/arm_arch_timer: Move enums and defines to header file

From: Fu Wei To support the arm_arch_timer via ACPI we need to share defines and enums between the driver and the ACPI parser code. Split out the relevant defines and enums into arm_arch_timer.h, and change "enum ppi_nr" to "enum arch_timer_ppi_nr" to avoid the potential name

Re: ATH9 driver issues on ARM64

Bharat Kumar Gogada writes: > > [+cc Kalle, ath9k list] Thanks, but please also CC linux-wireless. Full thread below for the folks there. >> On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: >> > Hi, >> > >> > Did anyone test Atheros ATH9

Re: [PATCH] x86/vm86: fix compilation warning on a unused variable

On Thu, 8 Dec 2016 09:33:05 +0100 Borislav Petkov wrote: > On Wed, Dec 07, 2016 at 11:38:33PM -0500, Jérémy Lefaure wrote: > > When CONFIG_TRANSPARENT_HUGEPAGE is disabled, split_huge_pmd is a no-op > > stub. In such case, vma is unused and a compiler raises a warning: > > > >

Re: [PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

On Wed, Dec 7, 2016 at 11:56 PM, Baoquan He wrote: > Dave Anderson ever told in Crash utility he makes judgement whether it's > a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's > recognized as kaslr. Then the current upstream kernel has a wrong behaviour, >

Re: [PATCH v2 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

Hi Peter, Sorry for taking so long to respond... On Thursday 24 November 2016 08:40 PM, Peter Zijlstra wrote: On Thu, Nov 24, 2016 at 08:14:29PM +0530, Hari Bathini wrote: @@ -862,6 +875,19 @@ enum perf_event_type { */ PERF_RECORD_SWITCH_CPU_WIDE = 15, + /*

Re: [RFC, PATCHv1 16/28] x86/asm: remove __VIRTUAL_MASK_SHIFT==47 assert

On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov wrote: > We don't need it anymore. 17be0aec74fb ("x86/asm/entry/64: Implement > better check for canonical addresses") made canonical address check > generic wrt. address width. This code existed in part to

Re: [RFC, PATCHv1 22/28] x86/espfix: support 5-level paging

On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov wrote: > XXX: how to test this? tools/testing/selftests/x86/sigreturn_{32,64}

[RFC 00/10] kmod: stress test driver, few fixes and enhancements

for filesystem drivers. These patches are available on my linux-next git-tree on my branch 20161208-kmod-test-driver-try2 [0], which is based on linux-next tag next-20161208. Patches are also available based on v4.9-rc8 [1] for those looking for a bit more stable tree given x86_64 on linux-next is hosed

[RFC 01/10] kmod: add test driver to stress test the module loader

This adds a new stress test driver for kmod: the kernel module loader. The new stress test driver, test_kmod, is only enabled as a module right now. It should be possible to load this as built-in and load tests early (refer to the force_init_test module parameter), however since a lot of test can

[PATCH v2 4/4] ARM: treewide: Replace uses of virt_to_phys with __pa_symbol

All low-level PM/SMP code using virt_to_phys() should actually use __pa_symbol() against kernel symbols. Update code where relevant to move away from virt_to_phys(). Signed-off-by: Florian Fainelli --- arch/arm/common/mcpm_entry.c | 12 ++--

Re: [PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

- Original Message - > On Wed, Dec 7, 2016 at 11:56 PM, Baoquan He wrote: > > Dave Anderson ever told in Crash utility he makes judgement whether it's > > a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's > > recognized as kaslr. Then the current

enabling COMPILE_TEST support for GCC plugins in v4.11

Hi, I'd like to get the GCC plugins building under allyesconfig/allmodconfig for -next soon (with the intention of landing the change in v4.11). Specifically, I intend to revert a519167e753e ("gcc-plugins: disable under COMPILE_TEST"). Right now the plugins are only supported on x86, arm, and

Re: [PATCH v2 3/3] kvm: svm: Use the hardware provided GPA instead of page walk

Hi Paolo, On 12/08/2016 09:39 AM, Brijesh Singh wrote: Hi Paolo, On 12/08/2016 08:52 AM, Paolo Bonzini wrote: On 23/11/2016 18:02, Brijesh Singh wrote: From: Tom Lendacky When a guest causes a NPF which requires emulation, KVM sometimes walks the guest page

[PATCH v2 1/4] mtd: lart: Rename partition defines to be prefixed with PART_

In preparation for defining KERNEL_START on ARM, rename KERNEL_START to PART_KERNEL_START, and to be consistent, do this for all partition-related constants. Signed-off-by: Florian Fainelli --- drivers/mtd/devices/lart.c | 24 1 file changed, 12

[PATCH v2 2/4] ARM: Define KERNEL_START and KERNEL_END

In preparation for adding CONFIG_DEBUG_VIRTUAL support, define a set of common constants: KERNEL_START and KERNEL_END which abstract CONFIG_XIP_KERNEL vs. !CONFIG_XIP_KERNEL. Update the code where relevant. Signed-off-by: Florian Fainelli --- arch/arm/include/asm/memory.h

[PATCH v2 3/4] ARM: Add support for CONFIG_DEBUG_VIRTUAL

x86 has an option: CONFIG_DEBUG_VIRTUAL to do additional checks on virt_to_phys calls. The goal is to catch users who are calling virt_to_phys on non-linear addresses immediately. This includes caller using __virt_to_phys() on image addresses instead of __pa_symbol(). This is a generally useful

[GIT PULL] SCSI fixes for 4.9-rc8

One small fix for a regression in a prior fix (again). This time the condition in the prior fix BUG_ON proved to be wrong under certain circumstances causing a BUG to trigger where it shouldn't in the lpfc driver. The patch is available here:

Re: crashkernel only allowing smaller allocations as kernel version increases

OK, after looking through some code, it looks like the behavior was change (back?) to only allocating under 896M with commit 55a20ee7804ab64ac90bcdd4e2868a42829e2784. In order to allocate more RAM than that, you have to specify crashkernel=1024M,high which reserves some RAM in low memory and the

Re: [RFC, PATCHv1 17/28] x86/mm: define virtual memory map for 5-level paging

On Thu, Dec 08, 2016 at 10:56:04AM -0800, Randy Dunlap wrote: > > @@ -23,6 +23,27 @@ a000 - ff5f (=1526 MB) module > > mapping space > > ff60 - ffdf (=8 MB) vsyscalls > > ffe0 - (=2 MB) unused hole > > > > +Virtual

[PATCH v18 06/15] clocksource/drivers/arm_arch_timer: Rework counter frequency detection.

From: Fu Wei Currently, the counter frequency detection call(arch_timer_detect_rate) combines all the ways to get counter frequency: device-tree property, system coprocessor register, MMIO timer. But in the most of use cases, we don't need all the ways to try: For example,

[PATCH v18 08/15] clocksource/drivers/arm_arch_timer: move arch_timer_needs_of_probing into DT init call

From: Fu Wei Because arch_timer_needs_of_probing is only for booting with device-tree, but arch_timer_common_init is a generic init call which shouldn't include the FW-specific code. It's better to put arch_timer_needs_of_probing into DT init function. But for per-cpu timer,

[PATCH v18 07/15] clocksource/drivers/arm_arch_timer: Refactor arch_timer_needs_probing

From: Fu Wei When system init with device-tree, we don't know which node will be initialized first. And the code in arch_timer_common_init should wait until per-cpu timer and MMIO timer are both initialized. So we need arch_timer_needs_probing to detect the init status of

[PATCH v18 10/15] clocksource/drivers/arm_arch_timer: Refactor the timer init code to prepare for GTDT

From: Fu Wei The patch refactor original memory-mapped timer init code: (1) Refactor "arch_timer_mem_init", make it become a common code for memory-mapped timer init. (2) Add a new function "arch_timer_mem_of_init" for DT init. Signed-off-by: Fu Wei

[PATCH v18 09/15] clocksource/drivers/arm_arch_timer: Introduce some new structs to prepare for GTDT

From: Fu Wei The patch introduce two new structs: arch_timer_mem, arch_timer_mem_frame. And also introduce a new define: ARCH_TIMER_MEM_MAX_FRAMES These will be used for refactoring the memory-mapped timer init code to prepare for GTDT Signed-off-by: Fu Wei

[PATCH v18 03/15] clocksource/drivers/arm_arch_timer: Improve printk relevant code

From: Fu Wei This patch defines pr_fmt(fmt) for all pr_* functions, then the pr_* doesn't need to add "arch_timer:" everytime. According to the suggestion from checkpatch.pl: (1) delete some Blank Spaces in arch_timer_banner; (2) delete a redundant Tab in a bland line of

[PATCH v18 05/15] clocksource/drivers/arm_arch_timer: rework PPI determination

From: Fu Wei Currently, the arch timer driver uses ARCH_TIMER_PHYS_SECURE_PPI to mean the driver will use the secure PPI *and* potentialy also use the non-secure PPI. This is somewhat confusing. For arm64, where it never makes sense to use the secure PPI, this means we must

[PATCH v18 02/15] clocksource/drivers/arm_arch_timer: Add a new enum for spi type

From: Fu Wei This patch add a new enum "arch_timer_spi_nr" and use it in the driver. Just for code's readability, no functional change. Signed-off-by: Fu Wei Acked-by: Mark Rutland --- drivers/clocksource/arm_arch_timer.c | 4 ++--

Re: net: deadlock on genl_mutex

On Thu, Dec 8, 2016 at 6:16 PM, Dmitry Vyukov wrote: > On Thu, Dec 8, 2016 at 5:16 PM, Dmitry Vyukov wrote: >> On Tue, Nov 29, 2016 at 6:59 AM, wrote: Issue was reported yesterday and is under investigation.

crashkernel only allowing smaller allocations as kernel version increases

I've been trying to capture a core to help in debuging a problem, but it seems that as I go up in kernel versions, I can only allocate less and less memory to crashkernel and with 4.9-rc8 I can't allocate enough to prevent OOM (specifically on CentOS with iSCSI root). I'm seeing the same reduction

Re: [PATCH] xen/pci: Bubble up error and fix description.

On Thu, Dec 08, 2016 at 07:58:29AM +0100, Juergen Gross wrote: > On 06/12/16 15:28, Konrad Rzeszutek Wilk wrote: > > The function is never called under PV guests, and only shows up > > when MSI (or MSI-X) cannot be allocated. Convert the message > > to include the error value. > > > >

Re: [PATCH 3/6] net: ethernet: ti: cpts: add support of cpts HW_TS_PUSH

On 12/03/2016 05:21 PM, Richard Cochran wrote: > On Mon, Nov 28, 2016 at 05:04:25PM -0600, Grygorii Strashko wrote: >> This also change overflow polling period when HW_TS_PUSH feature is >> enabled - overflow check work will be scheduled more often (every >> 200ms) for proper HW_TS_PUSH events

Re: [RFC, PATCHv1 16/28] x86/asm: remove __VIRTUAL_MASK_SHIFT==47 assert

On Thu, Dec 08, 2016 at 10:39:57AM -0800, Andy Lutomirski wrote: > On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov > wrote: > > We don't need it anymore. 17be0aec74fb ("x86/asm/entry/64: Implement > > better check for canonical addresses") made canonical

Re: [PATCH 0/3] Fix improper handling of pcie hotplug events.

On Sat, Nov 19, 2016 at 12:32:44AM -0800, Ashok Raj wrote: > This patch series fixes pciehp for certain special conditions observed during > testing. > > Ashok Raj (3): > pciehp: Prioritize data-link event over presence detect > pciehp: Fix led status when enabling already enabled slot. I

[PATCH v3 09/15] livepatch: remove unnecessary object loaded check

klp_patch_object()'s callers already ensure that the object is loaded, so its call to klp_is_object_loaded() is unnecessary. This will also make it possible to move the patching code into a separate file. Signed-off-by: Josh Poimboeuf --- kernel/livepatch/core.c | 3 --- 1

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

Change livepatch to use a basic per-task consistency model. This is the foundation which will eventually enable us to patch those ~10% of security patches which change function or data semantics. This is the biggest remaining piece needed to make livepatch more generally useful. This code stems

[PATCH v3 10/15] livepatch: move patching functions into patch.c

Move functions related to the actual patching of functions and objects into a new patch.c file. Signed-off-by: Josh Poimboeuf --- kernel/livepatch/Makefile | 2 +- kernel/livepatch/core.c | 202 +-- kernel/livepatch/patch.c | 213

Re: [RFC, PATCHv1 00/28] 5-level paging

On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov wrote: > > This patchset is still very early. There are a number of things missing > that we have to do before asking anyone to merge it (listed below). > It would be great if folks can start testing applications

[PATCH v3 02/15] x86/entry: define _TIF_ALLWORK_MASK flags explicitly

The _TIF_ALLWORK_MASK macro automatically includes the least-significant 16 bits of the thread_info flags, which is less than obvious and tends to create confusion and surprises when reading or modifying the code. Define the flags explicitly. Signed-off-by: Josh Poimboeuf

[PATCH] coredump: Ensure proper size of sparse core files

If the last section of a core file ends with an unmapped or zero page, the size of the file does not correspond with the last dump_skip() call. gdb complains that the file is truncated and can be confusing to users. After all of the vma sections are written, make sure that the file size is no

Re: [GIT PULL 1/3] ARM: exynos: Soc/mach for v4.10

On Thu, Dec 8, 2016 at 7:28 AM, Pankaj Dubey wrote: > On 3 December 2016 at 22:33, Krzysztof Kozlowski wrote: >> On Fri, Dec 02, 2016 at 10:52:57PM +0100, Arnd Bergmann wrote: >>> On Thursday, December 1, 2016 8:34:04 PM CET Krzysztof Kozlowski wrote:

Re: [PATCH] x86/vm86: fix compilation warning on a unused variable

On Thu, 8 Dec 2016 13:50:11 +0300 "Kirill A. Shutemov" wrote: > On Wed, Dec 07, 2016 at 11:38:33PM -0500, Jérémy Lefaure wrote: > > When CONFIG_TRANSPARENT_HUGEPAGE is disabled, split_huge_pmd is a no-op > > stub. In such case, vma is unused and a compiler raises

[PATCH v2] tracing: Replace kmap with copy_from_user() in trace_marker writing

Instead of using get_user_pages_fast() and kmap_atomic() when writing to the trace_marker file, just allocate enough space on the ring buffer directly, and write into it via copy_from_user(). Writing into the trace_marker file use to allocate a temporary buffer to perform the copy_from_user(),

Re: [PATCH] drivers: net: xgene: initialize slots

On Thu, Dec 8, 2016 at 3:17 AM, Colin King wrote: > From: Colin Ian King > > static analysis using cppcheck detected that slots was uninitialized. > Fix this by initializing it to buf_pool->slots - 1 > > Found using static analysis with

Re: [PATCH 1/1] arm64: mm: add config options for page table configuration

On Thu, Dec 08, 2016 at 08:30:36AM -0800, Scott Branden wrote: > On 16-12-08 02:00 AM, Catalin Marinas wrote: > >On Wed, Dec 07, 2016 at 11:40:00AM -0800, Scott Branden wrote: > >>Make MAX_PHYSMEM_BITS and SECTIONS_SIZE_BITS configurable by adding > >>config options. > >>Default to current

Re: [PATCH 1/2] mailbox: mailbox-test: add support for fasync/poll

On 29/11/16 14:37, Sudeep Holla wrote: > Currently the read operation on the message debug file returns error if > there's no data ready to be read. It expects the userspace to retry if > it fails. Since the mailbox response could be asynchronous, it would be > good to add support to block the

Re: [PATCH 08/11] ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel

On Thu, Dec 8, 2016 at 5:18 AM, Rafael J. Wysocki wrote: > On Thu, Dec 8, 2016 at 2:11 AM, Dan Williams wrote: >> On Tue, Nov 29, 2016 at 11:21 PM, Lv Zheng wrote: >>> ACPICA commit cac6790954d4d752a083e610b8a22febcd07 >>> >>>

Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7

On Thu, Dec 08, 2016 at 06:19:51PM +0100, Jesper Dangaard Brouer wrote: > > > See patch below signature. > > > > > > Besides I think you misunderstood me, you can adjust: > > > sysctl net.core.rmem_max > > > sysctl net.core.wmem_max > > > > > > And you should if you plan to use/set 851968 as

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

On Thu, Dec 08, 2016 at 12:20:58PM -0500, Keith Busch wrote: > On Thu, Dec 08, 2016 at 09:11:58AM -0600, Bjorn Helgaas wrote: > > On Wed, Dec 07, 2016 at 07:04:33PM -0500, Keith Busch wrote: > > > > > > It currently looks safe to nest the p_slot->lock under the > > > p_slot->hotplug_lock if that

Re: [PATCH v4 2/2] usb: dwc3: core: Support the dwc3 host suspend/resume

Hi, Baolin Wang writes: >> Baolin Wang writes: > On 28 November 2016 at 14:43, Baolin Wang wrote: >> For some mobile devices with strict power management, we also want to >> suspend >> the host when the

Re: staging: comedi: usbduxsigma: Split a condition check in usbduxsigma_alloc_usb_buffers()

On 08/12/16 15:46, SF Markus Elfring wrote: * Reduce memory allocation sizes for two function calls. Is this implementation detail worth for further considerations? I assume you are referring to the allocation of devpriv->ai_urbs and devpriv->ao_urbs? Your patch does not reduce their

Re: [PATCH v2 1/2] devicetree: i2c-hid: Add Wacom digitizer + regulator support

On Thu, Dec 08, 2016 at 10:26:41AM -0600, Rob Herring wrote: > On Thu, Dec 8, 2016 at 10:13 AM, Dmitry Torokhov > wrote: > > On December 8, 2016 8:03:06 AM PST, Rob Herring wrote: > >>On Thu, Dec 8, 2016 at 9:41 AM, Benjamin Tissoires >

[PATCH] ARM: Ignore compressed kernel build products

When we select a kernel compression scheme, we will end-up with e.g: piggy.xzkern under arch/arm/boot/compressed/, let's ignore these files. Signed-off-by: Florian Fainelli --- arch/arm/boot/compressed/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH] ARM: Ignore compressed kernel build products

When we select a kernel compression scheme, we will end-up with e.g: piggy.xzkern under arch/arm/boot/compressed/, let's ignore these files. Signed-off-by: Florian Fainelli --- arch/arm/boot/compressed/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH v2] rpmsg: qcom_smd: Add support for "label" property

On Thu 08 Dec 04:14 PST 2016, Jeremy McNicoll wrote: > On 2016-12-02 2:06 PM, Bjorn Andersson wrote: > >Add support for the "label" property, used to give the edge a name other > >than the one of the DT node. This allows the implementor to provide > >consistently named edges when using the rpmsg

[PATCH v2 0/4] ARM: Add support for CONFIG_DEBUG_VIRTUAL

This patch series builds on top of Laura's [PATCHv5 00/10] CONFIG_DEBUG_VIRTUAL for arm64 to add support for CONFIG_DEBUG_VIRTUAL for ARM. This was tested on a Brahma B15 platform (ARMv7 + HIGHMEM + LPAE). Note that the treewide changes would involve a huge CC list, which is why it has been

Re: [PATCH 5/8] efi: Get the secure boot status [ver #5]

Lukas Wunner wrote: > > +out_efi_err: > > + pr_efi_err(sys_table_arg, "Could not determine UEFI Secure Boot > > status.\n"); > > + if (status == EFI_NOT_FOUND) > > + return efi_secureboot_mode_disabled; > > + return efi_secureboot_mode_unknown; > > +} > > In

[PATCH v18 04/15] clocksource/drivers/arm_arch_timer: rename some enums and defines.

From: Fu Wei Rename some enums and defines, to unify the format of enums and defines in arm_arch_timer.h, also update all the users of these enums and defines: drivers/clocksource/arm_arch_timer.c virt/kvm/arm/hyp/timer-sr.c No functional change. Signed-off-by: Fu

Re: [PATCH v3 0/6] net: stmmac: make DMA programmable burst length more configurable

From: Niklas Cassel Date: Wed, 7 Dec 2016 15:20:02 +0100 > Make DMA programmable burst length more configurable in the stmmac driver. > > This is done by adding support for independent pbl for tx/rx through DT. > More fine grained tuning of pbl is possible thanks to a DT

[PATCH v3 11/15] livepatch: use kstrtobool() in enabled_store()

The sysfs enabled value is a boolean, so kstrtobool() is a better fit for parsing the input string since it does the range checking for us. Suggested-by: Petr Mladek Signed-off-by: Josh Poimboeuf --- kernel/livepatch/core.c | 11 --- 1 file

Re: [RFC, PATCHv1 00/28] 5-level paging

On December 8, 2016 10:16:07 AM PST, Linus Torvalds wrote: >On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov > wrote: >> >> This patchset is still very early. There are a number of things >missing >> that we have to do before

RE: ATH9 driver issues on ARM64

> On 08/12/16 15:29, Bharat Kumar Gogada wrote: > > Two things: > > > Here is the cat /proc/interrupts (after we do interface up): > > > > root@:~# ifconfig wlan0 up > > [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > root@Xilinx-ZCU102-2016_3:~# cat /proc/interrupts > >

Re: ATH9 driver issues on ARM64

On 08/12/16 18:33, Bharat Kumar Gogada wrote: >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: >> >> Two things: >> >>> Here is the cat /proc/interrupts (after we do interface up): >>> >>> root@:~# ifconfig wlan0 up >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready >>>

Re: [PATCH 1/1 linux-next] ASoC: samsung: include gpio consumer.h

On Wed, Dec 07, 2016 at 09:31:02PM +0100, Fabian Frederick wrote: > > > > On 07 December 2016 at 18:55 Krzysztof Kozlowski wrote: > > > > > > On Wed, Dec 07, 2016 at 08:39:02AM +0100, Fabian Frederick wrote: > > > Fix the following build errors > > > > I couldn't reproduce it

[PATCH] tracing: Replace kmap with copy_from_user() in trace_marker writing

Instead of using get_user_pages_fast() and kmap_atomic() when writing to the trace_marker file, just allocate enough space on the ring buffer directly, and write into it via copy_from_user(). Writing into the trace_marker file use to allocate a temporary buffer to perform the copy_from_user(), as

Re: [RFC PATCH 00/19] ide: remove deprecated host drivers (part 1)

From: Bartlomiej Zolnierkiewicz Date: Thu, 08 Dec 2016 18:14:33 +0100 > I asked you about this in private mail in August 2015, you told me to > bring this on the list. I did it (with these patches) in February > 2016. After two pings and months of waiting for a reply

[PATCH v3 03/15] livepatch: temporary stubs for klp_patch_pending() and klp_update_patch_state()

Create temporary stubs for klp_patch_pending() and klp_update_patch_state() so we can add TIF_PATCH_PENDING to different architectures in separate patches without breaking build bisectability. Signed-off-by: Josh Poimboeuf --- include/linux/livepatch.h | 7 ++-

[PATCH v3 06/15] livepatch/s390: reorganize TIF thread flag bits

From: Jiri Slaby Group the TIF thread flag bits by their inclusion in the _TIF_WORK and _TIF_TRACE macros. Signed-off-by: Jiri Slaby Signed-off-by: Josh Poimboeuf --- arch/s390/include/asm/thread_info.h | 22 ++ 1 file

Re: [GIT PULL 1/3] ARM: exynos: Soc/mach for v4.10

On Thu, Dec 08, 2016 at 10:25:35AM -0800, Olof Johansson wrote: > On Thu, Dec 8, 2016 at 7:28 AM, Pankaj Dubey wrote: > > On 3 December 2016 at 22:33, Krzysztof Kozlowski wrote: > >> On Fri, Dec 02, 2016 at 10:52:57PM +0100, Arnd Bergmann wrote: > >>> >

Re: [PATCH 0/4] g_NCR5380: Bug fix and some enhancements

On Monday 05 December 2016 07:07:19 Finn Thain wrote: > This patch series is based on the one submitted recently by Ondrej Zary. > > This version has a different irq probing fix for HP C2502 boards and > a more comprehensive patch to change the default irq parameter. > > It needs testing on actual

Re: [RFC, PATCHv1 17/28] x86/mm: define virtual memory map for 5-level paging

On 12/08/16 08:21, Kirill A. Shutemov wrote: > The first part of memory map (up to %esp fixup) simply scales existing > map for 4-level paging by factor of 9 -- number of bits addressed by > additional page table level. > > The rest of the map is uncahnged. unchanged.

Re: [RFC, PATCHv1 00/28] 5-level paging

On Thu, Dec 08, 2016 at 10:16:07AM -0800, Linus Torvalds wrote: > On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov > wrote: > > > > This patchset is still very early. There are a number of things missing > > that we have to do before asking anyone to merge it

Re: [RFC, PATCHv1 24/28] x86/mm: add sync_global_pgds() for configuration with 5-level paging

On Thu, Dec 08, 2016 at 10:42:19AM -0800, Andy Lutomirski wrote: > On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov > wrote: > > This basically restores slightly modified version of original > > sync_global_pgds() which we had before foldedl p4d was introduced.

Re: [PATCH 1/1] arm64: mm: add config options for page table configuration

On 16-12-08 10:57 AM, Catalin Marinas wrote: On Thu, Dec 08, 2016 at 08:30:36AM -0800, Scott Branden wrote: On 16-12-08 02:00 AM, Catalin Marinas wrote: On Wed, Dec 07, 2016 at 11:40:00AM -0800, Scott Branden wrote: Make MAX_PHYSMEM_BITS and SECTIONS_SIZE_BITS configurable by adding config

[RFC 10/10] kmod: add a sanity check on module loading

kmod has an optimization in place whereby if a some kernel code uses request_module() on a module already loaded we never bother userspace as the module already is loaded. This is not true for get_fs_type() though as it uses aliases. Additionally kmod <= v19 was broken -- it returns 0 to modprobe

Re: [RFC, PATCHv1 15/28] x86: detect 5-level paging support

On Thu, Dec 8, 2016 at 12:05 PM, Borislav Petkov wrote: > > The cpuid() in cpuflags.c doesn't zero ecx which, if we have to be > pedantic, it should do. It calls CPUID now with the ptr value of its 4th > on 64-bit and 3rd arg on 32-bit, respectively, IINM. In fact, just do a

[PATCH 1/7] blk-mq: add blk_mq_start_stopped_hw_queue()

We have a variant for all hardware queues, but not one for a single hardware queue. Signed-off-by: Jens Axboe --- block/blk-mq.c | 18 +++--- include/linux/blk-mq.h | 1 + 2 files changed, 12 insertions(+), 7 deletions(-) diff --git a/block/blk-mq.c

[PATCH 5/7] blk-mq-sched: add framework for MQ capable IO schedulers

Signed-off-by: Jens Axboe --- block/Makefile | 2 +- block/blk-core.c | 9 +- block/blk-exec.c | 3 +- block/blk-flush.c| 7 +- block/blk-merge.c| 3 + block/blk-mq-sched.c | 246 +++

[PATCH 3/7] elevator: make the rqhash helpers exported

Signed-off-by: Jens Axboe --- block/elevator.c | 8 include/linux/elevator.h | 5 + 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/block/elevator.c b/block/elevator.c index a18a5db274e4..40f0c04e5ad3 100644 --- a/block/elevator.c +++

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