Re: [PATCH] mm: cache largest vma

* Davidlohr Bueso wrote: > I will look into doing the vma cache per thread instead of mm (I hadn't > really looked at the problem like this) as well as Ingo's suggestion on > the weighted LRU approach. However, having seen that we can cheaply and > easily reach around ~70% hit rate in a lot o

service desk

Mailbox is full, 00.1 GB, Please reduce your mailbox size. Delete any items you don't need from your mailbox and expand your email quota (size) with the below web links: HERE: http://actlogistic.co.uk/ Thank you for your understanding. ©2013 Helpdesk -- To unsubscribe from this list: send the

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

(2013/10/31 22:27), Vivek Goyal wrote: On Wed, Oct 30, 2013 at 06:58:13PM -0600, jerry.hoem...@hp.com wrote: [..] Daisuke, Are you planning on making changes to the kexec tools to automate the setting of disable_cpu_apic to the capture kernel? Or do you know someone who is planning this? I t

Re: [RFC 04/12] phy: Add simple-phy driver

Hi, On Friday 25 October 2013 01:21 PM, Tomasz Stanislawski wrote: Hi, Please refer to the comments below. On 10/24/2013 05:52 PM, Kishon Vijay Abraham I wrote: Hi, On Monday 21 October 2013 07:48 PM, Tomasz Stanislawski wrote: Add simple-phy driver to support a single register PHY interface

Re: [PATCH] mm: cache largest vma

* Davidlohr Bueso wrote: > Btw, do you suggest using a high level tool such as perf for getting > this data or sprinkling get_cycles() in find_vma() -- I'd think that the > first isn't fine grained enough, while the later will probably variate a > lot from run to run but the ratio should be r

Re: [PATCH] mm: cache largest vma

On Sun, Nov 03, 2013 at 10:51:27AM -0800, Linus Torvalds wrote: > Ugh. This patch makes me angry. It looks way too ad-hoc. > > I can well imagine that our current one-entry cache is crap and could > be improved, but this looks too random. Different code for the > CONFIG_MMU case? Same name, but fo

Re: [PATCH] mm: cache largest vma

* Davidlohr Bueso wrote: > On Sun, 2013-11-03 at 11:12 +0100, Ingo Molnar wrote: > > * Davidlohr Bueso wrote: > > > > > While caching the last used vma already does a nice job avoiding > > > having to iterate the rbtree in find_vma, we can improve. After > > > studying the hit rate on a load o

Re: [REVIEW][PATCH 1/2] userns: Better restrictions on when proc and sysfs can be mounted

On Sat, Nov 2, 2013 at 8:06 AM, Gao feng wrote: > And another question, it looks like if we don't have proc/sys fs mounted, > then proc/sys will be failed to be mounted? I have been wondering the same. Was quite some illogical surprise that we have to be doing overlay mounts. This is the exact o

linux-next: Tree for Nov 4

Hi all, Changes since 20131101: The squashfs tree lost its build failure. The sound-asoc tree gained a build failure for which I reverted a commit. The modules tree introduced a very large number of warnings so I used the version from next-20131101. The block tree still had its build failure s

[PATCH v4] ASoC: Add pinctrl PM to components of active DAIs

It's quite popular that more drivers are using pinctrl PM, for example: (Documentation/devicetree/bindings/arm/primecell.txt). Just like what runtime PM does, it would deactivate and activate pin group depending on whether it's being used or not. And this pinctrl PM might be also beneficial to cpu

[tip:perf/core] perf test: Update command line callchain attribute tests

Commit-ID: 46d525eae2a076adfde92dca1db12d9a3b8ad8bb Gitweb: http://git.kernel.org/tip/46d525eae2a076adfde92dca1db12d9a3b8ad8bb Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 31 Oct 2013 09:46:59 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Nov 2013 10:42:57 -0300 per

Re: [PATCH RFC 1/4] phy: Add new Exynos5 USB 3.0 PHY driver

Hi Vivek, On Thursday 31 October 2013 01:15 PM, Vivek Gautam wrote: Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs. The new driver uses the generic PHY framework and will interact with DWC3 controller present on Exynos5 series of SoCs. In Exynos, you have a single IP that suppo

[tip:perf/core] perf bench: Fix two warnings

Commit-ID: 32bf5bd181026fc99c0e15045abe409167285ba8 Gitweb: http://git.kernel.org/tip/32bf5bd181026fc99c0e15045abe409167285ba8 Author: Wei Yang AuthorDate: Sun, 22 Sep 2013 16:49:24 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Nov 2013 10:41:54 -0300 perf bench: Fix two

[tip:perf/core] perf tools: Remove cast of non-variadic function to variadic

Commit-ID: 53805eca3d89b095062c11a6798689bb0af09216 Gitweb: http://git.kernel.org/tip/53805eca3d89b095062c11a6798689bb0af09216 Author: Michael Hudson-Doyle AuthorDate: Thu, 31 Oct 2013 16:47:45 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Nov 2013 10:40:51 -0300 perf to

Re: [PATCH] x86: Allow NR_CPUS=1024

* Josh Boyer wrote: > On Sun, Nov 03, 2013 at 11:21:32AM +0100, Ingo Molnar wrote: > > > > * Ingo Molnar wrote: > > > > > > > > * Josh Boyer wrote: > > > > > > > The current range for SMP configs is 2 - 512, or a full 4096 in the > > > > case > > > > of MAXSMP. There are machines that h

linux-next: build failure after merge of the final tree

Hi all, After merging the final tree, today's linux-next build (powerpc allyesconfig) failed like this: sound/soc/soc-pcm.c: In function 'soc_pcm_open': sound/soc/soc-pcm.c:186:2: error: implicit declaration of function 'pinctrl_pm_select_default_state' [-Werror=implicit-function-declaration]

Re: [PATCH] x86: Allow NR_CPUS=1024

* H. Peter Anvin wrote: > On 11/03/2013 07:57 AM, Josh Boyer wrote: > > > > OK, that makes sense. So in this scenario, we could probably either: > > > > a) do away with MAXSMP entirely and just depend on > > CONFIG_CPUMASK_OFFSTACK. > > > > b) make MAXSMP something even higher than 4096. Li

