[PATCH 02/18] perf tools: Fix accounting of ordered samples queue

Properly account flushed samples within the ordered samples queue. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Signed-off-by: Jiri Olsa ---

[PATCH 05/18] perf tools: Add ordered_events_(get|put) interface

Adding new ordered events interface to get|put event buffer: ordered_events_get - allocate event buffer from the cache ordered_events_put - return event buffer to the cache Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean

[PATCH 04/18] perf tools: Rename ordered_events_queue members

Rename 'struct ordered_events_queue' members to better fit the ordered events pattern. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Signed-off-by: Jiri Olsa

[PATCH 03/18] perf tools: Rename ordered_samples to ordered_events

The time ordering is generic for all kinds of events, so using generic name 'ordered_events' for related struct. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra

[PATCH] staging: Remove useless "default N" lines

Two Kconfig entries default to (uppercase) "N". It was clearly intended to use "default n". But since (lowercase) "n" is the default anyway, these lines might as well be removed. Reported-by: Martin Walch Signed-off-by: Paul Bolle --- Tested with "make menuconfig"and "make oldconfig". I think

[PATCH 10/18] perf tools: Create ordered-events object

Move ordered events code into separated object ordered-events.[ch]. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Signed-off-by: Jiri Olsa ---

[PATCH 08/18] perf tools: Flush ordered events in case of allocation failure

In previous patches we added a limit for ordered events queue allocation size. If we reach this size we need to flush (part of) the queue to get some free buffers. The current functionality is not affected, because the limit is hard coded to (u64) -1. The configuration code for size will come in

[PATCH 12/18] perf tools: Add ordered_events_queue_init function

Adding ordered_events_queue_init function for struct ordered_events_queue initialization. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Signed-off-by: Jiri Olsa

[PATCH 09/18] perf tools: Make perf_session_deliver_event global

Making perf_session_deliver_event global function, as it will be called from another object in following patch. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra

[PATCH 11/18] perf tools: Use list_move in ordered_event_put function

As Namhyung pointed out we can use list_move in ordered_event_put. Suggested-by: Namhyung Kim Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Signed-off-by: Jiri

[PATCH 15/18] perf tools: Add report.queue-size config file option

Adding report.queue-size config file option to setup the maximum allocation size for session's struct ordered_events_queue object. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc:

[PATCH 14/18] perf tools: Add perf_config_u64 function

From: Jiri Olsa Adding perf_config_u64 function to be able to parse 'llong' values out of config file. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra

Re: [PATCH v6 03/10] x86, mpx: add macro cpu_has_mpx

On 06/18/2014 07:44 AM, Borislav Petkov wrote: > On Wed, Jun 18, 2014 at 07:35:17AM -0700, Dave Hansen wrote: >> On 06/18/2014 02:57 AM, Borislav Petkov wrote: > @@ -339,6 +339,12 @@ extern const char * const x86_power_flags[32]; > #define cpu_has_eager_fpu

Re: [PATCH v6 03/10] x86, mpx: add macro cpu_has_mpx

On 06/18/2014 07:35 AM, Dave Hansen wrote: > > It looks like static_cpu_has() is the right thing to use instead of > boot_cpu_has(). But, this doesn't just obfuscate things. > > We actually _want_ the compiler to cull code out when the config option > is off. Things like do_bounds() will see

[PATCH 4/7] ARM: stih416-b2020e: Enable PWM on the B2020 Rev-E

All the infrastructure is now in place for ST's PWM controller. This patch takes the final step and enables the IP on the 2020 Rev-E development platform. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih416-b2020e.dts | 10 ++ 1 file changed, 10 insertions(+) diff --git

[PATCH 2/5] perf trace: add pagefault statistics

Signed-off-by: Stanislav Fomichev --- tools/perf/builtin-trace.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c index 6c7ae048db59..535f0b504950 100644 --- a/tools/perf/builtin-trace.c +++ b/tools/perf/builtin-trace.c @@

Re: [PATCH v5 1/7] efi: Use early_mem*() instead of early_io*()

On Wed, 18 Jun, at 02:59:57PM, Daniel Kiper wrote: > > I think that it improves readability a bit but if you wish I will not > do that in the future. That would be much appreciated. > > As Matthew pointed out we may also need to access EFI mapped flash > > devices. > > Right, but I think it

