* split off pmu info into singleton and per-cpu bits
* setup PMU on all cores
Cc: Peter Zijlstra
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Alexey Brodkin
---
No changes since v2.
Compared to v1:
[1] Rebase on top of previos patches hence changes in patch itself
[2] Cosmetics
arch/arc/ke
Cc: Peter Zijlstra
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Alexey Brodkin
---
No changes since v2.
No changes since v1.
arch/arc/include/asm/perf_event.h | 3 +++
arch/arc/kernel/perf_event.c | 16 ++--
2 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/arc
>
> On Fri, Aug 21, 2015 at 08:25:24PM +, Liang, Kan wrote:
>
> SNIP
>
> > >
> > > we need global topology information in perf.data and use the mapping
> > > from there, we can't use current server info
> > >
> > > we currently store core_siblings_list and thread_siblings_list, in
> > > topo
In times of ARC 700 performance counters didn't have support of
interrupt an so for ARC we only had support of non-sampling events.
Put simply only "perf stat" was functional.
Now with ARC HS we have support of interrupts in performance counters
which this change introduces support of.
ARC perfo
Hi Peter,
This mini-series adds perf support for ARCv2 based cores, which brings in
overflow interupts and SMP. Additionally now raw events are supported as well.
Please review !
Compared to v2 this series has:
[1] Removed patch with raw-events support.
It needs some rework and let's then
This generalization prepares for support of overflow interrupts.
Hardware event counters on ARC work that way:
Each counter counts from programmed start value (set in
ARC_REG_PCT_COUNT) to a limit value (set in ARC_REG_PCT_INT_CNT) and
once limit value is reached this timer generates an interrupt.
On Mon, 2015-08-24 at 09:51 +0200, Daniel Lezcano wrote:
> On 08/21/2015 04:39 PM, Yingjoe Chen wrote:
>
> [ ... ]
>
> >>- Does the spurious interrupt occurs *every* time ? at each boot ?
> >
> > Yes. If you applied this series to enable mtk timer without this fix on
> > mt8173 or mt8135 you
On Mon, Aug 24, 2015 at 11:21:15AM +0200, Maxime Ripard wrote:
> Just like for the XDMAC, the SoCs that embed the HDMAC don't have any kind
> of GPU, and need to accelerate a few framebuffer-related operations through
> their DMA controller.
>
> However, unlike the XDMAC, the HDMAC doesn't have th
This patch configure correctly the MMC-0 clock for STiH418 platform.
Signed-off-by: Gabriel Fernandez
Acked-by: Maxime Coquelin
---
arch/arm/boot/dts/stih418.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/stih418.dtsi b/arch/arm/boot/dts/stih418.dtsi
index 8160
On 08/24/2015 02:32 PM, Marc Zyngier wrote:
On 24/08/15 14:02, Qais Yousef wrote:
On 08/24/2015 01:49 PM, Thomas Gleixner wrote:
On Mon, 24 Aug 2015, Qais Yousef wrote:
Some drivers might require to send ipi to other cores. So export it.
Which IPIs do you need to send from a driver which are
On Mon, Aug 24, 2015 at 02:22:08PM +, Liang, Kan wrote:
> >
> > On Fri, Aug 21, 2015 at 08:25:24PM +, Liang, Kan wrote:
> >
> > SNIP
> >
> > > >
> > > > we need global topology information in perf.data and use the mapping
> > > > from there, we can't use current server info
> > > >
> > >
The HOWTO document needed updating for the new kernel versioning.
Signed-off-by: Mario Carrillo
---
Documentation/HOWTO | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index 93aa860..21152d3 100644
--- a
Hi Peter and Ingo and everybody,
Here's an update of my extended error reporting patchset, addressing
review comments and adding a few more error messages to PT and BTS
drivers.
Changes since v1:
* addressed Peter's comments,
* added perf_err() annotation to intel_pt and intel_bts drivers;
If kernel debugging is enabled, include additional information to extended
syscall error reports: file name and line number, to make error hunting even
easier.
And in really desperate times, this allows for such things (a variation on
Hugh Dickins' trick [1]):
#undef EINVAL
#defin
On Monday 24 August 2015 07:50 PM, Alexey Brodkin wrote:
> Cc: Peter Zijlstra
> Cc: Arnaldo Carvalho de Melo
> Signed-off-by: Alexey Brodkin
> ---
>
> No changes since v2.
>
> No changes since v1.
>
>
> }
>
> + hwc->config = 0;
> +
> + if (is_isa_arcv2()) {
> + /
It has been pointed several times out that perf syscall error reporting
leaves a lot to be desired [1].
This patch introduces a fairly simple extension that allows call sites
to annotate their error codes with arbitrary strings, which will then
be copied to userspace (if they asked for it) along w
On Fri, 2015-08-21 at 16:39 -0300, Danilo Cesar Lemes de Paula wrote:
> Using pandoc as the Markdown engine cause some minor side effects as
> pandoc includes main tags for almost everything.
> Original Markdown support approach removes those main tags, but it
> caused
> some inconsistencies when
On Mon, 2015-08-24 at 15:30 +0200, Daniel Lezcano wrote:
> After analysis done by Yingjoe Chen, the timer appears to have a pending
> interrupt when it is enabled.
>
> Fix this by acknowledging the pending interrupt when enabling the timer
> interrupt.
>
> Signed-off-by: Daniel Lezcano
Hi Daniel,
This patch annotates a few semi-random error paths in perf core to
illustrate the extended error reporting facility. Most of them can
be triggered from perf tools.
Signed-off-by: Alexander Shishkin
---
kernel/events/core.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(
This patch annotates a few x86-specific error paths with perf's extended
error reporting facility.
Signed-off-by: Alexander Shishkin
---
arch/x86/kernel/cpu/perf_event.c | 8 ++--
arch/x86/kernel/cpu/perf_event_intel_lbr.c | 2 +-
2 files changed, 7 insertions(+), 3 deletions(-)
d
On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
I am in the middle of implementing lock on fault this way, but I cannot
see how we will hanlde mremap of a lock on fault region.
If intel_bts events would conflict with other events that are active in
the system, provide an extended error message to the user along with the
usual EBUSY.
Signed-off-by: Alexander Shishkin
---
arch/x86/kernel/cpu/perf_event_intel_bts.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Event attribute validation is one of the biggest sources of EINVALs around
perf_event_open() syscall. This patch annotates error checks with extended
error reporting macros to provide the user with more details on what they
are doing wrong.
Signed-off-by: Alexander Shishkin
---
arch/x86/kernel/c
On Mon, 24 Aug 2015, Ramneek Mehresh wrote:
> > On Thu, 20 Aug 2015, Ramneek Mehresh wrote:
> >
> > > > > --- a/drivers/usb/host/ehci-fsl.h
> > > > > +++ b/drivers/usb/host/ehci-fsl.h
> > > > > @@ -63,4 +63,22 @@
> > > > > #define UTMI_PHY_EN (1<<9)
> > > > > #define ULPI_PHY_CLK_SE
On 08/24/15 04:52, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150821:
>
on x86_64:
drivers/built-in.o: In function `print_avi_infoframe':
tc358743.c:(.text.unlikely+0x7849): undefined reference to
`hdmi_infoframe_unpack'
tc358743.c:(.text.unlikely+0x787e): undefined reference to `h
On 2015-07-24 07:18, Masahiro Yamada wrote:
> Masahiro Yamada (2):
> kbuild: fixdep: optimize code slightly
> kbuild: fixdep: drop meaningless hash table initialization
>
> scripts/basic/fixdep.c | 26 --
> 1 file changed, 4 insertions(+), 22 deletions(-)
Applied to k
The asm macros for setting up and restoring the frame pointer aren't
currently being used. However, they will be needed soon to help asm
functions to comply with stackvalidate.
Rename FRAME/ENDFRAME to FRAME_BEGIN/FRAME_END for more symmetry. Also
make the code more readable and improve the comm
swsusp_arch_suspend() and restore_registers() are callable non-leaf
functions which don't honor CONFIG_FRAME_POINTER, which can result in
bad stack traces. Also they aren't annotated as ELF callable functions
which can confuse tooling.
Create a stack frame for them when CONFIG_FRAME_POINTER is en
Thunk functions are callable non-leaf functions that don't honor
CONFIG_FRAME_POINTER, which can result in bad stack traces. Also they
aren't annotated as ELF callable functions which can confuse tooling.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled and
add the ELF function t
efi_call() is a callable non-leaf function which doesn't honor
CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create a stack frame for it when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Reviewed-by: Matt Fleming
---
arch/x86/platform/efi/efi_stub_64.S | 3 +++
If a PVOP call macro is inlined at the beginning of a function, gcc can
insert the call instruction before setting up a stack frame, which
breaks frame pointer convention if CONFIG_FRAME_POINTER is enabled and
can result in a bad stack trace.
Force a stack frame to be created if CONFIG_FRAME_POINT
do_suspend_lowlevel() is a callable non-leaf function which doesn't
honor CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create a stack frame for it when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Acked-by: Pavel Machek
Cc: "Rafael J. Wysocki"
Cc: Len Brown
--
Hello!
On Aug 24, 2015, at 10:17 AM, Trond Myklebust wrote:
> Hi Stephen,
>
> On Sun, Aug 23, 2015 at 7:16 PM, Stephen Rothwell
> wrote:
>> Hi Trond,
>>
>> On Tue, 18 Aug 2015 10:56:34 +1000 Stephen Rothwell
>> wrote:
>>>
>>> After merging the nfs tree, today's linux-next build (x86_64 all
stackvalidate reports the following warning:
stackvalidate: arch/x86/crypto/aesni-intel_asm.o: _aesni_inc_init(): can't
find starting instruction
stackvalidate gets confused when it tries to disassemble the following
data in the .text section:
.Lbswap_mask:
.byte 15, 14, 13, 12, 1
clmul_ghash_mul() and clmul_ghash_update() are callable non-leaf
functions which don't honor CONFIG_FRAME_POINTER, which can result in
bad stack traces.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Cc: Herbert Xu
Cc: "David S. Miller"
---
ar
This adds a CONFIG_STACK_VALIDATION option which enables a host tool
named stackvalidate which runs at compile time. It analyzes every .o
file and ensures the validity of its stack metadata. It enforces a set
of rules on asm code and C inline assembly code so that stack traces can
be reliable.
F
On Mon, Aug 24, 2015 at 7:57 AM, Russell King - ARM Linux
wrote:
> On Sun, Aug 23, 2015 at 06:23:14PM -0500, Rob Herring wrote:
>> On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
>> > + -analogix,color-depth:
>> > + number of bits per colour component.
>> > +
A function created with the PV_CALLEE_SAVE_REGS_THUNK macro doesn't set
up a new stack frame before the call instruction, which breaks frame
pointer convention if CONFIG_FRAME_POINTER is enabled and can result in
a bad stack trace. Also, the thunk functions aren't annotated as ELF
callable functio
Hello, Jan.
On Mon, Aug 24, 2015 at 11:19:59AM +0200, Jan Kara wrote:
> > which shows unmount being the next writeback event queued and
> > executed after the IO completions have come in (that missed the
> > log). What is missing is the specific queue/exec events for
> > sync_sb_inodes() from the
aesni-intel_asm.S has several callable non-leaf functions which don't
honor CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Cc: Herbert Xu
Cc: "David S. Miller"
---
arch/x86/crypto/aes
stackvalidate reports the following warning:
stackvalidate: arch/x86/crypto/crc32c-pcl-intel-asm_64.o: crc_pcl()+0x11dd:
can't decode instruction
It gets confused when trying to decode jump_table data. Move jump_table
to the .rodata section which is a more appropriate home for read-only
data.
vide() is a callable function, but is missing the ELF function type,
which confuses tools like stackvalidate.
Properly annotate it to be a callable function. The generated code is
unchanged.
Signed-off-by: Josh Poimboeuf
---
arch/x86/kernel/cpu/amd.c | 5 -
1 file changed, 4 insertions(+),
stackvalidate reports a false positive warning for the ljmp instruction
in machine_real_restart(). Normally, ljmp isn't allowed in a function,
but this is a special case where it's jumping into real mode.
Add the jumps to a whitelist which tells stackvalidate to ignore them.
Signed-off-by: Josh
If a hypercall is inlined at the beginning of a function, gcc can insert
the call instruction before setting up a stack frame, which breaks frame
pointer convention if CONFIG_FRAME_POINTER is enabled and can result in
a bad stack trace.
Force a stack frame to be created if CONFIG_FRAME_POINTER is
stackvalidate reports the following false positive warnings:
stackvalidate: arch/x86/xen/enlighten.o: xen_cpuid()+0x41: can't find jump
dest instruction at .text+0x108
stackvalidate: arch/x86/xen/enlighten.o: xen_setup_gdt.constprop.23()+0x2e:
kernel entry/exit from callable instruction
The
Tell stackvalidate to skip validation of the following code:
- boot image
- vdso image
- kexec purgatory
- realmode
- efi libstub
- scripts/mod
They all run outside the kernel's normal mode of operation and they
don't affect runtime kernel stack traces, so they're free to skirt the
stackvalidate
On 2015-07-27 12:33, Valentin Rothberg wrote:
> Until now, checkkonfigsymbols.py did not check default statements for
> references on missing Kconfig symbols (i.e., undefined Kconfig options).
> Hence, add support to parse and check the Kconfig default statement.
>
> Signed-off-by: Valentin Rothbe
rwsem.S has several callable non-leaf functions which don't honor
CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
---
arch/x86/lib/rwsem.S | 11 ++-
1 file changed, 10 insertions
On Monday 24 August 2015 06:32 PM, Lee Jones wrote:
On Mon, 24 Aug 2015, Vaibhav Hiremath wrote:
88PM860 family of device supports dual phase mode on BUCK1 supply
providing total 6A capacity.
Note that by default they operate independently with 3A capacity.
This patch updates the devicetree
Hi Michal,
On Mon, Aug 24, 2015 at 4:49 PM, Michal Marek wrote:
> On 2015-07-27 12:33, Valentin Rothberg wrote:
>> Until now, checkkonfigsymbols.py did not check default statements for
>> references on missing Kconfig symbols (i.e., undefined Kconfig options).
>> Hence, add support to parse and c
Add new stackvalidate ignore macros: STACKVALIDATE_IGNORE_INSN and
STACKVALIDATE_IGNORE_FUNC. These can be used to tell stackvalidate to
skip validation of an instruction or a function, respectively.
Signed-off-by: Josh Poimboeuf
---
arch/x86/include/asm/stackvalidate.h | 45 +++
Add C versions of the frame pointer macros which can be used to create a
stack frame in inline assembly.
Signed-off-by: Josh Poimboeuf
---
arch/x86/include/asm/frame.h | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/frame.h b/arch/x8
This is v11 of the compile-time stack validation patch set, along with
proposed fixes for many of the warnings it found. It's based on the
tip/master branch.
The only real change since v10 is some improvements in patch 3 to the
documentation and changelog which attempt to better describe why stac
On Mon, 24 Aug 2015, Qais Yousef wrote:
> On 08/24/2015 01:49 PM, Thomas Gleixner wrote:
> > On Mon, 24 Aug 2015, Qais Yousef wrote:
> >
> > > Some drivers might require to send ipi to other cores. So export it.
> > Which IPIs do you need to send from a driver which are not exposed by
> > the SMP
On 2015-08-24 16:52, Valentin Rothberg wrote:
> Hi Michal,
>
> On Mon, Aug 24, 2015 at 4:49 PM, Michal Marek wrote:
>> On 2015-07-27 12:33, Valentin Rothberg wrote:
>>> Until now, checkkonfigsymbols.py did not check default statements for
>>> references on missing Kconfig symbols (i.e., undefined
On 08/19/2015 11:21 AM, Kirill A. Shutemov wrote:
Since 8456a648cf44 ("slab: use struct page for slab management") nobody
uses slab_page field in struct page.
Let's drop it.
Signed-off-by: Kirill A. Shutemov
Acked-by: Christoph Lameter
Acked-by: David Rientjes
Cc: Joonsoo Kim
Cc: Andi Kleen
On 08/19/2015 11:21 AM, Kirill A. Shutemov wrote:
Since 8456a648cf44 ("slab: use struct page for slab management") nobody
uses slab_page field in struct page.
Let's drop it.
Ah, how about dropping this comment in mm/slab.c:slab_destroy() as well?
/*
* RCU free
On 08/19/2015 11:21 AM, Kirill A. Shutemov wrote:
We are going to rework how compound_head() work. It will not use
page->first_page as we have it now.
The only other user of page->fisrt_page beyond compound pages is
^ typo
zsmalloc.
Let's use page->private ins
There is no 'crashkernel=auto' entry in kernel-parameters.txt, borrow it
from kexec-kdump-howto.txt file in the kexec-tools-2.0.0 package.
Signed-off-by: Yaowei Bai
---
Documentation/kernel-parameters.txt | 9 +
1 file changed, 9 insertions(+)
diff --git a/Documentation/kernel-parameter
On Mon, 24 Aug 2015, Qais Yousef wrote:
> On 08/24/2015 02:32 PM, Marc Zyngier wrote:
> > I'd rather see something more "architected" than this blind export, or
> > at least some level of filtering (the idea random drivers can access
> > such a low-level function doesn't make me feel very good).
>
On Mon, 24 Aug 2015, Vlastimil Babka wrote:
> On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
> >On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
> >>On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
>
>
> I am in the middle of implementing lock on fault this way, but
On 08/24/2015 03:55 PM, Thomas Gleixner wrote:
On Mon, 24 Aug 2015, Qais Yousef wrote:
On 08/24/2015 01:49 PM, Thomas Gleixner wrote:
On Mon, 24 Aug 2015, Qais Yousef wrote:
Some drivers might require to send ipi to other cores. So export it.
Which IPIs do you need to send from a driver whic
John Stoffel wrote:
>> vmap_info_gen should be initialized to 1 to force an initial
>> cache update.
> Blech, it should be initialized with a proper #define
> VMAP_CACHE_NEEDS_UPDATE 1, instead of more magic numbers.
Er... this is a joke, right?
First, this number is used exactly once, and it's
On 2015/8/17 14:52, Adrian Hunter wrote:
> On 17/08/15 06:36, Fu, Zhonghui wrote:
>> Hi,
>>
>> Any comments are welcome.
> Same comments as here:
>
> http://marc.info/?l=linux-kernel&m=143979428424353&w=2
Now, PM core support asynchronous device suspend/resume mode. If one device has
been
On Mon, Aug 24, 2015 at 1:57 AM, Lee Jones wrote:
> On Wed, 29 Jul 2015, Masahiro Yamada wrote:
>
>> Signed-off-by: Masahiro Yamada
>> ---
>>
>> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
>> 1 file changed, 1 insertion(+)
>
> Patch has been around for nearly a month and is pret
From: Andreas Dilger
Now that the lustre.org domain has been liberated we can again
use that for the main website URL and mailing list.
Also update the URL for userspace tools downloads and Git repo.
Signed-off-by: Andreas Dilger
Signed-off-by: Oleg Drokin
---
MAINTAINERS
On 23 Aug 09:05 PM, Robert Jarzmik wrote:
> After the conversion of pxa architecture to common clock framework, the
> NAND clock can be disabled on driver exit.
>
> In this case, it happens that if the driver used the NAND and set the
> DFI arbitration bit, the next access to a static memory contr
On Sun, Jul 26, 2015 at 8:49 PM, Wang Long wrote:
> Update the last pr_warning callsite in drivers/of.
> When we use script "./scripts/checkpatch.pl" to check
> a patch, using pr_warning will produce WARNING:
>
> WARNING: Prefer pr_warn(... to pr_warning(...
> #22: FILE: drivers/of
On 2015/8/17 14:51, Adrian Hunter wrote:
> On 17/08/15 06:38, Fu, Zhonghui wrote:
>> Hi,
>>
>> Any comments are welcome.
> Same comments as here:
>
> http://marc.info/?l=linux-kernel&m=143979428424353&w=2
Now, PM core support asynchronous device suspend/resume mode. If one device has
been
On Tue, Aug 4, 2015 at 8:11 AM, Geert Uytterhoeven
wrote:
> Add the "jedec" vendor prefix for the "JEDEC Solid State Technology
> Association" (formerly known as the "Joint Electron Device Engineering
> Council"), which is already in use in several bindings.
>
> Signed-off-by: Geert Uytterhoeven
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/8/17 23:55, Fu, Zhonghui wrote:
> Enable hid device to suspend/resume asynchronously. This can improve
> system suspend/resume speed.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/hid/hid-core.c |1 +
> 1 files changed, 1 insertion
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/8/18 0:07, Fu, Zhonghui wrote:
> Enable i2c device to suspend/resume asynchronously. This can improve
> system suspend/resume speed.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/i2c/i2c-core.c |1 +
> 1 files changed, 1 insertions
On Wed, Aug 19, 2015 at 3:17 PM, David Daney wrote:
> From: David Daney
>
> If the internal call to of_address_to_resource() fails, we end up
> looping forever in of_find_matching_node_by_address(). This can be
> caused by a defective device tree, or calling with an incorrect
> matches argument.
On Tue, Jul 28, 2015 at 8:25 PM, Bjorn Andersson wrote:
> On Wed, Jul 1, 2015 at 10:41 AM, Rob Herring wrote:
>> On Wed, Jul 1, 2015 at 7:01 AM, Thierry Reding
>> wrote:
>>> On Mon, Oct 13, 2014 at 01:54:09PM +0200, Thierry Reding wrote:
On Fri, Aug 01, 2014 at 03:50:44PM +0200, Thierry Re
On Monday 24 August 2015 07:24 PM, Lee Jones wrote:
On Wed, 08 Jul 2015, Vaibhav Hiremath wrote:
As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
(page 0) controls the method of clearing interrupt
status of 88pm800 family of devices;
0: clear on read
1: clear on write
If pdata
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/8/18 0:17, Fu, Zhonghui wrote:
> Enable i2c adapter to suspend/resume asynchronously. This can improve
> system suspend/resume speed.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/i2c/i2c-core.c |2 ++
> 1 files changed, 2 insertio
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/8/18 0:36, Fu, Zhonghui wrote:
> Enable i2c controller to suspend/resume asynchronously. This can improve
> system suspend/resume speed.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/i2c/busses/i2c-designware-platdrv.c |1 +
> 1 fi
On 08/15/2015 06:27 AM, Jonathan Corbet wrote:
> On Fri, 14 Aug 2015 15:46:52 -0700
> Tim Bird wrote:
>
>>> It sure would be nice if changes like this were accompanied by a patch
>>> fixing the additional warnings it drags in ... :) In this case I've put
>>> something together for workqueue.h
On Mon, Aug 24, 2015 at 8:27 PM, Eric W. Biederman
wrote:
>
>
> On August 24, 2015 1:56:13 AM PDT, Sean Fu wrote:
>>when the input argument "count" including the terminating byte "\0",
>>The write system call return EINVAL on proc file.
>>But it return success on regular file.
>
> Nonsense. It w
This is intended to add ZTE device PIDs on kernel.
Signed-off-by: Liu.Zhao
---
drivers/usb/serial/option.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index 876423b..6b4a766 100644
--- a/drivers/usb/seria
On 08/22, Paul E. McKenney wrote:
>
> Queued for testing, thank you, Oleg!
Thanks Paul!
> Right now, this is mostly relying on 0day and -next testing. Any thoughts
> for a useful torture test for this?
Right now I do not have any idea how to write the meaningful test for
rcu_sync... Perhaps som
On Mon, Aug 24, 2015 at 04:04:37PM +0200, Frederic Weisbecker wrote:
> On Mon, Aug 24, 2015 at 06:50:18AM -0700, Paul E. McKenney wrote:
> > On Mon, Aug 24, 2015 at 08:44:12AM +0200, Ingo Molnar wrote:
> > >
> > > * Paul E. McKenney wrote:
> > >
> > > > > here it's fully set - triggering the bug
On 24/08/15 15:15, Andrey Ryabinin wrote:
> 2015-08-24 16:45 GMT+03:00 Linus Walleij :
>> On Mon, Aug 24, 2015 at 3:15 PM, Russell King - ARM Linux
>> wrote:
>>> On Tue, Jul 21, 2015 at 11:27:56PM +0200, Linus Walleij wrote:
On Tue, Jul 21, 2015 at 4:27 PM, Andrey Ryabinin
wrote:
Fix autoloading ipmi modules when using device tree.
Signed-off-by: Brijesh Singh
---
drivers/char/ipmi/ipmi_si_intf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/char/ipmi/ipmi_si_intf.c b/drivers/char/ipmi/ipmi_si_intf.c
index 8a45e92..cddc7b0 100644
--- a/drivers/char/ipmi/ipm
On Mon, Aug 24, 2015 at 6:09 PM, Eric B Munson wrote:
> On Mon, 24 Aug 2015, Vlastimil Babka wrote:
>
>> On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
>> >On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
>> >>On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
>>
>>
>> >>
On 08/21/2015 09:34 PM, Andrew Morton wrote:
On Fri, 21 Aug 2015 22:31:09 +0300 "Kirill A. Shutemov"
wrote:
On Fri, Aug 21, 2015 at 11:11:27AM -0500, Christoph Lameter wrote:
On Fri, 21 Aug 2015, Kirill A. Shutemov wrote:
Is this really true? For example if it's a slab page, will that pag
On 2015-08-22 14:29, Tejun Heo wrote:
Hello, Paul.
On Fri, Aug 21, 2015 at 12:26:30PM -0700, Paul Turner wrote:
...
A very concrete example of the above is a virtual machine in which you
want to guarantee scheduling for the vCPU threads which must schedule
beside many hypervisor support threads
On Mon, 24 Aug 2015, Vaibhav Hiremath wrote:
>
>
> On Monday 24 August 2015 07:24 PM, Lee Jones wrote:
> >On Wed, 08 Jul 2015, Vaibhav Hiremath wrote:
> >
> >>As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
> >>(page 0) controls the method of clearing interrupt
> >>status of 88pm800 fami
On Mon, 24 Aug 2015, Konstantin Khlebnikov wrote:
> On Mon, Aug 24, 2015 at 6:09 PM, Eric B Munson wrote:
> > On Mon, 24 Aug 2015, Vlastimil Babka wrote:
> >
> >> On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
> >> >On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
> >> >>On 08/24/20
George> John Stoffel wrote:
>>> vmap_info_gen should be initialized to 1 to force an initial
>>> cache update.
>> Blech, it should be initialized with a proper #define
>> VMAP_CACHE_NEEDS_UPDATE 1, instead of more magic numbers.
George> Er... this is a joke, right?
Not really. The comment mad
2015-08-24 18:44 GMT+03:00 Vladimir Murzin :
>
> Another option would be having "sparse" shadow memory based on page
> extension. I did play with that some time ago based on ideas from
> original v1 KASan support for x86/arm - it is how 614be38 "irqchip:
> gic-v3: Fix out of bounds access to cpu_lo
On 08/23/2015 08:52 PM, 河合英宏 / KAWAI,HIDEHIRO wrote:
>> From: Corey Minyard [mailto:tcminy...@gmail.com] On Behalf Of Corey Minyard
>>
>> On 08/17/2015 09:54 PM, 河合英宏 / KAWAI,HIDEHIRO wrote:
From: Corey Minyard [mailto:tcminy...@gmail.com] On Behalf Of Corey Minyard
This patch will b
On 08/24/2015 02:09 AM, Jiri Slaby wrote:
This is the start of the stable review cycle for the 3.12.47 release.
There are 82 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by W
> -Original Message-
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: 2015年8月23日 5:58
> To: Wang Shenwei-B38339
> Cc: shawn@linaro.org; ja...@lakedaemon.net;
> linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; Huang
> Yongcai-B20788
> Subject: Re: [PATCH v
On 8/24/2015 6:36 AM, Franklin S Cooper Jr. wrote:
Hi Santosh,
All the patches except this one are in linux-next.
Yes I noticed it. I will queue this up for next merge window.
Thanks for reminder.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
On 24/08/15 17:00, Andrey Ryabinin wrote:
> 2015-08-24 18:44 GMT+03:00 Vladimir Murzin :
>>
>> Another option would be having "sparse" shadow memory based on page
>> extension. I did play with that some time ago based on ideas from
>> original v1 KASan support for x86/arm - it is how 614be38 "irqch
Am Montag, 24. August 2015, 09:48:27 schrieb Rob Herring:
> On Mon, Aug 24, 2015 at 7:57 AM, Russell King - ARM Linux
> > When we adopted the graph bindings for iMX DRM, I thought exactly at that
> > time "it would be nice if this could become the standard for binding DRM
> > components together" b
2015-08-24 19:16 GMT+03:00 Vladimir Murzin :
> On 24/08/15 17:00, Andrey Ryabinin wrote:
>> 2015-08-24 18:44 GMT+03:00 Vladimir Murzin :
>>>
>>> Another option would be having "sparse" shadow memory based on page
>>> extension. I did play with that some time ago based on ideas from
>>> original v1
On Mon, Aug 24, 2015 at 10:13:25AM +0300, Artem Bityutskiy wrote:
> Now, some user-space fails when direct I/O is not supported.
I think the whole argument rested on what it means when "some user space
fails"; apparently that "user space" is just a test suite (which
can/should be fixed).
> We can
On Mon, Aug 24, 2015 at 6:55 PM, Eric B Munson wrote:
> On Mon, 24 Aug 2015, Konstantin Khlebnikov wrote:
>
>> On Mon, Aug 24, 2015 at 6:09 PM, Eric B Munson wrote:
>> > On Mon, 24 Aug 2015, Vlastimil Babka wrote:
>> >
>> >> On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
>> >> >On Mon, Aug
601 - 700 of 945 matches
Mail list logo