Re: [GIT PULL 0/3] perf/urgent fixes

* Arnaldo Carvalho de Melo wrote: > From: Arnaldo Carvalho de Melo > > Hi Ingo, > > Please consider pulling, > > - Arnaldo > > The following changes since commit e8a923cc1fff6e627f906655ad52ee694ef2f6d7: > > perf/x86: Fix NMI measurements (2013-10-29 12:01:20 +0100) > > are availa

Re: [PATCH v2 8/9] phy: add Broadcom Kona USB2 PHY driver

Hi, On Saturday 02 November 2013 01:15 AM, Matt Porter wrote: Add a driver for the internal Broadcom Kona USB 2.0 PHY found on the BCM281xx family of SoCs. Signed-off-by: Matt Porter --- drivers/phy/Kconfig | 6 ++ drivers/phy/Makefile| 2 + drivers/phy/phy-bcm-

Re: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?

* Linus Torvalds wrote: > So I may be pessimistic, but I'd expect many developers would go "Let's > hunt bugs.. Wait. Oooh, shiny" and go off doing some new feature after > all instead. Or just take that release off. > > But I do wonder.. Maybe it would be possible, and I'm just unfairly > p

Fwd: [PATCH v2] kernel/resource.c: use signed length comparing instead of position comparing

Sorry, forgot to cc linux-kernel. Original Message Subject: [PATCH v2] kernel/resource.c: use signed length comparing instead of position comparing Date: Mon, 04 Nov 2013 11:05:30 +0800 From: Chen Gang To: Toshi Kani , "isimatu.yasu...@jp.fujitsu.com" , gong.c...@linux.inte

Re: [PATCH v2 1/9] phy: add phy_get_bus_width()/phy_set_bus_width() calls

Hi, On Saturday 02 November 2013 11:28 PM, Tomasz Figa wrote: On Saturday 02 of November 2013 13:47:09 Matt Porter wrote: On Sat, Nov 02, 2013 at 10:46:55PM +0530, Kishon Vijay Abraham I wrote: Hi Tomasz, On Saturday 02 November 2013 06:44 PM, Tomasz Figa wrote: Hi Matt, On Friday 01 of Nov

linux-next: manual merge of the random tree with Linus' tree

Hi Ted, Today's linux-next merge of the random tree got a conflict in drivers/base/core.c between commit 63967685605b ("driver core: add #include to core files") from Linus' tree and commit f0ed2b943a53 ("random: use device attach events for entropy") from the random tree. I fixed it up (see bel

[GIT] Networking

I'm sending a pull request of these lingering bug fixes for networking before the normal merge window material because some of this stuff I'd like to get to -stable ASAP. 1) cxgb3 stopped working on 32-bit machines, fix from Ben Hutchings. 2) Structures passed via netlink for netfilter logging a

[PATCH] ARM: imx: removed unused MACH_MXLADS Kconfig parameter

This removes the MACH_MXLADS Kconfig parameter, which was no longer used anywhere in the source code and Makefiles. Signed-off-by: Michael Opdenacker --- arch/arm/mach-imx/Kconfig | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig index 29

dm-writeboost: Progress Report

Hi, DM Guys Let me share a new progress report. I am sorry I have been off for weeks. Writeboost is getting better I believe. Many progress, please git pull https://github.com/akiradeveloper/dm-writeboost.git 1. Removing version switch macros Previously the code included 10 or more version swit

Re: [RFC 4/9] of/irq: Refactor interrupt-map parsing

