[PATCH v4 15/16] perf, x86: disable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode

2014-03-17 Thread Yan, Zheng
Due to a hardware bug of Haswell, LBR callstack does not work well with FREEZE_LBRS_ON_PMI. If FREEZE_LBRS_ON_PMI is set, PMIs near call/return instructions may cause superfluous increase/decrease of LBR_TOS. This patch modifies __intel_pmu_lbr_enable() to not enable FREEZE_LBRS_ON_PMI when LBR

[PATCH v4 16/16] perf, x86: Discard zero length call entries in LBR call stack

2014-03-17 Thread Yan, Zheng
Zero length call uses the attribute of the call instruction to push the immediate instruction pointer on to the stack and then pops off that address into a register. This is accomplished without any matching return instruction. It confuses the hardware and make the recorded call stack incorrect.

[PATCH v4 03/16] perf, x86: use context switch callback to flush LBR stack

2014-03-17 Thread Yan, Zheng
Previous commit introduces context switch callback, its function overlaps with the flush branch stack callback. So we can use the context switch callback to flush LBR stack. This patch adds code that uses the flush branch callback to flush the LBR stack when task is being scheduled in. The

Re: [PATCHv2 3/8] devfreq: exynos4: Add ppmu's clock control and code clean about regulator control

2014-03-17 Thread Chanwoo Choi
Hi Tomasz, On 03/17/2014 11:51 AM, Chanwoo Choi wrote: Hi Tomasz, On 03/15/2014 02:42 AM, Tomasz Figa wrote: Hi Chanwoo, On 13.03.2014 09:17, Chanwoo Choi wrote: There are not the clock controller of ppmudmc0/1. This patch control the clock of ppmudmc0/1 which is used for monitoring

[PATCH v4 11/16] perf, core: Pass perf_sample_data to perf_callchain()

2014-03-17 Thread Yan, Zheng
Haswell has a new feature that utilizes the existing Last Branch Record facility to record call chains. When the feature is enabled, function call will be collected as normal, but as return instructions are executed the last captured branch record is popped from the on-chip LBR registers. The LBR

[PATCH v4 01/16] perf, x86: Reduce lbr_sel_map size

2014-03-17 Thread Yan, Zheng
The index of lbr_sel_map is bit value of perf branch_sample_type. PERF_SAMPLE_BRANCH_MAX is 1024 at present, so each lbr_sel_map uses 4096 bytes. By using bit shift as index, we can reduce lbr_sel_map size to 40 bytes. This patch defines 'bit shift' for branch types, and use 'bit shift' to define

[PATCH v4 13/16] perf, x86: re-organize code that implicitly enables LBR/PEBS

2014-03-17 Thread Yan, Zheng
make later patch more readable, no logic change. Signed-off-by: Yan, Zheng zheng.z@intel.com --- arch/x86/kernel/cpu/perf_event.c | 59 1 file changed, 29 insertions(+), 30 deletions(-) diff --git a/arch/x86/kernel/cpu/perf_event.c

RE: [PATCH net-next v3 1/2]r8152:addRTL8152_EARLY_AGG_TIMEOUT_SUPER

2014-03-17 Thread hayeswang
From: David Miller [mailto:da...@davemloft.net] Sent: Saturday, March 15, 2014 2:43 AM [...] Besides, I don't wish to modify the setting by ethtool when re-loading the driver or rebooting every time. You have code to reset the driver, you can do it when the user asks for the setting to

[PATCH v4 10/16] perf, core: simplify need branch stack check

2014-03-17 Thread Yan, Zheng
event-attr.branch_sample_type is non-zero no matter branch stack is enabled explicitly or is enabled implicitly. we can use it to replace intel_pmu_needs_lbr_smpl(). This avoids duplicating code that implicitly enables the LBR. Signed-off-by: Yan, Zheng zheng.z@intel.com ---

[PATCH v4 14/16] perf, x86: enable LBR callstack when recording callchain

2014-03-17 Thread Yan, Zheng
If a task specific event wants user space callchain but does not want branch stack sampling, enable the LBR call stack facility implicitly. The LBR call stack facility can help perf to get user space callchain in case of there is no frame pointer. Note: this feature only affects how to get user

[PATCH v4 12/16] perf, x86: use LBR call stack to get user callchain

2014-03-17 Thread Yan, Zheng
Haswell has a new feature that utilizes the existing Last Branch Record facility to record call chains. When the feature is enabled, function call will be collected as normal, but as return instructions are executed the last captured branch record is popped from the on-chip LBR registers. The LBR

[PATCH v4 08/16] perf, x86: allocate space for storing LBR stack

2014-03-17 Thread Yan, Zheng
When the LBR call stack is enabled, it is necessary to save/restore the LBR stack on context switch. We can use pmu specific data to store LBR stack when task is scheduled out. This patch adds code that allocates the pmu specific data. Signed-off-by: Yan, Zheng zheng.z@intel.com Reviewed-by:

[PATCH v4 04/16] perf, x86: Basic Haswell LBR call stack support