[RFC PATCH 0/5] perf trace pagefaults

This patch series adds support for pagefaults tracing to 'perf trace' command. It seems this feature was planned by Namhyung Kim (http://events.linuxfoundation.org/images/stories/pdf/klf2012_n_kim.pdf page 17/28) but I couldn't find any prior patches/discussion and started from scratch. First

Re: [PATCH] ARM: dts: add support for Ka-Ro TX51

On Thu, Jun 12, 2014 at 03:09:44PM +0200, Lothar Waßmann wrote: > Add support for Ka-Ro electronics i.MX51 based TX51 modules > > Signed-off-by: Lothar Waßmann > --- > arch/arm/boot/dts/Makefile |1 + > arch/arm/boot/dts/imx51-tx51.dts | 620 > ++

[PATCH 5/5] perf trace: add events cache

Use session to cache and order events from all CPUs so we get correct ordering of comms/mmaps and faults. Signed-off-by: Stanislav Fomichev --- tools/perf/builtin-trace.c | 117 ++--- 1 file changed, 46 insertions(+), 71 deletions(-) diff --git

[PATCH 3/5] perf trace: add possibility to switch off syscall events

Signed-off-by: Stanislav Fomichev --- tools/perf/Documentation/perf-trace.txt | 7 ++ tools/perf/builtin-trace.c | 39 ++--- 2 files changed, 33 insertions(+), 13 deletions(-) diff --git a/tools/perf/Documentation/perf-trace.txt

Re: [ANNOUNCE] util-linux v2.25-rc1

Karel Zak wrote: The util-linux release v2.25 is available at ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.25 Feedback and bug reports, as always, are welcomed. In an LFS build environment, the configure, make, and make check are all clean. It is especially nice the way you tell

Re: [PATCH v6 03/10] x86, mpx: add macro cpu_has_mpx

On 06/18/2014 07:44 AM, Borislav Petkov wrote: > > Why? > > Practically, distros will have it enabled anyway (you have X86_INTEL_MPX > depend on CPU_SUP_INTEL). > > Are you talking about the miniscule percentage of people building their > own kernels? > We have people working hard to shave

[PATCH 17/18] perf tools: Limit the ordered events queue by default to 100MB

It's still configurable by report.queue-size config option, but looks like 100MB limit is more sane than no limit at all. There's some speedup for report on huge data files: With the limit of 100 MB, I've got around 15% speedup on reporting of ~10GB perf.data file. current code:

[PATCH 18/18] perf tools: Allow out of order messages in forced flush

In forced flush (OEQ_FLUSH__HALF) we break the rules of the flush timestamp via PERF_RECORD_FINISHED_ROUND event, so we could get out of order event. Do not force error in this case and also changing the output warning to use WARN_ONCE. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David

[PATCH 4/5] perf kvm: move perf_kvm__mmap_read into session utils

It will be reused by perf trace in the following commit. Signed-off-by: Stanislav Fomichev --- tools/perf/builtin-kvm.c | 88 +++ tools/perf/util/session.c | 85 + tools/perf/util/session.h | 5 +++ 3

[PATCH 16/18] perf tools: Add debug prints for ordered events queue

Adding some prints for ordered events queue, to help debug issues. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Signed-off-by: Jiri Olsa ---

[PATCH 13/18] perf tools: Add ordered_events_queue_free function

Adding ordered_events_queue_free function to release all the struct ordered_events_queue data. It's replacement for former perf_session_free_sample_buffers function. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc:

[PATCH 06/18] perf tools: Factor ordered_events_flush to be more generic

Centralizing the next_flush calculation under the ordered_events_flush function. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Jean Pihet Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Signed-off-by: Jiri Olsa ---

[PATCH 01/18] perf tools: Always force PERF_RECORD_FINISHED_ROUND event

The PERF_RECORD_FINISHED_ROUND governs queue flushing in reporting, so it needs to be stored for any kind of event. Forcing the PERF_RECORD_FINISHED_ROUND event to be stored any time we finish the round and wrote at least one event. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David

[PATCH 07/18] perf tools: Limit ordered events queue size

Add limit to the ordered events queue allocation. This way we will be able to control the size of the queue buffers. There's no limit at the moment (it's set to (u64) -1). The config code will come in following patches. Cc: Arnaldo Carvalho de Melo Cc: Corey Ashford Cc: David Ahern Cc:

