Re: [PATCH 1/6] ARM: dts: Create fragment for tps65090 PMU

On Tue, Aug 12, 2014 at 06:44:23PM +0200, Javier Martinez Canillas wrote: > The tps65090 is a Power Management Unit (PMU) used in several > boards so the same information is described on different DTS. > It is better to create a .dtsi fragment that can be included. Why is it better to do this? >

[PATCH] drivers: pci: convert generic host controller to DT host bridge creation API

From: Lorenzo Pieralisi In order to consolidate DT configuration for PCI host controllers in the kernel, a new API was introduced that allows creating a host bridge and its PCI bus from DT, removing duplicated code present in the majority of pci host driver implementations. This patch converts t

Re: [PATCH v9] arm64: Add architectural support for PCIe

Somehow, my cover letter went AWOL. Here it is: Hi, This patch adds support for PCI to AArch64. It is based on my v9 patch that adds support for creating generic host bridge structure from device tree. With that in place, I was able to boot a platform that has PCIe host bridge support and use a P

[PATCH 0/6] tps65090 DTS refactoring and improvements

This series does a refactoring by creating dtsi files for the tps65090 PMU that can be included by DT board files that have this component. This not only allow to remove duplicated code but also makes it easier to maintain the tps65090 information. So the series also improve the tps65090 descripti

[PATCH 2/6] ARM: dts: Use tps65090 fragment in exynos5250-snow

