[PATCH v6 1/8] block: move bvec iterator into include/linux/bvec.h

bvec iterator helpers should be used to implement by iterate_bvec():lib/iov_iter.c too, and move them into one header, so that we can keep bvec iterator header out of CONFIG_BLOCK. Then we can remove the reinventing of wheel in iterate_bvec(). Reviewed-by: Christoph Hellwig

[PATCH v6 3/8] block: mark 1st parameter of bvec_iter_advance as const

bvec_iter_advance() only writes the parameter of iterator, so the base address of bvec can be marked as const safely. Without the change, we can see compiling warning in the following patch for implementing iterate_bvec(): lib/iov_iter.c with bvec iterator. Reviewed-by: Christoph Hellwig

Re: [PATCH v2 2/4] Staging: comedi: Fix WARNING issue in s626.c

On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote: > This is a patch to the s626.c file that fixes up a Block comments > issues found by the checkpatch.pl tool. > > i.e. Block comments use a trailing */ on a separate line > > Signed-off-by: Ravishankar Karkala Mallikarjunayya

[PATCH 2/3] dt-bindings: watchdog: Add Meson GXBB Watchdog bindings

Signed-off-by: Neil Armstrong --- .../devicetree/bindings/watchdog/meson-gxbb-wdt.txt | 16 1 file changed, 16 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/meson-gxbb-wdt.txt diff --git

Re: [PATCH trivial] include/linux/memblock.h: Clean up code for several trivial details

On 5/29/16 23:08, Joe Perches wrote: > On Sun, 2016-05-29 at 22:36 +0800, cheng...@emindsoft.com.cn wrote: >> >> Use "!!" to let the boolean function return boolean value directly. > [] >> diff --git a/include/linux/memblock.h b/include/linux/memblock.h > [] >> @@ -191,12 +190,12 @@ static inline

Re: [PATCH 00/26] fb/drm: omapdss: Clean up the headers and separate the two stack

Hi Peter, Tony, On 30/05/16 14:42, Peter Ujfalusi wrote: > Hi, > > omapfb is deprecated. It will not receive new features, only bug fixes. On > the. > other hand omapdrm is in active development and the fact that both > implementation (omapfb and omapdrm) is using the same header file >

Re: [PATCH v4 09/10] cpuidle/powernv: Add support for POWER ISA v3 idle states

On 05/24/2016 03:15 PM, Shreyas B. Prabhu wrote: POWER ISA v3 defines a new idle processor core mechanism. In summary, a) new instruction named stop is added. b) new per thread SPR named PSSCR is added which controls the behavior of stop instruction. Supported idle states and value

[PATCH v1 1/2] lib/uuid: add a test module

It appears that somehow I missed a test of the latest UUID rework which landed in the kernel. Present a small test module to avoid such cases in the future. Signed-off-by: Andy Shevchenko --- lib/Kconfig.debug | 3 ++ lib/Makefile | 1 +

[PATCH v1 2/2] lib/uuid.c: use correct offset in uuid parser

From: Bjørn Mork Use '+ 0' and '+ 1' as offsets, like they were intended, instead of adding to the result. Fixes: 2b1b0d66704a ("lib/uuid.c: introduce a few more generic helpers") Signed-off-by: Bjørn Mork Signed-off-by: Andy Shevchenko

[PATCH] iio: as3935: improve error reporting in as3935_event_work

gcc warns about a potentially uninitialized variable use in as3935_event_work: drivers/iio/proximity/as3935.c: In function ‘as3935_event_work’: drivers/iio/proximity/as3935.c:231:6: error: ‘val’ may be used uninitialized in this function [-Werror=maybe-uninitialized] This case specifically

Re: [PATCH v5 2/6] clocksource/drivers/arm_arch_timer: Add a new enum for spi type

On 05/24/2016 03:30 PM, fu@linaro.org wrote: From: Fu Wei This patch add a new enum "spi_nr" and use it in the driver. Just for code's readability, no functional change. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 4 ++--

[PATCH 0/6 -v2] Handle oom bypass more gracefully

Hi, based on the feedback from Tetsuo and Vladimir (thanks to you both) I had to change some of my assumptions and rework some patches. I planned to resend later this week but I guess it would help to argue about the code after those changes if I resubmit earlier. The previous version was posted

[PATCH 4/6] mm, oom: skip vforked tasks from being selected

From: Michal Hocko vforked tasks are not really sitting on any memory. They are sharing the mm with parent until they exec into a new code. Until then it is just pinning the address space. OOM killer will kill the vforked task along with its parent but we still can end up