[PATCH kvm-unit-tests 1/5] x86: Testing nop instruction on 64-bit

Previously, nop instruction emulation on 64-bit caused RAX bits [63:32] to be cleared. This test checks the behavior is correct and RAX is unmodified. Signed-off-by: Nadav Amit --- x86/emulator.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/x86/emulator.c b/x86/emulator.c

[PATCH 1/7] ARM: stih407: Add DT nodes for for PWM

Supply top level nodes for the STiH407 based development boards. The Pinctrl configuration has already been applied, so the only missing piece of the DT puzzle is for a board's DTB to enable the nodes. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih407.dtsi | 27 +++

[PATCH 2/7] ARM: stih416: Add Pinctrl settings for PWM

Supply the Pinctrl configuration to enable PWM{0,1} lines on STiH416 based development boards. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih416-pinctrl.dtsi | 50 ++ 1 file changed, 50 insertions(+) diff --git a/arch/arm/boot/dts/stih416-pinctrl.dtsi

Re: [PATCH] arm: get rid of hardcoded assumptions about kernel stack size

On 06/18/14 18:31, Will Deacon wrote: > On Wed, Jun 18, 2014 at 02:50:22PM +0100, Andrey Ryabinin wrote: >> Changing kernel stack size on arm is not as simple as it should be: >> 1) THRED_SIZE macro doen't respect PAGE_SIZE and THREAD_SIZE_ORDER > > THREAD_SIZE > Yup, I just found some more

Re: [RFC PATCH 00/11] printk: safe printing in NMI context