2014-03-17 Thread Yan, Zheng
Haswell has a new feature that utilizes the existing LBR facility to record call chains. To enable this feature, bits (JCC, NEAR_IND_JMP, NEAR_REL_JMP, FAR_BRANCH, EN_CALLSTACK) in LBR_SELECT must be set to 1, bits (NEAR_REL_CALL, NEAR-IND_CALL, NEAR_RET) must be cleared. Due to a hardware bug of

[PATCH v4 09/16] perf, x86: Save/resotre LBR stack during context switch

2014-03-17 Thread Yan, Zheng
When the LBR call stack is enabled, it is necessary to save/restore the LBR stack on context switch. The solution is saving/restoring the LBR stack to/from task's perf event context. The LBR stack is saved/restored only when there are events that use the LBR call stack. If no event uses LBR call

[PATCH v4 05/16] perf, core: pmu specific data for perf task context

2014-03-17 Thread Yan, Zheng
Introduce a new field to 'struct pmu' to specify the size of PMU specific data. If the size is not zero, also allocate memory for the PMU specific data when allocating perf task context. The PMU specific data are initialized to zeros. Later patches will use PMU specific data to save LBR stack.

[PATCH v4 06/16] perf, core: always switch pmu specific data during context switch

2014-03-17 Thread Yan, Zheng
If two tasks were both forked from the same parent task, Events in their perf task contexts can be the same. Perf core may leave out switching the perf event contexts. Previous patch inroduces pmu specific data. The data is for saving the LBR stack, it is task specific. So we need to switch the

RE: [PATCH net-next v3 1/2] r8152:addRTL8152_EARLY_AGG_TIMEOUT_SUPER

2014-03-17 Thread hayeswang
From: Francois Romieu [mailto:rom...@fr.zoreil.com] Sent: Saturday, March 15, 2014 7:43 AM [...] Besides, I don't wish to modify the setting by ethtool when re-loading the driver or rebooting every time. Why ? The recipe is different but there isn't much setup difference between a

Re: Re: [PATCH V3] serial/uart/8250: Add tunable RX interrupt trigger I/F of FIFO buffers