[PATCH 3/6] mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj

From: Michal Hocko oom_score_adj is shared for the thread groups (via struct signal) but this is not sufficient to cover processes sharing mm (CLONE_VM without CLONE_THREAD resp. CLONE_SIGHAND) and so we can easily end up in a situation when some processes update their

[PATCH 5/6] mm, oom: kill all tasks sharing the mm

From: Michal Hocko Currently oom_kill_process skips both the oom reaper and SIG_KILL if a process sharing the same mm is unkillable via OOM_ADJUST_MIN. After "mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj" all such processes are sharing the same

[PATCH 6/6] mm, oom: fortify task_will_free_mem

From: Michal Hocko task_will_free_mem is rather weak. It doesn't really tell whether the task has chance to drop its mm. 98748bd72200 ("oom: consider multi-threaded tasks in task_will_free_mem") made a first step into making it more robust for multi-threaded applications so now

Re: [v10, 7/7] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0

On Thursday, May 26, 2016 9:44:10 AM CEST Ulf Hansson wrote: > On 26 May 2016 at 06:05, Yangbo Lu wrote: > > Hi Uffe, > > > > Could we merge this patchset? ... > > It has been a long time to wait for Arnd's response... > > > > Thanks a lot. > > > > > > As we are still in the

Re: [PATCH] usb: echi-hcd: Add ehci_setup check before echi_shutdown

On 19 May 2016 at 15:42, Srinivas Kandagatla wrote: > Fixes 4bb3cad7125b ("usb: host: ehci-msm: Register usb shutdown function") > Signed-off-by: Srinivas Kandagatla Was seeing this crash while doing a reboot on db410c which is

[PATCH v3 1/4] reset: Add support for the Amlogic Meson SoC Reset Controller

This patch adds the platform driver for the Amlogic Meson SoC Reset Controller. The Meson8b and GXBB SoCs are supported. Signed-off-by: Neil Armstrong --- drivers/reset/Makefile | 1 + drivers/reset/reset-meson.c | 136

[PATCH v3 3/4] ARM64: dts: amlogic: Enable Reset Controller on GXBB-based platforms

Update DTSI file to add the reset controller node. Signed-off-by: Neil Armstrong --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi

[PATCH v2 1/2] crypto: engine: permit to enqueue ashash_request

The current crypto engine allow only ablkcipher_request to be enqueued. Thus denying any use of it for hardware that also handle hash algo. This patch convert all ablkcipher_request references to the more general crypto_async_request. Signed-off-by: LABBE Corentin ---

Re: [PATCH] cpufreq: stats: Make the stats code non-modular

On Mon, May 30, 2016 at 6:53 AM, Viresh Kumar wrote: > On 28-05-16, 15:15, Rafael J. Wysocki wrote: >> It does, but there's a problem. >> >> If fast frequency switching is in use, the stats attributes just sit there >> full of zeros (because the stats are not updated

Re: [PATCH v2 6/7] iio: inv_mpu6050: Reformat sample for active scan mask

On 05/29/2016 06:47 PM, Jonathan Cameron wrote: > On 18/05/16 16:00, Crestez Dan Leonard wrote: >> Right now it is possible to only enable some of the x/y/z channels, for >> example you can enable accel_z without x or y but if you actually do >> that what you get is actually only the x channel. >>

Re: [PATCH] staging: iio: fix ad7606_spi regression

On Mon, May 30, 2016 at 3:50 PM, Arnd Bergmann wrote: > As pointed out by Geert Uytterhoeven, the patch was incorrect > and breaks the driver, which was fortunately pointed out by > this gcc warning: > > drivers/staging/iio/adc/ad7606_spi.c: In function ‘ad7606_spi_read_block’: >

Re: [PATCH v2 1/4] staging : comedi : fix type issues in s626.c

On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote: > This is a patch to the s626.c file that fixes up a type issues like > i.e Prefer kernel type 'u8' over 'uint8_t' > Prefer kernel type 'u16' over 'uint16_t' > Prefer kernel type 'u32' over 'uint32_t' > Prefer kernel type

Re: [patch V2 2/7] futex: Hash private futexes per process

On Mon, May 30, 2016 at 03:59:51PM +0200, Sebastian Andrzej Siewior wrote: > On 05/30/2016 03:49 PM, Peter Zijlstra wrote: > >> The same thing can happen within a Task if you take my story from above > >> and replace task with thread. Completely understood. > > > > Right; so I don't see the point

Re: [PATCH v8 00/14] USB OTG/dual-role framework