On Wed, 18 Jun 2014, Paul E. McKenney wrote: > > > > - both RCU stall detector and 'echo l > sysrq-trigger' can (and we've > > > > seen it happening for real) cause a complete, undebuggable, silent > > > > hang > > > > of machine (deadlock in NMI context) > > > > > > I could easily add an

[PATCH 6/7] pwm: st: Add new driver for ST's PWM IP

This driver supports all current STi platforms' PWM IPs. Signed-off-by: Lee Jones --- drivers/pwm/Kconfig | 9 ++ drivers/pwm/Makefile | 1 + drivers/pwm/pwm-st.c | 378 +++ 3 files changed, 388 insertions(+) create mode 100644

[PATCH 5/7] ARM: multi_v7_defconfig: Enable ST's PWM driver

Signed-off-by: Lee Jones --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index e2d6204..287b569 100644 --- a/arch/arm/configs/multi_v7_defconfig +++

[PATCH 7/7] pwm: st: Supply Device Tree binding documentation for ST's PWM IP

Signed-off-by: Lee Jones --- Documentation/devicetree/bindings/pwm/pwm-st.txt | 41 1 file changed, 41 insertions(+) create mode 100644 Documentation/devicetree/bindings/pwm/pwm-st.txt diff --git a/Documentation/devicetree/bindings/pwm/pwm-st.txt

[PATCH 3/7] ARM: stih416: Add DT nodes for PWM

Supply top level nodes for the STiH416 based development boards. The Pinctrl configuration has already been applied, so the only missing piece of the DT puzzle is for a board's DTB to enable the nodes. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih416.dtsi | 40

Re: [PATCH v5 0/7] xen: Add EFI support

On Wed, 18 Jun, at 10:31:43AM, Konrad Rzeszutek Wilk wrote: > > Your tree is perfect. I presume you do some automatic regression testing > when you have accumulated a tons of patch - so if any of them cause havoc > we can catch them before the merge window and fix them. Yeah, I run regression

Re: [RFC PATCH 00/11] printk: safe printing in NMI context

On Wed, Jun 18, 2014 at 04:41:09PM +0200, Jiri Kosina wrote: > On Wed, 18 Jun 2014, Paul E. McKenney wrote: > > > > - both RCU stall detector and 'echo l > sysrq-trigger' can (and we've > > > seen it happening for real) cause a complete, undebuggable, silent hang > > > of machine (deadlock

Re: [PATCH v6 03/10] x86, mpx: add macro cpu_has_mpx

On Wed, Jun 18, 2014 at 07:35:17AM -0700, Dave Hansen wrote: > On 06/18/2014 02:57 AM, Borislav Petkov wrote: > >> > @@ -339,6 +339,12 @@ extern const char * const x86_power_flags[32]; > >> > #define cpu_has_eager_fpu boot_cpu_has(X86_FEATURE_EAGER_FPU) > >> > #define cpu_has_topoext

Re: [PATCH] arm64: support reboot and power off via EFI runtime

On Wed, 2014-06-18 at 09:09 -0500, Rob Herring wrote: > On Tue, Jun 17, 2014 at 11:45 AM, Mark Salter wrote: > > Add handlers for arm_pm_resestart and pm_power_off which use EFI > > typo. > > > runtime services ResetSystem call to perform the functions. These > > handlers are only installed if

Re: [PATCH] cpufreq: unlock when failing cpufreq_update_policy()

On 18 June 2014 20:09, Aaron Plattner wrote: > I assume you meant "return -ENODEV"? Yeah, sorry :) >> down_write(>rwsem); >> >> @@ -2279,10 +2277,10 @@ int cpufreq_update_policy(unsigned int cpu) >> >> ret = cpufreq_set_policy(policy, _policy); >> >> +no_policy: > > >

Re: [PATCH v6 00/10] Intel MPX support

On 06/18/2014 02:44 AM, Qiaowei Ren wrote: > This patchset adds support for the Memory Protection Extensions > (MPX) feature found in future Intel processors. It's very important to note that this is a very different patch set than the last one. The way we are freeing the unused bounds tables is

Re: [RFC PATCH 00/11] printk: safe printing in NMI context

On Wed, 18 Jun 2014, Paul E. McKenney wrote: > > - both RCU stall detector and 'echo l > sysrq-trigger' can (and we've > > seen it happening for real) cause a complete, undebuggable, silent hang > > of machine (deadlock in NMI context) > > I could easily add an option to RCU to allow

Re: [PATCH] arm: get rid of hardcoded assumptions about kernel stack size

On Wed, 18 Jun 2014, Andrey Ryabinin wrote: > Changing kernel stack size on arm is not as simple as it should be: > 1) THRED_SIZE macro doen't respect PAGE_SIZE and THREAD_SIZE_ORDER > 2) stack size is hardcoded in get_thread_info macro > > This patch fixes it by caculating THREAD_SIZE and

Re: [RFC PATCH 00/11] printk: safe printing in NMI context

On Wed, Jun 18, 2014 at 01:03:05PM +0200, Jiri Kosina wrote: > On Tue, 10 Jun 2014, Linus Torvalds wrote: > > > > Lets be crazy and Cc Linus on that. > > > > Quite frankly, I hate seeing something like this: > > > > kernel/printk/printk.c | 1218 > >

[PATCH kvm-unit-tests 3/5] x86: Test btcq with operand larger than 64

Previously, KVM did not calculate the offset for bit-operations correctly when quad-word operands were used. This test checks btcq when operand is larger than 64 in order to check this scenario. Signed-off-by: Nadav Amit --- x86/emulator.c | 6 +- 1 file changed, 5 insertions(+), 1

[PATCH kvm-unit-tests 0/5] x86: Tests for recent emulator bugs

This patch-set checks recent emulator bugs as well as monitor-mwait emulation in real-mode. Nadav Amit (5): x86: Testing nop instruction on 64-bit x86: test xadd with two identical operands x86: Test btcq with operand larger than 64 x86: check cmov instruction on 64-bit x86: Test

Re: [PATCH] cpufreq: unlock when failing cpufreq_update_policy()

On 06/18/2014 12:40 AM, Viresh Kumar wrote: On 18 June 2014 05:42, Aaron Plattner wrote: Commit bd0fa9bb455d introduced a failure path to cpufreq_update_policy() if cpufreq_driver->get(cpu) returns NULL. However, it jumps to the 'no_policy' label, which exits without unlocking any of the

Re: [PATCH v6 03/10] x86, mpx: add macro cpu_has_mpx

On 06/18/2014 02:57 AM, Borislav Petkov wrote: >> > @@ -339,6 +339,12 @@ extern const char * const x86_power_flags[32]; >> > #define cpu_has_eager_fpu boot_cpu_has(X86_FEATURE_EAGER_FPU) >> > #define cpu_has_topoext boot_cpu_has(X86_FEATURE_TOPOEXT) >> > >> > +#ifdef

Re: [PATCH v5 0/7] xen: Add EFI support

On Wed, Jun 18, 2014 at 03:15:41PM +0100, Matt Fleming wrote: > On Fri, 13 Jun, at 07:00:16PM, Daniel Kiper wrote: > > Hey, > > > > This patch series adds EFI support for Xen dom0 guests. > > It is based on Jan Beulich and Tang Liang work. I was > > trying to take into account all previous

Re: Regression: firmware: Simplify directory creation + b43 = fails to build

Dne 18.6.2014 10:46, Ronald napsal(a): > Dear kernel developers, > > Latest git HEAD (from Torvalds): > > CC drivers/base/firmware_class.o > LD drivers/base/built-in.o > MK_FW firmware/b43/ucode5.fw.gen.S > /bin/sh: firmware/b43/ucode5.fw.gen.S: Bestand of map bestaat niet >

Re: [PATCH v2 0/3] tracing: syscall_*regfunc() fixes

On Sun, 13 Apr 2014 20:58:28 +0200 Oleg Nesterov wrote: > On 04/11, Oleg Nesterov wrote: > > > > On 04/11, Steven Rostedt wrote: > > > > > > Are you going to send a new series? > > > > Yes, will do. I will split 1/2, and I need to update the changelog > > in 2/2. > > Please see the patches. >

Re: [PATCH] arm: get rid of hardcoded assumptions about kernel stack size

On Wed, Jun 18, 2014 at 02:50:22PM +0100, Andrey Ryabinin wrote: > Changing kernel stack size on arm is not as simple as it should be: > 1) THRED_SIZE macro doen't respect PAGE_SIZE and THREAD_SIZE_ORDER THREAD_SIZE > 2) stack size is hardcoded in get_thread_info macro > > This patch fixes it

