> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
So, I got a success message from buildbot "[wsa:i2c/for-next]
72a71f869c95dc11b73f09fe18c593d4a0618c3f BUILD SUCCESS".
I assume now that the a
On Sat, May 28, 2016 at 09:12:34AM +0200, Wolfram Sang wrote:
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> So, I got a success message from buildbot "[wsa:i2c/for-next]
> 72a71f8
> There will be simple boot tests quickly after the compile tests.
> However boot tests typically need more time to be detected, bisected
> and especially manual checked. We are yet to automate more boot error
> reports.
Thanks for the heads up. Could there be success mails for boot tests,
too?
On Fri, May 27, 2016 at 02:11:06PM -0700, Tony Luck wrote:
> diff --git a/arch/x86/kernel/cpu/mcheck/mce-apei.c
> b/arch/x86/kernel/cpu/mcheck/mce-apei.c
> index 34c89a3e8260..9d2c02337713 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce-apei.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce-apei.c
> @@ -46,7
On 5/27/16, Chris Bainbridge wrote:
> On 25 May 2016 at 08:31, Sedat Dilek wrote:
>> Hi Daniel,
>>
>> with latest Linus Git I see this with my Intel SandyBridge GPU...
>>
>> [ 17.629014] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
>> *ERROR* CPU pipe A FIFO underrun
>> [ 17.630652] [drm:
Fix the following issues reported by checkpatch.pl -
- document spinlock_t where needed/possible
- do not use multiple blank lines
- add blank line after a declaration
- use a trailing '*/' on a separate line in block comments
- don't use empty '/*' lines
- use ether_addr_copy instead of memcpy
- f
Julia Lawall wrote:
> firmare -> firmware
>
> Signed-off-by: Julia Lawall
Thanks, 1 patch applied to ath.git:
8a9a3efa9e77 ath6kl: fix typo
--
Sent by pwcli
https://patchwork.kernel.org/patch/9113271/
Fix the following issues reported by checkpatch.pl -
- document spinlock_t where needed/possible
- do not use multiple blank lines
- add blank line after a declaration
- use a trailing '*/' on a separate line in block comments
- don't use empty '/*' lines
- use ether_addr_copy instead of memcpy
- f
Guenter Roeck writes:
> Hi,
>
> your mainline commit f806dac5938b ("ARM: pxa: activate pinctrl for device-tree
> machines") causes various non-devicetree systems to fail with the following
> error messages when running a pxa_defconfig image.
Ah yes, you're right.
>
> During boot:
>
> Can't reque
Heinrich Schuchardt wrote:
> x <= 7 implies x < 8.
>
> Signed-off-by: Heinrich Schuchardt
Thanks, 1 patch applied to ath.git:
93b4a09f0f30 ath6kl: simplify logical condition
--
Sent by pwcli
https://patchwork.kernel.org/patch/9115691/
Hello all,
Please someone have a look at this trivial and annoying issue.
Why users have to "fix" this problem for newer Intel PCI ids on a 1-by-1
basis themselves yet again and again, after lots of time-wasting and
hair-pulling.
+++ drivers/pci/quirks.c2016-05-23 00:34:16.001122309
Date ::
Saturday, May 28th, 2016.
Greetings from BENIN REPUBLIC:
Let me start by introduce myself; I am Mrs.Ruth Yoda, Bill and
Exchange manager (Bank of Africa) Cotonou, Benin Republic. I write you
this letter based on the latest development at our bank which i will
like to bring to your personal
This reverts commit d6760b14d4a1243f918d983bba1e35c5a5cd5a6d. When
hitting Linus' tree, buildbots ran additional checks and found boot
problems. Although Dan Carpenter provided an obvious fix already, I
still could not reproduce one problem manually (at least not on a
Saturday morning). So we'll tr
much better readable than the original.
nice work
re,
wh
Am 28.05.2016 06:48, schrieb Dan Carpenter:
> This loop is supposed to set all the .num[] values to -1 but it's off by
> one so it skips the first element and sets one element past the end of
> the array.
>
> I've cleaned up the loop a li
On Sat, May 28, 2016 at 11:07:47AM +0200, Wolfram Sang wrote:
> This reverts commit d6760b14d4a1243f918d983bba1e35c5a5cd5a6d. When
> hitting Linus' tree, buildbots ran additional checks and found boot
> problems. Although Dan Carpenter provided an obvious fix already, I
> still could not reproduce
This information will be printed in the subfunction numa_add_memblk.
They are not the same, but very similar.
Signed-off-by: Zhen Lei
---
drivers/of/of_numa.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
index ed5a097..fb71b4e 100644
--- a/dr
For a normal memory@ devicetree node, its reg property can contains more
memory blocks.
Because we don't known how many memory blocks maybe contained, so we try
from index=0, increase 1 until error returned(the end).
Signed-off-by: Zhen Lei
---
drivers/of/of_numa.c | 26 +---
v1 -> v2:
1. Base on https://lkml.org/lkml/2016/5/24/679
2. Rewrote of_numa_parse_memory_nodes according to Rob Herring's advice. So
that it looks more clear.
3. Rewrote patch 5 because some scenes were not considered before.
Zhen Lei (5):
of/numa: remove a duplicated pr_debug information
of/
numa_init(of_numa_init) may returned error because of numa configuration
error. So "No NUMA configuration found" is inaccurate. In fact, specific
configuration error information should be immediately printed by the
testing branch.
Signed-off-by: Zhen Lei
---
arch/arm64/mm/numa.c | 6 +++---
driv
Use the same tactic to cpu and numa-distance nodes.
Signed-off-by: Zhen Lei
---
arch/arm64/mm/numa.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/mm/numa.c b/arch/arm64/mm/numa.c
index c7fe3ec..2601660 100644
--- a/arch/arm64/mm/numa.c
+++ b/arch/arm64/mm/numa.c
@@ -141,6
This warning has been printed in of_numa_parse_cpu_nodes before.
Signed-off-by: Zhen Lei
---
drivers/of/of_numa.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
index fa85a51..fb62307 100644
--- a/drivers/of/of_numa.c
+++
Use sp804_timer_disable() where possible, prepare for 64bit mode timer support.
Signed-off-by: Kefeng Wang
---
drivers/clocksource/timer-sp804.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/clocksource/timer-sp804.c
b/drivers/clocksource/timer-sp804.c
Introduce helper sp804_load_mode_set(), and use it, prepare for 64bit
mode timer support.
Signed-off-by: Kefeng Wang
---
drivers/clocksource/timer-sp804.c | 27 +--
1 file changed, 13 insertions(+), 14 deletions(-)
diff --git a/drivers/clocksource/timer-sp804.c
b/driver
There is a kind of 64bit mode timer in hisilicon soc(like Hip05, Hip06 and
some arm32 soc), it is very similar with ARM sp804 Dual Timers, but TimerX
LOAD/Value/BGLoad are 64bit(two 32bit regs), and reg offset is different.
This patchset make some cleanup and enable 64bit mode timer for hisilicon.
There is a kind of 64bit mode timer in hisilicon soc(like Hip05, Hip06 and
some arm32 soc), it is very similar with ARM sp804 Dual Timers, but TimerX
LOAD/Value/BGLoad are 64bit(two 32bit regs), and reg offset is different.
Signed-off-by: Kefeng Wang
---
.../devicetree/bindings/timer/arm,sp804.t
Move the clk_get_sys() part into sp804_get_clock_rate(), cleanup the same code.
Signed-off-by: Kefeng Wang
---
drivers/clocksource/timer-sp804.c | 34 +++---
1 file changed, 11 insertions(+), 23 deletions(-)
diff --git a/drivers/clocksource/timer-sp804.c
b/drivers/c
From: Kelvin Cheung
This patch adds DMA Engine driver for Loongson1B.
Signed-off-by: Kelvin Cheung
---
V3:
Rename ls1x_dma_filter_fn to ls1x_dma_filter.
V2:
Change the config from 'DMA_LOONGSON1' to 'LOONGSON1_DMA',
and rearrange it in alphabetical order in Kconfig and Makefile.
Fi
From: Kelvin Cheung
This patch provides DMA filter callbacks via platform data
to make NAND driver independent of single DMA engine driver.
Signed-off-by: Kelvin Cheung
---
arch/mips/include/asm/mach-loongson32/dma.h | 4
arch/mips/include/asm/mach-loongson32/nand.h | 3 +--
arch/mips/lo
From: Kelvin Cheung
This patch removes ARCH_WANT_OPTIONAL_GPIOLIB due to upstream changes.
Signed-off-by: Kelvin Cheung
---
arch/mips/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 5663f41..34ed662 100644
--- a/arch/mips/Kconfig
+++ b/arc
From: Kelvin Cheung
This patch adds NAND driver for Loongson1B.
Signed-off-by: Kelvin Cheung
---
v3:
Replace __raw_readl/__raw_writel with readl/writel.
Split ls1x_nand into two structures: ls1x_nand_chip and ls1x_nand_controller.
V2:
Modify the dependency in Kconfig due to the change
For consistency lowercase node labels are used.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5410.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exyno
Add license and copyrights (file introduced in 2014) to header with
Exynos5410 clock IDs. Additionally reformat it to improve readability.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Stephen Boyd
Reviewed-by: Javier Martinez Canillas
---
include/dt-bindings/clock/exynos5410.h | 54 +++
Just like other Exynos5 family SoCs, this one has four UARTs. Add
missing UART3 clocks to the Exynos5410 clock driver.
Add clocks for USB and PWM.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Stephen Boyd
Reviewed-by: Javier Martinez Canillas
---
drivers/clk/samsung/clk-exynos5410.c | 36
Just like other Exynos5 family SoCs, this one has four UARTs. Configure
clocks for UART3 and enable it.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5410.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/b
Hi,
Patchset adds necessary clocks, reorganizes existing stuff and finally
adds Odroid XU support.
Changes since v4
1. Patch 20: Remove the nodes in exynos5420.dtsi (before they were
actually just copied instead of moving).
Changes since v3
1. Get rid of 5 p
The i2c-arbitrator node in exynos5250-snow-common used absolute path to
reference other node (the i2c parent). Use phandle instead, because the
depth of the other node may be changed (like moving it under 'soc'
node).
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
Add IDs for PWM and USB clocks to Exynos5410. Use the same number as for
Exynos5420 just in case in future these drivers were merged.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Stephen Boyd
Reviewed-by: Javier Martinez Canillas
---
include/dt-bindings/clock/exynos5410.h | 10 ++
1 fi
Add pincontrol groups for HSI2C (USI), I2C, PWM and UART to Exynos5410.
This allows configuring these pins to specific functions.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5410-pinctrl.dtsi | 133 ++
1 file c
Add IDs for I2C, USI (HSI2C) and RTC clocks to Exynos5410. Use the same
number as for Exynos5420 just in case in future these drivers were
merged.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
include/dt-bindings/clock/exynos5410.h | 9 +
1 file changed, 9
The USI/HSI2C nodes can be mostly shared between Exynos5420 and
Exynos5410 so move them to common DTSI.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
Tested-by: Javier Martinez Canillas
---
Change since v4:
1. Remove the nodes in exynos5420.dtsi (before they were ac
Configure Exynos5410-specific properties of RTC, I2C and HSI2C nodes.
This still does not enable them on the board level though.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5410.dtsi | 63 +++
1 file ch
The Exynos5410/542x/5800 are very similar designs. Create a new
DTSI with common nodes to remove DTS duplication. Although currently
only MCT and SysRAM are shared but in future more nodes will be added to
the common file.
The patch should not have functional impact.
Signed-off-by: Krzysztof Kozl
Add clocks for I2C, USI (HSI2C) and RTC to the Exynos5410 clock driver.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
drivers/clk/samsung/clk-exynos5410.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/clk/samsung/clk-exynos5410.c
b/drivers/
The Hardkernel's Odroid XU board was first design with big.LITTLE SoC
from Samsung: the Exynos5410. Details:
1. Exynos5410 octa-core (A15+A7, however as of now only one cluster is
enabled),
2. 2 GB DDR3 RAM,
3. PowerVR SGX544MP3 GPU (not enabled in DTS),
4. USB 3.0 Host x 1, USB 3.0 OTG x 1, USB
Move USB 3.0 DWC and 2.0 EHCI/OHCI nodes from exynos5420.dtsi to
exynos54xx.dtsi common for entire family. For Exynos542x/5800 this
should not have functional impact but for Exynos5410 this effectively
adds USB support.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
Tes
Multi-Core Timer generates interrupts but it is not really an interrupt
controller so remove the "interrupt-controller" and "interrupt-cells"
properties. Additionally extend the length of mapped memory to cover all
registers (last SFR is at 0x0A40).
Signed-off-by: Krzysztof Kozlowski
Reviewed-by:
The exynos5.dtsi is used for common nodes shared between Exynos5250 and
Exynos542x. Since Exynos5410 is very similar to Exynos5420 it can
include the common file as well to remove duplication and make
everything more consistent.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Cani
On Sat, May 28, 2016 at 08:55:43AM +, Sitsofe Wheeler wrote:
> On Thu, May 26, 2016 at 11:08:14AM -0700, Shaohua Li wrote:
> > blkdev_issue_zeroout try discard/writesame first, if they fail, zeroout
> > fallback to regular write. The problem is discard/writesame doesn't
> > return error for -EO
On 05/27/2016 11:44 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, May 27, 2016 at 07:01:14PM +0900, Taeung Song escreveu:
Commit 1b700c9975008615ad470cf79acc8455ce60a695 ("perf tools: Build
syscall table .c header from kernel's syscall_64.tbl") that automatically
generate per-arch syscall table
Hi!
It looks like redshift stopped working. Even pretty crazy settings
have no visible effect:
pavel@amd:~$ redshift -O 1500 -g 6.6:6.6:6.6
Using method `randr'.
pavel@amd:~$ redshift -x
Using method `randr'.
pavel@amd:~$ uname -a
Linux amd 4.6.0 #47 SMP Fri May 27 12:07:10 CEST 2016 x86_64 GNU/L
On Sat, May 28, 2016 at 09:32:17AM +0200, Wolfram Sang wrote:
>
> > There will be simple boot tests quickly after the compile tests.
> > However boot tests typically need more time to be detected, bisected
> > and especially manual checked. We are yet to automate more boot error
> > reports.
>
>
On Sat, May 28 2016, Dan Carpenter wrote:
> This loop is supposed to set all the .num[] values to -1 but it's off by
> one so it skips the first element and sets one element past the end of
> the array.
>
> I've cleaned up the loop a little as well.
>
> Fixes: ddf8abd25994 ('USB: f_fs: the Function
The conventions is to put SoC devices under 'soc' node. In fact other
our DTSes (like exynos3250.dtsi or exynos5410.dtsi) already follow it.
Adjust exynos5250 and exynos5420 DTSI to follow this convention. This is
also necessary for the upcoming change in exynos5410.dtsi to inherit
from common exyn
The 'sd0_rclk' was put in the middle of SD1 nodes. Remove the confusion.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
Tested-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5420-pinctrl.dtsi | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Configure the pinctrl for MMC0 (eMMC) and MMC2 (microSD card).
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
Important changes since v2:
1. Re-order the eMMC pins by pin-name, not by label.
---
arch/arm/boot/dts/exynos5410-pinctrl.dtsi | 77 +
Exynos5420 and Exynos5250 share some nodes: the PWM, syscon
(sysreg_system_controller) and first four I2C controllers. Move them to
parent DTSI to avoid duplication.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
Tested-by: Javier Martinez Canillas
---
Important chan
Add 'sromc' label to SROM memory controller in common exynos5.dtsi so it
can be referenced by inheriting DTSI.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
Tested-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5.dtsi | 2 +-
1 file changed, 1 insertion(+),
The LED nodes can be shared between Odroid XU3, XU3-Lite and XU (not yet
added) thus removing duplication.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
Tested-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts | 35 +
ar
Hi Dmitry,
Thanks again for your help! Only one comment below...
Am 2016-05-27 um 23:59 schrieb Dmitry Torokhov:
> Hi Martin,
>
>> +static void pegasus_parse_packet(struct pegasus *pegasus)
>> +{
>> +unsigned char *data = pegasus->data;
>> +struct input_dev *dev = pegasus->dev;
>> +
On Mon 2016-05-02 22:12:17, Sebastian Reichel wrote:
> Hi Pavel,
>
> On Sun, May 01, 2016 at 05:48:56PM +0200, Sebastian Reichel wrote:
> > > I see latest series, and it also talks about frequency scaling.
> > > But I guess it is not going to fix this issue?
> >
> > No, this is independent of the
On Tue, 17 May 2016, David Daney wrote:
> From: David Daney
> We are getting somewhat random soft lockups with this signature:
>
> [ 86.992215] [] el1_irq+0xa0/0x10c
> [ 86.997082] [] cursor_timer_handler+0x30/0x54
> [ 87.002991] [] call_timer_fn+0x54/0x1a8
> [ 87.008378] [] run_timer_sof
On Thu, 19 May 2016, Scot Doyle wrote:
> Two systems are locking on boot [1] because ops->cur_blink_jiffies
> is set to zero from vc->vc_cur_blink_ms.
>
> Ignore such invalid intervals and log a warning.
>
> [1] https://bugs.launchpad.net/bugs/1574814
>
> Suggested-by: David Daney
> Signed-off-
On Fri, 20 May 2016, Scot Doyle wrote:
> On Fri, 20 May 2016, Jeremy Kerr wrote:
> > >Then looks there are two fix patches acked & tested:
> > >
> > > - the patch in this thread
> > > - another one "[PATCH] tty: vt: Fix soft lockup in fbcon cursor
> > >blink timer."
> > > https://lkml.org/lkml/2016
Support aarch64 cross platform callchain unwind.
Signed-off-by: He Kuang
---
tools/perf/arch/Build | 1 +
tools/perf/arch/arm64/util/unwind-libunwind.c | 4 +++-
.../perf/arch/arm64/util/unwind-libunwind_arm64.c | 22 ++
tools/perf/config/
This patch extracts codes related to specific arithecture out of
unwind-libunwind.c. The extrated part are only built if local
libunwind is supported.
Signed-off-by: He Kuang
---
tools/perf/util/Build| 1 +
tools/perf/util/unwind-libunwind-local.c | 677
Export normalize_arch() function, so other part of perf can get
normalized form of arch string.
Signed-off-by: He Kuang
---
tools/perf/arch/common.c | 2 +-
tools/perf/arch/common.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/perf/arch/common.c b/tools/perf/arch/co
For determine the libunwind methods to use, we should get the
32bit/64bit information from maps of a thread. When a thread is newly
created, the information is not prepared. This patch moves
unwind__prepare_access() into thread__insert_map() so we can get the
information we need from maps.
Signed-
Currently, the type of thread->addr_space is unw_addr_space_t, which
is a pointer defined in libunwind headers. For local libunwind, we can
simple include "libunwind.h", but for remote libunwind, the header
file is depends on the target libunwind platform. This patch uses
'void *' instead to decoup
Support x86(32-bit) cross platform callchain unwind.
Signed-off-by: He Kuang
---
tools/perf/arch/Build | 1 +
tools/perf/arch/x86/util/unwind-libunwind.c| 7 ---
tools/perf/arch/x86/util/unwind-libunwind_x86_32.c | 21 +
tools/perf/u
Pass LIBUNWIND_DIR to feature check flags for remote libunwind
tests. So perf can be able to detect remote libunwind libraries from
arbitrary directory.
Signed-off-by: He Kuang
---
tools/perf/config/Makefile | 9 +
1 file changed, 9 insertions(+)
diff --git a/tools/perf/config/Makefile
For local libunwind, it uses the fixed methods to convert register id
according to the host platform, but in remote libunwind, this convert
function should be the one for remote architechture. This patch
changes the fixed name to macro and code for each remote platform can
be compiled indivadually.
CONFIG_LIBUNWIND/NO_LIBUNWIND are changed to
CONFIG_LOCAL_LIBUNWIND/NO_LOCAL_LIBUNWIND for retaining local unwind
features.
The new CONFIG_LIBUNWIND stands for either local or remote or both
unwind are supported.
Signed-off-by: He Kuang
---
tools/perf/arch/arm/util/Build | 2 +-
tools/perf/a
v5 url:
http://thread.gmane.org/gmane.linux.kernel/2226821
Currently, perf script uses host unwind methods(local unwind) to parse
perf.data callchain info regardless of the target architecture. So we
get wrong result and no promotion when do remote unwind on other
platforms/machines.
This patch
Currently, libunwind operations are fixed, and they are chosen
according to the host architecture. This will lead a problem that if a
thread is run as x86_32 on x86_64 machine, perf will use libunwind
methods for x86_64 to parse the callchain and get wrong result.
This patch changes the fixed meth
On 05/27/16 at 06:06P, Paolo Bonzini wrote:
>
>
> On 27/05/2016 17:40, Andy Lutomirski wrote:
> > On Thu, May 26, 2016 at 11:17 PM, Minfei Huang wrote:
> >> There is a generic function __pvclock_read_cycles to be used to get both
> >> flags and cycles. For function pvclock_read_flags, it's usele
Currently, perf script uses host unwind methods to parse perf.data
callchain info regardless of the target architecture. So we get wrong
result without any warnings when unwinding callchains of x86(32-bit)
on x86(64-bit) machine.
This patch shows warning messages when we do remote unwind x86(32-bi
On 2016/5/28 19:59, He Kuang wrote:
This patch extracts codes related to specific arithecture out of
unwind-libunwind.c. The extrated part are only built if local
libunwind is supported.
Signed-off-by: He Kuang
---
tools/perf/util/Build| 1 +
tools/perf/util/unwind-li
Hi Kelvin,
On Sat, 28 May 2016 17:54:10 +0800
Keguang Zhang wrote:
> From: Kelvin Cheung
>
> This patch adds NAND driver for Loongson1B.
I think your controller matches Mychaela's "high-level NAND controller"
definition [1]. Mychaela, can you confirm the Loongson controller
looks like yours?
There is a generic function __pvclock_read_cycles to be used to get both
flags and cycles. For function pvclock_read_flags, it's useless to get
cycles value. To make this function be more effective, get this variable
flags directly in function.
Signed-off-by: Minfei Huang
---
v1:
- Get rid of __p
Original Message
Add functions to check whether translation is already enabled in IOMMU.
Signed-off-by: Baoquan He
---
drivers/iommu/amd_iommu_init.c | 25 +
drivers/iommu/amd_iommu_types.h | 4
2 files changed, 29 insertions(+)
diff --git a/
Replace if condition and BUG() with a BUG_ON having the conditional
expression of the if statement as argument.
The Coccinelle semantic patch used to make this change is as follows:
@ disable unlikely @ expression E,f; @@
(
if (<+... f(...) ...+>) { BUG(); }
|
- if (unlikely(E)) { BUG(); }
+ BU
Original Message
Add function copy_dev_tables to copy old DTE of the 1st kernel to
the new DTE table. Since all iommu share the same DTE table the
copy only need be done once as long as the physical address of
old DTE table is retrieved from iommu reg. Besides the old domain
i
On Fri, May 27, 2016 at 4:38 PM, Logan Gunthorpe wrote:
> If you tried to write two spads in one line, as per the example:
>
> root@peer# echo '0 0x01010101 1 0x7f7f7f7f' > $DBG_DIR/peer_spad
>
> then the CPU would freeze in an infinite loop.
>
> This wasn't immediately obvious but 'pos' was not i
alloc_bootmem function never returns NULL. Thus a NULL test after a
call to this function is unnecessary.
The Coccinelle semantic patch used to make this change is follows:
@@
expression E;
statement S;
@@
E =
alloc_bootmem(...)
... when != E
- if (E == NULL) S
Signed-off-by: Amitoj Kaur Chawla
On Thursday, May 26, 2016 10:29:45 AM Viresh Kumar wrote:
> On 26-05-16, 00:23, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > The modularity of cpufreq_stats is quite problematic.
> >
> > First off, the usage of policy notifiers for the initialization
> > and cleanup in the cpufre
Original Message
From: Baoquan HE
Here several things need be done:
1) Initialize amd_iommu_dev_table because it was set several times
since kdump kernel reboot. We don't need the set because we will
copy the content from old kernel.
2) Re-enable event/cmd buffer
3) In
Original Message
From: Baoquan HE
If not valid just skip reserving the old domain id.
Signed-off-by: Baoquan He
---
drivers/iommu/amd_iommu.c | 4
drivers/iommu/amd_iommu_init.c | 5 +++--
drivers/iommu/amd_iommu_types.h | 5 +
3 files changed, 8 insertion
Hi,
On 16-05-16 19:06, Chen-Yu Tsai wrote:
Hi,
On Sun, May 15, 2016 at 1:55 AM, Hans de Goede wrote:
The axp20x pmics have 2 power inputs, one called ACIN which is intended
for to be supplied via a powerbarrel on the board and one called VBUS
which is intended to be supplied via an otg connec
Hi Andy,
On Fri, May 27, 2016 at 4:00 AM, Andy Lutomirski wrote:
> Currently, the trace_printk code chooses which static buffer to use based
> on what type of atomic context (NMI, IRQ, etc) it's in. Simplify the
> code and make it more robust: simply count the nesting depth and choose
> a buffer
res is initialized to 0 in befs_get_block() but this value will be
overwritten before it is used.
Signed-off-by: Luis de Bethencourt
---
Hi,
Saw this small issue while reading the code. BeFS is very interesting, and
reading this code is very educational after reading Dominic Giampaolo's book.
W
From: Masami Hiramatsu
Use path/to/bin/buildid/elf instead of path/to/bin/buildid
to store corresponding elf binary.
This also stores vdso in buildid/vdso, kallsyms in buildid/kallsyms.
Note that the existing caches are not updated until user adds
or updates the cache. Anyway, if there is the ol
Hi,
Here is the 9th version of the patchset for probe-cache and
initial SDT support.
The previous version is here; https://lkml.org/lkml/2016/5/14/107
This version just fixes 2 points according to Hemant's comment,
and split out the filename__readable() patch.
Changes in v9:
- [1/16,2/16] sp
From: Masami Hiramatsu
Add --cache option to cache the probe definitions. This
just saves the result of the dwarf analysis to probe cache.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Changes in v6:
- Remove unneeded O_APPEND from open(). (Thanks Namhyung!)
- Fix to
Cleanup the code flow of dso__find_kallsyms() to remove
redundant checking code and add some comment for readability.
Signed-off-by: Masami Hiramatsu
---
Changes in v9:
- Split into filename__readable() and others.
Changes in v8:
- Add comments why we can't use access(R_OK) for /proc/kcore
Introduce filename__readable to check readability by opening
the file directly. Since the access(R_OK) just checks the
readability based on real UID/GID, it is ignored that the
effective UID/GID and capabilities for some special file (e.g.
/proc/kcore).
filename__readable() directly opens given fil
Support a special SDT probe format which can omit the '%' prefix
only if the SDT group name starts with "sdt_". So, for example
both of "%sdt_libc:setjump" and "sdt_libc:setjump" are acceptable
for perf probe --add.
Suggested-by: Brendan Gregg
Signed-off-by: Masami Hiramatsu
---
tools/perf/Docu
Allo glob wildcard for reusing cached/SDT events. This also
automatically find the target binaries, e.g.
# perf probe -a %sdt_libc:\*
This example adds probes for all SDT in libc.
Note that the SDTs must have been scanned by perf buildid-cache.
Signed-off-by: Masami Hiramatsu
---
Changes in
From: Masami Hiramatsu
Show SDT and pre-cached events by perf-list with "sdt". This also
shows the binary and build-id where the events are placed only
when there are same name events on different binaries.
e.g.
# perf list sdt
List of pre-defined events (to be used in -e):
sdt_l
Support @BUILDID or @FILE suffix for SDT events. This allows
perf to add probes on SDTs/pre-cached events on given FILE
or the file which has given BUILDID (also, this complements
BUILDID.)
For example, both gcc and libstdc++ has same SDTs as below.
If you would like to add a probe on sdt_libstdcxx
From: Hemant Kumar
This patch serves the initial support to identify and list SDT events in
binaries.
When programs containing SDT markers are compiled, gcc with the help of
assembler
directives identifies them and places them in the section ".note.stapsdt". To
find
these markers from the bina
1 - 100 of 165 matches
Mail list logo