On Fri, Nov 01, 2013 at 11:54:01AM -0700, Grant Likely wrote: > On Fri, 01 Nov 2013 10:53:17 -0700, Grant Likely > wrote: > > On Thu, 31 Oct 2013 11:57:14 -0700, Olof Johansson wrote: > > > On Wed, Oct 30, 2013 at 02:25:21PM -0700, Grant Likely wrote: > > > > (Sorry for HTML mail) > > > > > > >

linux-next: build warning after merge of the infiniband tree

Hi all, After merging the infiniband tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/infiniband/hw/ipath/ipath_user_sdma.c: In function 'ipath_user_sdma_pin_pages': drivers/infiniband/hw/ipath/ipath_user_sdma.c:283:6: warning: 'j' is used uninitialized in thi

converting unicore32 to gate_vma as done for arm (was Re: [PATCH] mm: cache largest vma)

On Sun, Nov 03, 2013 at 08:20:10PM -0800, Davidlohr Bueso wrote: > > > diff --git a/arch/unicore32/include/asm/mmu_context.h > > > b/arch/unicore32/include/asm/mmu_context.h > > > index fb5e4c6..38cc7fc 100644 > > > --- a/arch/unicore32/include/asm/mmu_context.h > > > +++ b/arch/unicore32/include/

linux-next: manual merge of the dt-rh tree with the imx-mxs tree

Hi Rob, Today's linux-next merge of the dt-rh tree got a conflict in Documentation/devicetree/bindings/vendor-prefixes.txt between commit 064d7f6c985a ("ARM: dts: Add vendor prefix for Voipac Technologies s.r.o") from the imx-mxs tree and commit d6c3073e7fb5 ("DT: sort vendor-prefixes.txt") from t

Re: [PATCH] [extcon]:remove freed groups caused the panic or warning in unregister flow

On 11/04/2013 12:47 PM, Liu, Chuansheng wrote: > > >> -Original Message- >> From: Chanwoo Choi [mailto:cw00.c...@samsung.com] >> Sent: Monday, November 04, 2013 10:37 AM >> To: Wang, Xiaoming >> Cc: myungjoo@samsung.com; linux-kernel@vger.kernel.org; Liu, >> Chuansheng; Zhang, Dongxin

Re: [PATCH] mm: cache largest vma

On Sun, 2013-11-03 at 18:57 -0500, KOSAKI Motohiro wrote: > >> I'm slightly surprised this cache makes 15% hit. Which application > >> get a benefit? You listed a lot of applications, but I'm not sure > >> which is highly depending on largest vma. > > > > Well I chose the largest vma because it giv

Re: [PATCH] mm: cache largest vma

On Sun, 2013-11-03 at 11:12 +0100, Ingo Molnar wrote: > * Davidlohr Bueso wrote: > > > While caching the last used vma already does a nice job avoiding > > having to iterate the rbtree in find_vma, we can improve. After > > studying the hit rate on a load of workloads and environments, > > it was

Re: [PATCH] mm: cache largest vma

On Sun, 2013-11-03 at 10:51 -0800, Linus Torvalds wrote: > Ugh. This patch makes me angry. It looks way too ad-hoc. > > I can well imagine that our current one-entry cache is crap and could > be improved, but this looks too random. Indeed, my approach is random *because* I wanted to keep things

Re: [PATCH 0/4] per anon_vma lock and turn anon_vma rwsem lock to rwlock_t

On Fri, Nov 01, 2013 at 08:15:13PM -0700, Davidlohr Bueso wrote: > On Fri, 2013-11-01 at 18:16 +0800, Yuanhan Liu wrote: > > On Fri, Nov 01, 2013 at 09:21:46AM +0100, Ingo Molnar wrote: > > > > > > * Yuanhan Liu wrote: > > > > > > > > Btw., another _really_ interesting comparison would be agains

[PATCH] tpm: tpm_tis: Fix compile problems with CONFIG_PM_SLEEP/CONFIG_PNP

If CONFIG_PM_SLEEP=n, CONFIG_PNP=y we get this warning: drivers/char/tpm/tpm_tis.c:706:13: warning: 'tpm_tis_reenable_interrupts' defined but not used [-Wunused-function] This seems to have been introduced in a2fa3fb0d 'tpm: convert tpm_tis driver to use dev_pm_ops from legacy pm_ops' Also, unp

RE: [PATCH] [extcon]:remove freed groups caused the panic or warning in unregister flow

> -Original Message- > From: Chanwoo Choi [mailto:cw00.c...@samsung.com] > Sent: Monday, November 04, 2013 10:37 AM > To: Wang, Xiaoming > Cc: myungjoo@samsung.com; linux-kernel@vger.kernel.org; Liu, > Chuansheng; Zhang, Dongxing > Subject: Re: [PATCH] [extcon]:remove freed groups cau