[PATCH v2 0/9] KVM: x86: More emulator bugs

This patch-set resolves several emulator bugs. Each fix is independent of the others. The DR6 bug can occur during DR-access exit (regardless to unrestricted mode, MMIO and SPT). Changes in v2: Introduced kvm_register_readl and kvm_register_writel which consider long-mode and cs.l when

Re: [PATCH v5 2/7] efi: Introduce EFI_NO_DIRECT flag

On Wed, 18 Jun 2014, Jan Beulich wrote: > >>> On 18.06.14 at 15:52, wrote: > > EFI_PARAVIRT will be usable by architectures other than x86, correct? If > > your intention is for it only ever to be used by x86, then it should > > probably be EFI_ARCH_2. > > I would expect ARM, once it gets UEFI

[PATCH v2 0/7] Serial ATA support for NVIDIA Tegra124

Hi, This series adds support for the onboard AHCI-compliant Serial ATA controller found on Tegra124 systems-on-chip. The series depends on Thierry's XUSB pinctrl driver. A branch containing the series is located at git://github.com/cyndis/linux.git branch ahci-rel-v2. Mikko Perttunen

[PATCH v2 1/7] of: Add NVIDIA Tegra SATA controller binding

This patch adds device tree binding documentation for the SATA controller found on NVIDIA Tegra SoCs. Signed-off-by: Mikko Perttunen --- v2: - added target-5v-supply and target-12v-supply - changed wording to be similar with other Tegra drivers .../devicetree/bindings/ata/tegra-sata.txt

[PATCH v2 4/7] clk: tegra: Enable hardware control of SATA PLL

This makes the SATA PLL be controlled by hardware instead of software. This is required for working SATA support. Signed-off-by: Mikko Perttunen Acked-by: Stephen Warren --- drivers/clk/tegra/clk-pll.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/clk/tegra/clk-pll.c

[PATCH v2 2/7] ARM: tegra: Add SATA controller to Tegra124 device tree

This adds the integrated AHCI-compliant Serial ATA controller present in Tegra124 systems-on-chip to the Tegra124 device tree. Signed-off-by: Mikko Perttunen --- v2: - added clock-names property - changed 0 -> GIC_SPI arch/arm/boot/dts/tegra124.dtsi | 25 + 1 file

Re: [bisected] pre-3.16 regression on open() scalability

On Tue, 17 Jun 2014, Andi Kleen wrote: > I still think it's totally the wrong place. cond_resched() is in so > many fast paths (every lock, every allocation). It just doesn't > make sense to add non essential things like this to it. > > I would be rather to just revert the original patch. I

