Re: [PATCH v2] usb: dwc2: reset dwc2 core before dwc2_get_hwparams()

On 10/7/2015 5:50 PM, Doug Anderson wrote: > John, > > On Mon, Oct 5, 2015 at 3:02 PM, John Youn wrote: >> On 10/1/2015 1:50 PM, Doug Anderson wrote: >>> John, >>> >>> On Tue, Aug 18, 2015 at 5:19 PM, John Youn wrote: Hi Yunzhi, My

Re: [RESEND PATCH v4 0/8] i2c: Relax mandatory I2C ID table passing

As said to Kieran personally in Dublin, I want a verification that all binding methods still work, especially runtime instantiation for drivers without i2c_device_ids. Also, for the last patch, a verification should be done if the drivers i2c_device_id hasn't been used meanwhile. I'd also like to

Re: [PATCH 0/7][v4] Add OTG support for FSL socs

Hi, Ramneek Mehresh writes: > Add support for otg for all freescale socs having internal > usb phy. > > Ramneek Mehresh (7): > usb:fsl:otg: Make fsl otg driver as tristate > usb:fsl:otg: Add controller version based ULPI and UTMI phy > usb:fsl:otg: Add

[PATCH v3 3/7] drm/vc4: Add KMS support for Raspberry Pi.

This is enough for fbcon and bringing up X using xf86-video-modesetting. It doesn't support the 3D accelerator or power management yet. Signed-off-by: Eric Anholt Acked-by: Daniel Vetter --- v2: Drop FB_HELPER select thanks to Archit's patches. Do

[PATCH v3 7/7] ARM: bcm2835: Add VC4 to the device tree.

VC4 is the GPU (display and 3D) present on the 2835. Signed-off-by: Eric Anholt --- v2: Sort by register address, mark HDMI as disabled by default in the SoC file and enable it from -rpi. v3: Add references to the pixel/HSM clocks for HDMI. Rename compatibility

[PATCH v3 5/7] drm/vc4: Allow vblank to be disabled

From: Derek Foreman Signed-off-by: Derek Foreman Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_kms.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/vc4/vc4_kms.c b/drivers/gpu/drm/vc4/vc4_kms.c

Re: [RFC v2 1/1] i2c: acpi: scan ACPI enumerated I2C mux channels

> I'm working on a revision that incorporates Mika's suggested patch I > think you'll want to wait just a bit for that. I'll happily do. Thanks! signature.asc Description: Digital signature

[PATCH 0/2] Add updated DAX locking to ext2

The first patch in this series is a somewhat related bug fix. The second patch adds new locking to ext2 to isolate DAX faults (page faults, PMD faults, page mkwrite and pfn mkwrite) from ext2 operations that modify a given inode's data block allocations. In my first attempt at this fix I

[PATCH 2/2] ext2: Add locking for DAX faults

Add locking to ensure that DAX faults are isolated from ext2 operations that modify the data blocks allocation for an inode. This is intended to be analogous to the work being done in XFS by Dave Chinner: http://www.spinics.net/lists/linux-fsdevel/msg90260.html Compared with XFS the ext2 case

[PATCH 1/2] dax: dax_pfn_mkwrite() truncate race check

Update dax_pfn_mkwrite() so that it validates i_size before returning. This is necessary to ensure that the page fault has not raced with truncate and is now pointing to a region beyond the end of the current file. This change is based on a similar outstanding patch for XFS from Dave Chinner

[PATCH 0/2] arm: mvebu: disable unused rtc + cosmetic patch for ReadyNAS devices

Hi, Here are two simple patches for Armada-based ReadyNAS devices. The first one disables Armada 370/XP rtc in the .dts files of ReadyNAS 102, 104 and 2120 devices. Those use an Intersil ISL12057 I2C RTC chip and do not use the internal Armada RTC. Because it is enabled in included

Re: [PATCH 2/2] ext2: Add locking for DAX faults

On Fri, Oct 9, 2015 at 3:02 PM, Ross Zwisler wrote: > Add locking to ensure that DAX faults are isolated from ext2 operations > that modify the data blocks allocation for an inode. This is intended to > be analogous to the work being done in XFS by Dave Chinner: > >

Re: [PATCH] Smack: fix a NULL dereference in wrong smack_import_entry() usage

On 8/25/2015 3:39 AM, Lukasz Pawelczyk wrote: > The e774ad683f425a51f87711164ea166d9dcc41477 commit made this function > return proper error codes instead of NULL. Reflect that. > > This is a fix for a NULL dereference introduced in > 21abb1ec414c75abe32c3854848ff30e2b4a6113: > > echo

Re: arm/arm64: GICv2 driver does not have irq_disable implemented