Re: [PATCH] tpm/tpm_i2c_stm_st33: Check return code of get_burstcount (fix CID: 986658)

On Tue, 2013-10-29 at 20:07 -0700, Greg KH wrote: > On Wed, Oct 30, 2013 at 01:42:11AM +0100, Peter Hüwe wrote: > > Hi Greg, > > > > > > > > CID: 986658 > > > What is this field for? > > > > That's the scan id in the coverity database. > > If you think that's just noise I can leave it out. > > I

[PATCH 1/5 v2] tpm: Pull everything related to /dev/tpmX into tpm-dev.c

CLASS-dev.c is a common idiom for Linux subsystems This pulls all the code related to the miscdev into tpm-dev.c and makes it static. The identical file_operation structs in the drivers are purged and the tpm common code unconditionally creates the miscdev. Signed-off-by: Jason Gunthorpe Reviewe

[PATCH 2/5 v2] tpm: Pull everything related to sysfs into tpm-sysfs.c

CLASS-sysfs.c is a common idiom for linux subsystems. This pulls all the sysfs attribute functions and related code into tpm-sysfs.c. To support this change some constants are moved from tpm.c to tpm.h and __tpm_pcr_read is made non-static and is called tpm_pcr_read_dev. Signed-off-by: Jason Gunt

tpm: Remainder of earlier clean up

Here is the last five patches from the prior series I sent that didn't get picked up yet. There are no changes, these are just rebased onto 3.12rc7 + Peter's for-james branch. (Peter: Note, there are TPM changes to the Xen driver in 3.12rc7 that are not in your for-james branch) The intent of the

[PATCH 5/5 v2] tpm: Make tpm-dev allocate a per-file structure

This consolidates everything that is only used within tpm-dev.c into tpm-dev.c and out of the publicly visible struct tpm_chip. The per-file allocation lays the ground work for someday fixing the strange forced O_EXCL behaviour of the current code. Signed-off-by: Jason Gunthorpe Reviewed-by: Joe

[PATCH 3/5 v2] tpm: Create a tpm_class_ops structure and use it in the drivers

This replaces the static initialization of a tpm_vendor_specific structure in the drivers with the standard Linux idiom of providing a const structure of function pointers. Signed-off-by: Jason Gunthorpe Reviewed-by: Joel Schopp --- drivers/char/tpm/tpm-interface.c| 10 -- drivers/c

Re: linux-next: build failure after merge of the block tree

Hi Jens, On Sun, 3 Nov 2013 20:23:41 -0700 Jens Axboe wrote: > > Don't have ppc64 cross compiling handy, but the below should do the https://www.kernel.org/pub/tools/crosstool/ > trick. That patch fixes it for me. Compile-tested-by: Stephen Rothwell -- Cheers, Stephen Rothwell

[PATCH 4/5 v2] tpm: Use the ops structure instead of a copy in tpm_vendor_specific

This builds on the last commit to use the ops structure in the core and reduce the size of tpm_vendor_specific. Signed-off-by: Jason Gunthorpe Reviewed-by: Joel Schopp --- drivers/char/tpm/tpm-interface.c| 34 -- drivers/char/tpm/tpm-sysfs.c| 2 +- d

Re: [PATCH 4/4] mm/rmap.c: move anon_vma initialization code into anon_vma_ctor