On 30/05/16 12:29, Peter Chen wrote: > On Fri, May 13, 2016 at 01:03:14PM +0300, Roger Quadros wrote: >> Hi, >> >> This series centralizes OTG/Dual-role functionality in the kernel. >> As of now I've got Dual-role functionality working pretty reliably on >> dra7-evm and am437x-gp-evm. >> NOTE: my

"systemd[1]: Failed to apply local time delta" with v4.7-rc1

Hi, I noticed that when I boot my Lenovo Yoga 900 with v4.7-rc1 I get following error from systemd: systemd[1]: Failed to apply local time delta, ignoring: Invalid argument and my system time is left being 180 minutes off. With following commits reverted it works fine: 86d3473224b0 time:

Re: [PATCH 0/3] watchdog: Add Amlogic Meson GXBB Watchdog Timer driver

On 05/30/2016 03:45 PM, Carlo Caione wrote: > On 30/05/16 15:29, Neil Armstrong wrote: >> Adds support for the Amlogic Meson GXBB SoC Watchdog Timer. >> It differs from the meson6/meson8b HW, so need for a separate driver. >> The HW provides a divider capable of having a 1ms timebase thus

[PATCH stable] serial: samsung: Reorder the sequence of clock control when call s3c24xx_serial_set_termios()

From: Chanwoo Choi commit b8995f527aac143e83d3900ff39357651ea4e0f6 upstream. This patch fixes the broken serial log when changing the clock source of uart device. Before disabling the original clock source, this patch enables the new clock source to protect the clock off

Re: [PATCH v6 10/11] perf callchain: Support x86 target platform

On Mon, May 30, 2016 at 06:58:40PM +0800, Hekuang wrote: SNIP > > I think it's ok to include arch/arm/c > > from arch/x86/util/unwind-libunwind-arm64.c > > > > jirka > > By following your advise, if ARCH=x86, the file tree will > be like this: > > arch/x86 > -

Re: [PATCH 00/10] Documentation/Sphinx

On Mon, 30 May 2016, Markus Heiser wrote: > Here my 5cents about Jani's patch series: > > 1. Migration implementations should not be a part of the kernel tree If you're referring to the conversion scripts, I don't care either way. It's probably helpful to have them

Re: [PATCH RFT 1/2] phylib: add device reset GPIO support

On Thu, May 26, 2016 at 9:00 PM, Uwe Kleine-König wrote: > On Thu, May 26, 2016 at 11:00:55AM +0200, Linus Walleij wrote: >> On Thu, May 12, 2016 at 8:42 PM, Uwe Kleine-König >> wrote: >> >> > [added Linus Walleij to Cc, there is a

Re: [PATCH 1/4] base: soc: introduce soc_device_match() interface

On Monday, May 30, 2016 3:14:38 PM CEST Arnd Bergmann wrote: > We keep running into cases where device drivers want to know the exact > version of the SoC a they are currently running on. In the past, this > has usually been done through a vendor specific API that can be called > by a driver, or

Re: [PATCH] nbd: fix race in ioctl

Hi, On Friday 27 May 2016 12:59:35 Vegard Nossum wrote: > Quentin ran into this bug: > > WARNING: CPU: 64 PID: 10085 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x65/0x80 > sysfs: cannot create duplicate filename '/devices/virtual/block/nbd3/pid' > Modules linked in: nbd > CPU: 64 PID: 10085 Comm:

Re: [PATCH] pinctrl: imx: fix initialization of imx_pinctrl_desc

Hi Linus, Shawn Kindly ping.. Do you have any comments on this patch? Thanks, Peng. On Wed, May 18, 2016 at 05:31:59PM +0800, Peng Fan wrote: >To i.MX7D, there are two iomux controllers, iomuxc and iomuxc_lpsr. >They should not share one pin controller descriptor, otherwise >the value filled

[PATCH v2 3/4] PCI: Add a new option for resource_alignment to reassign alignment

When using resource_alignment kernel parameter, the current implement reassigns the alignment by changing resources' size which can potentially break some drivers. For example, the driver uses the size to locate some register whose length is related to the size. This patch adds a new option

[PATCH v2 1/4] PCI: Ignore resource_alignment if PCI_PROBE_ONLY was set

The resource_alignment will releases memory resources allocated by firmware so that kernel can reassign new resources later on. But this will cause the problem that no resources can be allocated by kernel if PCI_PROBE_ONLY was set, e.g. on pSeries platform because PCI_PROBE_ONLY force kernel to

[PATCH v2 0/4] PCI: Add support for enforcing all MMIO BARs not to share PAGE_SIZE

This series aims to add an option for PCI resource allocator to force BARs not to share PAGE_SIZE. This would make sense to VFIO driver. Because current VFIO implementation disallows to mmap sub-page(size < PAGE_SIZE) MMIO BARs which may share the same page with other BARs for security

[PATCH v2 2/4] PCI: Do not Use IORESOURCE_STARTALIGN to identify bridge resources

Now we use the IORESOURCE_STARTALIGN to identify bridge resources in __assign_resources_sorted(). That's quite fragile. We can't make sure that the PCI devices' resources will not use IORESOURCE_STARTALIGN any more. In this patch, we try to use a more robust way to identify bridge resources.

BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice)