Now that there is a .dtsi fragment file for the tps65090 PMU, include it in the Exynos Snow DTS file to reduce duplication. Signed-off-by: Javier Martinez Canillas --- arch/arm/boot/dts/exynos5250-snow.dts | 108 +- 1 file changed, 54 insertions(+), 54 deletions(-

[PATCH 1/6] ARM: dts: Create fragment for tps65090 PMU

The tps65090 is a Power Management Unit (PMU) used in several boards so the same information is described on different DTS. It is better to create a .dtsi fragment that can be included. Signed-off-by: Javier Martinez Canillas --- arch/arm/boot/dts/tps65090.dtsi | 57 +

[PATCH 3/6] ARM: dts: Create cros-tps65090 fragment

The tps65090 PMU is a component used in many ChromeOS devices so instead of having the same device tree definitions in many files, create a .dtsi fragment that can be included in DTS. This fragment is based on the DT definitions for Peach boards. Signed-off-by: Javier Martinez Canillas --- arch

[PATCH 6/6] ARM: dts: Add tps65090 FETs constraints

The tps65090 PMU data manual [0] has a table that list the "Recommended operating conditions" for each regulator. Add the information about the FET constraints to its dtsi file. [0]: http://www.ti.com/lit/ds/symlink/tps65090.pdf Signed-off-by: Javier Martinez Canillas --- arch/arm/boot/dts/tps6

[PATCH 5/6] ARM: dts: Improve cros-tps65090 power scheme

The DeviceTree files for the Peach Pit and Pi machines have a simplistic model of the connections between the different regulators since not all the tps65090 regulators get their input supply voltage from the VDC. DCDC1-3, LD0-1 and fet7 parent supply is indded VDC but the fet1-6 get their input su

[PATCH 4/6] ARM: dts: Use cros-tps65090 fragment in Peach boards

Peach Pit and Pi machines have the same regulators connection and regulator name so the cros-tps65090 dtsi file can be used to remove duplicated code. Signed-off-by: Javier Martinez Canillas --- arch/arm/boot/dts/exynos5420-peach-pit.dts | 95 +++--- arch/arm/boot/dts/exy

[PATCH v9] arm64: Add architectural support for PCIe

Use the generic PCI domain and host bridge functions to provide support for PCI Express on arm64. Signed-off-by: Liviu Dudau [Generic PCI domain support] Signed-off-by: Catalin Marinas --- arch/arm64/Kconfig| 22 +++- arch/arm64/include/asm/Kbuild | 1 + arch/arm64/

Re: [PATCH] Documentation: kmemleak: correct spelling mistake

On 07/31/14 11:20, Rahul Bedarkar wrote: > Signed-off-by: Rahul Bedarkar Acked-by: Randy Dunlap Jiri, please add to trivial. Thanks. > --- > Documentation/kmemleak.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/kmemleak.txt b/Documentation/kmemlea

Re: [PATCH] Input: atmel_mxt_ts - fix a few issues reported by Coverity

On 08/12/2014 10:38 AM, Nick Dyer wrote: On 11/08/14 19:03, Dmitry Torokhov wrote: This should fix the following issues reported by Coverity: *** CID 1230625: Logically dead code (DEADCODE) /drivers/input/touchscreen/atmel_mxt_ts.c: 1692 in mxt_initialize() *** CID 1230627: Missing break in

Re: [PATCH] Input: atmel_mxt_ts - fix a few issues reported by Coverity

On 11/08/14 19:03, Dmitry Torokhov wrote: > This should fix the following issues reported by Coverity: > > *** CID 1230625: Logically dead code (DEADCODE) > /drivers/input/touchscreen/atmel_mxt_ts.c: 1692 in mxt_initialize() > > *** CID 1230627: Missing break in switch (MISSING_BREAK) > /driv

[RFC PATCH] checkpatch: Warn on patch subjects with "checkpatch"

I think patch subject lines with "checkpatch" in them are almost never really useful. Maybe a new checkpatch test to see if a subject line is perhaps less than informational should be added. Something like: --- scripts/checkpatch.pl | 7 +++ 1 file changed, 7 insertions(+) diff --git a/scri

[PATCH v9 03/12] PCI: Introduce helper functions to deal with PCI I/O ranges.

Some architectures do not have a simple view of the PCI I/O space and instead use a range of CPU addresses that map to bus addresses. For some architectures these ranges will be expressed by OF bindings in a device tree file. This patch introduces a pci_register_io_range() helper function with a g

[PATCH v9 11/12] arm64: Add pgprot_device() interface for device mappings.

Add pgprot_device(). It will be aliased to pgprot_noncached for architectures that do not support special attributes for device mapping. Used by arm64 to define new attributes for devices. Cc: Arnd Bergmann Cc: Catalin Marinas Signed-off-by: Liviu Dudau --- include/asm-generic/pgtable.h| 4

[PATCH v9 09/12] OF: Introduce helper function for getting PCI domain_nr

Add of_pci_get_domain_nr() to retrieve the PCI domain number of a given device from DT. If the information is not present, the function can be requested to allocate a new domain number. Cc: Bjorn Helgaas Cc: Arnd Bergmann Cc: Grant Likely Cc: Rob Herring Signed-off-by: Liviu Dudau --- driver

[PATCH v9 06/12] ARM: integrator: Correct usage of of_pci_range_to_resource()

Previously, of_pci_range_to_resource() would return a resource that contained physical addresses of the IO space even if the IORESOURCE_IO flags mandate a logical port set of values. Now that the function has been fixed we need to update the drivers that were taking advantage of the old behaviour.

[PATCH v9 00/12] Support for creating generic PCI host bridges from DT

This is my updated attempt at adding support for generic PCI host bridge controllers that make use of device tree information to configure themselves. This version incorporates Catalin's proposal for managing domain numbers that got Bjorn's approval. I am now requesting ACKs from the relevant maint

[PATCH v9 02/12] PCI: OF: Parse and map the IRQ when adding the PCI device.

Enhance the default implementation of pcibios_add_device() to parse and map the IRQ of the device if a DT binding is available. Cc: Bjorn Helgaas Cc: Grant Likely Cc: Rob Herring Signed-off-by: Liviu Dudau --- drivers/pci/pci.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/pc

[PATCH v9 10/12] OF: PCI: Add support for creating a generic host_bridge from DT

Provide a function to parse the PCI DT ranges and use it to create a pci_host_bridge structure together with its associated bus. Scan all the child busses and add the devices found. This is the OF equivalent of pci_scan_root_bus() where all the resources needed for creating the root bus are discov

[PATCH] ib_umem_release should decrement mm->pinned_vm from ib_umem_get

From: Shawn Bohrer In debugging an application that receives -ENOMEM from ib_reg_mr() I found that ib_umem_get() can fail because the pinned_vm count has wrapped causing it to always be larger than the lock limit even with RLIMIT_MEMLOCK set to RLIM_INFINITY. The wrapping of pinned_vm occurs bec

[PATCH v9 12/12] PCI: Introduce pci_remap_iospace() for remapping PCI I/O bus resources into CPU space

Introduce a default implementation for remapping PCI bus I/O resources onto the CPU address space. Architectures with special needs may provide their own version, but most should be able to use this one. Cc: Bjorn Helgaas Cc: Arnd Bergmann Cc: Rob Herring Signed-off-by: Liviu Dudau --- driver

[PATCH v9 05/12] ARM: Define PCI_IOBASE as the base of virtual PCI IO space.

This is needed for calls into OF code that parses PCI ranges. It signals support for memory mapped PCI I/O accesses that are described be device trees. Cc: Russell King Cc: Catalin Marinas Cc: Arnd Bergmann Cc: Rob Herring Signed-off-by: Liviu Dudau --- arch/arm/include/asm/io.h | 1 + 1 fil

[PATCH v9 04/12] PCI: OF: Fix the conversion of IO ranges into IO resources.

The ranges property for a host bridge controller in DT describes the mapping between the PCI bus address and the CPU physical address. The resources framework however expects that the IO resources start at a pseudo "port" address 0 (zero) and have a maximum size of IO_SPACE_LIMIT. The conversion fr

[PATCH v9 08/12] PCI: Introduce generic domain handling for PCI busses.

The handling of PCI domains (or PCI segments in ACPI speak) is usually a straightforward affair but its implementation is currently left to the architectural code, with pci_domain_nr(b) querying the value of the domain associated with bus b. This patch introduces CONFIG_PCI_DOMAINS_GENERIC as an o

[PATCH v9 01/12] Fix ioport_map() for !CONFIG_GENERIC_IOMAP cases.

The inline version of ioport_map() that gets used when !CONFIG_GENERIC_IOMAP is wrong. It returns a mapped (i.e. virtual) address that can start from zero and completely ignores the PCI_IOBASE and IO_SPACE_LIMIT that most architectures that use !CONFIG_GENERIC_MAP define. Signed-off-by: Liviu Duda

[PATCH v9 07/12] PCI: Create pci_host_bridge before its associated bus in pci_create_root_bus.

Before commit 7b5436635800 the pci_host_bridge was created before the root bus. As that commit has added a needless dependency on the bus for pci_alloc_host_bridge() the creation order has been changed for no good reason. Revert the order of creation as we are going to depend on the pci_host_bridg

Re: [PATCH v3 2/2] ksm: provide support to use deferrable timers for scanner thread

Hi Hugh, Typically, on our setup we observed, 10% less power consumption with some use-cases in which CPU goes to power collapse frequently. For example, playing audio while typically CPU remains idle. I'm probably stupid, but I don't quite get your scenario from that description: please wou

Re: seccomp: add "seccomp" syscall

On Mon, Aug 11, 2014 at 1:07 PM, Geert Uytterhoeven wrote: > Hi Kees, > > v3.17 is gonna get a lot of new syscalls... 4 so far! :P > > On Wed, Aug 6, 2014 at 6:27 PM, Linux Kernel Mailing List > wrote: >> Gitweb: >> http://git.kernel.org/linus/;a=commit;h=48dc92b9fc3926844257316e75ba11eb5c

[PATCH] ata: remove deprecated struct ahci_platform_data

The last user of the deprecated struct ahci_platform_data has been cleaned up recently (SPEAr1340 got a proper PHY driver). Cc: Hans de Goede Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/ata/ahci_platform.c| 18 +- drivers/ata/libahci_platform.c | 23

Re: [PATCH v6 2/2] mmc: jz4740: prepare next dma transfer in parallel with current transfer

On 21 July 2014 06:37, Apelete Seketeli wrote: > Make use of the MMC asynchronous request capability to prepare the > next DMA transfer request in parallel with the current transfer. > This is done by adding pre-request and post-request callbacks that are > used by the MMC framework during an acti

Re: [PATCH 0/5] locks: move most locks_release_private calls outside of i_lock

On Tue, 12 Aug 2014 08:32:29 -0700 Christoph Hellwig wrote: > Btw, I might be missing something here, but wouldn't it be better > to reference count the file_lock structure and grab a reference to > it where we currently call (__)locks_copy_lock? > It's not really possible with the way this cod

Re: [PATCH v6 1/2] mmc: jz4740: add dma infrastructure for data transfers

On 21 July 2014 06:37, Apelete Seketeli wrote: > Until now the MMC driver for JZ4740 SoC was relying on PIO mode only > for data transfers. > This patch allows the use of DMA for data trasnfers in addition to PIO > mode by relying on DMA Engine. > > DMA tranfers performance might be further improv

Re: x86: vmalloc and THP

Hi Kirill, I saw the thread has developed nicely :), still - wanted to answer your question below. On 8/12/2014 9:07 AM, Kirill A. Shutemov wrote: On Tue, Aug 12, 2014 at 08:00:54AM +0300, Oren Twaig wrote: plain/text, please. Yes - noticed the html, sent again in plain text. If not, is