On Fri, Nov 01, 2013 at 11:04:40AM -0700, Linus Torvalds wrote: > On Fri, Nov 1, 2013 at 12:54 AM, Yuanhan Liu > wrote: > > @@ -67,19 +67,7 @@ static struct kmem_cache *anon_vma_chain_cachep; > > > > static inline struct anon_vma *anon_vma_alloc(void) > > { > > - struct anon_vma *anon_vma;

Re: linux-next: build failure after merge of the block tree

On Sun, Nov 03 2013, Jens Axboe wrote: > On Mon, Nov 04 2013, Stephen Rothwell wrote: > > Hi Jens, > > > > [I merged the block tree *before* the aio-direct tree today ...] > > > > After merging the block tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In fi

[PATCH] mm: improve the description for dirty_background_ratio/dirty_ratio sysctl

From: Zheng Liu Now dirty_backgraound_ratio/dirty_ratio contains a percentage of total avaiable memory, which contains free pages and reclaimable pages. The number of these pages is not equal to the number of total system memory. But they are described as a percentage of total system memory in

Re: [PATCH 1/2] Tick: Introduce tick_nohz_check() to check nohz enable status

On 2013年10月29日 18:29, Lan Tianyu wrote: > On 10/29/2013 05:51 PM, Paul E. McKenney wrote: >> On Tue, Oct 29, 2013 at 04:48:56PM +0800, Lan Tianyu wrote: >>> In some cases, nohz enable status needs to be checked. E.G, in RCU >>> and cpufreq >>> ondemand governor. So add tick_nohz_check() to return >

Re: [PATCH v2 04/13] uprobes: allow arch-specific initialization

On 11/01/13 09:52, Oleg Nesterov wrote: On 10/31, David Long wrote: On 10/28/13 14:58, Oleg Nesterov wrote: On 10/22, David Long wrote: I simply do not understand why uprobes.c uses module_init/module_exit, it can't be compiled as a module. I guess that makes sense, assuming it can never be m

Re: linux-next: build failure after merge of the block tree

On Mon, Nov 04 2013, Stephen Rothwell wrote: > Hi Jens, > > [I merged the block tree *before* the aio-direct tree today ...] > > After merging the block tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/linux/blkdev.h:18:0, >

linux-next: build failure after merge of the block tree

Hi Jens, [I merged the block tree *before* the aio-direct tree today ...] After merging the block tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/linux/blkdev.h:18:0, from drivers/block/ps3disk.c:22: drivers/block/ps3disk.

Re: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?

On Sun, Nov 3, 2013 at 4:10 PM, Linus Torvalds wrote: > And the reason I mention "4.0" is that it would be a lovely time to do > that. Roughly a years heads-up that "ok, after 3.19 (or whatever), > we're doing a release with *just* fixes, and then that becomes 4.0". > > Comments? Unless you are p

Re: [ 00/32] 3.4.68-stable review

At Fri, 1 Nov 2013 14:43:11 -0700, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.4.68 release. > There are 32 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. >

linux-next: build warnings after merge of the modules tree

Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) produced these warning: WARNING: vmlinux: 'pci_restore_msi_state' exported twice. Previous export was in vmlinux WARNING: vmlinux: '__mod_zone_page_state' exported twice. Previous export was in vmlinux WARN

Re: [PATCH] [extcon]:remove freed groups caused the panic or warning in unregister flow

On 11/04/2013 11:07 AM, Wang, Xiaoming wrote: > Dear Choi > > -Original Message- > From: Chanwoo Choi [mailto:cw00.c...@samsung.com] > Sent: Monday, November 04, 2013 9:43 AM > To: Wang, Xiaoming > Cc: myungjoo@samsung.com; linux-kernel@vger.kernel.org; Liu, Chuansheng; > Zhang, Dong

Re: [PATCH] xfs: simplify kmem_{zone_}zalloc

Hi Dave, On 11/02/2013 04:58 AM, Dave Chinner wrote: > On Fri, Nov 01, 2013 at 06:25:11PM +0800, Gu Zheng wrote: >> Introduce flag KM_ZERO which is used to alloc zeroed entry, and convert >> kmem_{zone_}zalloc to call kmem_{zone_}alloc() with KM_ZERO directly, >> in order to avoid the setting to z

[f2fs-dev] [PATCH] f2fs: remove unnecessary TestClearPageError when wait pages writeback

In wait_on_node_pages_writeback we will test and clear error flag for all pages in radix tree, but not necessary. So we only do this for pages belong to the specified inode. Signed-off-by: Chao Yu --- fs/f2fs/node.c |7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/f

RE: [PATCH] [extcon]:remove freed groups caused the panic or warning in unregister flow

Dear Choi -Original Message- From: Chanwoo Choi [mailto:cw00.c...@samsung.com] Sent: Monday, November 04, 2013 9:43 AM To: Wang, Xiaoming Cc: myungjoo@samsung.com; linux-kernel@vger.kernel.org; Liu, Chuansheng; Zhang, Dongxing Subject: Re: [PATCH] [extcon]:remove freed groups caused

Re: [PATCH] mfd: max77693: Fix up bug of wrong interrupt number

Ping! Thanks, Chanwoo Choi On 10/10/2013 10:05 AM, Chanwoo Choi wrote: > The max77693 MFD device use irq domain method which has hardware interrupt > number > and virtual interrupt number getting through irq domain mapping. This patch > use hardware interrupt number instead of virtual interrupt

[PATCHv3 0/3] ARM: dts: exynos: Add missing dt data to bring up kernel featurea

This patchset add missing dt data to bring up kernel feature - GPS_ALIVE power domain - PMU - Clock data for Multi core timer Changes since v2: - Delete MAUDIO power domain Changes since v1: - Fix wrong address of GPS_ALIVE power domain Chanwoo Choi (2): ARM: dts: exynos4212: Add PMU dt data f

[PATCHv3 3/3] ARM: dts: exynos4x12: Add gps_alive power domain for exynos4x12

This patch gps_alive power domain to exynos4x12.dtsi. Signed-off-by: Chanwoo Choi Signed-off-by: Kyungmin Park --- arch/arm/boot/dts/exynos4x12.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/exynos4x12.dtsi b/arch/arm/boot/dts/exynos4x12.dtsi index ad531fe..3f5