On Fri, Oct 9, 2015 at 2:52 PM, Thomas Gleixner wrote: > On Fri, 9 Oct 2015, Duc Dang wrote: >> On Fri, Oct 9, 2015 at 10:52 AM, Thomas Gleixner wrote: >> > On Fri, 9 Oct 2015, Duc Dang wrote: >> >> In APM ARM64 X-Gene Enet controller driver, we use

[PATCH 07/20] x86: switch from ioremap_cache to memremap

In preparation for deprecating ioremap_cache() convert its usage in arch/x86/ to memremap. Cc: Thomas Gleixner Cc: H. Peter Anvin Cc: Ingo Molnar Cc: Borislav Petkov Signed-off-by: Dan Williams

[PATCH 12/20] memconsole: fix __iomem mishandling, switch to memremap

The memconsole driver is not using proper accessors for __iomem. Switch to memremap to fix this issue, and this also prepares the driver for the removal of ioremap_cache. Cc: Mike Waychison Signed-off-by: Dan Williams ---

[PATCH 10/20] acpi: switch from ioremap_cache to memremap

In preparation for deprecating ioremap_cache() convert its usage in drivers/acpi and include/acpi/ to memremap. This includes dropping the __iomem annotation throughout ACPI since the memremap can be treated as a normal memory pointer. Finally, memremap automatically handles requests to map

Re: linux-next: build warning after merge of the driver-core tree

On Friday, October 09, 2015 12:01:55 PM Viresh Kumar wrote: > On 09-10-15, 16:36, Stephen Rothwell wrote: > > Hi Rafael, > > > > On Thu, 08 Oct 2015 22:30:45 +0200 "Rafael J. Wysocki" > > wrote: > > > > > > On Thursday, October 08, 2015 12:39:54 PM Viresh Kumar wrote: > > >

Re: [PATCH v2] x86/apic: Use smaller array for __apicid_to_node[] mapping

On Fri, 9 Oct 2015, Jiang Liu wrote: > On 2015/10/9 22:15, Thomas Gleixner wrote: > > On Mon, 5 Oct 2015, Daniel J Blueman wrote: > >> +struct apicid_to_node { > >> + int apicid; > >> + s16 node; > >> +}; > > > > Instead of having this array, why don't you use a radix tree and be > > done with

[PATCH v2 1/7] soc: qcom: smd: Introduce callback setter

Introduce a setter for the callback function pointer to clarify the locking around the operation and to reduce some duplication. Signed-off-by: Bjorn Andersson --- Changes since v1: - New patch drivers/soc/qcom/smd.c | 25 +

Re: [PULL] GIC changes for Linux 4.4

On Fri, 9 Oct 2015, Marc Zyngier wrote: > The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46: > > Linux 4.3-rc4 (2015-10-04 16:57:17 +0100) That's not the best base. tip irq/core already has gic modifications which conflict. Can you please rebase to tip irq/core?

Re: [PATCH v3 00/12] pwm: add support for atomic update

Hi Thierry, On Mon, 21 Sep 2015 11:33:17 +0200 Boris Brezillon wrote: > Hello, > > This series adds support for atomic PWM update, or IOW, the capability > to update all the parameters of a PWM device (enabled/disabled, period, > duty and polarity) in one

Re: [PULL] GIC changes for Linux 4.4

On Fri, 9 Oct 2015 22:52:48 +0200 Thomas Gleixner wrote: > On Fri, 9 Oct 2015, Marc Zyngier wrote: > > The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46: > > > > Linux 4.3-rc4 (2015-10-04 16:57:17 +0100) > > That's not the best base. tip irq/core

Re: [PATCH v2 7/7] Bluetooth: btqcomsmd: Qualcomm WCNSS HCI driver

Hi Bjorn, > The Qualcomm WCNSS chip provides two SMD channels to the BT core; one > for command and one for event packets. This driver exposes the two > channels as a hci device. > > Signed-off-by: Bjorn Andersson > --- > > Changes since v1: > - With the

Re: [RFC v2 1/1] i2c: acpi: scan ACPI enumerated I2C mux channels

On Fri, Aug 14, 2015 at 12:31:33PM -0700, Dustin Byford wrote: > > Set an ACPI companion for I2C mux channels enumerated through ACPI and > ensure they are scanned for devices. > > Signed-off-by: Dustin Byford Mika, is this one okay with you? > --- >

Re: [PATCH 2/2] smack: smk_ipv6_port_list should be static

On 9/27/2015 8:10 AM, Geliang Tang wrote: > Fixes the following sparse warning: > > security/smack/smack_lsm.c:55:1: warning: symbol 'smk_ipv6_port_list' > was not declared. Should it be static? > > Signed-off-by: Geliang Tang Acked-by: Casey Schaufler