[PATCH 1/5] staging: android: ion: ion.c Fix checkpatch warning

This patch fix the coding style - Add a new line after variable declaration - Remove return of void fuction Tested by compilation Signed-off-by: Phong Tran --- drivers/staging/android/ion/ion.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/android/ion/ion.

Re: [PATCH] rpmsg: compute number of buffers to allocate from vrings

Hi Ohad, On 08/12/2014 10:30 AM, Ohad Ben-Cohen wrote: > Hi Suman, > > On Thu, Jul 3, 2014 at 11:53 PM, Suman Anna wrote: >> The buffers to be used for communication are allocated during >> the rpmsg virtio driver's probe, and the number of buffers is >> currently hard-coded to 512. Remove this

[PATCH 4/5] staging: android: ion: ion_carveout_heap.c Fix checkpatch warning

This patch fix coding style - Remove return of void function Tested by compilation Signed-off-by: Phong Tran --- drivers/staging/android/ion/ion_carveout_heap.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/android/ion/ion_carveout_heap.c b/drivers/staging/android/ion/ion

[PATCH 3/5] staging: android: ion: ion_system_heap.c Fix checkpatch warning

This patch fix coding rule - Remove return of void function Tested by compilation Signed-off-by: Phong Tran --- drivers/staging/android/ion/ion_system_heap.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/android/ion/ion_system_heap.c b/drivers/staging/android/ion/ion_syst