[PATCHv3 1/3] ARM: dts: exynos4212: Add PMU dt data for pmu-irq

Signed-off-by: Chanwoo Choi Signed-off-by: Kyungmin Park --- arch/arm/boot/dts/exynos4212.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/exynos4212.dtsi b/arch/arm/boot/dts/exynos4212.dtsi index 6f34d7f..3081bae 100644 --- a/arch/arm/boot/dts/exynos4212.dtsi ++

[PATCHv3 2/3] ARM: dts: exynos4212: Add missing clock for multi core timer

From: Marek Szyprowski Signed-off-by: Marek Szyprowski Signed-off-by: Kyungmin Park --- arch/arm/boot/dts/exynos4212.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/exynos4212.dtsi b/arch/arm/boot/dts/exynos4212.dtsi index 3081bae..d7a3fbc 100644 --- a/arch/arm/bo

Re: [PATCH] [extcon]:remove freed groups caused the panic or warning in unregister flow

Hi Wang, > drivers/extcon/extcon-class.c |3 ++- > 1 files changed, 2 insertions(+), 1 deletions(-) > > diff --git a/drivers/extcon/extcon-class.c b/drivers/extcon/extcon-class.c > index 148382f..48f4669 100644 > --- a/drivers/extcon/extcon-class.c > +++ b/drivers/extcon/extcon-class.c > @@

Re: [PATCH v2 0/4] Exynos 5410 Dual cluster support

Today, I checked 3.12 but I could not find this patch. Is it dead or under development? If it is under development, any external link? Thanks with sincerely respects... On Mon, Oct 14, 2013 at 5:08 PM, Vyacheslav Tyrtov wrote: > The series of patches represent support of Exynos 5410 SoC > > The

RE: [PATCH] [extcon]:remove freed groups caused the panic or warning in unregister flow

> -Original Message- > From: Wang, Xiaoming > Sent: Saturday, November 02, 2013 6:48 AM > To: myungjoo@samsung.com; cw00.c...@samsung.com; > linux-kernel@vger.kernel.org > Cc: Liu, Chuansheng; Zhang, Dongxing; Wang, Xiaoming > Subject: [PATCH] [extcon]:remove freed groups caused the p

[GIT PULL] Remove h8300 platform support

Hi Linus, Please pull the patch series to remove support for the h8300 platform from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git h8300-for-linus The patch series has been in -next for more than one relase cycle. I did get a number of Acks, and no objec

Re: [PATCH] kernel: trace: blktrace: remove redundent memcpy() in compat_blk_trace_setup()

On 11/04/2013 01:36 AM, Steven Rostedt wrote: > A quick review of this patch looks fine to me. > > Although, using ARRAY_SIZE() for a character string seems to me a bit > over paranoid. But I'm fine with it, as it makes sure that the string > is an array and not a pointer. > Yeah. > Jens, > >

Re: [git pull] fixes for 3.12-final

On Sun, Nov 03, 2013 at 03:39:14PM -0800, Linus Torvalds wrote: > On Sun, Nov 3, 2013 at 11:54 AM, Al Viro wrote: > > > > IIRC, at some point such an attempt has seriously hurt iget() on 32bit > > boxen, so we ended up deciding not to go there. Had been years ago, > > though... > > Yeah, I think

Re: [PATCH] kernel: trace: blktrace: remove redundent memcpy() in compat_blk_trace_setup()

On 11/04/2013 04:15 AM, Steven Rostedt wrote: > On Sun, 3 Nov 2013 11:16:39 -0700 > Jens Axboe wrote: > >> Thanks, but I'll just queue it up with the other block bits for 3.13. >> > > OK, > Thank all of you. :-) -- Chen Gang -- To unsubscribe from this list: send the line "unsubscribe linux-k

Re: [PATCH 2/2] extcon: arizona: Fix race with microphone detection and removal

On 10/28/2013 01:19 AM, Charles Keepax wrote: > The microphone detection code is run as delayed work to provide > additional debounce, it is possible that the jack could have been > removed by the time we process the microphone detection. Turn this case > into a no op. > > Signed-off-by: Charles K

Re: [PATCH v2 1/2] extcon: arizona: Fix reset of HPDET after race with removal

Hi Charles, On 10/28/2013 01:19 AM, Charles Keepax wrote: > We need to make sure we reset back to our starting state, especially > making sure that we have disabled poll in the register cache. > > Signed-off-by: Charles Keepax > --- > drivers/extcon/extcon-arizona.c |8 +++- > 1 files c

[PATCH on top of 3/3] ACPI / hotplug: Remove unnecessary get_device() and put_device()

From: Rafael J. Wysocki The get_device() and put_device() calls made by acpi_bus_device_eject() and acpi_scan_hot_remove(), respectively, are not necessary any more, so remove them. Signed-off-by: Rafael J. Wysocki --- Actually, after https://patchwork.kernel.org/patch/3134091/ the get_device(