2014-03-17 Thread Yoshihiro YUNOMAE
Hi Alan, Thank you for your reply. (2014/03/14 21:04), One Thousand Gnomes wrote: @@ -2325,10 +2323,19 @@ serial8250_do_set_termios(struct uart_port *port, struct ktermios *termios, if ((baud 2400 !up-dma) || fifo_bug) { fcr = ~UART_FCR_TRIGGER_MASK;

[PATCH v4 07/16] perf, x86: track number of events that use LBR callstack

2014-03-17 Thread Yan, Zheng
When enabling/disabling an event, check if the event uses the LBR callstack feature, adjust the LBR callstack usage count accordingly. Later patch will use the usage count to decide if LBR stack should be saved/restored. Signed-off-by: Yan, Zheng zheng.z@intel.com ---

[PATCH v4 02/16] perf, core: introduce pmu context switch callback

2014-03-17 Thread Yan, Zheng
The callback is invoked when process is scheduled in or out. It provides mechanism for later patches to save/store the LBR stack. For the schedule in case, the callback is invoked at the same place that flush branch stack callback is invoked. So it also can replace the flush branch stack callback.

[PATCH v4 00/16] perf, x86: Haswell LBR call stack support

2014-03-17 Thread Yan, Zheng
For many profiling tasks we need the callgraph. For example we often need to see the caller of a lock or the caller of a memcpy or other library function to actually tune the program. Frame pointer unwinding is efficient and works well. But frame pointers are off by default on 64bit code (and on

[PATCH V3] NTFS: Logging clean-up

2014-03-17 Thread Fabian Frederick
-Convert spinlock/static array to va_format (inspired by Joe Perches help on previous logging patches). -Convert printk(KERN_ERR to pr_warn in __ntfs_warning. -Convert printk(KERN_ERR to pr_err in __ntfs_error. -Convert printk(KERN_DEBUG to pr_debug in __ntfs_debug. (Note that __ntfs_debug is

Re: [RFA][PATCH 3/4] tracing/module: Remove include of tracepoint.h from module.h

2014-03-17 Thread Steven Rostedt
On Mon, 2014-03-17 at 13:04 +1030, Rusty Russell wrote: Steven Rostedt rost...@goodmis.org writes: On Wed, 26 Feb 2014 14:01:43 -0500 Hi Rusty, This patch doesn't need to be stable, and can wait till v3.15. But I have other patches that will break with this patch (headers that needed

Re: [PATCH net V2] vhost: net: switch to use data copy if pending DMAs exceed the limit

2014-03-17 Thread Ronen Hod
On 03/13/2014 09:28 AM, Jason Wang wrote: On 03/10/2014 04:03 PM, Michael S. Tsirkin wrote: On Fri, Mar 07, 2014 at 01:28:27PM +0800, Jason Wang wrote: We used to stop the handling of tx when the number of pending DMAs exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation of

Re: [RESEND v2 PATCH 1/2] aio, memory-hotplug: Fix confliction when migrating and accessing ring pages.

2014-03-17 Thread Tang Chen
On 03/14/2014 11:14 PM, Benjamin LaHaise wrote: .. What about the following patch? It adds additional reference to protect the page avoid being freed when we reading it. ps.It is applied on linux-next(3-13). I think that's even worse than the spinlock approach since we'll end up bouncing

Re: [PATCH] perf sched latency: prettify printed table

2014-03-17 Thread Jiri Olsa
On Sat, Mar 15, 2014 at 12:17:38PM -0400, Ramkumar Ramachandra wrote: Cc: Frederic Weisbecker fweis...@gmail.com Cc: David Ahern dsah...@gmail.com Cc: Jiri Olsa jo...@redhat.com Cc: Arnaldo Carvalho de Melo a...@redhat.com Signed-off-by: Ramkumar Ramachandra artag...@gmail.com ---

[PATCH 1/8] printk: Remove outdated comment

2014-03-17 Thread Jan Kara
Comment about interesting interlocking between lockbuf_lock and console_sem is outdated. It was added in 2002 by commit a880f45a48be2956d2c78a839c472287d54435c1 during conversion of console_lock to console_sem + lockbuf_lock. At that time release_console_sem() (today's equivalent is

[PATCH 8/8] printk: Add config option for disabling printk offloading

2014-03-17 Thread Jan Kara
Necessity for offloading of printing was observed only for large systems. So add a config option (disabled by default) which removes most of the overhead added by this functionality. Signed-off-by: Jan Kara j...@suse.cz --- Documentation/kernel-parameters.txt | 13 +++-- init/Kconfig

[PATCH 7/8] kernel: Avoid softlockups in stop_machine() during heavy printing

2014-03-17 Thread Jan Kara
When there are lots of messages accumulated in printk buffer, printing them (especially over serial console) can take a long time (tens of seconds). stop_machine() will effectively make all cpus spin in multi_cpu_stop() waiting for the CPU doing printing to print all the messages which triggers

[PATCH 0/8 v3] printk: Cleanups and softlockup avoidance

2014-03-17 Thread Jan Kara
Hello, this is another revision of the printk softlockup series. Since previous version I have fixed up some small problems pointed out by Andrew, added possibility to configure out the printk offloading logic (for small systems), and offload kthreads are now started only once

[PATCH 6/8] printk: Start printing handover kthreads on demand

2014-03-17 Thread Jan Kara
Start kthreads for handing over printing only when printk.offload_chars is set to value 0 (i.e., when print offloading gets enabled). Signed-off-by: Jan Kara j...@suse.cz --- kernel/printk/printk.c | 64 +++--- 1 file changed, 50 insertions(+), 14

[PATCH 5/8] printk: Hand over printing to console if printing too long

2014-03-17 Thread Jan Kara
Currently, console_unlock() prints messages from kernel printk buffer to console while the buffer is non-empty. When serial console is attached, printing is slow and thus other CPUs in the system have plenty of time to append new messages to the buffer while one CPU is printing. Thus the CPU can

[PATCH 2/8] printk: Release lockbuf_lock before calling console_trylock_for_printk()

2014-03-17 Thread Jan Kara
There's no reason to hold lockbuf_lock when entering console_trylock_for_printk(). The first thing this function does is calling down_trylock(console_sem) and if that fails it immediately unlocks lockbuf_lock. So lockbuf_lock isn't needed for that branch. When down_trylock() succeeds, the rest of

[PATCH 3/8] printk: Enable interrupts before calling console_trylock_for_printk()

2014-03-17 Thread Jan Kara
We need interrupts disabled when calling console_trylock_for_printk() only so that cpu id we pass to can_use_console() remains valid (for other things console_sem provides all the exclusion we need and deadlocks on console_sem due to interrupts are impossible because we use down_trylock()).

[PATCH 4/8] printk: Remove separate printk_sched buffers and use printk buf instead

2014-03-17 Thread Jan Kara
From: Steven Rostedt rost...@goodmis.org To prevent deadlocks with doing a printk inside the scheduler, printk_sched() was created. The issue is that printk has a console_sem that it can grab and release. The release does a wake up if there's a task pending on the sem, and this wake up grabs the

Re: [PATCH 1/5] perf tests: Add tip/pid mmap automated tests

2014-03-17 Thread Jiri Olsa
On Fri, Mar 14, 2014 at 05:24:21PM -0300, Arnaldo Carvalho de Melo wrote: Em Fri, Mar 14, 2014 at 03:00:02PM +0100, Jiri Olsa escreveu: Adding automated test for memory maps lookup within multiple machines threads. CC /tmp/build/perf/arch/x86/util/tsc.o tests/mmap-events.c: In

Re: [PATCH 3/5] perf tools: Allocate thread map_groups dynamicaly

2014-03-17 Thread Namhyung Kim
On Fri, 14 Mar 2014 15:00:04 +0100, Jiri Olsa wrote: Moving towards sharing map groups within a process threads. Because of this we need the map groups to be dynamically allocated. No other functional change is intended in here. @@ -664,7 +664,7 @@ void thread__find_addr_map(struct thread

Re: [PATCH 4/5] perf tools: Add machine pointer into thread struct

2014-03-17 Thread Namhyung Kim
Hi Arnaldo, On Fri, 14 Mar 2014 11:16:12 -0300, Arnaldo Carvalho de Melo wrote: Em Fri, Mar 14, 2014 at 03:00:05PM +0100, Jiri Olsa escreveu: Need machine pointer in thread object, so we could lookup the process thread in following patch. Can't we use the already existing thread-mg.machine

Re: [PATCH 5/5] perf tools: Share process map groups within process threads

2014-03-17 Thread Namhyung Kim
On Fri, 14 Mar 2014 15:00:06 +0100, Jiri Olsa wrote: + if (!mg) { + struct thread *leader = thread__get_leader(thread); + + if (!leader) + return NULL; + + if (leader-mg) + mg = leader-mg; + else

Re: [PATCH] virtio-blk: make the queue depth configurable

2014-03-17 Thread Joe Perches
On Sun, 2014-03-16 at 22:00 -0700, Joe Perches wrote: On Mon, 2014-03-17 at 14:25 +1030, Rusty Russell wrote: Erk, our tests are insufficient. Testbuilding an allmodconfig with this now: Good idea. diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h [] @@

linux-next: manual merge of the usb tree with the tip tree

2014-03-17 Thread Stephen Rothwell
Hi Greg, Today's linux-next merge of the usb tree got a conflict in arch/arm/mach-shmobile/Kconfig between commit aeb8fb7910fc (ARM: shmobile: Remove CMT, TMU and STI Kconfig entries) from the tip tree and commit f6723b569a67 (usb: host: remove selects of USB_ARCH_HAS_?HCI) from the usb tree. I

linux-next: manual merge of the usb tree with the tip tree

2014-03-17 Thread Stephen Rothwell
Hi Greg, Today's linux-next merge of the usb tree got a conflict in arch/sh/Kconfig between commit fbfa893458ed (sh: Remove Kconfig entries for TMU, CMT and MTU2) from the tip tree and commit f6723b569a67 (usb: host: remove selects of USB_ARCH_HAS_?HCI) from the usb tree. I fixed it up (see

[PATCH v2 4/6] compile the DRBG code

2014-03-17 Thread Stephan Mueller
Signed-off-by: Stephan Mueller smuel...@chronox.de --- diff --git a/crypto/Makefile b/crypto/Makefile index b29402a..0d63373 100644 --- a/crypto/Makefile +++ b/crypto/Makefile @@ -92,6 +92,7 @@ obj-$(CONFIG_CRYPTO_842) += 842.o obj-$(CONFIG_CRYPTO_RNG2) += rng.o obj-$(CONFIG_CRYPTO_RNG2) +=

[PATCH v2 1/6] SP800-90A Deterministic Random Bit Generator

2014-03-17 Thread Stephan Mueller
This is a clean-room implementation of the DRBG defined in SP800-90A. All three viable DRBGs defined in the standard are implemented: * HMAC: This is the leanest DRBG and compiled per default * Hash: The more complex DRBG can be enabled at compile time * CTR: The most complex DRBG can also be

[PATCH v2 6/6] Add DRBG test code to testmgr

2014-03-17 Thread Stephan Mueller
The DRBG test code implements the CAVS test approach. As discussed for the test vectors, all DRBG types are covered with testing. However, not every backend cipher is covered with testing. To prevent the testmgr from logging missing testing, the NULL test is registered for all backend ciphers not

[PATCH v2 2/6] header file for DRBG

2014-03-17 Thread Stephan Mueller
The header file includes the definition of: * DRBG data structures with - struct drbg_state as main structure - struct drbg_core referencing the backend ciphers - struct drbg_state_ops callbach handlers for specific code supporting the Hash, HMAC, CTR DRBG

[PATCH v2 3/6] DRBG kernel configuration options

2014-03-17 Thread Stephan Mueller
The different DRBG types of CTR, Hash, HMAC can be enabled or disabled at compile time. At least one DRBG type shall be selected. The default is the HMAC DRBG as its code base is smallest. Signed-off-by: Stephan Mueller smuel...@chronox.de --- diff --git a/crypto/Kconfig b/crypto/Kconfig index

[PATCH v2 5/6] DRBG testmgr test vectors

2014-03-17 Thread Stephan Mueller
All types of the DRBG (CTR, HMAC, Hash) are covered with test vectors. In addition, all permutations of use cases of the DRBG are covered: * with and without predition resistance * with and without additional information string * with and without personalization string As

Re: [PATCH] EDAC: remove deprecated IRQF_DISABLED

2014-03-17 Thread Johannes Thumshirn
On Sat, Mar 08, 2014 at 06:15:18AM +0100, Michael Opdenacker wrote: On 03/05/2014 07:49 AM, Borislav Petkov wrote: On Wed, Mar 05, 2014 at 06:04:37AM +0100, Michael Opdenacker wrote: My patch still applies to 3.14-rc5, which means that mpc85xx_edac is still there. I'd like to get rid of

[PATCH] xen: declare notifier_block on xen-ops.h

2014-03-17 Thread Stanislaw Gruszka
Patch fixes below warnings: In file included from arch/x86/xen/xen-ops.h:7:0, from arch/x86/xen/vga.c:9: include/xen/xen-ops.h:19:42: warning: 'struct notifier_block' declared inside parameter list [enabled by default] void xen_resume_notifier_register(struct

[PATCH V4 01/11] ACPI: introduce .match() callback for ACPI scan handler

2014-03-17 Thread Zhang Rui
Currently, ACPI scan handler uses strcmp() to match device ids and scan handler ids. When converting PNPACPI enumeration into a scan handler, which I will do later in this patch set, the current code becomes not flexible enough because ACPI pnp scan handler requires wildcase and case insensitive

[PATCH V4 00/11] ACPI: change the way of enumerating PNPACPI/Platform devices

2014-03-17 Thread Zhang Rui
Hi, all, Currently, PNP bus is used as the default bus for for enumerating ACPI devices with _HID/_CID. For a device that needs to be enumerated to platform bus, we need to add its id string to the platform scan handler white list explicitly. This becomes a problem as more and more _HID devices

[PATCH V4 11/11] ACPI: introduce dummy memory hotplug scan handler

2014-03-17 Thread Zhang Rui
If CONFIG_ACPI_HOTPLUG_MEMORY is cleared, platform devices would be created for ACPI hotplug memory device objects. Introduce a dummy memory hotplug scan handler in this patch, to prevent those platform devices from being created. Signed-off-by: Zhang Rui rui.zh...@intel.com ---

[PATCH V4 09/11] ACPI: introduce acpi platform exclude id list

2014-03-17 Thread Zhang Rui
For ACPI PIC (PNP) and Timer (PNP0100) device objects, although they have _HID control method, but they should not be enumerated to platform bus, because there will never be any platform drivers for them. Thus an exclude id list is introduced in this patch to prevent those platform device

[PATCH V4 10/11] ACPI: introduce dummy container scan handler

2014-03-17 Thread Zhang Rui
When CONFIG_ACPI_CONTAINER is cleared, platform devices would be created for ACPI container objects. Introduce a dummy container scan handler in this patch to prevent these platform devices from being created. Signed-off-by: Zhang Rui rui.zh...@intel.com --- drivers/acpi/Makefile|2 +-

[PATCH V4 08/11] ACPI: introduce dummy lpss scan handler

2014-03-17 Thread Zhang Rui
When the lpss scan handler is compiled out, aka, CONFIG_X86_INTEL_LPSS is cleared, those ACPI device objects will be recgonized as regular _HID devices, and a platform device would be created for each of them. This is wrong because the platform drivers for those devices would be loaded, but with

[PATCH V4 06/11] ACPI: introduce platform_id flag

2014-03-17 Thread Zhang Rui
Only certain kind of ACPI device objects can be enumerated to platform bus. These ACPI device objects include 1. ACPI device objects that have _HID control method. 2. some ACPI device objects that have Linux specified HID strings. In order to distinguish those device objects from the others, a

[PATCH V4 02/11] PNPACPI: use whilte list for pnpacpi device enumeration

2014-03-17 Thread Zhang Rui
ACPI can be used to enumerate PNP devices, but the code does not handle this in a good manner. Currently, if an ACPI device 1. has _CRS method, 2. has an identifications of three capital charactors followed by four hex numbers, 3. is not in the excluded id list, it is enumerated to PNP bus.

[PATCH V4 07/11] ACPI: use platform bus as the default bus for _HID enumeration

2014-03-17 Thread Zhang Rui
Because of the growing demand for enumerating ACPI devices to platform bus, this patch changes the code to enumerate ACPI devices with _HID to platform bus by default, unless the device already has a scan handler attached. Signed-off-by: Zhang Rui rui.zh...@intel.com ---

[PATCH V4 03/11] ACPI: remove ids that does not comply with the ACPI PNP id rule

2014-03-17 Thread Zhang Rui
The acpi pnp scan handler id list just copies all the ids from all the struct pnp_device_id instances, but some of them do not comply with the ACPI PNP id rule (3 Alpha Charactors + 4 Hex numbers). For those ids, the coressponding devices will never be enumerated via ACPI, so it is safe to remove

[PATCH V4 05/11] ACPI: check and enumerate CMOS RTC devices explicitly

2014-03-17 Thread Zhang Rui
For CMOS RTC devices, the acpi pnp scan handler does not work because there is already a cmos rtc scan handler installed, thus we need to check those devices and enumerate them to PNP bus explicitly. Plus, the cmos rtc scan handler needs to return 1 so that it will not be enumerated to platform

[PATCH V4 04/11] ACPI: remove unsupported serial PNP ids from acpi pnp scan handler id lsit

2014-03-17 Thread Zhang Rui
The serial pnp driver supports some unknown PNP modems (PNPCXXX/PNPDXXX) by matching magic strings in the pnp device name or the pnp device card name. ACPI enumerated PNP device neither supports pnp card, nor supports those magic strings in its device name, which means this mechamism never works

linux-next: manual merge of the staging tree with the v4l-dvb tree

2014-03-17 Thread Stephen Rothwell
Hi Greg, Today's linux-next merge of the staging tree got a conflict in drivers/media/platform/exynos4-is/fimc-is.c between commit d265d9ac6c7c ([media] exynos4-is: Use external s5k6a3 sensor driver) from the v4l-dvb tree and commit fd9fdb78a9bf ([media] of: move graph helpers from

Re: [PATCH] iio: cm36651: Fix i2c client leak and possible NULL pointer dereference

2014-03-17 Thread Krzysztof Kozlowski
Hi, On Sat, 2014-03-15 at 16:24 +, Jonathan Cameron wrote: On 06/03/14 09:33, Krzysztof Kozlowski wrote: During probe the driver allocates dummy I2C devices (i2c_new_dummy()) but they aren't unregistered during driver remove or probe failure. Additionally driver does not check the

Re: [PATCHSET 0/9] perf tools: Update on filtered entries' percentage output (v7)

2014-03-17 Thread Namhyung Kim
Ping! On Mon, 10 Mar 2014 16:43:51 +0900, Namhyung Kim wrote: Hello, I added --percentage option to perf report to control display of percentage of filtered entries. usage: perf report [options] --percentage relative|absolute how to display percentage

linux-next: manual merge of the staging tree with the net-next tree

2014-03-17 Thread Stephen Rothwell
Hi Greg, Today's linux-next merge of the staging tree got a conflict in drivers/staging/wlan-ng/cfg80211.c between commit 3ead0d2e220e (wlan-ng: fixup staging driver for removal of ieee80211_dsss_chan_to_freq) from the net-next tree and commit 4e5e9d7c66f0 (staging: wlan-ng: replace function

Re: [PATCH] spi: dw-mmio: add oftree support

2014-03-17 Thread Steffen Trumtrar
Hi! On Fri, Mar 14, 2014 at 04:26:14PM +, Mark Brown wrote: On Fri, Mar 14, 2014 at 04:14:03PM +, Mark Rutland wrote: +Synopsys DesignWare SPI master controller. + +Required properties: +- compatible : snps,dw-spi-mmio Is there not a better name than dw-spi-mmio?

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

2014-03-17 Thread Stephen Rothwell
Hi all, On Wed, 12 Mar 2014 00:51:52 + Mark Brown broo...@kernel.org wrote: After merging the driver-core tree, today's linux-next build () failed like this on a PowerPC defconfig: HEAD is now at ceb98e684dec Merge remote-tracking branch 'driver-core/driver-core-next' GEN

RE: [RFC V2] mfd: da9063: Add support for production silicon variant code

2014-03-17 Thread Opensource [Steve Twiss]
On 14 March 2014 14:37 Philipp Zabel wrote: Hi, Am Freitag, den 14.02.2014, 16:43 + schrieb Lee Jones: From: Opensource [Steve Twiss] stwiss.opensou...@diasemi.com Add the correct silicon variant code ID (0x5) to the driver. This new code is the 'production' variant code ID for

[f2fs-dev] [PATCH 1/2] f2fs: introduce f2fs_has_xattr_block for better readability

2014-03-17 Thread Chao Yu
This patch introduces a help function f2fs_has_xattr_block for better readability. Signed-off-by: Chao Yu chao2...@samsung.com --- fs/f2fs/f2fs.h |5 + fs/f2fs/node.c |4 ++-- fs/f2fs/node.h |2 +- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/f2fs.h

[f2fs-dev] [PATCH 2/2] f2fs: avoid to return incorrect errno of read_normal_summaries

2014-03-17 Thread Chao Yu
We should return error number of read_normal_summaries instead of -EINVAL when read_normal_summaries failed. Signed-off-by: Chao Yu chao2...@samsung.com --- fs/f2fs/segment.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c

linux-next: manual merge of the powernv-cpuidle tree with the powerpc tree

2014-03-17 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the powernv-cpuidle tree got a conflict in arch/powerpc/include/asm/opal.h between commit c7e64b9ce04a (powerpc/powernv Platform dump interface) from the powerpc tree and commit 97eb001f0349 (powerpc/powernv: Add OPAL call to resync timebase on wakeup) from the

linux-next: manual merge of the powernv-cpuidle tree with the powerpc tree

2014-03-17 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the powernv-cpuidle tree got a conflict in arch/powerpc/platforms/powernv/opal-wrappers.S between commit c7e64b9ce04a (powerpc/powernv Platform dump interface) from the powerpc tree and commit 97eb001f0349 (powerpc/powernv: Add OPAL call to resync timebase on

Re: [PATCH v10 net-next 1/3] filter: add Extended BPF interpreter and converter

2014-03-17 Thread Pablo Neira Ayuso
On Sat, Mar 15, 2014 at 08:53:55PM +0100, Daniel Borkmann wrote: On 03/14/2014 09:08 PM, David Miller wrote: From: Alexei Starovoitov a...@plumgrid.com Date: Fri, 14 Mar 2014 12:51:17 -0700 can you please explain why the status of these patches is 'deferred' in patchwork ? Is it because of

[PATCH v3 3/3] Documentation: mfd: s2mps11: Describe S5M8767 and S2MPS14 clocks

2014-03-17 Thread Krzysztof Kozlowski
Add bindings documentation for clocks on S5M8767 and S2MPS14 devices. Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com Cc: Tomasz Figa t.f...@samsung.com Cc: devicet...@vger.kernel.org Cc: Rob Herring robh...@kernel.org Cc: Pawel Moll pawel.m...@arm.com Cc: Mark Rutland

[PATCH v3 0/3] clk: s2mps11: Add support for S2MPS14 clocks

2014-03-17 Thread Krzysztof Kozlowski
Hi, This is third version of patchset adding support for the S2MPS14 device to the s2mps11 clock driver. The patchset *depends on*: == 1. Work done by Tushar Behera: [PATCH V2 0/2] Add support for clocks in S5M8767

[PATCH v3 1/3] clk: s2mps11: Add support for S2MPS14 clocks

2014-03-17 Thread Krzysztof Kozlowski
This patch adds support for S2MPS14 PMIC clocks (BT and AP) to the s2mps11 clock driver. Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com Reviewed-by: Yadwinder Singh Brar yadi.b...@samsung.com Reviewed-by: Tomasz Figa t.f...@samsung.com --- drivers/clk/Kconfig |8 +++---

[PATCH v3 2/3] mfd: sec-core: Add of_compatible strings for clock MFD cells

2014-03-17 Thread Krzysztof Kozlowski
Add of_compatible strings for S5M8767 and S2MPS14 clock MFD cells. Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com --- drivers/mfd/sec-core.c |3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/mfd/sec-core.c b/drivers/mfd/sec-core.c index d163c66edebb..716606479235

Re: [PATCH 1/3] vrange: Add vrange syscall and handle splitting/merging and marking vmas

2014-03-17 Thread Jan Kara
On Fri 14-03-14 11:33:31, John Stultz wrote: This patch introduces the vrange() syscall, which allows for specifying ranges of memory as volatile, and able to be discarded by the system. This initial patch simply adds the syscall, and the vma handling, splitting and merging the vmas as

kmemcheck: OS boot failed because NMI handlers access the memory tracked by kmemcheck

2014-03-17 Thread Xishi Qiu
OS boot failed when set cmdline kmemcheck=1. The reason is that NMI handlers will access the memory from kmalloc(), this will cause page fault, because memory from kmalloc() is tracked by kmemcheck. watchdog_nmi_enable() perf_event_create_kernel_counter()

linux-next: manual merge of the akpm-current tree with the audit tree

2014-03-17 Thread Stephen Rothwell
Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in arch/ia64/Kconfig between commit b4df597ae51f (audit: Add CONFIG_HAVE_ARCH_AUDITSYSCALL) from the audit tree and commit a13978c6e0ba (ia64: select CONFIG_TTY for use of tty_write_message in unaligned) from the

linux-next: manual merge of the akpm-current tree with the gfs2 tree

2014-03-17 Thread Stephen Rothwell
Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in fs/fs-writeback.c between commit 774016b2d455 (GFS2: journal data writepages update) from the gfs2 tree and commit c830ee18343d (bdi: avoid oops on device removal) from the akpm-current tree. I fixed it up (see below)

Re: [alsa-devel] [PATCH v3 2/4] ASoC: simple-card: dynamically allocate the DAI link and properties

2014-03-17 Thread Jyri Sarha
On 03/15/2014 01:09 PM, Jean-Francois Moine wrote: The DAI link array and the properties (fmt, sysclk slots) are hard-coded for a single CPU / CODEC link. This patch dynamically allocates the DAI link array and the properties with the aim of supporting many DAI links. Signed-off-by:

Re: [PATCH 0/2] KVM: x86 emulator: emulate MOVAPS and MOVAPD SSE instructions

2014-03-17 Thread Paolo Bonzini
Il 15/03/2014 23:42, H. Peter Anvin ha scritto: Stupid question... what instructions do NOT need emulsion in KVM? It would seem that at least anything that touches memory would? Yes, indeed. Anything that touches memory can be used on MMIO and then needs emulation. Paolo On March 15,

linux-next: manual merge of the akpm-current tree with the tip tree

2014-03-17 Thread Stephen Rothwell
Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in kernel/locking/Makefile between commit fb0527bd5ea9 (locking/mutexes: Introduce cancelable MCS lock for adaptive spinning) from the tree and commit 4dc0fe493027 (lglock: map to spinlock when !CONFIG_SMP) from the

[GIT] HID

2014-03-17 Thread Jiri Kosina
Linus, please pull from git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus to receive - fix for ordering of device removal actions in hidraw, by Fernando Luis Vázquez Cao - fix for uninitialized workqueue usage in hid-sony, by Frank Praznik - signature addition for

Re: [PATCH 3/3] ath10k: add firmware files

2014-03-17 Thread Alex Hacker
+* No Reverse engineering, decompiling, decrypting, or disassembling of + this software is permitted. Ups, I did it already... once. So sorry about my offending behaviour. I never do it again, I promise. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of

Re: linux-next: manual merge of the akpm-current tree with the tip tree

2014-03-17 Thread Peter Zijlstra
On Mon, Mar 17, 2014 at 08:31:24PM +1100, Stephen Rothwell wrote: Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in kernel/locking/Makefile between commit fb0527bd5ea9 (locking/mutexes: Introduce cancelable MCS lock for adaptive spinning) from the tree and

Re: [PATCH v3 5/5] gpio / ACPI: Add support for ACPI GPIO operation regions

2014-03-17 Thread Mika Westerberg
On Fri, Mar 14, 2014 at 05:25:39PM +0100, Linus Walleij wrote: On Fri, Mar 14, 2014 at 4:58 PM, Mika Westerberg mika.westerb...@linux.intel.com wrote: GPIO operation regions is a new feature introduced in ACPI 5.0 specification. This feature adds a way for platform ASL code to call back

Re: [PATCH 5/9] powerpc/85xx: disable irq by hardware when suspend for 64-bit

2014-03-17 Thread Chenhui Zhao
On Fri, Mar 14, 2014 at 05:41:41PM -0500, Scott Wood wrote: On Wed, 2014-03-12 at 15:46 +0800, Chenhui Zhao wrote: On Tue, Mar 11, 2014 at 06:51:20PM -0500, Scott Wood wrote: On Fri, 2014-03-07 at 12:58 +0800, Chenhui Zhao wrote: In 64-bit mode, kernel just clears the irq soft-enable

Re: [PATCH 2/3] vrange: Add purged page detection on setting memory non-volatile

2014-03-17 Thread Jan Kara
On Fri 14-03-14 11:33:32, John Stultz wrote: Users of volatile ranges will need to know if memory was discarded. This patch adds the purged state tracking required to inform userland when it marks memory as non-volatile that some memory in that range was purged and needs to be regenerated.

[f2fs-dev] [PATCH] f2fs: fix incorrect parsing with option string

2014-03-17 Thread Chao Yu
Previously 'background_gc={on***,off***}' is being parsed as correct option, with this patch we cloud fix the trivial bug in mount process. Signed-off-by: Chao Yu chao2...@samsung.com --- fs/f2fs/super.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/super.c

Re: [PATCH 1/3] vrange: Add vrange syscall and handle splitting/merging and marking vmas

2014-03-17 Thread Jan Kara
On Mon 17-03-14 10:21:18, Jan Kara wrote: On Fri 14-03-14 11:33:31, John Stultz wrote: + for (;;) { + unsigned long new_flags; + pgoff_t pgoff; + unsigned long tmp; + + if (!vma) + goto out; + + if

[PATCH 6/8] ASoC: atmel: support CCF based clks

2014-03-17 Thread Bo Shen
From: Boris BREZILLON b.brezil...@overkiz.com Provide dev to clk_get function if we're using CCF based clks. CCF based prog clks support automatic parent selection when asking for a specific rate: remove the clk32k clk retrieval if we're using these clks. Signed-off-by: Boris BREZILLON

Re: kmemcheck: OS boot failed because NMI handlers access the memory tracked by kmemcheck

2014-03-17 Thread Michal Hocko
On Mon 17-03-14 17:19:33, Xishi Qiu wrote: OS boot failed when set cmdline kmemcheck=1. The reason is that NMI handlers will access the memory from kmalloc(), this will cause page fault, because memory from kmalloc() is tracked by kmemcheck. watchdog_nmi_enable()

Re: [PATCH] backing_dev: Fix hung task on sync

2014-03-17 Thread Jan Kara
On Sat 15-03-14 13:22:53, dbasehore . wrote: Resurrecting this for further discussion about the root of the problem. mod_delayed_work_if_later addresses the problem one way, but the problem is still there for mod_delayed_work. But flusher works care about only that one way, don't they? We

[PATCH RFC 0/5] Move tda998x to a couple encoder/connector

2014-03-17 Thread Jean-Francois Moine
The 'slave encoder' structure of the tda998x driver asks for glue between the DRM driver and the encoder/connector structures. Changing the tda998x driver to a simple encoder/connector simplifies the code of the tilcdc driver. This change is permitted by Russell's infrastructure for componentised

Re: [PATCH 7/8] ASoC: atmel: document clock properties of the wm8904 driver

2014-03-17 Thread Bo Shen
On 03/17/2014 05:45 PM, Bo Shen wrote: From: Boris BREZILLON b.brezil...@overkiz.com Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com Signed-off-by: Bo Shen voice.s...@atmel.com Oh, sorry for my SOB. Please remove it when apply. ---

[PATCH RFC 3/5] drm/i2c: tda998x: Add required properties

2014-03-17 Thread Jean-Francois Moine
The I2C address of the HDMI subdevice is needed for the driver to be loaded and initialized at system startup time. The origin of the video must be indicated by a reverse phandle according to the media video interface. Signed-off-by: Jean-Francois Moine moin...@free.fr ---

[PATCH RFC 4/5] drm/tilcd: dts: Add the video sink

2014-03-17 Thread Jean-Francois Moine
The connection between the video source and sink must follow the media video interface. Signed-off-by: Jean-Francois Moine moin...@free.fr --- Documentation/devicetree/bindings/drm/tilcdc/slave.txt | 18 -- .../devicetree/bindings/drm/tilcdc/tilcdc.txt | 6 ++ 2

  1   2   3   4   5   6   7   >