[PATCH 2/5] staging: android: ion: ion_chunk_heap.c Fix checkpatch warning

This patch fix coding style - Remove return of void function Tested by compilation Signed-off-by: Phong Tran --- drivers/staging/android/ion/ion_chunk_heap.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/android/ion/ion_chunk_heap.c b/drivers/staging/android/ion/ion_chunk

[PATCH 5/5] staging: android: ion: ion_dummy_driver.c Fix checkpatch warning

This patch fix coding style - Replace kzalloc() by kcalloc() - Remove return of void function Tested by compilation Signed-off-by: Phong Tran --- drivers/staging/android/ion/ion_dummy_driver.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/android/ion/io

staging: android: ion checkpatch.pl cleanups

Hi Greg, These patches fix checkpatch warning. Apply for staging-next branch. Regards, Phong. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please

[PATCH 0/5] MMC cleanup of dev_pm_ops and .owner

This series cleans up a few platform drivers in how they are declaring there dev_pm_ops structs, and gets rid of a few now redundant #else conditions. Also it removes the .owner field of drivers which use module_platform_driver api to register themselves, as this field gets overwritten. Peter Gri

[PATCH 2/5] mmc: dw_mmc-pci: Remove superflous #else condition on CONFIG_PM_SLEEP

As the code is using SIMPLE_DEV_PM_OPS helper, this compiles away to nothing if CONFIG_PM_SLEEP is disabled. Thus we don't need to #define the suspend/resume callbacks to NULL. Signed-off-by: Peter Griffin --- drivers/mmc/host/dw_mmc-pci.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/dr

[PATCH 4/5] mmc: sdhci-pci: Use SET_RUNTIME_PM_OPS macro to set runtime pm callbacks

This allows us to get rid of the #else condition, as the macro compiles away to nothing if not enabled. Signed-off-by: Peter Griffin --- drivers/mmc/host/sdhci-pci.c | 11 ++- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/drivers/mmc/host/sdhci-pci.c b/drivers/mmc/host/sd

[PATCH 3/5] mmc: dw_mmc-pltfm: Remove superflous #else condition on CONFIG_PM_SLEEP

As the code is using SIMPLE_DEV_PM_OPS helper, this compiles away to nothing if CONFIG_PM_SLEEP is disabled. Thus we don't need to #define the suspend/resume callbacks to NULL. Signed-off-by: Peter Griffin --- drivers/mmc/host/dw_mmc-pltfm.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/

[PATCH 5/5] mmc: sdhci-acpi.c: Use SET_RUNTIME_PM_OPS macro to set runtime pm callbacks

This allows us to get rid of the #else condition, as the macro compiles away to nothing if not enabled. Signed-off-by: Peter Griffin --- drivers/mmc/host/sdhci-acpi.c | 11 ++- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/drivers/mmc/host/sdhci-acpi.c b/drivers/mmc/host/

[PATCH 1/5] mmc: remove .owner field for drivers using module_platform_driver

This patch removes the superflous .owner field for drivers which use the module_platform_driver API, as this is overriden in platform_driver_register anyway. Signed-off-by: Peter Griffin --- drivers/mmc/host/jz4740_mmc.c | 1 - drivers/mmc/host/moxart-mmc.c | 1 - drivers/mmc/host/mxcm

Re: [PATCH] of: Deep-copy names of platform devices

On Aug 11, 2014, at 9:42 PM, Stepan Moskovchenko wrote: > When we parse the device tree and allocate platform > devices, the 'name' of the newly-created platform_device > is set to point to the 'name' field of the 'struct device' > embedded within the platform_device. This is dangerous, > becaus

Re: 3.16-rcX crashes on resume from Suspend-To-RAM

As I said earlier in this thread, echo'ing "devices" into "pm_test" does not result in a crash; but doing so for "platform" does. Markus On Aug 12, 2014 1:26 AM, "Zhang Rui" wrote: > > On Sat, 2014-08-09 at 03:14 -0700, Markus Gutschke wrote: > > I am back and have physical access to the machine

Re: [PATCH tip/core/rcu 1/2] rcu: Parallelize and economize NOCB kthread wakeups

On Tue, Aug 12, 2014 at 10:57:26AM +0530, Amit Shah wrote: > On (Mon) 11 Aug 2014 [13:34:21], Paul E. McKenney wrote: > > On Tue, Aug 12, 2014 at 01:48:45AM +0530, Amit Shah wrote: [ . . . ] > > > > In addition "sendkey alt-sysrq-t" at the "(qemu)" prompt dumps all > > > > tasks' > > > > stacks,

Re: [PATCH tip/core/rcu 1/2] rcu: Parallelize and economize NOCB kthread wakeups

On Tue, Aug 12, 2014 at 11:03:21AM +0530, Amit Shah wrote: > On (Mon) 11 Aug 2014 [20:45:31], Paul E. McKenney wrote: [ . . . ] > > > That is a bit surprising. Is it possible that the system is OOMing > > > quickly due to grace periods not proceeding? If so, maybe giving the > > > VM more memor