[PATCH 1/2] arm: mvebu: disable unused Armada RTC on ReadyNAS 102, 104 and 2120

By default, armada-370-xp.dtsi file has internal RTC enabled. NETGEAR ReadyNAS 102, 104 and 2120 all use an Intersil ISL12057 I2C RTC chip. The internal RTC not being disabled in the .dts files of those devices result in the following useless first line during boot: [4.500056] rtc-mv

[PATCH 2/2] arm: mvebu: reorder nodes under internal-regs by address in RN2120 .dts file

This cosmetic patch reorder nodes under internal-regs by increasing address order, as epxected. Signed-off-by: Arnaud Ebalard --- arch/arm/boot/dts/armada-xp-netgear-rn2120.dts | 86 +- 1 file changed, 43 insertions(+), 43 deletions(-) diff --git

[PATCH] staging: r8188eu: Add _enter_critical_mutex() error handling

_enter_critical_mutex() is a simple call to mutex_lock_interruptible(), but there is no error handling code for it. The patch removes wrapper _enter_critical_mutex() and adds error handling for mutex_lock_interruptible(). Found by Linux Driver Verification project (linuxtesting.org).

[PATCH v9] gpio: Add GPIO support for the ACCES 104-IDIO-16

The ACCES 104-IDIO-16 family of PC/104 utility boards feature 16 optically isolated inputs and 16 optically isolated FET solid state outputs. This driver provides GPIO support for these 32 channels of digital I/O. Change-of-State detection interrupts are not supported. GPIO 0-15 correspond to

[PATCH] f2fs: set GFP_NOFS for grab_cache_page

For normal inodes, their pages are allocated with __GFP_FS, which can cause filesystem calls when reclaiming memory. This can incur a dead lock condition accordingly. So, this patch addresses this problem by introducing f2fs_grab_cache_page(.., bool for_write), which calls

randconfig build error with next-20151009, in lib/zlib_deflate/deftree.c