Hi Mel, On Fri, May 20, 2016 at 7:42 PM, Linux Kernel Mailing List wrote: > Web: > https://git.kernel.org/torvalds/c/c33d6c06f60f710f0305ae792773e1c2560e1e51 > Commit: c33d6c06f60f710f0305ae792773e1c2560e1e51 > Parent:

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

Hi guys, I'm attaching a diff instead of full v3. I'm not yet adding attributes for the reset and cable_reset. I still don't understand what is the case where the userspace would need to be able to tricker reset? Why isn't it enough for the userspace to be able to enter/exit modes? Oliver! Can

[PATCH 4/4] Revert "powerpc/fsl: Move fsl_guts.h out of arch/powerpc"

All users of this driver are PowerPC specific and the header file has no business in the global include/linux/ hierarchy, so move it back before anyone starts using it on ARM. This reverts commit 948486544713492f00ac8a9572909101ea892cb0. Signed-off-by: Arnd Bergmann --- This part

[PATCH v3 2/4] dt-bindings: reset: Add bindings for the Meson SoC Reset Controller

Add DT bindings for the Meson SoC Reset Controller documentation and the associated include file. Acked-by: Rob Herring Signed-off-by: Neil Armstrong --- .../bindings/reset/amlogic,meson-reset.txt | 18 ++

[PATCH v3 0/4] Amlogic: Meson: Add reset controller

Patchset to add and enable the reset controller driver on Meson SoCs platforms. This reset controller has up to 256 reset lines with reset pulse generation only, so the assert and deassert calls are not available. Depends on the patch : - "reset: add devm_reset_controller_register API" [1]

[PATCH 1/3] watchdog: Add Meson GXBB Watchdog Driver

Add watchdog specific driver for Amlogic Meson GXBB SoC. Signed-off-by: Neil Armstrong --- drivers/watchdog/Makefile | 1 + drivers/watchdog/meson_gxbb_wdt.c | 277 ++ 2 files changed, 278 insertions(+) create mode 100644

[PATCH 0/3] watchdog: Add Amlogic Meson GXBB Watchdog Timer driver

Adds support for the Amlogic Meson GXBB SoC Watchdog Timer. It differs from the meson6/meson8b HW, so need for a separate driver. The HW provides a divider capable of having a 1ms timebase thus simplifying the counter update. The restart call is not provided even if the HW is capable of triggering

[PATCH 3/3] ARM64: dts: amlogic: meson-gxbb: Add watchdog node

Signed-off-by: Neil Armstrong --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi index 832815d..bcca82f 100644 ---

[PATCH v3 0/4] Amlogic: Meson: Add reset controller

Patchset to add and enable the reset controller driver on Meson SoCs platforms. This reset controller has up to 256 reset lines with reset pulse generation only, so the assert and deassert calls are not available. Depends on the patch : - "reset: add devm_reset_controller_register API" [1]

Re: [PATCH 0/3] watchdog: Add Amlogic Meson GXBB Watchdog Timer driver

On 30/05/16 15:29, Neil Armstrong wrote: > Adds support for the Amlogic Meson GXBB SoC Watchdog Timer. > It differs from the meson6/meson8b HW, so need for a separate driver. > The HW provides a divider capable of having a 1ms timebase thus simplifying > the counter update. > The restart call is

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Mon, 2016-05-30 at 16:19 +0300, Heikki Krogerus wrote: > Hi guys, > > I'm attaching a diff instead of full v3. I'm not yet adding attributes > for the reset and cable_reset. I still don't understand what is the > case where the userspace would need to be able to tricker reset? Why > isn't it

[PATCH 2/2] PCI: hv: handle all pending messages in hv_pci_onchannelcallback()

