From: Andi Kleen
With all the recently added fields in the perf stat CSV output
we should finally document them in the man page. Do this here.
v2: Fix fields in documentation (Jiri)
v3: fix order of fields again (Jiri)
v4: Change order again.
v5: Document more fields (Jiri)
v6: Move time stamp f
From: Andi Kleen
Only put the frontend/backend stalled cycles into the default
perf stat events when the CPU actually supports them.
This avoids empty columns with --metric-only on newer Intel CPUs.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c | 22 --
1 file ch
From: Andi Kleen
Add an extra check for frontend stalled in the metrics.
This avoids an extra column for the --metric-only case
when the CPU does not support frontend stalled.
v2: Add separate init function
Acked-by: Jiri Olsa
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c | 1 +
From: Andi Kleen
Now support CSV output for metrics. With the new output callbacks
this is relatively straight forward by creating new callbacks.
This allows to easily plot metrics from CSV files.
The new line callback needs to know the number of fields to skip them
correctly
Example output be
From: Andi Kleen
Add metric only support for -A too. This requires a new print
function that prints the metrics in the right order.
v2: Fix manpage
Signed-off-by: Andi Kleen
---
tools/perf/Documentation/perf-stat.txt | 2 +-
tools/perf/builtin-stat.c | 48
Thanks, Julian! I really appreciate your feedback.
My comments below.
On 03/02/2016 04:08 PM, Julian Calaby wrote:
Hi Khalid,
On Thu, Mar 3, 2016 at 7:39 AM, Khalid Aziz wrote:
Enable Application Data Integrity (ADI) support in the sparc
kernel for applications to use ADI in userspace. ADI
From: Andi Kleen
Enable metrics printing in --per-core / --per-socket mode. We need
to save the shadow metrics in a unique place. Always use the first
CPU in the aggregation. Then use the same CPU to retrieve the
shadow value later.
Example output:
% perf stat --per-core -a ./BC1s
Performance
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/en_main.c
between commit:
85082dba0a50 ("net/mlx5e: Correctly handle RSS indirection table when
changing number of channels")
from the net tree and commit:
08fb1dacdd76 ("ne
On Wed, Mar 02, 2016 at 02:43:04PM +0800, Xiong Zhou wrote:
> Hi,
>
> mkdir failed IO error on pmem DAX ext2/3 fs mount using ext4 module.
>
> This happends only on -next tree, not on Linus' tree,
> at least from 4.5.0-rc5-next-20160224.
I was able to reproduce this and bisect it to the followin
On Mar 1, 2016 5:11 PM, "Christopher Hall" wrote:
>
> Andy,
>
> On Mon, 29 Feb 2016 06:33:47 -0800, Christopher S. Hall
> wrote:
>
> Do you have any comment on this? John needs your ACK. Thanks.
>
It's fine with me. I think Intel messed up the design of the feature
(there should have been an
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/en_tx.c
between commit:
b081da5ee186 ("net/mlx5e: Add rx/tx bytes software counters")
from the net tree and commits:
9879515895ff ("net/mlx5e: Add TX stateless offloads for t
On Mar 2, 2016 12:10 PM, "Chris Metcalf" wrote:
>
> In prepare_exit_to_usermode(), call task_isolation_ready()
> when we are checking the thread-info flags, and after we've handled
> the other work, call task_isolation_enter() unconditionally.
>
> In syscall_trace_enter_phase1(), we add the necess
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than r8a7791 but that doesn't imply that the latter is a
descendant of
Add fallback compatibility strings for rcar phy drivers.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than r8a7791
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than r8a7791 but that doesn't imply that the latter is a
descendant of
This adds the ability for CONFIG_STACK_VALIDATION to work in a
cross-compiled environment against an x86 kernel. Based on tip/master.
Josh Poimboeuf (2):
x86/asm/decoder: Use explicitly signed chars
objtool: Support CROSS_COMPILE
arch/x86/lib/insn.c | 6 +++---
tools/li
When running objtool on a ppc64le host to analyze x86 binaries, it
reports a lot of false warnings like:
ipc/compat_mq.o: warning: objtool: compat_SyS_mq_open()+0x91: can't find jump
dest instruction at .text+0x3a5
The warnings are caused by the x86 instruction decoder setting the wrong
value
When building with CONFIG_STACK_VALIDATION on a ppc64le host with an x86
cross-compiler, Stephen Rothwell saw the following objtool build errors:
DESCEND objtool
CC /home/sfr/next/x86_64_allmodconfig/tools/objtool/builtin-check.o
CC /home/sfr/next/x86_64_allmodconfig/tools
On Mar 1, 2016 11:01 AM, "Rountree, Barry L." wrote:
>
>
>
> On 2/29/16, 3:41 PM, "Borislav Petkov" wrote:
>
> >On Mon, Feb 29, 2016 at 10:35:12PM +, Mcfadden, Marty Jay wrote:
> >> The examples provided were to address why bit-level access granularity
> >> was needed. They were not intended
On Tue, Feb 16, 2016 at 09:03:45AM +0100, Ingo Molnar wrote:
>
>
> So I think it would be useful to name this in a way the expresses that this
> is a
> mask.
>
> 'tick_dep_mask' or so?
[...]
> >
> > +enum tick_dependency_bit {
>
> s/tick_dep_bits
>
> > + TICK_POSIX_TIMER_BIT= 0,
>
From: Kuninori Morimoto
commit 23b92e4cf5fd ("regmap: remove regmap_write_bits()")
removed regmap_write_bits(), but MFD driver was using it.
So, commit e30fccd6771d ("regmap: Keep regmap_write_bits()")
turns out it, but it is using original style.
This patch uses regmap_update_bits_base() for re
Hi Khalid,
On Thu, Mar 3, 2016 at 11:25 AM, Khalid Aziz wrote:
> Thanks, Julian! I really appreciate your feedback.
No problem!
> My comments below.
>
> On 03/02/2016 04:08 PM, Julian Calaby wrote:
>>
>> Hi Khalid,
>>
>> On Thu, Mar 3, 2016 at 7:39 AM, Khalid Aziz
>> wrote:
>>>
>>>
>>> Enable
On Wed, Mar 2, 2016 at 4:13 PM, Yinghai Lu wrote:
> On Wed, Mar 2, 2016 at 2:32 PM, H. Peter Anvin wrote:
>>
>> I'm trying to think of any reason why we couldn't simply have a symbol at
>> the top of the initial stack? Then a simple leaq would suffice; this is for
>> the BSP after all.
>
> Why
Because Linux might use bigger pages than the 4K pages to handle those mmio
ioremaps, the kmmio code shouldn't rely on the pade id as it currently does.
Using the memory address instead of the page id let's us lookup how big the
page is and what it's base address is, so that we won't get a page fa
Hi -
Can we allocate an official device major number for virtio devices?
Currently it's using 240-254 (LOCAL/EXPERIMENTAL USE). The reason we
ask for this is because userspace will need to treat virtio block
devices differently and need a way to detect such device. For example,
it checks major num
Thanks acme,
On Wednesday 02 March 2016 09:52 PM, Arnaldo Carvalho de Melo wrote:
Em Wed, Mar 02, 2016 at 09:16:48PM +0530, Ravi Bangoria escreveu:
Thanks Arnaldo,
Please find my comments.
On Wednesday 02 March 2016 07:55 PM, Arnaldo Carvalho de Melo wrote:
Em Wed, Feb 24, 2016 at 02:37:45PM
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
io-streamid
commit 3d63546519428f2ed1b79e93e4321cf37c5a0d83 ("block: add support for
carrying a stream ID in a bio")
udevd[279]: failed to execute '/sbin/modprobe' '/sbin/modprobe -bv
of
Hi David,
On Wed, Mar 02, 2016 at 01:00:21PM -0800, David Ahern wrote:
> On 3/2/16 12:31 PM, Jeremiah Mahler wrote:
> >>On Tue, Mar 01, 2016 at 08:11:54AM +, Dexuan Cui wrote:
> >>>Hi, I got this line every 10 seconds with today's linux-next in a Hyper-V
> >>>guest, even
> >>>when I didn't co
(cc -mm and Joonsoo Kim)
On 03/02/2016 05:52 AM, Hanjun Guo wrote:
Hi,
I came across a suspicious error for CMA stress test:
Before the test, I got:
-bash-4.3# cat /proc/meminfo | grep Cma
CmaTotal: 204800 kB
CmaFree: 195044 kB
After running the test:
-bash-4.3# cat /proc/me
On Wed, Mar 02, 2016 at 05:08:00PM -0800, Jin Qian wrote:
> Hi -
>
> Can we allocate an official device major number for virtio devices?
> Currently it's using 240-254 (LOCAL/EXPERIMENTAL USE). The reason we
> ask for this is because userspace will need to treat virtio block
> devices differently
Hi,
> From: Borislav Petkov [mailto:b...@alien8.de]
> On Wed, Mar 02, 2016 at 02:18:24PM +0100, Michal Hocko wrote:
> > On Wed 02-03-16 19:36:26, Hidehiro Kawai wrote:
> > [...]
> > > +void nmi_panic(struct pt_regs *regs, const char *fmt, ...)
> >
> > Do we really need vargs? All the current users
Hi Khalid,
A couple of other comments:
On Thu, Mar 3, 2016 at 5:54 AM, Khalid Aziz wrote:
>
> Enable Application Data Integrity (ADI) support in the sparc
> kernel for applications to use ADI in userspace. ADI is a new
> feature supported on sparc M7 and newer processors. ADI is supported
> for
On 2016/3/2 22:38, Joonsoo Kim wrote:
> 2016-03-02 21:26 GMT+09:00 Xishi Qiu :
>> ___slab_alloc()
>> deactivate_slab()
>> add_full(s, n, page);
>> The page will be added to full list and the frozen is 0, right?
>>
>> __slab_free()
>> prior = page->freelist; // prio
With this, user can add a 'resets' property into dw_mmc dts
node, and when driver probe and parse_dt, it will call
reset APIs to reset dw_mmc host controller.
Please also refer to Documentation/devicetree/bindings/reset/reset.txt
Signed-off-by: Guodong Xu
Signed-off-by: Xinwei Kong
Signed-off-b
Add resets property to synopsys-dw-mshc bindings. It is intended to
represent the hardware reset signal present internally in some host
controller IC designs.
See Documentation/devicetree/bindings/reset/reset.txt for details.
Signed-off-by: Guodong Xu
---
Documentation/devicetree/bindings/mmc/s
On Thu, Mar 3, 2016 at 1:43 AM, Todd Brandt
wrote:
> On Thu, 2016-03-03 at 01:19 +0100, Rafael J. Wysocki wrote:
>> On Thu, Mar 3, 2016 at 1:05 AM, Todd Brandt
>> wrote:
>> > Pause/unpause graph tracing around do_suspend_lowlevel as it has
>> > inconsistent call/return info after it jumps to the
Well, fix up the Steven's address.
On Thu, Mar 3, 2016 at 2:34 AM, Rafael J. Wysocki wrote:
> On Thu, Mar 3, 2016 at 1:43 AM, Todd Brandt
> wrote:
>> On Thu, 2016-03-03 at 01:19 +0100, Rafael J. Wysocki wrote:
>>> On Thu, Mar 3, 2016 at 1:05 AM, Todd Brandt
>>> wrote:
>>> > Pause/unpause graph
On 2016/3/3 5:12, Paul E. McKenney wrote:
> On Wed, Mar 02, 2016 at 11:55:43AM -0800, Davidlohr Bueso wrote:
>> On Tue, 02 Feb 2016, Davidlohr Bueso wrote:
>>
>> I've just hit this issue myself and remembered this thread :)
>>
>> Paul, folks, does the below patch look reasonable to you? If so
>>
Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
This is part of an ongoing process to migrate from ARCH_SHMOBILE to
ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
Signed-off-by: Simon Horma
On 03/01, Srinivas Kandagatla wrote:
> The issue with setting up a fixed clock rate at probe is that it would
> overwrite the console rate set by the bootloader for its console device.
> This would result in serial out corruption or missing log when we system
> is booted with earlycon. This is not
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Leo Yan
> Cc: Bintian Wang
> Cc: Zhangfei Gao
> Cc: Haojian Zhuang
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Lin
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: James Liao
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
From: Gu Zheng
The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So that,
when node online/offline happens, cache based on cpuid <-> nodeid mapping such
as
wq_numa_possible_cpumask will not cause any problem.
It contains 4 steps:
1. Enable apic registeration flow to handle
From: Gu Zheng
The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So that,
when node online/offline happens, cache based on cpuid <-> nodeid mapping such
as
wq_numa_possible_cpumask will not cause any problem.
It contains 4 steps:
1. Enable apic registeration flow to handle
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Shawn Guo
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
From: Gu Zheng
The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So that,
when node online/offline happens, cache based on cpuid <-> nodeid mapping such
as
wq_numa_possible_cpumask will not cause any problem.
It contains 4 steps:
1. Enable apic registeration flow to handle
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Joachim Eastwood
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Robert Jarzmik
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
From: Gu Zheng
[Problem]
cpuid <-> nodeid mapping is firstly established at boot time. And workqueue
caches
the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
When doing node online/offline, cpuid <-> nodeid mapping is
established/destroyed,
which means, cpuid <-> nodeid
From: Tang Chen
For now, x86 does not support memory-less node. A node without memory
will not be onlined, and the cpus on it will be mapped to the other
online nodes with memory in init_cpu_to_node(). The reason of doing this
is to ensure each cpu has mapped to a node with memory, so that it wil
[Problem]
cpuid <-> nodeid mapping is firstly established at boot time. And workqueue
caches
the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
When doing node online/offline, cpuid <-> nodeid mapping is
established/destroyed,
which means, cpuid <-> nodeid mapping will chan
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Viresh Kumar
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Rhyland Klein
> Cc: Thierry Reding
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Projec
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Tero Kristo
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Ulf Hansson
> Cc: Linus Walleij
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Do you mean detecting device name string as in /dev/...?
Just checked latest virtio_blk code, it's dynamic but not using
anything specific to experimental range. I guess we're fine here but
Yu can confirm.
Thanks,
jin
On Wed, Mar 2, 2016 at 5:25 PM, Greg Kroah-Hartman
wrote:
> On Wed, Mar 02, 2
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Sören Brinkmann
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Uwe Kleine-König
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Philipp Zabel
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Sudeep Holla
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 03/01, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Andi Shyti
> Cc: Krzysztof Kozlowski
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Proj
Hi Dmitry,
Is there any update on this patch?
Looking forward to your response.
Thanks,
Dudley
> -Original Message-
> From: Dudley Du [mailto:d...@cypress.com]
> Sent: 2016?1?14? 13:41
> To: dmitry.torok...@gmail.com; eugene...@gmail.com
> Cc: Dudley Du; ble...@google.com; jmmah...@gmail
Hi Thomas, Ingo, hpa,
Would you please help to review the X86 part of this patch-set ?
Thanks,
Zhu
On 03/03/2016 09:42 AM, Zhu Guihua wrote:
[Problem]
cpuid <-> nodeid mapping is firstly established at boot time. And workqueue
caches
the mapping in wq_numa_possible_cpumask in wq_numa_init()
Hi Andy,
This series patches ware verified on my github with RK3368 evb and
RK30236 board.
https://github.com/Caesar-github/rockchip/tree/for-reboot-mode-tests
在 2016年03月01日 20:09, Andy Yan 写道:
This driver parse the reboot commands like "reboot loader"
and "reboot recovery" to get a boot mo
drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c:115:15-21: ERROR:
application of sizeof to pointer
sizeof when applied to a pointer typed expression gives the size of
the pointer
Generated by: scripts/coccinelle/misc/noderef.cocci
CC: Giuseppe Cavallaro
Signed-off-by: Fengguang Wu
---
Hi Guodong,
On 2016/3/3 9:33, Guodong Xu wrote:
With this, user can add a 'resets' property into dw_mmc dts
node, and when driver probe and parse_dt, it will call
reset APIs to reset dw_mmc host controller.
Please also refer to Documentation/devicetree/bindings/reset/reset.txt
I have no hard
On Thu, 3 Mar 2016 02:36:26 +0100
"Rafael J. Wysocki" wrote:
> > OK, applied, but let Steven and the x86 folks see it.
The below patch looks fine to me. Anything else I should look at?
-- Steve
> >
> >>>
> >>> > ---
> >>> > arch/x86/kernel/acpi/sleep.c | 7 +++
> >>> > 1 file changed,
Hi,
On Thu, Mar 3, 2016 at 2:42 AM, Zhu Guihua wrote:
> [Problem]
>
> cpuid <-> nodeid mapping is firstly established at boot time. And workqueue
> caches
> the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
>
> When doing node online/offline, cpuid <-> nodeid mapping is
>
Hi Gu,
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.5-rc6 next-20160302]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Zhu-Guihua/Make-cpuid-nodeid-mapping-persistent
Hi Peter,
Patch 10/46 to 14/46 were sent separately to you and modified
follow your suggestion. Do you have further comment on it?
Thank you.
On 2016/2/29 23:39, Arnaldo Carvalho de Melo wrote:
Em Fri, Feb 26, 2016 at 09:31:58AM +, Wang Nan escreveu:
Add new ioctl() to pause/resume ring-
Hello Krzysztof,
On 03/02/2016 09:21 PM, Krzysztof Kozlowski wrote:
On 03.03.2016 02:30, Javier Martinez Canillas wrote:
[snip]
+wdt->wdt_device.min_timeout = 1;
+wdt->wdt_device.max_timeout = s3c2410wdt_max_timeout(wdt->clock);
Can the frequency of clock change? E.g. with devfreq
On Thu, Mar 3, 2016 at 3:07 AM, Steven Rostedt wrote:
> On Thu, 3 Mar 2016 02:36:26 +0100
> "Rafael J. Wysocki" wrote:
>
>> > OK, applied, but let Steven and the x86 folks see it.
>
> The below patch looks fine to me. Anything else I should look at?
No, that was it, thanks!
Hi,
On 03/03/2016 10:08 AM, Rafael J. Wysocki wrote:
Hi,
On Thu, Mar 3, 2016 at 2:42 AM, Zhu Guihua wrote:
[Problem]
cpuid <-> nodeid mapping is firstly established at boot time. And workqueue
caches
the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
When doing node on
On 03/03/2016 10:11 AM, kbuild test robot wrote:
Hi Gu,
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.5-rc6 next-20160302]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux
3.2.77-rt112-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
Atleast on X86 we die a recursive death
|CPU: 3 PID: 585 Comm: bash Not tainted 4.4.1-rt4+ #198
|Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS D
Dear RT Folks,
This is the RT stable review cycle of patch 3.2.77-rt112-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release can
3.2.77-rt112-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
With interrupts off it makes no sense to do the long path since we can't
leave the CPU anyway. Also we might end up in a recursion with lockdep.
Signed-off
3.2.77-rt112-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Clark Williams
RT has dropped support of rcu_bh, comment out in rcutorture.
Signed-off-by: Clark Williams
Signed-off-by: Sebastian Andrzej Siewior
Signed-off-by: Thomas Gleixner
3.2.77-rt112-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
We unlock the lock while the interrupts are off. This isn't a problem
now but will get because the migrate_disable() + enable are not
symmetrical in regard
3.2.77-rt112-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 9969a4b69fad..80c07f1b2fd7
3.2.77-rt112-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
preempt_disable() invokes preempt_count_add() which saves the caller in
current->preempt_disable_ip. It uses CALLER_ADDR1 which does not look for its
caller
3.2.77-rt112-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Yang Shi
When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled,
the below error is reported:
[ INFO: suspicious RCU usage. ]
4.4.1-rt6 #1 Not tainted
include/tra
This patch is porting Raydium I2C touch driver. Developer can enable raydium
touch driver by modifying define "CONFIG_TOUCHSCREEN_RM_TS".
Signed-off-by: jeffrey.lin
---
drivers/input/touchscreen/Kconfig | 12 +
drivers/input/touchscreen/Makefile | 1 +
drivers/input/touchscr
On 03.03.2016 11:14, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 03/02/2016 09:21 PM, Krzysztof Kozlowski wrote:
>> On 03.03.2016 02:30, Javier Martinez Canillas wrote:
>
> [snip]
>
>
> +wdt->wdt_device.min_timeout = 1;
> +wdt->wdt_device.max_timeout = s3c2410wd
One of my machines is an A10 Kaveri desktop, with a good old VGA
connection to the monitor. I've only just started trying to boot
any 4.5 kernel on it, but with 4.5.0-rc6 and now linus's tree from a
few hours ago (4.5.0-rc6-00018-gf983cd3) I get a blank screen, with
no video signal, as soon as it
This patch introduce cap-enhanced-strobe for platforms which
want to enable enhanced strobe function from DT if the mmc host
controller claims to support enhanced strobe.
Signed-off-by: Shawn Lin
---
Documentation/devicetree/bindings/mmc/mmc.txt | 1 +
drivers/mmc/core/host.c
Hi Josh,
Just a couple of quick comments ...
On Wed, 2 Mar 2016 18:39:37 -0600 Josh Poimboeuf wrote:
>
> diff --git a/tools/objtool/Makefile b/tools/objtool/Makefile
> index c4f0713..e4a6bd5 100644
> --- a/tools/objtool/Makefile
> +++ b/tools/objtool/Makefile
I was wondering if this would be m
Hello Ulf and Adrian,
This RFC patch is going to support enhanced strobe function
for emmc version 5.1+ introduced by JEDEC recently.
Firstly，from the former discussion of sdhci, I write these code
inspired by Adrian's patch[0] for variant drivers to overwrite the
callback in order not to add ne
Enhanced strobe stuff currently is beyond the scope
of Secure Digital Host Controller Interface. So we can't
find a register here to enable/disable it. We experct
variant drivers to finish the details according to their
vendor settings.
Signed-off-by: Shawn Lin
---
drivers/mmc/host/sdhci.c | 11
On Thu, 2016-03-03 at 10:29 +0800, jeffrey.lin wrote:
> This patch is porting Raydium I2C touch driver. Developer can enable raydium
> touch driver by modifying define "CONFIG_TOUCHSCREEN_RM_TS".
trivial comments:
> diff --git a/drivers/input/touchscreen/raydium_i2c_ts.c
> b/drivers/input/touch
Currently sdhci-arasan 5.1 can support enhanced strobe function,
but considering the potential requirement in the future for other
version IP, we don't limit it just for "arasan,sdhci-5.1". Add
cap-enhanced-strobe in DT to enable the function if we'r sure our
controller can support it.
Signed-off-
Controllers use data strobe line to latch data from devices
under hs400 mode, but not for cmd line. So from emmc 5.1, JEDEC
introduces enhanced strobe mode for latching cmd response from
emmc devices to host controllers. This new feature is optional.
Signed-off-by: Shawn Lin
---
drivers/mmc/cor
Hi Tejun, Haggai,
On Thu, Mar 3, 2016 at 1:28 AM, Parav Pandit wrote:
>>> + rpool->refcnt--;
>>> + if (rpool->refcnt == 0 && rpool->num_max_cnt == pool_info->table_len)
>>> {
>>
>> If the caller charges 2 and then uncharges 1 two times, the refcnt
>> underflows? Why not just track how m
On Wed, Mar 2, 2016 at 8:49 AM, Michael Turquette
wrote:
>
[cut]
> I do not have any data to back up a case for stalls caused by RT/DL
> starvation, but conceptually I would say that latency is fundamentally
> more important in a scheduler-driven cpu frequency selection scenario,
> versus the le
On Wed, Mar 2, 2016 at 5:00 PM, Yinghai Lu wrote:
> On Wed, Mar 2, 2016 at 4:13 PM, Yinghai Lu wrote:
>> On Wed, Mar 2, 2016 at 2:32 PM, H. Peter Anvin wrote:
>>>
>>> I'm trying to think of any reason why we couldn't simply have a symbol at
>>> the top of the initial stack? Then a simple leaq
HELLO,
This my testimony too every one of you. I got your mail. My name is Jeaga
Jaruh. from India, a great day have come across you today, to make it in
life. join use today and realize your dreams.
Easy way to join the Illuminati in the world, and invest on your own company.
Are you a business
Sometimes it is not worth for the iommu allocating big chunks.
Here we enable DMA_ATTR_ALLOC_SINGLE_PAGES which could help avoid to
allocate big chunks while iommu allocating buffer.
More information about this attribute, please check Doug's commit[1].
[1]: https://lkml.org/lkml/2016/1/11/720
Cc
Hi, Joe,
recently in this patch https://lkml.org/lkml/2016/3/2/281,
I found the original author of the modified code was not
suggested as a patch reviewer.
This surprised me at first. But later I realized that it is not trivial
to define "original author", since the last modification might be
j
From: David Rivshin
This series adds support for the ISSI IS31FL32xx family of I2C LED
controllers. Since the IS31FL3218 is actually the same device as the
SN3218, the dedicated leds-sn3218 driver is removed and the compatible
string is folded into this driver.
Changes from RFC [1]:
- Removed m
From: David Rivshin
The IS31FL32xx family of LED controllers are I2C devices with multiple
constant-current channels, each with independent 256-level PWM control.
Datasheets: http://www.issi.com/US/product-analog-fxled-driver.shtml
This has been tested on the IS31FL3236 and IS31FL3216, on an AR
1 - 100 of 1085 matches
Mail list logo