Re: Dual-channel DSI

Added DT maintainers as we have here quite fundamental DT question: How shall we model hardware connected to multiple buses, in DT? Here we have panel connected to two MIPI-DSI buses. Below is the summary of our propositions, followed by lengthly detailed discussion, including proposed bindings.

Re: [PATCH 3/3 v4 RESEND] ASoC: arizona: Add DVFS handling for sample rate control

On Tue, Aug 12, 2014 at 02:34:58PM +0100, Charles Keepax wrote: > On Fri, Aug 08, 2014 at 02:35:10PM +0100, Richard Fitzgerald wrote: > > From: Richard Fitzgerald > > Some codecs need to boost DVFS for higher sample rates. > > Signed-off-by: Richard Fitzgerald > > Signed-off-by: Charles Keepax

[PATCH] timekeeping: Another fix to the VSYSCALL_OLD update_vsyscall

Benjamin Herrenschmidt pointed out that I firuther missed modifying update_vsyscall after the wall_to_mono value was changed to a timespec64. This causes issues on powerpc32, which expects a 32bit timespec. This patch fixes the problem my properly converting from a timespec64 to a timespec before

[PATCH 4/4] Documentation/scheduler/sched-deadline.txt: add tests suite appendix

Add an appendix briefly describing tools that can be used to test SCHED_DEADLINE (and the scheduler in general). Links to where source code of the tools is hosted are also provided. Signed-off-by: Juri Lelli Cc: Randy Dunlap Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Henrik Austad Cc: Dario Fagg