[RESEND 2][PATCH] hwrng: add randomness to system from rng sources

When bringing a new RNG source online, it seems like it would make sense to use some of its bytes to make the system entropy pool more random, as done with all sorts of other devices that contain per-device or per-boot differences. Signed-off-by: Kees Cook --- Added linux-crypto list to CC. ---

[PATCH 0/3] ACPI scan and hotplug fixes for 3.14

Hi, The following three patches fix some issues that we have in the common ACPI hotplug infrastructure. If anyone sees any problems with them, please let me know. Thanks! -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send

Linux 3.12 released .. and no merge window yet .. and 4.0 plans?

I was vacillating whether to do an rc8 or just cut the final 3.12, but since the biggest reason to *not* do a final release was not so much the state of the code, as simply the fact that I'll be traveling with very bad internet connection next week, I didn't really want to delay the release. Sure,

[PATCH 3/3] ACPI / hotplug: Merge device hot-removal routines

From: Rafael J. Wysocki The only substantial difference between acpi_bus_device_eject() and acpi_bus_hot_remove_device() is the get_device() done by the former which is supposed to be done by callers of the latter. However, at least one caller of acpi_bus_hot_remove_device(), which is handle_roo

[PATCH 1/3] ACPI / scan: Start matching drivers after trying scan handlers

From: Rafael J. Wysocki ACPI scan handlers should always be attached to struct acpi_device objects before any ACPI drivers, but there is a window during which a driver may be attached to a struct acpi_device before checking if there is a matching scan handler. Namely, that will happen if an ACPI

[PATCH 2/3] ACPI / hotplug: Refuse to hot-remove all objects with disabled hotplug

From: Rafael J. Wysocki In theory, an ACPI device object may be the parent of another device object whose hotplug is disabled by user space thorugh its scan handler. In that case, the eject operation targeting the parent should fail as though the parent's own hotplug was disabled, but currently

Re: [PATCH] mm: cache largest vma

>> I'm slightly surprised this cache makes 15% hit. Which application >> get a benefit? You listed a lot of applications, but I'm not sure >> which is highly depending on largest vma. > > Well I chose the largest vma because it gives us a greater chance of > being already cached when we do the look

Re: [git pull] fixes for 3.12-final

On Sun, Nov 3, 2013 at 11:54 AM, Al Viro wrote: > > IIRC, at some point such an attempt has seriously hurt iget() on 32bit > boxen, so we ended up deciding not to go there. Had been years ago, > though... Yeah, I think the circumstances have changed. 32-bit is less important, and iget() is much

Re: [RFC] arch: Introduce new TSO memory barrier smp_tmb()

On Sun, Nov 3, 2013 at 2:42 PM, Paul E. McKenney wrote: > > smp_storebuffer_mb() -- A barrier that enforces those orderings > that do not invalidate the hardware store-buffer optimization. Ugh. Maybe. Can you guarantee that those are the correct semantics? And why talk about the hardware

Re: [PATCH] CPU Jitter RNG: inclusion into kernel crypto API and /dev/random

Hi! > Another friend of mine mentioned that he assumes the rise and fall times > of transistors varies very slightly and could be the main reason for the > jitter. I do not think that this is really the case, because our gates > that form the CPU instructions comprise of many transistors. The

Re: [PATCH] Staging: ft1000: fixed a few styling issues

On Sun, Nov 03, 2013 at 04:20:38PM +0200, Aldo Iljazi wrote: > Fixed a few styling issues, specifically: > Gar... No one wants to read that changelog. That was over 700 lines of repeated text. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel"

Re: [PATCH 1/4] random: use device attach events for entropy

On Sun, Nov 03, 2013 at 08:33:12AM -0500, Theodore Ts'o wrote: > Some investigation from FreeBSD shows that there is entropy available > from measuring the device attach times: > > http://lists.randombit.net/pipermail/cryptography/2013-October/005689.html > > This will hopefully help us more quic

Re: perf events ring buffer memory barrier on powerpc

On Sun, Nov 03, 2013 at 05:07:59PM +, Will Deacon wrote: > On Sun, Nov 03, 2013 at 02:40:17PM +, Paul E. McKenney wrote: > > On Sat, Nov 02, 2013 at 10:32:39AM -0700, Paul E. McKenney wrote: > > > On Fri, Nov 01, 2013 at 03:56:34PM +0100, Peter Zijlstra wrote: > > > > On Wed, Oct 30, 2013 a

Re: [RFC] arch: Introduce new TSO memory barrier smp_tmb()

On Mon, Nov 04, 2013 at 07:59:23AM +1100, Benjamin Herrenschmidt wrote: > On Sun, 2013-11-03 at 16:17 +0100, Peter Zijlstra wrote: > > On Sun, Nov 03, 2013 at 06:40:17AM -0800, Paul E. McKenney wrote: > > > If there was an smp_tmb(), I would likely use it in rcu_assign_pointer(). > > > > Well, I'm