When we have an interrupt from host we have a bit set in event page indicating there are messages for the particular channel. We need to read them all as we won't get signaled for what was on the queue before we cleared the bit in vmbus_on_event(). This applies to all Hyper-V drivers and the

[PATCH 1/2] PCI: hv: don't leak buffer in hv_pci_onchannelcallback()

We don't free buffer on several code paths in hv_pci_onchannelcallback(), put kfree() to the end of the function to fix the issue. Direct { kfree(); return; } can now be replaced with a simple 'break'; Signed-off-by: Vitaly Kuznetsov --- drivers/pci/host/pci-hyperv.c | 11

[PATCH 0/2] PCI: hv: fix a couple of issues in hv_pci_onchannelcallback()

kmemleak helped me to identify a memory leak in hv_pci_onchannelcallback() and while fixing it I stumbled upon an unrelated issue(s) there. Vitaly Kuznetsov (2): PCI: hv: don't leak buffer in hv_pci_onchannelcallback() PCI: hv: handle all pending messages in hv_pci_onchannelcallback()

[PATCH 5/5] clk: qcom: ipq4019: Added the turbo frequency for apps cpu

Added the CPU turbo frequency (710 Mhz) to frequency table of APPS CPU clock. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/gcc-ipq4019.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/clk/qcom/gcc-ipq4019.c

[PATCH 3/5] clk: qcom: ipq4019: Added the cpu pll divider and changed regmap limit

This patch adds the APSS CPU PLL divider in clock framework and its binding in IPQ4019 device tree binding. Also, it changed the max_register value to 0x2 in regmap config to support the APSS CPU PLL divider operations. Signed-off-by: Abhishek Sahu ---

[PATCH 2/5] clk: qcom: ipq4019: Added the apss cpu pll divider clock node

The existing code does not have support for all the frequency supported by APPS CPU. APPS CPU frequency is provided with APSS CPU PLL divider which divides down the VCO frequency. This divider is nonlinear and specific to IPQ4019 so the standard divider code cannot be used for this. This patch

Re: [PATCH trivial] include/linux/memblock.h: Clean up code for several trivial details

On Mon, 2016-05-30 at 22:21 +0800, Chen Gang wrote: > On 5/29/16 23:08, Joe Perches wrote: > > On Sun, 2016-05-29 at 22:36 +0800, cheng...@emindsoft.com.cn wrote: > > > Use "!!" to let the boolean function return boolean value directly. > > [] > > > diff --git a/include/linux/memblock.h

[PATCH 4/5] clk: qcom: ipq4019: Added the cpu clock frequency change notifier

The current IPQ4019 clock driver code gives the crash or gets hang while switching the CPU frequency some time. The APSS CPU Clock divider is not glitch free so the APPS clock need to be switched for stable clock duringthe change. This patch adds the frequency change notifier for APSS CPU clock.

Re: [PATCH 1/3] watchdog: Add Meson GXBB Watchdog Driver

On 05/30/2016 06:29 AM, Neil Armstrong wrote: Add watchdog specific driver for Amlogic Meson GXBB SoC. Signed-off-by: Neil Armstrong --- drivers/watchdog/Makefile | 1 + drivers/watchdog/meson_gxbb_wdt.c | 277 ++ 2

Re: [PATCH] Add virtio gpu driver.