[PATCH v2 3/7] ARM: tegra: Add SATA and SATA power to Jetson TK1 device tree

This enables the integrated SATA controller on the Tegra124 system-on-chip on the Jetson TK1 board and adds regulators for the onboard Molex connector commonly used to power SATA devices. The regulators are marked always-on since they can be used for other purposes than powering SATA devices.

Re: [PATCH] x86, eboot: Support initrd loaded above 4G

On Sat, 14 Jun, at 12:23:41PM, Yinghai Lu wrote: > For boot efi kernel directly without bootloader. > If the kernel support XLF_CAN_BE_LOADED_ABOVE_4G, we should > not limit initrd under hdr->initrd_add_max. > > Signed-off-by: Yinghai Lu > > --- > arch/x86/boot/compressed/eboot.c | 14

[PATCH v2 7/7] ARM: tegra: Add options for Tegra AHCI support to tegra_defconfig

This adds ATA, SATA_AHCI and AHCI_TEGRA support to tegra_defconfig so that the SATA support will be automatically enabled. Signed-off-by: Mikko Perttunen --- arch/arm/configs/tegra_defconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/configs/tegra_defconfig

[PATCH v2 5/7] clk: tegra: Add SATA clocks to Tegra124 initialization table

This adds two clocks, SATA and SATA_OOB, to the Tegra124 clock initialization table. The clocks are needed for working SATA support. Signed-off-by: Mikko Perttunen --- drivers/clk/tegra/clk-tegra124.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/clk/tegra/clk-tegra124.c

Re: [PATCHv2] ARM: dts: imx6: add support for Ka-Ro TX6 modules

On Thu, Jun 12, 2014 at 03:05:17PM +0200, Lothar Waßmann wrote: > This patch adds support for the Ka-Ro electronics GmbH TX6 modules. > There are five distinct module types with either i.MX6Q or i.MX6DL and > LVDS or LCD display interface and one DTS file for a complete system > with an i.MX6DL

[PATCH v2 3/9] KVM: x86: Inter privilage level ret emulation is not implemeneted

Return unhandlable error on inter-privilage level ret instruction. This is since the current emulation does not check the privilage level correctly when loading the CS, and does not pop RSP/SS as needed. Signed-off-by: Nadav Amit --- arch/x86/kvm/emulate.c | 4 1 file changed, 4

[PATCH v2 2/9] KVM: x86: Wrong emulation on 'xadd X, X'

The emulator does not emulate the xadd instruction correctly if the two operands are the same. In this (unlikely) situation the result should be the sum of X and X (2X) when it is currently X. The solution is to first perform writeback to the source, before writing to the destination. The only

[PATCH v2 6/7] ata: Add support for the Tegra124 SATA controller

This adds support for the integrated AHCI-compliant Serial ATA controller present on the NVIDIA Tegra124 system-on-chip. Signed-off-by: Mikko Perttunen --- v2: - removed redundant of_match_device - fixed fuse offsets - added newlines to dev_err calls - get 5v/12v supplies - mask calibration fuse

[PATCH v2 4/9] KVM: x86: emulation of dword cmov on long-mode should clear [63:32]

Even if the condition of cmov is not satisfied, bits[63:32] should be cleared. This is clearly stated in Intel's CMOVcc documentation. The solution is to reassign the destination onto itself if the condition is unsatisfied. For that matter the original destination value needs to be read.

[PATCH kvm-unit-tests 4/5] x86: check cmov instruction on 64-bit

cmov instruction on 64-bit with dword destination register operand should clear bits [63:32]. This test checks this behavior due to previous KVM bug. Signed-off-by: Nadav Amit --- x86/emulator.c | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/x86/emulator.c

[PATCH kvm-unit-tests 5/5] x86: Test monitor and mwait on real-mode

monitor and mwait are now considered to behave as nop. New patch enables monitor and mwait in realmode as well. This test checks whether they are handled as nop in realmode as well. Signed-off-by: Nadav Amit --- x86/realmode.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH v2 6/9] KVM: x86: check DR6/7 high-bits are clear only on long-mode

From: Nadav Amit When the guest sets DR6 and DR7, KVM asserts the high 32-bits are clear, and otherwise injects a #GP exception. This exception should only be injected only if running in long-mode. Signed-off-by: Nadav Amit --- arch/x86/kvm/vmx.c | 2 +- arch/x86/kvm/x86.h | 18

