On Mon, Jun 30, 2014 at 09:45:32AM +0800, Tang Chen wrote:
On 06/21/2014 04:39 AM, Marcelo Tosatti wrote:
On Fri, Jun 20, 2014 at 05:31:46PM -0300, Marcelo Tosatti wrote:
IIRC your shadow page pinning patch series support flushing of ptes
by mmu notifier by forcing MMU reload and, as a result,
On Fri, 27 Jun 2014 19:01:43 +0200, Oleg Nesterov wrote:
I do not know why dd9fa555d7bb tracing/uprobes: Move argument fetching
to uprobe_dispatcher() added the UPROBE_HANDLER_REMOVE, but it looks
wrong.
OK, perhaps it makes sense to avoid store_trace_args() if the tracee is
nacked by
Hi Oleg,
On Fri, 27 Jun 2014 19:01:36 +0200, Oleg Nesterov wrote:
This reverts commit 43fe98913c9f67e3b523615ee3316f9520a623e0.
This patch is very wrong. Firstly, this change leads to unbalanced
uprobe_unregister(). Just for example,
# perf probe -x /lib/libc.so.6 syscall
#
From: Aubrey Li aubrey...@linux.intel.com
The Power Management Controller (PMC) controls many of the power
management features present in the SoC. This driver provides the power
off functionality and s0ix residency control, also provides the SOC
device state and platform sleep state observation
The Power Management Controller (PMC) controls many of the power
management features present in the Atom SoC. This driver provides
a native power off function via PMC PCI IO port.
On some ACPI hardware-reduced platforms(e.g. ASUS-T100), ACPI sleep
registers are not valid so that (*pm_power_off)()
Disable PMC S0IX_WAKE_EN events coming from LPC block(unused) and
also from GPIO_SUS ored dedicated IRQs (must be disabled as per PMC
programming rule), GPIOSCORE ored dedicated IRQs (must be disabled
as per PMC programming rule), GPIO_SUS shared IRQ (not necessary
since the IOAPIC_DS wake event
Add the following interfaces to exposes PMC device state and sleep
state residency via debugfs:
/sys/kernel/debugfs/pmc_atom/dev_state
/sys/kernel/debugfs/pmc_atom/sleep_state
Signed-off-by: Aubrey Li aubrey...@linux.intel.com
Signed-off-by: Kasagar, Srinidhi
On Fri, 27 Jun 2014 19:01:46 +0200, Oleg Nesterov wrote:
The usage of uprobe_buffer_enable() added by dcad1a20 is very wrong,
1. uprobe_buffer_enable() and uprobe_buffer_disable() are not balanced,
_enable() should be called only if !enabled.
2. If uprobe_buffer_enable() fails
Hi Russell,
-Original Message-
It's not that serious... I know that the FEC ethernet driver is horrendously
racy (I have had a patch set for about the last six months which fixes some of
its problems) but as I've had a lot of patches to deal with, and it's been
pushed to the back of
From: Sami Laine laine.j.s...@gmail.com
Sparse warning corrections for incorrect printk format characters.
Signed-off-by: Sami Laine laine.j.s...@gmail.com
---
diff --git a/drivers/staging/rts5208/rtsx.c b/drivers/staging/rts5208/rtsx.c
index c0a0e60..e0e8693 100644
---
Commit 8d6f7c5a: powerpc/powernv: Make it possible to skip the IRQHAPPENED
check in power7_nap() added code that prevents even cores which enter sleep
on idle, from checking for pending interrupts. Fix this.
Signed-off-by: Preeti U Murthy pre...@linux.vnet.ibm.com
---
All its callers depends on the return value of -ENOBUFS to reallocate a
bigger buffer and retry the receiving. So there's no need to call
pr_err() here since it was not a real issue, otherwise syslog will be
flooded by this false warning.
Cc: K. Y. Srinivasan k...@microsoft.com
Cc: Haiyang Zhang
On 2014/6/28 6:10, Luck, Tony wrote:
Not all machine checks are fatal - it would be bad for us to go into
an infinite spin instead of executing the recovery code.
Then for the time being extlog shouldn't hook into the decoder chain
but into mce_process_work, i.e. the last should call it. Or
This patch set is made based on kernel 3.15.0-rc8.
It's aimed to re-architecture the cyapa driver to support
old gen3 trackpad device and new gen5 trackpad device in one
cyapa driver for easily productions support based on
customers' requirements, and add sysfs functions and interfaces
supported
Add suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the power management
strategy of trackpad device as their requirements.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git
Add runtime_suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the runtime power
management strategy of trackpad device as their requirements.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git
Hello,
thanks for your reply!
On Fri, 27 Jun 2014 10:46:28 -0700
Greg Kroah-Hartman gre...@linuxfoundation.org wrote:
On Fri, Jun 27, 2014 at 01:37:21PM +0200, Richard Leitner wrote:
Replace all hardcoded ttyGS strings with the PREFIX macro.
Why?
Because IMHO if PREFIX is available it
Add key basic function interfaces in cyapa driver in sysfs system,
these interfaces are commonly used in pre- and after production, and
for trackpad device state checking, manage and firmware image updating.
These interfaces including firmware_version and product_id interfaces
for reading firmware
On Sunday 29 June 2014 22:52:40 Nicholas Krause wrote:
disables the IRQ line in gemmi_idle before calling cpu_do_idle.
In addition, according to the Fixme message in this file fixes
races that may occur due to not disabling the IRQ before calling
cpu_do_idle.
Signed-off-by: Nicholas Krause
Based on the cyapa core, add the gen3 trackpad device's basic functions
supported, so gen3 trackpad device can work with kernel input system.
The basic function is absolutely same as previous cyapa driver only
support gen3 trackpad device.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley
Add read_fw and raw_data debugfs interfaces for easier issues location
and collection when report by user.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git a/drivers/input/mouse/cyapa.c b/drivers/input/mouse/cyapa.c
index 3b80de6..b5dc9f9 100644
---
Add firmware image update function supported for gen3 trackpad device,
which its function is supplied through cyapa core update_fw interface.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git a/drivers/input/mouse/cyapa_gen3.c b/drivers/input/mouse/cyapa_gen3.c
Add report baseline and force calibrate functions supported for gen3
trackpad device, which these functions are supplied through
cyapa core baseline and calibrate interfaces.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git a/drivers/input/mouse/cyapa_gen3.c
Add read firmware image function supported for gen3 trackpad device,
which its function is supplied through cyapa core read_fw interface.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git a/drivers/input/mouse/cyapa_gen3.c b/drivers/input/mouse/cyapa_gen3.c
index
Add firmware image update function supported for gen5 trackpad device,
which its function is supplied through cyapa core update_fw interface.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git a/drivers/input/mouse/Kconfig b/drivers/input/mouse/Kconfig
index
On 2014-06-30 04:04, Hui Wang wrote:
On 06/29/2014 07:33 PM, Jan Kiszka wrote:
On 2013-11-27 07:47, Hui Wang wrote:
Most Thinkpad Edge series laptops use conexant codec, so far although
the codecs have different minor Vendor Id and minor Subsystem Id,
they all belong to the cxt5066 family,
Add report baseline and force calibrate functions supported for gen5
trackpad device, which these functions are supplied through
cyapa core baseline and calibrate interfaces.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley d...@cypress.com
---
diff --git a/drivers/input/mouse/cyapa_gen5.c
Add read firmware image function supported for gen5 trackpad device,
which its function is supplied through cyapa core read_fw interface.
Through this interface, upper layer application can read out, check
and backup the firmware image in trackpad device before updated
with new one when new
Add the function to monitor lid close event to suspend and resume
trackpad device.
Because system suspend takes some time to trigger from user space,
and in that time, the lid panel of the laptop may couple with the
active trackpad. This may generate stray input events, which may
in turn cancel
From: Sami Laine laine.j.s...@gmail.com
Sparse warning correction:
CHECK drivers/staging/media/solo6x10/solo6x10-v4l2-enc.c
drivers/staging/media/solo6x10/solo6x10-jpeg.h:113:21: warning: symbol 'jpeg_dqt
' was not declared. Should it be static?
The symbol jpeg_dqt is used just in
On (Sun) 29 Jun 2014 [10:41:33], Fabian Frederick wrote:
Fix checkpatch warning:
WARNING: debugfs_remove_recursive(NULL) is safe this check is probably not
required
Cc: Amit Shah amit.s...@redhat.com
Cc: Arnd Bergmann a...@arndb.de
Cc: virtualizat...@lists.linux-foundation.org
On Sun 2014-06-29 17:04:28, Theodore Ts'o wrote:
On Sun, Jun 29, 2014 at 10:25:16PM +0200, Pavel Machek wrote:
One more thing that I noticed: fsck notices bad checksum on inode, and
then offers to fix the checksum with 'y' being the default. If there's
trash in the inode, that will just
From: Stephen Rothwell s...@canb.auug.org.au
Date: Mon, 30 Jun 2014 12:47:50 +1000
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from include/net/inet_connection_sock.h:23:0,
from
Hi all,
The powerpc allyesconfig is again broken more than usual.
Changes since 20140627:
The net-next tree gained a build failure so I used the version from
next-20140627.
The staging tree still had its build failure for which I disabled a driver.
Non-merge commits (relative to Linus' tree):
Hi All,
Sorry for the disturb again.
The 14 caypa V2 patches I re-sent through 14:41 to 14:45 at 2014/6/30 still
have some of them corrupted by the mail server.
Please ignore them. I will try to fix them.
Thanks,
Dudley
This message and any attachments may contain Cypress (or its subsidiaries)
OS_phystov()/OS_vtophys() are replaced with
phys_to_virt()/virt_to_phys().
Signed-off-by: Daeseok Youn daeseok.y...@gmail.com
---
V2: use virt_to_phys()/phys_to_virt() instead of __pa()/__va().
drivers/staging/cxt1e1/musycc.c | 16
OS_mem_token_tlen() is same return value as OS_mem_token_len().
That means packet count is always 1. So OS_mem_token_tlen()
must be total length of packet and OS_mem_token_len() has a
length of fragmented packet. And then it can count total
count of fragmented packets properly.
And
On Sat, Jun 28, 2014 at 11:55:19PM -0400, Ed Tomlinson wrote:
On Saturday 28 June 2014 15:28:22 Ed Tomlinson wrote:
Resend without html krud which causes list to bounce the message.
Hi
This commit ( a4de05268e674e8ed31df6348269e22d6c6a1803 ) hangs my boot with
3.16-git. Reverting
OS_mem_token_ interfaces are useless, so just replaced with
sk_buff related fuctions.
Signed-off-by: Daeseok Youn daeseok.y...@gmail.com
---
V2: rebased on changes in the first one.
drivers/staging/cxt1e1/musycc.c | 45 +-
drivers/staging/cxt1e1/pmcc4_drv.c
On Sat, Jun 28, 2014 at 01:28:19AM +0200, Borislav Petkov wrote:
Ok, cool. So guys, can we apply this one so that I can continue with the
next round?
Ok, I had this crazy idea recently:
How about we copy the perf tool code we need for the RAS daemon and
start hacking on it in a separate repo,
-Original Message-
From: Mark Brown [mailto:broo...@kernel.org]
Sent: Saturday, June 28, 2014 12:01 AM
To: Opensource [James Seong-Won Ban]
Cc: Liam Girdwood; Support Opensource; LKML; David Dajun Chen
Subject: Re: [PATCH V3] regulator: DA9211 : new regulator driver
On Mon, Jun
This was introduced by:
commit 206a81c18401c0cde6e579164f752c4b147324ce
Author: Greg Kroah-Hartman gre...@linuxfoundation.org
Date: Fri Jun 20 22:00:53 2014 -0700
lzo: properly check for overruns
Thanks,
//richard
Original-Nachricht
Betreff: New Defects reported by
Simply use ret variable instead.
Also remove unneeded initialize for ret variable.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/act8865-regulator.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/regulator/act8865-regulator.c
Silence below build warning:
CC [M] drivers/regulator/act8865-regulator.o
drivers/regulator/act8865-regulator.c: In function ‘act8865_pmic_probe’:
drivers/regulator/act8865-regulator.c:321: warning: ‘of_node’ may be used
uninitialized in this function
Signed-off-by: Axel Lin
On 06/18/2014 12:50 PM, Michael wang wrote:
By testing we found that after put benchmark (dbench) in to deep cpu-group,
tasks (dbench routines) start to gathered on one CPU, which lead to that the
benchmark could only get around 100% CPU whatever how big it's task-group's
share is, here is the
Hi Linus,
On Fri, Jun 27, 2014 at 07:03:45PM -0700, Linus Torvalds wrote:
this email was in my spam-box. No real indication as to why, although
the usual suspect is
Received-SPF: none (google.com: j...@8bytes.org does not designate
permitted sender hosts) client-ip=85.214.48.195;
Hmm,
Recently testing show that the cpu-cgroup was failed on managing the mixed
workloads of dbench and stress, by doing:
mkdir /cgroup/cpu/l1/
mkdir /cgroup/cpu/l1/A
mkdir /cgroup/cpu/l1/B
mkdir /cgroup/cpu/l1/C
echo $$ /cgroup/cpu/l1/A/tasks ; dbench 6
I now booted 3.16-rc3 and suddenly see an oops during boot:
the oops during boot: http://tny.cz/2301e393
also below
lshw if interesting: http://tny.cz/3c9a7609
the full boot log: http://tny.cz/88260b19
does anyone have an idea?
thanks
the oops:
Jun 30
On Sat, 28 Jun 2014, Fabian Frederick wrote:
Fix checkpatch warning:
WARNING: debugfs_remove(NULL) is safe this check is probably not required
Cc: Jiri Kosina jkos...@suse.cz
Cc: linux-in...@vger.kernel.org
Signed-off-by: Fabian Frederick f...@skynet.be
---
On 06/26/2014 06:06 PM, Tero Kristo wrote:
On 06/26/2014 05:22 PM, Roger Quadros wrote:
+Tero
On 06/26/2014 12:36 PM, Roger Quadros wrote:
On 06/26/2014 10:31 AM, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [140625 15:29]:
On 06/25/2014 07:56 AM, Roger Quadros wrote:
The SATA and USB
The size of the buffer program has been increased from 256 to 512 , 2ms maximum
timeout for do_write_buffer can not adapt to all the different vendor's
norflash.There maximum timeout information in the CFI area,so the best way is
to choose the result calculated according to timeout field of
On 27 June 2014 07:45, Viresh Kumar viresh.ku...@linaro.org wrote:
On 27 June 2014 07:23, Mike Turquette mturque...@linaro.org wrote:
but it isn't future-proof if/when the clock framework starts returning
dynamically allocated clock pointers for each clk_get() invocation.
Maybe we need a
Am 2014-06-30 03:29, schrieb Aaron Lu:
On 06/29/2014 04:42 PM, Martin Kepplinger wrote:
Am 2014-06-23 22:30, schrieb Martin Kepplinger:
Fix backlight control for Acer TravelMate B113 Laptop by adding
it to the video_dmi_table.
A workaround before that was to use acpi_osi=Linux or
Signed-off-by: Zhou Wang wangzhou@gmail.com
---
arch/arm/boot/dts/hip04.dtsi | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/hip04.dtsi b/arch/arm/boot/dts/hip04.dtsi
index abb42ca..e63fc61 100644
--- a/arch/arm/boot/dts/hip04.dtsi
+++
Signed-off-by: Zhou Wang wangzhou@gmail.com
---
drivers/mtd/nand/Kconfig |5 +
drivers/mtd/nand/Makefile|1 +
drivers/mtd/nand/hisi_nand.c | 847 ++
3 files changed, 853 insertions(+)
create mode 100644 drivers/mtd/nand/hisi_nand.c
This series patches add the support for NAND controller of hisilicon
hip04 Soc. These patches are base on branch integration-hilt-working-v3.14
in linaro landing-team git repository[1].
The NAND controller IP was developed by hisilicon and need a new driver
to support. The driver is usable and I
On Mon, 2014-06-30 at 15:36 +0800, Michael wang wrote:
On 06/18/2014 12:50 PM, Michael wang wrote:
By testing we found that after put benchmark (dbench) in to deep cpu-group,
tasks (dbench routines) start to gathered on one CPU, which lead to that the
benchmark could only get around 100%
Signed-off-by: Zhou Wang wangzhou@gmail.com
---
.../devicetree/bindings/mtd/hisi-nand.txt | 38
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mtd/hisi-nand.txt
diff --git
On Mon, 2014-06-30 at 09:52 +0200, Martin Kepplinger wrote:
I now booted 3.16-rc3 and suddenly see an oops during boot:
the oops during boot: http://tny.cz/2301e393
also below
lshw if interesting: http://tny.cz/3c9a7609
the full boot log: http://tny.cz/88260b19
does anyone have
Hi
On Mon, Jun 30, 2014 at 8:59 AM, Chris Wilson ch...@chris-wilson.co.uk wrote:
On Sat, Jun 28, 2014 at 11:55:19PM -0400, Ed Tomlinson wrote:
On Saturday 28 June 2014 15:28:22 Ed Tomlinson wrote:
Resend without html krud which causes list to bounce the message.
Hi
This commit (
On Mon, 2014-06-30 at 16:18 +0800, Zhang Rui wrote:
On Mon, 2014-06-30 at 09:52 +0200, Martin Kepplinger wrote:
I now booted 3.16-rc3 and suddenly see an oops during boot:
the oops during boot: http://tny.cz/2301e393
also below
lshw if interesting: http://tny.cz/3c9a7609
On Fri, Jun 27, 2014 at 02:44:41PM -0400, Mikulas Patocka wrote:
I suggest - split it to two patches, a minimal patch that fixes the bug by
changing sleeper to completion and the second patch with remaining changes
- so that only the first patch can be backported to stable kernels.
Agreed.
On Sat, 2014-06-28 at 09:59 -0700, Christopher Li wrote:
Oops, I just click send before I type up the reply. Here we go again.
On Tue, Jun 17, 2014 at 2:11 AM, Andy Shevchenko
andriy.shevche...@linux.intel.com wrote:
Very dumb patch to just skip --param allow-store-data-races=0 introduced
We encountered a scenario in which after an INIT is delivered, a pending
interrupt is delivered, although it was sent before the INIT. As the SDM
states in section 10.4.7.1, the ISR and the IRR should be cleared after INIT as
KVM does. This also means that pending interrupts should be cleared.
Replaces all hardcoded ttyGS strings with the PREFIX macro.
Due to the fact the strings are spread over different source files the
PREFIX definition is moved to u_serial.h
Signed-off-by: Richard Leitner richard.leit...@skidata.com
---
v2: removed checkpatch.pl resovling (will be in a separate
The EHCI packet buffer in/out threshold is programmable for Intel
Quark X1000 USB host controller, and the default value is 0x20 dwords.
The in/out threshold can be programmed to 0x80 dwords, but only when
isochronous/interrupt transactions are not initiated by the USB host
controller.
From: Of Richard Leitner
Replaces all hardcoded ttyGS strings with the PREFIX macro.
Due to the fact the strings are spread over different source files the
PREFIX definition is moved to u_serial.h
Lots of changes like:
- DBG(cdev, acm ttyGS%d completion, err %d\n,
-
On Mon, Jun 30, 2014 at 11:35:27AM +0300, Nadav Amit wrote:
We encountered a scenario in which after an INIT is delivered, a pending
interrupt is delivered, although it was sent before the INIT. As the SDM
states in section 10.4.7.1, the ISR and the IRR should be cleared after INIT
as
KVM
Hi, Mike :)
On 06/30/2014 04:06 PM, Mike Galbraith wrote:
On Mon, 2014-06-30 at 15:36 +0800, Michael wang wrote:
On 06/18/2014 12:50 PM, Michael wang wrote:
By testing we found that after put benchmark (dbench) in to deep cpu-group,
tasks (dbench routines) start to gathered on one CPU, which
From 28bb276ff858caecddfde78133f6b5b261c40a59 Mon Sep 17 00:00:00 2001
From: Matwey V. Kornilov mat...@sai.msu.ru
Date: Wed, 25 Jun 2014 00:53:54 +0400
Subject: [PATCH 1/2] parport: parport_pc: Introduce intel_bug_present function.
Put the code to check present of the Intel bug from
From: Matwey V. Kornilov mat...@sai.msu.ru
Date: Wed, 25 Jun 2014 00:53:54 +0400
Subject: [PATCH 0/2] parport: parport_pc: Introduce option to disable checking
for Intel bug
Hi,
The following patch series is to deal with the issue on false-positives
of Intel EPP bug check [1].
More than a
From f5384f47688c116ac765b18bfb01e28b4233b97f Mon Sep 17 00:00:00 2001
From: Matwey V. Kornilov mat...@sai.msu.ru
Date: Wed, 25 Jun 2014 01:08:45 +0400
Subject: [PATCH 2/2] parport: parport_pc: Add force_epp module option for
parport_pc.
The detection of Intel EPP bug is known to produce much
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.
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
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
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
On Mon, Jun 30, 2014 at 1:32 AM, Andy Shevchenko
andriy.shevche...@linux.intel.com wrote:
Hmm... I'd just added test printf to the handle_param() and see if I
print *next, it is either --param or --param=*. So, using return (next +
2) helps, otherwise we end up with the same situation as
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.
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
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
---
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:
LBR callstack is designed for PEBS, It does not work well with
FREEZE_LBRS_ON_PMI for non PEBS event. If FREEZE_LBRS_ON_PMI is set for
non PEBS event, PMIs near call/return instructions may cause superfluous
increase/decrease of LBR_TOS.
This patch modifies __intel_pmu_lbr_enable() to not enable
This patchset makes it possible to use kgdb's NMI infrastructure on ARM
platforms.
The patches have been previously circulated as part of a large patchset
mixing together ARM architecture code and driver changes
(http://thread.gmane.org/gmane.linux.ports.arm.kernel/333901 ). This
patchset is
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
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
---
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
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
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
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
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.
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
Hi,
On Mon, 30 Jun 2014 08:41:18 +
David Laight david.lai...@aculab.com wrote:
From: Of Richard Leitner
Replaces all hardcoded ttyGS strings with the PREFIX macro.
Due to the fact the strings are spread over different source files the
PREFIX definition is moved to u_serial.h
Lots
Currently sparse warning only output to stderr.
In the parallel build process, different source
file output is fixed together. It is hard to keep
track of the warning.
Add the CLOG=logname option in command line to
save the sparse warning into individual log file.
Typical usage:
make -j8 C=2
On Mon, 2014-06-30 at 01:51 -0700, Christopher Li wrote:
On Mon, Jun 30, 2014 at 1:32 AM, Andy Shevchenko
andriy.shevche...@linux.intel.com wrote:
Hmm... I'd just added test printf to the handle_param() and see if I
print *next, it is either --param or --param=*. So, using return (next +
Hi Gleb,
On 06/30/2014 02:00 PM, Gleb Natapov wrote:
On Mon, Jun 30, 2014 at 09:45:32AM +0800, Tang Chen wrote:
On 06/21/2014 04:39 AM, Marcelo Tosatti wrote:
On Fri, Jun 20, 2014 at 05:31:46PM -0300, Marcelo Tosatti wrote:
IIRC your shadow page pinning patch series support flushing of ptes
Currently enable_fiq/disable_fiq use a simple offset to convert an IRQ
virq into a FIQ virq. This is too inflexible for multi-platform kernels
and makes runtime error checking impossible.
We solve this by introducing a flexible mapping that allows interrupt
controllers that support FIQ to
Since the USB 2.0 PHYs are required only with EHCI/OHCI USB drivers,
make it depend on them and default to ARCH_EXYNOS as they are meant
for Exynos platforms. Also, make the sub-drivers silent options enabling
them based on the SoC platforms that they are meant to work with. This
will make life
USB DWC3 driver on Exynos platform does not work without its
corresponding phy driver. Hence make the PHY driver depend on
Exynos DWC3 driver and default it to yes to make things easier
for the end user.
Signed-off-by: Sachin Kamat sachin.ka...@samsung.com
---
drivers/phy/Kconfig |2 ++
1
From c89138e2c968c07dd11b3c6bfc05a803d0c5434d Mon Sep 17 00:00:00 2001
From: Matwey V. Kornilov mat...@sai.msu.ru
Date: Wed, 25 Jun 2014 00:53:54 +0400
Subject: [PATCHv2 1/2] parport: parport_pc: Introduce intel_bug_present
function.
Put the code to check present of the Intel bug from
From: Anton Vorontsov anton.voront...@linaro.org
Just move the macros into header file as we would want to use them for
KGDB FIQ entry code.
The following macros were moved:
- svc_entry
- usr_entry
- kuser_cmpxchg_check
- vector_stub
To make kuser_cmpxchg_check actually work across
1 - 100 of 1906 matches
Mail list logo