[PATCH 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity

From: Luca Abeni Several small changes regarding SCHED_DEADLINE documentation that fix terminology and improve clarity and readability: - "current runtime" becomes "remaining runtime" - readablity of an equation is improved by introducing more spacing - clarify when admission control will c

[PATCH 0/4] SCHED_DEADLINE documentation fixes and improvements

Hello everyone, This small patchset fixes and improves SCHED_DEADLINE documentation. Patch 1/4 fixes and clarifies terminology; patch 2/4 aligns Section 4 to the current interface; patch 3/4 improves and clarifies what admission control means on UP an SMP systems; patch 4/4 introduces an appendix

[PATCH 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits

From: Luca Abeni Admission control is of key importance for SCHED_DEADLINE, since it guarantees system schedulability (or tells us something about the degree of guarantees we can provide to the user). This patch improves and clarifies bits and pieces regarding AC, both for UP and SMP systems. S

[PATCH 2/4] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro

Section 4 intro was still describing the old interface. Rewrite it. Signed-off-by: Juri Lelli Signed-off-by: Luca Abeni Cc: Randy Dunlap Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Henrik Austad Cc: Dario Faggioli Cc: Juri Lelli Cc: linux-...@vger.kernel.org Cc: linux-kernel@vger.kernel.org ---

Re: [PATCH] hugetlb_cgroup: use lockdep_assert_held rather than spin_is_locked

Michal Hocko writes: > spin_lock may be an empty struct for !SMP configurations and so > arch_spin_is_locked may return unconditional 0 and trigger the VM_BUG_ON > even when the lock is held. > > Replace spin_is_locked by lockdep_assert_held. We will not BUG anymore > but it is questionable wheth

Re: [PATCH 0/5] locks: move most locks_release_private calls outside of i_lock

Btw, I might be missing something here, but wouldn't it be better to reference count the file_lock structure and grab a reference to it where we currently call (__)locks_copy_lock? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger

Re: [PATCH] rpmsg: compute number of buffers to allocate from vrings

Hi Suman, On Thu, Jul 3, 2014 at 11:53 PM, Suman Anna wrote: > The buffers to be used for communication are allocated during > the rpmsg virtio driver's probe, and the number of buffers is > currently hard-coded to 512. Remove this hard-coded value, as > this can vary from one platform to another

Re: [tip:timers/core] timekeeping: Fixup typo in update_vsyscall_old definition

On 08/10/2014 09:19 PM, Benjamin Herrenschmidt wrote: > On Wed, 2014-07-30 at 00:31 -0700, tip-bot for John Stultz wrote: >> Commit-ID: 953dec21aed4038464fec02f96a2f1b8701a5bce >> Gitweb: >> http://git.kernel.org/tip/953dec21aed4038464fec02f96a2f1b8701a5bce >> Author: John Stultz >> Auth

Re: [PATCH 05/33] perf record: Allow the user to disable time stamps

Em Tue, Aug 12, 2014 at 04:58:19PM +0200, Ingo Molnar escreveu: > * Arnaldo Carvalho de Melo wrote: > > Em Tue, Aug 05, 2014 at 08:08:56AM +0200, Ingo Molnar escreveu: > > > This patch looks dangerous and misleading to me. > > I took it more from the angle: hey, it fixes a regression, i.e. > > -

Re: [RFC] ACPI: Add GPIO-signaled event simulator.

On Tue, Aug 12, 2014 at 07:15:41AM -0700, Alexandre Courbot wrote: > On Tue, Aug 12, 2014 at 3:01 AM, Mika Westerberg > wrote: > > On Fri, Aug 08, 2014 at 02:36:02PM +0200, Linus Walleij wrote: > >> On Thu, Jul 24, 2014 at 5:51 PM, Tomasz Nowicki > >> wrote: > >> > >> > GPIO signaled events is qu

Re: [alsa-devel] [PATCH v3] ASOC: dapm: add code to configure dai link parameters

On Mon, Aug 11, 2014 at 01:19:12PM +0100, Mark Brown wrote: > On Mon, Aug 11, 2014 at 11:54:29AM +0530, Vinod Koul wrote: > > On Thu, Aug 07, 2014 at 06:13:24PM +0100, Mark Brown wrote: > > > On Thu, Aug 07, 2014 at 07:46:05PM +0530, Vinod Koul wrote: > > > > > I was thinking about this as well a

Re: io-domain voltages as regulators?

Hi, On Mon, Aug 11, 2014 at 5:46 AM, Ulf Hansson wrote: > On 11 August 2014 09:44, Linus Walleij wrote: >> On Mon, Aug 4, 2014 at 12:18 AM, Heiko Stübner wrote: >> >> [Adding Ulf Hansson to this discussion...] >> >>> Hi Mark, Linus, >>> >>> I'd like to clarify what the appropriate way to handle

Re: [PATCH v4] kprobes: arm: enable OPTPROBES for ARM 32

(2014/08/12 22:03), Wang Nan wrote: > Hi Masami and everyone, > > When checking my code I found a problem: if we replace a stack operatinon > instruction, > it is possible that the emulate execution of such instruction destroy the > stack used > by kprobeopt: > >> + >> +asm ( >> +

[GIT PULL] Quota, reiserfs, udf updates for 3.17-rc1 (v2)

Hello Linus, could you please pull from git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus to get scalability improvements for quota, a few reiserfs fixes, and couple of misc cleanups (udf, ext2). Top of the tree is 01777836c870. The full shortlog is: Andy Shevchenko

[PATCH v2 3/3] ARM: EXYNOS: Fix build with PM_SLEEP=n and ARM_EXYNOS_CPUIDLE=y

Fix building of exynos_defconfig with CONFIG_PM_SLEEP disabled and CONFIG_ARM_EXYNOS_CPUIDLE enabled by: * adding EXYNOS_CPU_SUSPEND config option * building pm.o and sleep.o if EXYNOS_CPU_SUSPEND is enabled * moving suspend specific code from pm.c to suspend.c * enabling pm-common.o build also fo

[PATCH v2 2/3] ARM: mm: Fix ifdef around cpu_*_do_[suspend,resume] ops

Ifdef around cpu_\name\()_do_suspend and cpu_\name\()_do_resume ops in proc-macros.S should check for CONFIG_ARM_CPU_SUSPEND and not CONFIG_PM_SLEEP. Fix it. [ Please note that cpu_v7_do_[suspend,resume] code in proc-v7.S already correctly checks for CONFIG_ARM_CPU_SUSPEND, same is true for f

[PATCH v2 0/3] ARM: EXYNOS: Fix builds with PM_SLEEP=n

Hi, This patch series fixes builds with CONFIG_PM_SLEEP config option disabled. It has been runtime tested on Exynos4210 based Origen board. Depends on: - next-20140811 branch of linux-next kernel Changes since v1: (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34079.html) -

[PATCH v2 1/3] ARM: EXYNOS: Fix build with PM_SLEEP=n and ARM_EXYNOS_CPUIDLE=n

Fix building of exynos_defconfig with disabled CONFIG_PM_SLEEP by adding checking whether Exynos cpuidle support is enabled before accessing exynos_enter_aftr. The build error message: arch/arm/mach-exynos/built-in.o:(.data+0x74): undefined reference to `exynos_enter_aftr' make: *** [vmlinux] Err

Re: [PATCH] resource: Fix the case of null pointer access

On Tue, Aug 12, 2014 at 04:49:35PM +0200, Richard Weinberger wrote: > Am 12.08.2014 16:46, schrieb Vivek Goyal: > > Richard and Daniel reported that UML is broken due to changes to resource > > traversal functions. Problem is that iomem_resource.child can be null > > and new code does not consider

[PATCH v2 1/1] virtio: rng: add derating factor for use by hwrng core

The khwrngd thread is started when a hwrng device of sufficient quality is registered. The virtio-rng device is backed by the hypervisor, and we trust the hypervisor to provide real entropy. A malicious hypervisor is a scenario that's irrelevant -- such a setup is bound to cause all sorts of badn

[PATCH 1/4] perf tools: Fix CLOEXEC probe for perf_event_paranoid == 2

With /proc/sys/kernel/perf_event_paranoid set to 2, the probe of PERF_FLAG_FD_CLOEXEC would fail. Fix by excluding kernel profiling from the probe event. Signed-off-by: Adrian Hunter --- tools/perf/util/cloexec.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/util/cloexec.c b/to

[PATCH 2/4] perf tools: Fix one of the probe events to exclude kernel

When probing the kernel API the kernel should be excluded otherwise the probe will fail for users with insufficient privilege to profile the kernel. Signed-off-by: Adrian Hunter --- tools/perf/util/record.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/util/recor

[PATCH 0/4] perf tools: API probing fixes

Hi Here are some fixes for API probing issues that I have run into, and a second attempt at the jump-label problem. Patches apply to your tmp.perf/core branch. Adrian Hunter (4): perf tools: Fix CLOEXEC probe for perf_event_paranoid == 2 perf tools: Fix one of the probe events to ex

[PATCH 3/4] perf tools: Fix probing the kernel API with cpu-wide events

Fall back to probing with the current pid if cpu-wide probing fails. This primarily affects the setting of comm_exec flag when the user is un-privileged and /proc/sys/kernel/perf_event_paranoid > 0. The change to comm_exec can be observed by using -vv with perf record and a kernel that supports c

[PATCH 4/4] perf tools: Prefer to use a cpu-wide event for probing CLOEXEC

When doing a system-wide trace with Intel PT, the jump label set up as a result of probing CLOEXEC gets reset while the trace is running. That causes an Intel PT decoding error because the object code (obtained from /proc/kcore) does not match the running code at that point. While we can't expect

Re: [PATCH 6/7] arm: mediatek: enable gpt6 on boot up to make arch timer working

On Tue, Aug 12, 2014 at 4:02 AM, Matthias Brugger wrote: > 2014-08-11 9:15 GMT+02:00 Linus Walleij : >> On Thu, Jul 31, 2014 at 6:42 PM, Matthias Brugger >> wrote: >> >>> We enable GTP6 which ungates the arch timer clock. Apart we write the >>> frequency with which the timer is running in the CNT

Re: x86: vmalloc and THP

On Tue, Aug 12, 2014 at 05:28:52AM -0700, Eric Dumazet wrote: > On Tue, 2014-08-12 at 09:07 +0300, Kirill A. Shutemov wrote: > > On Tue, Aug 12, 2014 at 08:00:54AM +0300, Oren Twaig wrote: > > >If not, is there any fast way to change this behavior ? Maybe by > > >changing the granularity/alignment

[tip:sched/core] sched: Rename a misleading variable in build_overlap_sched_groups()

Commit-ID: aaecac4ad46b35ad308245384d019633fb9bc21b Gitweb: http://git.kernel.org/tip/aaecac4ad46b35ad308245384d019633fb9bc21b Author: Zhihui Zhang AuthorDate: Fri, 1 Aug 2014 21:18:03 -0400 Committer: Ingo Molnar CommitDate: Tue, 12 Aug 2014 12:48:21 +0200 sched: Rename a misleading v

Re: [PATCH 1/1] virtio: rng: add derating factor for use by hwrng core

On 08/11/2014 10:27 PM, Amit Shah wrote: > On (Mon) 11 Aug 2014 [15:11:03], H. Peter Anvin wrote: >> On 08/11/2014 11:49 AM, Amit Shah wrote: >>> The khwrngd thread is started when a hwrng device of sufficient >>> quality is registered. The virtio-rng device is backed by the >>> hypervisor, and we

Re: [sched] 143e1e28cb4: +17.9% aim7.jobs-per-min, -9.7% hackbench.throughput

. Sent using Boxer On Aug 10, 2014 8:23 PM, Fengguang Wu wrote: > > On Sun, Aug 10, 2014 at 05:05:03PM +0200, Peter Zijlstra wrote: > > On Sun, Aug 10, 2014 at 06:54:13PM +0800, Fengguang Wu wrote: > > > The "brickland1/aim7/6000-page_test" is the test case part. > > > > > > The "TOTAL XXX"

Re: [PATCH] staging: lustre: lustre: libcfs: workitem.c: Cleaning up missing null-terminate after strncpy call

On Sat, Aug 9, 2014 at 4:46 PM, Rickard Strandqvist wrote: > Added a guaranteed null-terminate after call to strncpy. > > Signed-off-by: Rickard Strandqvist > --- > drivers/staging/lustre/lustre/libcfs/workitem.c |1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/staging/lustre/

Re: [PATCH 05/33] perf record: Allow the user to disable time stamps

* Arnaldo Carvalho de Melo wrote: > Em Tue, Aug 05, 2014 at 08:08:56AM +0200, Ingo Molnar escreveu: > > * Arnaldo Carvalho de Melo wrote: > > > From: Andi Kleen > > > This patch looks dangerous and misleading to me. > > I took it more from the angle: hey, it fixes a regression, i.e. > -T/-

[tip:sched/core] sched/fair: Allow calculate_imbalance() to move idle cpus

Commit-ID: 9a5d9ba6a3631d55c358fe1bdbaa162a97471a05 Gitweb: http://git.kernel.org/tip/9a5d9ba6a3631d55c358fe1bdbaa162a97471a05 Author: Peter Zijlstra AuthorDate: Tue, 29 Jul 2014 17:15:11 +0200 Committer: Ingo Molnar CommitDate: Tue, 12 Aug 2014 12:48:20 +0200 sched/fair: Allow calcula

Re: [PATCH] tcp: don't use timestamp from repaired skb-s to calculate RTT

On Tue, Aug 12, 2014 at 2:45 AM, Andrey Vagin wrote: > We don't know right timestamp for repaired skb-s. Wrong RTT estimations > isn't good, because some congestion modules heavily depends on it. > > This patch adds the TCPCB_REPAIRED flag, which is included in > TCPCB_RETRANS. > > Thanks to Eric

[tip:sched/core] sched/numa: Fix off-by-one in capacity check

Commit-ID: b932c03c34f3b03c7364c06aa8cae5b74609fc41 Gitweb: http://git.kernel.org/tip/b932c03c34f3b03c7364c06aa8cae5b74609fc41 Author: Rik van Riel AuthorDate: Mon, 4 Aug 2014 13:23:27 -0400 Committer: Ingo Molnar CommitDate: Tue, 12 Aug 2014 12:48:22 +0200 sched/numa: Fix off-by-one i

[tip:sched/core] sched/fair: Make update_sd_pick_busiest() return 'true' on a busier sd

Commit-ID: caeb178c60f4f93f1b45c0bc056b5cf6d217b67f Gitweb: http://git.kernel.org/tip/caeb178c60f4f93f1b45c0bc056b5cf6d217b67f Author: Rik van Riel AuthorDate: Mon, 28 Jul 2014 14:16:28 -0400 Committer: Ingo Molnar CommitDate: Tue, 12 Aug 2014 12:48:19 +0200 sched/fair: Make update_sd_

[tip:sched/core] sched/numa: Fix numa capacity computation

Commit-ID: 83d7f2424741c9dc76c21377c9d00d47abaf88df Gitweb: http://git.kernel.org/tip/83d7f2424741c9dc76c21377c9d00d47abaf88df Author: Rik van Riel AuthorDate: Mon, 4 Aug 2014 13:23:28 -0400 Committer: Ingo Molnar CommitDate: Tue, 12 Aug 2014 12:48:23 +0200 sched/numa: Fix numa capacit

[tip:sched/core] sched/fair: Make calculate_imbalance() independent

Commit-ID: 743cb1ff191f00fee653212bdbcee1e56086d6ce Gitweb: http://git.kernel.org/tip/743cb1ff191f00fee653212bdbcee1e56086d6ce Author: Peter Zijlstra AuthorDate: Tue, 29 Jul 2014 17:00:21 +0200 Committer: Ingo Molnar CommitDate: Tue, 12 Aug 2014 12:48:18 +0200 sched/fair: Make calculat

RE: [RFC PATCH 01/10] scsi/constants: Cleanup printk message in __scsi_print_sense()

> -Original Message- > From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi- > ow...@vger.kernel.org] On Behalf Of Yoshihiro YUNOMAE > Sent: Friday, 08 August, 2014 6:50 AM ... > Subject: [RFC PATCH 01/10] scsi/constants: Cleanup printk message in > __scsi_print_sense() > > A device

Re: [PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

* xiaofeng.yan wrote: > It could be wrong for the precision of runtime and deadline > when the precision is within microsecond level. For example: > Task runtime deadline period > P1 200us 500us 500us > > This case need enbale HRTICK feature by the next command > > PC#echo "HRTICK" > /sy

[PATCH 1/5] locks: don't call locks_release_private from locks_copy_lock

All callers of locks_copy_lock pass in a brand new file_lock struct, so there's no need to calls locks_release_private on it. Replace that with a warning that fires in the event that we receive a target lock that doesn't look like it's properly initialized. Signed-off-by: Jeff Layton --- fs/lock

Re: [PATCH] resource: Fix the case of null pointer access

Am 12.08.2014 16:46, schrieb Vivek Goyal: > Richard and Daniel reported that UML is broken due to changes to resource > traversal functions. Problem is that iomem_resource.child can be null > and new code does not consider that possibility. Old code used a for loop > and that loop will not even exe

[PATCH 3/5] locks: defer freeing locks in locks_delete_lock until after i_lock has been dropped

In commit 72f98e72551fa (locks: turn lock_flocks into a spinlock), we moved from using the BKL to a global spinlock. With this change, we lost the ability to block in the fl_release_private operation. This is problematic for NFS (and probably some other filesystems as well). Add a new list_head ar

<    1   2   3   4   5   6   7   >