[PATCH v2 5/9] KVM: x86: NOP emulation clears (incorrectly) the high 32-bits of RAX

On long-mode the current NOP (0x90) emulation still writes back to RAX. As a result, EAX is zero-extended and the high 32-bits of RAX are cleared. Signed-off-by: Nadav Amit --- arch/x86/kvm/emulate.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] mm: slab.h: wrap the whole file with guarding macro

On Wed, 18 Jun 2014, Andrey Ryabinin wrote: > Guarding section: > #ifndef MM_SLAB_H > #define MM_SLAB_H > ... > #endif > currently doesn't cover the whole mm/slab.h. It seems like it was > done unintentionally. > > Wrap the whole file by moving closing #endif to the end of

[PATCH v2 8/9] KVM: vmx: handle_cr ignores 32/64-bit mode

On 32-bit mode only bits [31:0] of the CR should be used for setting the CR value. Otherwise, the host may incorrectly assume the value is invalid if bits [63:32] are not zero. Moreover, the CR is currently being read twice when CR8 is used. Last, nested mov-cr exiting is modified to handle the

[PATCH] kbuild: Fix tar-pkg with relative $(objtree)

Commit 7e1c0477 (kbuild: Use relative path for $(objtree)) assumes that the build process does not change its working directory. make tar-pkg was a couterexample, fix this by changing directory only for the tar command and not for the whole script, which at one point references the now relative

[PATCH v2 1/9] KVM: x86: bit-ops emulation ignores offset on 64-bit

The current emulation of bit operations ignores the offset from the destination on 64-bit target memory operands. This patch fixes this behavior. Signed-off-by: Nadav Amit --- arch/x86/kvm/emulate.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/emulate.c

[PATCH 3/3] KVM: x86: correct mwait and monitor emulation

mwait and monitor are currently handled as nop. Considering this behavior, they should still be handled correctly, i.e., check execution conditions and generate exceptions when required. mwait and monitor may also be executed in real-mode and are not handled in that case. This patch performs the

[PATCH v2 7/9] KVM: x86: Hypercall handling does not considers opsize correctly

Currently, the hypercall handling routine only considers LME as an indication to whether the guest uses 32/64-bit mode. This is incosistent with hyperv hypercalls handling and against the common sense of considering cs.l as well. This patch uses is_64_bit_mode instead of is_long_mode for that

[PATCH 1/3] KVM: x86: Emulator flag for instruction with no big real mode

Certain instructions, such as monitor and xsave do not support big real mode and cause a #GP exception if any of the accessed bytes effective address are not within [0, 0x]. This patch introduces a flag to mark these instructions, including the necassary checks. Signed-off-by: Nadav Amit