Building with the attached random configuration file, lib/built-in.o: In function `__bitrev32': deftree.c:(.text+0x1e799): undefined reference to `byte_rev_table' deftree.c:(.text+0x1e7a0): undefined reference to `byte_rev_table' deftree.c:(.text+0x1e7b4): undefined reference to `byte_rev_table'

[PATCH v2 3/7] soc: qcom: smd: Refactor channel open and close handling

Refactor opening and closing of channels into two separate functions instead of open coding this in the various places. Signed-off-by: Bjorn Andersson --- Changes since v1: - New patch drivers/soc/qcom/smd.c | 62

[PATCH v2 7/7] Bluetooth: btqcomsmd: Qualcomm WCNSS HCI driver

The Qualcomm WCNSS chip provides two SMD channels to the BT core; one for command and one for event packets. This driver exposes the two channels as a hci device. Signed-off-by: Bjorn Andersson --- Changes since v1: - With the introduction of

[PATCH v2 4/7] soc: qcom: smd: Support multiple channels per sdev

This patch allows chaining additional channels to a SMD device, enabling implementation of multi-channel SMD devies - like Bluetooth. Signed-off-by: Bjorn Andersson --- Changes since v1: - New patch drivers/soc/qcom/smd.c | 14 +++--- 1 file changed, 11

[PATCH v2 2/7] soc: qcom: smd: Split discovery and state change work

Split the two steps of channel discovery and state change handling into two different workers. This allows for new channels to be found while we're are probing, which is required as we introduce multi-channel support. Signed-off-by: Bjorn Andersson --- Changes

Re: [PATCH 10/15] block, dax: fix lifetime of in-kernel dax mappings

On Wed, Oct 7, 2015 at 3:56 PM, Logan Gunthorpe wrote: > Hi Dan, > > We've uncovered another issue during testing with these patches. We get a > kernel panic sometimes just while using a DAX filesystem. I've traced the > issue back to this patch. (There's a stack trace at the

Re: [PATCH] [v4] x86, suspend: Save/restore extra MSR registers for suspend

On Thursday, August 27, 2015 11:18:27 AM Chen Yu wrote: > A bug is reported(https://bugzilla.redhat.com/show_bug.cgi?id=1227208) > that, after resumed from S3, CPU is running at a low speed. > After investigation, it is found that, BIOS has modified the value > of THERM_CONTROL register during S3,

Re: [PATCH v2] sunrpc: fix waitqueue_active without memory barrier in sunrpc

On Fri, Oct 9, 2015 at 5:18 PM, J. Bruce Fields wrote: > > On Fri, Oct 09, 2015 at 06:29:44AM +, Kosuke Tatsukawa wrote: > > Neil Brown wrote: > > > Kosuke Tatsukawa writes: > > > > > >> There are several places in net/sunrpc/svcsock.c which calls >

[PATCH v3 2/7] MAINTAINERS: Add myself for the new VC4 (RPi GPU) graphics driver.

Signed-off-by: Eric Anholt --- v2: Mark it Supported, not Maintained. MAINTAINERS | 6 ++ 1 file changed, 6 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 7ba7ab7..e331e46 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3653,6 +3653,12 @@ S: Maintained

Re: arm/arm64: GICv2 driver does not have irq_disable implemented

On Fri, 9 Oct 2015, Duc Dang wrote: > On Fri, Oct 9, 2015 at 10:52 AM, Thomas Gleixner wrote: > > On Fri, 9 Oct 2015, Duc Dang wrote: > >> In APM ARM64 X-Gene Enet controller driver, we use disable_irq_nosync to > >> disable interrupt before calling __napi_schedule to schedule

Re: [PATCH v3 2/7] MAINTAINERS: Add myself for the new VC4 (RPi GPU) graphics driver.

Hi Eric, On 9 October 2015 at 22:27, Eric Anholt wrote: > Signed-off-by: Eric Anholt > --- > > v2: Mark it Supported, not Maintained. > > MAINTAINERS | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index

[PATCH 00/20] tree-wide convert to memremap()

The memremap() api [1] was merged in 4.3 [2] with an initial implementation for x86 and a conversion of the pmem driver. Complete the conversion for the rest of the kernel. Feel free to either ack or directly apply a conversion-patch as I will defer the final removal patches until all the

[PATCH 01/20] x86: introduce arch_memremap()

In preparation for removing ioremap_cache() introduce arch_memremap() for x86. For now, arch_memremap(..., MEMREMAP_WB) and arch_memremap(..., MEMREMAP_WT) are aliases for ioremap_cache() and ioremap_wt() respectively. While the memremap() conversion patches are filtering through the other

[PATCH 03/20] ia64: introduce arch_memremap()

In preparation for removing ioremap_cache() introduce arch_memremap() for ia64. Given that ia64 does not allow external control for caching types, this simply aliases arch_memremap() with the ia64 ioremap() implementation. Cc: Arnd Bergmann Cc: Tony Luck Cc:

[PATCH 02/20] arm: introduce arch_memremap()

In preparation for removing ioremap_cache() introduce arch_memremap() for arm. For now, arch_memremap(..., MEMREMAP_WB) is an alias for ioremap_cache(). Note that arch_memremap() is relying on memremap() to handle remap requests to "System RAM". Cc: Arnd Bergmann Cc: Russell

Re: [PATCH] PCI/MSI: Export all remapped MSIs to sysfs attributes

[+cc Neil, Thomas, linux-kernel] Hi Romain, On Thu, Sep 24, 2015 at 01:31:16AM +0200, Romain Bezut wrote: > irqbalance uses these attributes to populate its internal database, which is > then used to bind the irq on the appropriate NUMA node. > > On a device accepting multiple MSIs and with

Re: [PATCH 2/2] ext2: Add locking for DAX faults

On Fri, Oct 09, 2015 at 03:18:11PM -0700, Dan Williams wrote: > On Fri, Oct 9, 2015 at 3:02 PM, Ross Zwisler > wrote: > > Add locking to ensure that DAX faults are isolated from ext2 operations > > that modify the data blocks allocation for an inode. This is

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

On Thursday, October 08, 2015 05:05:00 PM Al Stone wrote: > On 10/08/2015 04:50 PM, Rafael J. Wysocki wrote: > > On Thursday, October 08, 2015 02:32:15 PM Al Stone wrote: > >> On 10/08/2015 02:41 PM, Rafael J. Wysocki wrote: > >>> On Thursday, October 08, 2015 10:37:55 PM Rafael J. Wysocki wrote:

Re: [PATCH v7 0/4] perf: add support for profiling jitted code

On Sun, Oct 4, 2015 at 1:05 PM, Stephane Eranian wrote: > > Brendan, > > On Thu, Oct 1, 2015 at 3:45 PM, Brendan Gregg > wrote: > > G'Day, > > > > On Wed, Sep 30, 2015 at 11:45 PM, Stephane Eranian > > wrote: > >> > >> This

Re: [PATCH 0/7][v4] Add OTG support for FSL socs

Felipe Balbi writes: > Hi, > > Ramneek Mehresh writes: >> Add support for otg for all freescale socs having internal >> usb phy. >> >> Ramneek Mehresh (7): >> usb:fsl:otg: Make fsl otg driver as tristate >> usb:fsl:otg: Add controller version

RE: [PATCH][RFC] mm: Introduce kernelcore=reliable option

> I remember Kame has already suggested this idea. In my opinion, > I still think it's better to add a new migratetype or a new zone, > so both user and kernel could use mirrored memory. A new zone would be more flexible ... and probably the right long term solution. But this looks like a very

Re: [PATCH 13/16] perf callchain: Switch default to 'graph,0.5,caller'

Em Fri, Oct 09, 2015 at 01:34:33PM -0700, Brendan Gregg escreveu: > On Mon, Oct 5, 2015 at 2:03 PM, Arnaldo Carvalho de Melo > wrote: > > > > From: Arnaldo Carvalho de Melo > > > > Which is the most common default found in other similar tools. > > Interactive

Re: [PATCH v3 2/7] MAINTAINERS: Add myself for the new VC4 (RPi GPU) graphics driver.

Emil Velikov writes: > Hi Eric, > > On 9 October 2015 at 22:27, Eric Anholt wrote: >> Signed-off-by: Eric Anholt >> --- >> >> v2: Mark it Supported, not Maintained. >> >> MAINTAINERS | 6 ++ >> 1 file changed, 6 insertions(+) >>

[PATCH 01/14] cgroup: remove an unused parameter from cgroup_task_migrate()

cgroup_task_migrate() no longer uses @old_cgrp. Remove it. Signed-off-by: Tejun Heo --- kernel/cgroup.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/kernel/cgroup.c b/kernel/cgroup.c index ae23814..49f30f1 100644 --- a/kernel/cgroup.c +++

[PATCHSET cgroup/for-4.4] cgroup: make zombies retain cgroup membership and fix pids controller

Hello, cgroup currently disassociates a task from its cgroups on exit and reassigns it to the root cgroup. This behavior turns out to be problematic for several reasons. * Resources can't be tracked for zombies. This breaks pids controller as zombies escape resource restriction. A cgroup

[PATCH 02/14] cgroup: make cgroup->nr_populated count the number of populated css_sets

Currently, cgroup->nr_populated counts whether the cgroup has any css_sets linked to it and the number of children which has non-zero ->nr_populated. This works because a css_set's refcnt converges with the number of tasks linked to it and thus there's no css_set linked to a cgroup if it doesn't

[PATCH 04/14] cgroup: move check_for_release() invocation

To trigger release agent when the last task leaves the cgroup, check_for_release() is called from put_css_set_locked(); however, css_set being unlinked is being decoupled from task leaving the cgroup and the correct condition to test is cgroup->nr_populated dropping to zero which

Re: pidns: Make pid accounting and pid_max per namespace

On 10/10/15 11:35, Zefan Li wrote: > On 2015/10/9 18:29, Zhang Haoyu wrote: >> I started multiple docker containers in centos6.6(linux-2.6.32-504.16.2), >> and there's one bad program was running in one container. >> This program produced many child threads continuously without free, so more >>

Re: [Linux] Linux PID algorithm is BRAINDEAD!

> On Oct 10, 2015, at 10:00, Dave Goel wrote: > > Pardon the subject line! I think the PID algo. is actually pretty > good and cheap. > > > I just think that a very minor tweak could actually make it *actually* do > what it always intended to do (that is, satisfy the

Re: pidns: Make pid accounting and pid_max per namespace

On 2015/10/9 18:29, Zhang Haoyu wrote: I started multiple docker containers in centos6.6(linux-2.6.32-504.16.2), and there's one bad program was running in one container. This program produced many child threads continuously without free, so more and more pid numbers were consumed by this

Re: CFS scheduler unfairly prefers pinned tasks

Hi Paul, On 10/8/15 4:19 PM, Mike Galbraith wrote: On Tue, 2015-10-06 at 04:45 +0200, Mike Galbraith wrote: On Tue, 2015-10-06 at 08:48 +1100, paul.sz...@sydney.edu.au wrote: The Linux CFS scheduler prefers pinned tasks and unfairly gives more CPU time to tasks that have set CPU affinity. This

Re: [PATCH] thermal: exynos: fix register read in TMU

W dniu 09.10.2015 o 21:07, Lukasz Majewski pisze: > Hi Krzysztof, > >> 2015-10-08 23:21 GMT+09:00 Sudip Mukherjee >> : >>> On Fri, Oct 02, 2015 at 08:43:52AM +0900, Krzysztof Kozlowski wrote: 2015-10-01 23:12 GMT+09:00 Sudip Mukherjee

[PATCH] soc: qcom: smd: Correct SMEM items for upper channels

Update the SMEM items for the second set of SMD channels, as these where incorrect. Signed-off-by: Bjorn Andersson --- drivers/soc/qcom/smd.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/soc/qcom/smd.c b/drivers/soc/qcom/smd.c

Re: [PATCH] blk-mq: fix waitqueue_active without memory barrier in block/blk-mq-tag.c

Jens Axboe wrote: > On 10/08/2015 06:35 PM, Kosuke Tatsukawa wrote: >> blk_mq_tag_update_depth() seems to be missing a memory barrier which >> might cause the waker to not notice the waiter and fail to send a >> wake_up as in the following figure. >> >> blk_mq_tag_update_depth

Re: [PATCH v2] tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c

Peter Hurley wrote: > On 10/09/2015 01:28 PM, Peter Hurley wrote: >> Tatsukawa-san, >> >> I would still like to root-cause the reported stall; is the reported >> stall resolved if smp_mb() is added before the waitqueue_active() >> in __receive_buf()? > > Nevermind, I see it now. > > The store to

Re: [PATCH] btrfs: fix waitqueue_active without memory barrier in btrfs

David Sterba wrote: > On Fri, Oct 09, 2015 at 12:35:48AM +, Kosuke Tatsukawa wrote: >> This patch removes the call to waitqueue_active() leaving just wake_up() >> behind. This fixes the problem because the call to spin_lock_irqsave() >> in wake_up() will be an ACQUIRE operation. > > Either we

Re: [PATCH v3 7/9] xen/blkback: separate ring information out of struct xen_blkif

On 10/05/2015 10:55 PM, Roger Pau Monné wrote: > El 05/09/15 a les 14.39, Bob Liu ha escrit: >> Split per ring information to an new structure:xen_blkif_ring, so that one >> vbd >> device can associate with one or more rings/hardware queues. >> >> This patch is a preparation for supporting multi

[PATCH] Staging: most: Fix typo in staging/most

This patch fix spelling typo found in most Signed-off-by: Masanari Iida --- drivers/staging/most/Documentation/ABI/sysfs-class-most.txt | 2 +- drivers/staging/most/hdm-dim2/Kconfig | 2 +- drivers/staging/most/hdm-usb/hdm_usb.c

[RESEND PATCH] soc: qcom: smd: Correct SMEM items for upper channels

From: Bjorn Andersson Update the SMEM items for the second set of SMD channels, as these where incorrect. Signed-off-by: Bjorn Andersson --- Corrected .gitconfig mishap which gave wrong author. drivers/soc/qcom/smd.c | 4 ++--

[PATCH] ASoc: sh: Fit typo in Kconfig

s/SUR/SRU/g Signed-off-by: Masanari Iida --- sound/soc/sh/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/sh/Kconfig b/sound/soc/sh/Kconfig index 6ca90aa..206d1ed 100644 --- a/sound/soc/sh/Kconfig +++ b/sound/soc/sh/Kconfig @@ -41,7

[PATCH 03/14] cgroup: replace cgroup_has_tasks() with cgroup_is_populated()

Currently, cgroup_has_tasks() tests whether the target cgroup has any css_set linked to it. This works because a css_set's refcnt converges with the number of tasks linked to it and thus there's no css_set linked to a cgroup if it doesn't have any live tasks. To help tracking resource usage of

[PATCH 09/14] cgroup: factor out css_set_move_task()

A task is associated and disassociated with its css_set in three places - during migration, after a new task is created and when a task exits. The first is handled by cgroup_task_migrate() and the latter two are open-coded. These are similar operations and spreading them over multiple places

[PATCH 08/14] cgroup: keep css_set and task lists in chronological order

css task iteration will be updated to not leak cgroup internal locking to iterator users. In preparation, update css_set and task lists to be in chronological order. For tasks, as migration path is already using list_splice_tail_init(), only cgroup_enable_task_cg_lists() and cgroup_post_fork()

[PATCH 10/14] cgroup: reorganize css_task_iter functions

* Rename css_advance_task_iter() to css_task_iter_advance_css_set() and make it clear it->task_pos too at the end of the iteration. * Factor out css_task_iter_advance() from css_task_iter_next(). The new function whines if called on a terminated iterator. Except for the termination check,

[PATCH 05/14] cgroup: relocate cgroup_[try]get/put()

Relocate cgroup_get(), cgroup_tryget() and cgroup_put() upwards. This is pure code reorganization to prepare for future changes. Signed-off-by: Tejun Heo --- kernel/cgroup.c | 32 1 file changed, 16 insertions(+), 16 deletions(-) diff --git

[PATCH 07/14] cgroup: make cgroup_destroy_locked() test cgroup_is_populated()

cgroup_destroy_locked() currently tests whether any css_sets are associated to reject removal if the cgroup contains tasks. This works because a css_set's refcnt converges with the number of tasks linked to it and thus there's no css_set linked to a cgroup if it doesn't have any live tasks. To

[PATCH 06/14] cgroup: make css_sets pin the associated cgroups

Currently, css_sets don't pin the associated cgroups. This is okay as a cgroup with css_sets associated are not allowed to be removed; however, to help resource tracking for zombie tasks, this is scheduled to change such that a cgroup can be removed even when it has css_sets associated as long as

Re: pidns: Make pid accounting and pid_max per namespace

On 10/10/15 12:40, Zhang Haoyu wrote: > On 10/10/15 11:35, Zefan Li wrote: >> On 2015/10/9 18:29, Zhang Haoyu wrote: >>> I started multiple docker containers in centos6.6(linux-2.6.32-504.16.2), >>> and there's one bad program was running in one container. >>> This program produced many child

Re: [PATCH v2] tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c

On 10/09/2015 01:28 PM, Peter Hurley wrote: > Tatsukawa-san, > > I would still like to root-cause the reported stall; is the reported > stall resolved if smp_mb() is added before the waitqueue_active() > in __receive_buf()? Nevermind, I see it now. The store to commit_head is deferred until

Re: [PATCH 1/1] perf,tools: fix core dump caused by per-socket/core system-wide stat

On Fri, Oct 09, 2015 at 06:59:23AM -0400, kan.li...@intel.com wrote: > From: Kan Liang > > Perf will core dump if --per-socket/core -a are applied for perf stat. > > The root cause is that cpu_map__build_map set refcnt of evlist's cpu_map > to 1. > It should set refcnt for

Re: [PATCH v2] sunrpc: fix waitqueue_active without memory barrier in sunrpc

On Fri, Oct 09, 2015 at 06:29:44AM +, Kosuke Tatsukawa wrote: > Neil Brown wrote: > > Kosuke Tatsukawa writes: > > > >> There are several places in net/sunrpc/svcsock.c which calls > >> waitqueue_active() without calling a memory barrier. Add a memory > >> barrier just

Re: [PATCH v2 19/25] pxa2xx-flash: switch from ioremap_cache to memremap

On Fri, Oct 2, 2015 at 10:51 AM, Brian Norris wrote: > + linux-mtd > > On Fri, Jul 24, 2015 at 10:39:45PM -0400, Dan Williams wrote: >> In preparation for deprecating ioremap_cache() convert its usage in >> pxa2xx-flash to memremap. >> >> Cc: David Woodhouse

Re: [Bugfix v4 1/2] iommu/amd: Prevent binding other PCI drivers to IOMMU PCI devices

On Fri, Oct 09, 2015 at 10:07:31PM +0800, Jiang Liu wrote: > AMD IOMMU driver makes use of IOMMU PCI devices, so prevent binding other > PCI drivers to IOMMU PCI devices. > > This fixes a bug reported by Boris that system suspend/resume gets broken > on AMD platforms. For more information, please

[PATCH 3/3] sched: start stopper early

From: Peter Zijlstra Ensure the stopper thread is active 'early', because the load balancer pretty much assumes that its available. And when 'online && active' the load-balancer is fully available. Not only the numa balancing stop_two_cpus() caller relies on it, but also

[PATCH 1/3] stop_machine: kill smp_hotplug_thread->pre_unpark, introduce stop_machine_unpark()

1. Change smpboot_unpark_thread() to check ->selfparking, just like smpboot_park_thread() does. 2. Introduce stop_machine_unpark() which sets ->enabled and calls kthread_unpark(). 3. Change smpboot_thread_call() and cpu_stop_init() to call stop_machine_unpark() by hand. This way:

[PATCH 2/3] stop_machine: kill cpu_stop_threads->setup() and cpu_stop_unpark()

Now that we always use stop_machine_unpark() to wake the stopper threas up, we can kill ->setup() and fold cpu_stop_unpark() into stop_machine_unpark(). And we do not need stopper->lock to set stopper->enabled = true. Signed-off-by: Oleg Nesterov --- kernel/stop_machine.c |

Re: [RFC] arm: add relocate initrd support

On Fri, Oct 09, 2015 at 11:55:09PM +0800, yalin wang wrote: > Add support for initrd on ARM arch, in case > mem= boot option change the memory size or the initrd are > not placed in low memory region, we need copy the initrd > to low memory region. > > Signed-off-by: yalin wang

[PATCH] ARM: hisilicon: DT: Drop console= and earlyprintk bootargs parameter

Replace console with stdout-path so that we don't have to put the console on the kernel command line. Remove earlyprintk to allow the kernel to boot on a system even if DEBUG_LL is configured for another system. Signed-off-by: Wei Xu Tested-by: Zhangfei Gao

Re: [PATCH 3/3] fpga manager: Adding FPGA Manager support for Xilinx Zynq 7000

Hey Moritz- On Fri, Oct 09, 2015 at 12:45:07AM +0200, Moritz Fischer wrote: > This commit adds FPGA Manager support for the Xilinx Zynq chip. > The code heavily borrows from the xdevcfg driver in Xilinx' > vendor tree. > > Signed-off-by: Moritz Fischer [..] > +++

Re: [PATCH] trace: stop critical timings before idle loop on idle=poll

On Thu, 8 Oct 2015 15:36:06 -0300 Daniel Bristot de Oliveira wrote: > When using idle=poll, the preemptoff tracer is always showing the idle > task as the culprit for long latencies. That happens because critical > timings are not stopped before idle loop. This patch stops

Re: [PATCH] locktorture: fix wrong parameter handling

On Fri, Oct 09, 2015 at 04:53:49PM +0200, Christian Borntraeger wrote: > Am 09.10.2015 um 16:46 schrieb Paul E. McKenney: > > On Fri, Oct 09, 2015 at 02:14:45PM +0200, Christian Borntraeger wrote: > >> Calling locktorture with a wrong parameter makes it > >> unusable: > >> > >> $ modprobe

Re: [PATCH 3/4] arm64: Juno: Add support for the PCIe host bridge on Juno R1

On Fri, Oct 09, 2015 at 03:11:07PM +0100, Liviu Dudau wrote: > On Fri, Oct 09, 2015 at 08:54:33AM -0500, Rob Herring wrote: > > On Fri, Oct 9, 2015 at 8:45 AM, Liviu Dudau wrote: > > > Juno R1 board sports a functional PCIe host bridge that is > > > compliant with the SBSA

[RFC] arm: add relocate initrd support

Add support for initrd on ARM arch, in case mem= boot option change the memory size or the initrd are not placed in low memory region, we need copy the initrd to low memory region. Signed-off-by: yalin wang --- arch/arm/include/asm/fixmap.h | 1 +

Re: [PATCH 1/9] drm: bridge/dw_hdmi-ahb-audio: add audio driver

On Tue, Oct 06, 2015 at 05:25:16PM -0300, Fabio Estevam wrote: > On Tue, Oct 6, 2015 at 3:54 PM, Russell King - ARM Linux > wrote: > > > Make sure you have the ALSA config file, as alsalib won't get on > > with dw-hdmi only accepting 24-bit audio without this. A copy is

Re: [PATCH v4] clocksource/drivers/tango_xtal: Add new timer for Tango SoCs

Marc Gonzalez writes: > Måns Rullgård wrote: > >> Marc Gonzalez wrote: >> >>> Sigma Designs Tango platforms provide a 27 MHz crystal oscillator. >>> Use it for clocksource, sched_clock, and delay_timer. >> >> Given the nature of this hardware, I think it would

Re: [PATCH 1/9] drm: bridge/dw_hdmi-ahb-audio: add audio driver

On Fri, Oct 9, 2015 at 1:00 PM, Russell King - ARM Linux wrote: >> Thanks, Russell! >> >> Got audio to play on my HDMI TV :-) >> >> For the entire series: >> >> Tested-by: Fabio Estevam > > Just to confirm - that's for _all_ of these 8

[PATCH 0/3] make stopper threads more "selfparking"

On top of "[PATCH 0/3]" I sent yesterday, although it doesn't really depend on that series. Peter, note that 3/3 is from you ;) I hope you won't object. Thomas, could you please comment? 1/3 looks like a cleanup to me (if correct), but cleanups are always subjective, so please nack if you don't

Re: [PATCH 3/4] arm64: Juno: Add support for the PCIe host bridge on Juno R1

On Fri, Oct 09, 2015 at 05:49:18PM +0200, Arnd Bergmann wrote: > On Friday 09 October 2015 16:44:08 Mark Rutland wrote: > > On Fri, Oct 09, 2015 at 03:11:07PM +0100, Liviu Dudau wrote: > > > On Fri, Oct 09, 2015 at 08:54:33AM -0500, Rob Herring wrote: > > > Or maybe I can claim the use of the

Re: [PATCH v7 03/60] sparc/PCI: Unify pci_register_region()

On Thu, 2015-10-08 at 14:38 -0700, Yinghai Lu wrote: > We register regions for legacy and iommu and all have open code. > > Unify them to pci_register_region() and call it accordingly. > > Signed-off-by: Yinghai Lu Tested on sparc platforms Tested-by: Khalid Aziz

<    7   8   9   10   11   12   13   14   15   16   >