Re: [RFC] arch: Introduce new TSO memory barrier smp_tmb()

On Sun, Nov 03, 2013 at 09:01:24PM +0100, Peter Zijlstra wrote: > On Sun, Nov 03, 2013 at 10:08:14AM -0800, Linus Torvalds wrote: > > On Sun, Nov 3, 2013 at 7:17 AM, Peter Zijlstra wrote: > > > On Sun, Nov 03, 2013 at 06:40:17AM -0800, Paul E. McKenney wrote: > > >> If there was an smp_tmb(), I wo

Re: Quality plastic raw materials

Dear Sir, Good day! We had dealing plastic raw materials for many years . And supplied high quality different grade HDPE/LDPE/PP/PET to our old and new customers. Should any of the items be of interest to you, please let me know. We shall be glad to give you our lowest quotations upon receip

Re: [PATCH net] net: flow_dissector: fail on evil iph->ihl

On 11/01/2013 08:01 AM, Jason Wang wrote: We don't validate iph->ihl which may lead a dead loop if we meet a IPIP skb whose iph->ihl is zero. Fix this by failing immediately when iph->ihl is evil (less than 5). This issue were introduced by commit ec5efe7946280d1e84603389a1030ccec0a767ae (rps: s

[Topic closed] A Desktop Linux idea: modulized open hardware database for the linux kernel config

Theodore Ts'o wrote on Sunday, 03rd November 2013: > It's an idea that people have tossed around before, but utltimately, > it's far more work than it's worth, and it's a maintenance nightmare. > For most non-technical users, using a distro kernel is quite good > enough. Yes, I get it. Thanks for

Kære : Vinder

Kære : Vinder Vi er glade for at informere dig om den endelige annoncering af Microsoft International salgsfremmende online programm, er din email ID opstået dig en vinder af 815.810.00 euro ( otte hundrede og femten tusinde , otte hundrede og ti euro kun ) i Microsoft salgsfremmende program , Men

Re: Strange location and name for platform devices when device-tree is used.

On Sat, 2013-11-02 at 13:40 -0700, Greg Kroah-Hartman wrote: > On Sun, Nov 03, 2013 at 07:22:10AM +1100, Benjamin Herrenschmidt wrote: > > On Sat, 2013-11-02 at 08:58 -0700, Greg Kroah-Hartman wrote: > > > Just loop through all the platform devices before registering it to > > > determine if you ne

Re: Strange location and name for platform devices when device-tree is used.

On Sat, 2 Nov 2013 08:58:24 -0700 Greg Kroah-Hartman wrote: > So go blame them for this, not me, remember, I'm the one who _hates_ > platform devices and wish they had never been created... Have you ever written up why you hate them? I did a bit of googling and couldn't find anything obvious.

Re: [PATCH v3] can: c_can: Speed up rx_poll function

On 11/03/2013 08:20 PM, Wolfgang Grandegger wrote: > On 11/01/2013 10:36 AM, Markus Pargmann wrote: >> This patch speeds up the rx_poll function by reducing the number of >> register reads. >> >> Replace the 32bit register read by a 16bit register read. Currently >> the 32bit register read is imple

Re: [RFC] arch: Introduce new TSO memory barrier smp_tmb()

On Sun, 2013-11-03 at 16:17 +0100, Peter Zijlstra wrote: > On Sun, Nov 03, 2013 at 06:40:17AM -0800, Paul E. McKenney wrote: > > If there was an smp_tmb(), I would likely use it in rcu_assign_pointer(). > > Well, I'm obviously all for introducing this new barrier, for it will > reduce a full mfenc

Re: perf events ring buffer memory barrier on powerpc

On Fri, 2013-11-01 at 18:30 +0200, Victor Kaplansky wrote: > "David Laight" wrote on 11/01/2013 06:25:29 PM: > > gcc will do unexpected memory accesses for bit fields that are > > adjacent to volatile data. > > In particular it may generate 64bit sized (and aligned) RMW cycles > > when accessing b

Re: [PATCH 1/2] staging: et131x: drop packet when error occurs in et131x_tx()

On 3 November 2013 01:40, ZHAO Gang wrote: > Drop packet instead of return NETDEV_TX_BUSY when tx failed. > > Signed-off-by: ZHAO Gang Hi, Looks good. If you could also send a patch to remove this item from the et131x/README TODO list, then I'm happy to add: Acked-by: Mark Einon Cheers, Mar

Re: [PATCH 2/2] staging: et131x: improve code readability

On 3 November 2013 01:41, ZHAO Gang wrote: > Signed-off-by: ZHAO Gang Acked-by: Mark Einon -- 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 r

  1   2   3   >