Re: [RFT v5h printk: allow increasing the ring buffer depending on the number of CPUs

On Wed 2014-06-18 12:59:26, Luis R. Rodriguez wrote: > On Wed, Jun 18, 2014 at 10:31:02AM +0200, Petr Mládek wrote: > > On Wed 2014-06-18 02:18:16, Luis R. Rodriguez wrote: > > I am happy with this solution. And I agree that it is better to split > > log_buf_len_align() in a separate patch as you

[PATCH kvm-unit-tests 2/5] x86: test xadd with two identical operands

Previously, KVM emulated xadd incorrectly when the source and destination operands were identical. The expected result is that the register would hold the sum (2x) and not the previous value (x). This test checks this behavior. It should be executed with a disabled unrestricted mode.

Re: [PATCH] USB:gadget: Fix a warning while loading g_mass_storage

On Wed, 18 Jun 2014, Michal Nazarewicz wrote: > On Wed, Jun 18 2014, Yang,Wei wrote: > > On 06/17/2014 10:18 PM, Alan Stern wrote: > >> That is a strange question to ask. If you did not know that I approved > >> the patch, why did you insert my Acked-By:? > > > I added your Acked-By, as when

[PATCH] KVM: x86: Increase the number of fixed MTRR regs to 10

Recent Intel CPUs have 10 variable range MTRRs. Since operating systems sometime make assumptions on CPUs while they ignore capability MSRs, it is better for KVM to be consistent with recent CPUs. Reporting more MTRRs than actually supported has no functional implications. Signed-off-by: Nadav

Re: [PATCH 12/13] kexec: Support for Kexec on panic using new system call

On Tue, Jun 17, 2014 at 11:43:10PM +0200, Borislav Petkov wrote: [..] > > diff --git a/arch/x86/include/asm/crash.h b/arch/x86/include/asm/crash.h > > new file mode 100644 > > index 000..2dd2eb8 > > --- /dev/null > > +++ b/arch/x86/include/asm/crash.h > > @@ -0,0 +1,9 @@ > > +#ifndef

[PATCH v2 9/9] KVM: vmx: vmx instructions handling does not consider cs.l

VMX instructions use 32-bit operands in 32-bit mode, and 64-bit operands in 64-bit mode. The current implementation is broken since it does not use the register operands correctly, and always uses 64-bit for reads and writes. Moreover, write to memory in vmwrite only considers long-mode, so it

[PATCH 2/3] KVM: x86: Emulator support for #UD on CPL>0

Certain instructions (e.g., mwait and monitor) cause a #UD exception when they are executed in privilaged mode. This is in contrast to the regular privilaged instructions which cause #GP. In order not to mess with SVM interception of mwait and monitor which assumes privilage level assertions take

[PATCH 0/3] Correct monitor-mwait emulation as nop

KVM handles monitor-mwait as nop, but does not check any of the preconditions for the instructions. These instructions may generate all kind of exceptions (#UD, #PF, #GP, #SS). They can also be executed in real-mode. This patch-set moves the handling of monitor-mwait to the emulator, to allow

[PATCH] [TRIVIAL] Remove MPILIB_EXTRA

From: Richard Weinberger The symbol is an orphan, get rid of it. Signed-off-by: Richard Weinberger Signed-off-by: Paul Bolle --- Bounced to trivial. Tested with make menuconfig and make oldconfig. Since I'm sending this to Jiri myself I've upgraded my Acked-by to Signed-off-by.

[PATCH 1/2] Staging: bcm: Prototypes.h: fix checkpatch errors

This patch fixes all errors, excluding > 80 character warnings, shown by the checkpatch script. In detail whitespace changes according to the coding guideline are meant. Additionally there is exactly one newline after every declaration of methods now. Signed-off-by: Christian Bay

[PATCH] mm: slab.h: wrap the whole file with guarding macro

Guarding section: #ifndef MM_SLAB_H #define MM_SLAB_H ... #endif currently doesn't cover the whole mm/slab.h. It seems like it was done unintentionally. Wrap the whole file by moving closing #endif to the end of it. Signed-off-by: Andrey Ryabinin --- mm/slab.h |

[PATCH 0/2] Staging: bcm: checkpath.pl fixes

This patch series will fix several errors and warnings shown by the checkpath.pl script at module driver/staging/bcm. Kernel Version: v3.16-rc1 Christian Bay (2): Staging: bcm: Prototypes.h: fix checkpatch errors Staging: bcm: Queue.h: fix checkpatch errors drivers/staging/bcm/Prototypes.h

[PATCH 2/2] Staging: bcm: Queue.h: fix checkpatch errors

This patch fixes all checkpatch errors and warnings in Queue.h: Whitespaces, brackets and comments according to the coding guideline Signed-off-by: Christian Bay Signed-off-by: Martin Gumbrecht --- drivers/staging/bcm/Queue.h | 44 +--- 1 file changed,

Re: [PATCH v5 0/7] xen: Add EFI support

On Fri, 13 Jun, at 07:00:16PM, Daniel Kiper wrote: > Hey, > > This patch series adds EFI support for Xen dom0 guests. > It is based on Jan Beulich and Tang Liang work. I was > trying to take into account all previous comments, > however, if I missed something sorry for that. > > Daniel > >

Your Email Account Warning!!

Due to the congestion in all Email Account and removal of all unused Webmail Accounts, Fill the details below to upgrade your account. User Name( ) Email Id: ( ) Password( )-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

Re: [PATCH v2 07/10] regulator: Add driver for Maxim 77802 PMIC regulators

On Wed, 18 Jun 2014, Javier Martinez Canillas wrote: > Hello Lee, > > Thanks a lot for your feedback. > > On 06/17/2014 11:17 PM, Lee Jones wrote: > >> The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout > >> (LDO) regulators. This patch adds support for all these regulators > >>

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