On Mon, May 30, 2016 at 03:50:36PM +0200, Gerd Hoffmann wrote: > Hi, > > > - add a small core function to registerr HOT_X/HOT_Y for a (cursor) plane, > > e.g. drm_plane_register_hotspot(). That should allocate the properties > > (if they don't exist yet) and then attach those props to the

[PATCH v7 02/10] kthread: Allow to call __kthread_create_on_node() with va_list args

kthread_create_on_node() implements a bunch of logic to create the kthread. It is already called by kthread_create_on_cpu(). We are going to extend the kthread worker API and will need to call kthread_create_on_node() with va_list args there. This patch does only a refactoring and does not

[PATCH v7 00/10] kthread: Kthread worker API improvements

I send the kthread worker API improvements separately as discussed in v6, see https://lkml.kernel.org/g/<20160511105224.ge2...@pathway.suse.cz> They seem to be ready for inclusion in 4.8. I will send the conversion of the particular kthreads once the API changes are in some maintainers three

[PATCH v7 01/10] kthread/smpboot: Do not park in kthread_create_on_cpu()

kthread_create_on_cpu() was added by the commit 2a1d446019f9a5983e ("kthread: Implement park/unpark facility"). It is currently used only when enabling new CPU. For this purpose, the newly created kthread has to be parked. The CPU binding is a bit tricky. The kthread is parked when the CPU has

Re: [PATCH v9 7/7] MAINTAINERS: add maintainer entry for Intel USB dual role mux drivers

Hi Heikki, On 05/30/2016 04:16 PM, Heikki Krogerus wrote: > Hi Baolu, > > On Mon, May 30, 2016 at 01:51:44PM +0800, Lu Baolu wrote: >> Add a maintainer entry for Intel USB dual role mux drivers and >> add myself as a maintainer. >> >> Signed-off-by: Lu Baolu >> --- >>

[PATCH net] bnx2x: avoid leaking memory on bnx2x_init_one() failures

bnx2x_init_bp() allocates memory with bnx2x_alloc_mem_bp() so if we fail later in bnx2x_init_one() we need to free this memory with bnx2x_free_mem_bp() to avoid leakages. E.g. I'm observing memory leaks reported by kmemleak when a failure (unrelated) happens in bnx2x_vfpf_acquire().

[PATCH 2/6] proc, oom_adj: extract oom_score_adj setting into a helper

From: Michal Hocko Currently we have two proc interfaces to set oom_score_adj. The legacy /proc//oom_adj and /proc//oom_score_adj which both have their specific handlers. Big part of the logic is duplicated so extract the common code into __set_oom_adj helper. Legacy knob still

[PATCH v2 4/4] PCI: Add support for enforcing all MMIO BARs to be page aligned

When vfio passthrough a PCI device of which MMIO BARs are smaller than PAGE_SIZE, guest will not handle the mmio accesses to the BARs which leads to mmio emulations in host. This is because vfio will not allow to passthrough one BAR's mmio page which may be shared with other BARs. Otherwise,

[PATCH 1/6] proc, oom: drop bogus task_lock and mm check

From: Michal Hocko both oom_adj_write and oom_score_adj_write are using task_lock, check for task->mm and fail if it is NULL. This is not needed because the oom_score_adj is per signal struct so we do not need mm at all. The code has been introduced by 3d5992d2ac7d ("oom: add

[PATCH v4] vfio-pci: Allow to mmap sub-page MMIO BARs if the mmio page is exclusive

Current vfio-pci implementation disallows to mmap sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio page may be shared with other BARs. This will cause some performance issues when we passthrough a PCI device with this kind of BARs. Guest will be not able to handle the mmio accesses to

Re: [RFC PATCH 1/2] sched: encapsulate priority changes in a sched_set_prio static function

- On May 27, 2016, at 5:16 PM, Julien Desfossez jdesfos...@efficios.com wrote: > Currently, the priority of tasks is modified directly in the scheduling > functions. Encapsulate priority updates to enable instrumentation of > priority changes. This will enable analysis of real-time

Re: [RFC PATCH 2/2] tracing: add sched_set_prio tracepoint

- On May 27, 2016, at 5:16 PM, Julien Desfossez jdesfos...@efficios.com wrote: > This tracepoint allows to keep track of all priority changes made by all > sites that can change this value. The impacted system calls are > sched_setscheduler, sched_setattr, sched_process_fork and

[PATCH v3 4/4] ARM: dts: amlogic: Enable Reset Controller on Meson8b platforms

Update DTSI file to add the reset controller node. Signed-off-by: Neil Armstrong --- arch/arm/boot/dts/meson8b.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/meson8b.dtsi b/arch/arm/boot/dts/meson8b.dtsi index 2bfe401..fc4080d 100644

[PATCH v2 2/2] crypto: omap: convert to the new cryptoengine API

Since the crypto engine has been converted to use crypto_async_request instead of ablkcipher_request, minor changes are needed to use it. Signed-off-by: LABBE Corentin --- drivers/crypto/omap-aes.c | 10 ++ drivers/crypto/omap-des.c | 10 ++ 2 files

[PATCH v2 0/2] crypto: engine: permit to enqueue ashash_request

Hello I wanted to use the crypto engine for my Allwinner crypto driver but something prevented me to use it: it cannot enqueue hash requests. The first patch convert crypto engine to permit enqueuing of ahash_requests. The second patch convert the only driver using crypto engine. The second

[PATCH v2 1/6] PCI: Add a new PCI_BUS_FLAGS_MSI_REMAP flag

We introduce a new pci_bus_flags, PCI_BUS_FLAGS_MSI_REMAP which indicates interrupts of all devices on the bus are managed by the hardware enabling IRQ remapping(intel naming). When the capability is enabled, a given PCI device can only shoot the MSIs assigned for it. In other words, the hardware

[PATCH v2 3/6] PCI: Set PCI_BUS_FLAGS_MSI_REMAP if IOMMU have capability of IRQ remapping

The capability of IRQ remapping is abstracted on IOMMU side on some archs. There is a existing flag IOMMU_CAP_INTR_REMAP for this. To have a universal flag to test this capability for different archs on PCI side, we set PCI_BUS_FLAGS_MSI_REMAP for PCI buses when IOMMU_CAP_INTR_REMAP is set.

[PATCH v6 8/8] block: mark BIO_MAX_SIZE as obsolete

Some in-tree drivers may use big bio which size is more than BIO_MAX_SIZE, also the macro is seldom used in tree. So mark it as obsolete now, and it doesn't make sense after multipage bvec is introduced. Signed-off-by: Ming Lei --- include/linux/bio.h | 7 +++ 1

[PATCH v2 2/6] PCI: Set PCI_BUS_FLAGS_MSI_REMAP if MSI controller enables IRQ remapping

On ARM HW the capability of IRQ remapping is abstracted on MSI controller side. MSI_FLAG_IRQ_REMAPPING is used to advertise this [1]. To have a universal flag to test this capability for different archs on PCI side, we set PCI_BUS_FLAGS_MSI_REMAP for PCI buses when MSI_FLAG_IRQ_REMAPPING is set.

[PATCH v2 0/6] vfio-pci: Add support for mmapping MSI-X table

Current vfio-pci implementation disallows to mmap the page containing MSI-X table in case that users can write directly to MSI-X table and generate an incorrect MSIs. However, this will cause some performance issue when there are some critical device registers in the same page as the MSI-X

Re: [patch V2 2/7] futex: Hash private futexes per process

On 05/30/2016 02:06 PM, Peter Zijlstra wrote: >> We >> never rehash the hash. To rehash the hash on runtime we would need an >> empty futex hash and some locking in the fast path. > > Nah; you can do lockless rehashing. Little tricky, but entirely doable. > At worst we'd need an rcu_read_lock(),

[PATCH v6 7/8] block: drbd: avoid to use BIO_MAX_SIZE

Use BIO_MAX_PAGES instead and we will remove BIO_MAX_SIZE. Reviewed-by: Christoph Hellwig Signed-off-by: Ming Lei --- drivers/block/drbd/drbd_int.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/block/drbd/drbd_int.h

Re: [PATCH 1/3] watchdog: Add Meson GXBB Watchdog Driver

On 30/05/16 15:29, Neil Armstrong wrote: > Add watchdog specific driver for Amlogic Meson GXBB SoC. > > Signed-off-by: Neil Armstrong > + > +#define GXBB_WDT_CTRL1_REG 0x4 ... > +#define GXBB_WDT_CTRL_EE_RESET_NOW BIT(26) ... > +#define

[PATCH] staging: iio: fix ad7606_spi regression

As pointed out by Geert Uytterhoeven, the patch was incorrect and breaks the driver, which was fortunately pointed out by this gcc warning: drivers/staging/iio/adc/ad7606_spi.c: In function ‘ad7606_spi_read_block’: drivers/staging/iio/adc/ad7606_spi.c:34: warning: ‘data’ is used uninitialized in

Re: [PATCH] Add virtio gpu driver.

Hi, > - add a small core function to registerr HOT_X/HOT_Y for a (cursor) plane, > e.g. drm_plane_register_hotspot(). That should allocate the properties > (if they don't exist yet) and then attach those props to the cursor. We > don't want those props everywhere, but only on drivers that

Re: [patch V2 2/7] futex: Hash private futexes per process

On 05/30/2016 03:49 PM, Peter Zijlstra wrote: >> The same thing can happen within a Task if you take my story from above >> and replace task with thread. Completely understood. > > Right; so I don't see the point of PREALLOCATE_HASH to cater for RT > workloads if it still doesn't guarantee

Re: [PATCH v2 3/4] Staging: comedi:Fix unsigned int to bare use of unsigned issue in s626.c

On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote: > This is a patch to the s626.c file that fixes up a > WARNING: Prefer 'unsigned int' to bare use of 'unsigned' > found by the checkpatch.pl tool > > Signed-off-by: Ravishankar Karkala Mallikarjunayya The

Re: [PATCH 1/6] proc, oom: drop bogus task_lock and mm check

On Mon, May 30, 2016 at 03:05:51PM +0200, Michal Hocko wrote: > From: Michal Hocko > > both oom_adj_write and oom_score_adj_write are using task_lock, > check for task->mm and fail if it is NULL. This is not needed because > the oom_score_adj is per signal struct so we do not

Re: [PATCH v2 4/4] Staging: comedi: fix line over 80 characters issue in s626.c

On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote: > This is a patch to the s626.c file that fixes up a line over 80 > characters issues found by the checkpatch.pl tool. > > Signed-off-by: Ravishankar Karkala Mallikarjunayya Looks good :) This is the only

Re: [PATCH v2 3/3] cpufreq: schedutil: map raw required frequency to driver frequency

On Mon, May 30, 2016 at 12:18 PM, Viresh Kumar wrote: > On 29-05-16, 02:40, Rafael J. Wysocki wrote: >> I can't really parse the above question, so I'm not going to try to >> answer it. :-) > > Sorry about that :( > > IOW, I think that we should make this change into the

Re: [PATCH perf/core v9 00/16] perf-probe --cache and SDT support

On Mon, 30 May 2016 12:54:58 +0900 Namhyung Kim wrote: > Hi Masami, > > On Sun, May 29, 2016 at 12:15:01AM +0900, Masami Hiramatsu wrote: > > Hi, > > > > Here is the 9th version of the patchset for probe-cache and > > initial SDT support. > > > > The previous version is

[PATCH 0/5] Patches for QCOM IPQ4019 clock driver

These patches are related to Qualcomm IPQ4019 GCC (Global Clock Controller) driver code mainly adding support for multiple CPU frequencies and corrected fixed clock values. Abhishek Sahu (5): clk: qcom: ipq4019: Modified the fixed clock rate to proper values clk: qcom: ipq4019: Added the apss

[PATCH 1/5] clk: qcom: ipq4019: Modified the fixed clock rate to proper values

Modified the fixed clock rate initialization in the IPQ4019 clock probe function with correct values. Also some of the fixed clocks entries were not added in the current driver file so added the same. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/gcc-ipq4019.c | 14

RE: [PATCH 5/7] net:mdio-mux: Add MDIO mux driver for iProc SoCs

Hi Andrew, Thanks for reviewing. Please see my comment inline. > -Original Message- > From: Andrew Lunn [mailto:and...@lunn.ch] > Sent: 30 May 2016 19:05 > To: Pramod Kumar > Cc: Rob Herring; Pawel Moll; Mark Rutland; Ian Campbell; Kumar Gala; Catalin > Marinas; Will Deacon; Kishon Vijay

Re: [lkp] [rcu] ac3c30e891: kmsg.shift_exponent#is_too_large_for#-bit_type'long_unsigned_int'

On Mon, May 30, 2016 at 10:21:07AM +0800, kernel test robot wrote: > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git > dev.2016.05.17a > commit ac3c30e8911d244986e3bb2c56f7d3ca84405d98 ("rcu: Correctly handle > sparse possible

Re: WMI driver no longer load after switching to generic UUID library

On Mon, 2016-05-30 at 12:52 +0200, Bjørn Mork wrote: > How about the untested attached patch? >  Facepalm.jpg! Good catch! The question is how it passed in our internal tree without being notified (it even included a lot of ACPI code updated)!? My explanation since I have no access to archive

Re: ARC stable backport request

On 05/25/2016, 01:43 PM, Vineet Gupta wrote: > Can we please backport a6416f57ce57fb390b "ARC: use ASL assembler mnemonic". > Newer binutils don't like ASL instruction and fail to build kernels prior to > v4.4 > which added this fix. Added to 3.12. Thanks. -- js suse labs

Re: [PATCH block/for-4.7-fixes] writeback: use higher precision calculation in domain_dirty_limits()

On 05/27/2016 12:34 PM, Tejun Heo wrote: As vm.dirty_[background_]bytes can't be applied verbatim to multiple cgroup writeback domains, they get converted to percentages in domain_dirty_limits() and applied the same way as vm.dirty_[background]ratio. However, if the specified bytes is lower

[PATCH v7 09/10] kthread: Allow to modify delayed kthread work

There are situations when we need to modify the delay of a delayed kthread work. For example, when the work depends on an event and the initial delay means a timeout. Then we want to queue the work immediately when the event happens. This patch implements mod_delayed_kthread_work() as inspired

[PATCH v7 04/10] kthread: Add drain_kthread_worker()

flush_kthread_worker() returns when the currently queued works are proceed. But some other works might have been queued in the meantime. This patch adds drain_kthread_worker() that is inspired by drain_workqueue(). It returns when the queue is completely empty and warns when it takes too long.

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