On Fri, Feb 28, 2014 at 10:52:32AM +0300, Dan Carpenter wrote:
> On Fri, Feb 28, 2014 at 01:31:20AM -0600, Chase Southwood wrote:
> > hwdrv_apci1564.c had numerous lines over the column limit. This patch
> > splits all such lines to bring them in compliance with coding style.
> >
> > Signed-off-b
On Fri, Feb 28, 2014 at 01:31:20AM -0600, Chase Southwood wrote:
> hwdrv_apci1564.c had numerous lines over the column limit. This patch
> splits all such lines to bring them in compliance with coding style.
>
> Signed-off-by: Chase Southwood
> ---
> .../comedi/drivers/addi-data/hwdrv_apci1564.
>
> A quick grep reveals:
> mc13783.c:codec->control_data = dev_get_regmap(codec->dev->parent, NULL);
> si476x.c: codec->control_data = dev_get_regmap(codec->dev->parent, NULL);
> wm5102.c: codec->control_data = priv->core.arizona->regmap;
> wm5110.c: codec->control_data = priv->c
* Paul E. McKenney wrote:
> Hello, Ingo,
>
> The major changes to this series are:
>
> 1.Update RCU documentation. These were posted to LKML at
> https://lkml.org/lkml/2014/2/17/555.
>
> 2.Miscellaneous fixes. These were posted to LKML at
> https://lkml.org/lkml/2014/2/1
On 02/27/2014 05:00 PM, Nishanth Menon wrote:
> The other option might be to blindly configure 6040 to max speed ->
> but then you do have an issue with that single register write
> operation to configure the speed?
Yes, exactly. It is unfortunate that twl6040's i2c speed is configured via i2c
wri
clean up checkpatch.pl warnings:
WARNING: Line length over 80 characters
Signed-off-by: Daeseok Youn
---
drivers/staging/cxt1e1/hwprobe.c | 45 --
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git a/drivers/staging/cxt1e1/hwprobe.c b/drivers/st
Smatch located a handful of while loops testing readl calls in s626.c.
Since these while loops depend on readl succeeding, it's safer to make
sure they time out eventually.
Signed-off-by: Chase Southwood
---
Ian and/or Hartley, I'd love your comments on this. It seems to me that
we want these ki
OK. sorry.
I will send again.
Thanks.
Daeseok Youn
2014-02-28 16:28 GMT+09:00 Dan Carpenter :
> On Fri, Feb 28, 2014 at 04:12:22PM +0900, Daeseok Youn wrote:
>>
>> clean up checkpatch.pl warnings:
>> WARNING: Line length over 80 characters
>>
>
> Patch is white space dammaged and doesn't apply.
Am Donnerstag, den 27.02.2014, 16:18 -0800 schrieb Andy Lutomirski:
> I'd still like someone else to confirm that the 32-bit vDSO is working
> on all common configurations before I'm happy with it, but this should
> be a considerable improvement.
>
> Someone who maintains the clock code should rev
A handful of variables here were being initialized to 0 upon declaration,
however they are always then set to another value before their first use,
so initialization here is useless and we can remove it.
Signed-off-by: Chase Southwood
---
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1564.c
hwdrv_apci1564.c had numerous lines over the column limit. This patch
splits all such lines to bring them in compliance with coding style.
Signed-off-by: Chase Southwood
---
.../comedi/drivers/addi-data/hwdrv_apci1564.c | 50 --
1 file changed, 36 insertions(+), 14 dele
Nearly every variable in hwdrv_apci035.c is initialized to 0 when it is
declared, and then set to some other value before ever being used. As
such, we can remove all of these initializations. They are accomplishing
nothing.
Signed-off-by: Chase Southwood
---
.../comedi/drivers/addi-data/hwdrv_
On Wed, Feb 26, 2014 at 10:49:49AM -0500, Dave Jones wrote:
> On Wed, Feb 26, 2014 at 02:18:52PM +0100, Borislav Petkov wrote:
> > On Wed, Feb 26, 2014 at 07:12:59PM +0700, Chris Bainbridge wrote:
> > > @@ -226,6 +234,15 @@ static void intel_workarounds(struct cpuinfo_x86 *c)
> > >
On Fri, Feb 28, 2014 at 04:12:22PM +0900, Daeseok Youn wrote:
>
> clean up checkpatch.pl warnings:
> WARNING: Line length over 80 characters
>
Patch is white space dammaged and doesn't apply.
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Am Donnerstag, den 27.02.2014, 16:18 -0800 schrieb Andy Lutomirski:
> There's no reason for the vDSO to use a special function call ABI. Use
> the platform defaults.
>
The only reason was performance. What is good for the kernel should be
also good for the VDSO. Now all functions inside the VDSO
On Tue, Jul 30, 2013 at 3:04 PM, Luciano Coelho wrote:
> Hi,
>
> This patch series adds device tree support to the wlcore_sdio driver,
> which is used by WiLink6, WiLink7 and WiLink8.
>
> The first patches do some clean-up to make the data needed in the
> wilink device tree node smaller. The rema
(2014/02/27 23:57), Benjamin LaHaise wrote:
On Thu, Feb 27, 2014 at 06:40:16PM +0800, Tang Chen wrote:
When doing aio ring page migration, we migrated the page, and update
ctx->ring_pages[]. Like the following:
aio_migratepage()
|-> migrate_page_copy(new, old)
| ..
Am Mittwoch, den 26.02.2014, 16:55 -0800 schrieb Andy Lutomirski:
> Um. This code doesn't work. I'll send a patch. I can't speak
> towards how well it compiles in different configurations.
>
> I can't speak towards how well it compiles in different
> configurations. Also, vdso_fallback_gettime
Am Donnerstag, den 27.02.2014, 16:18 -0800 schrieb Andy Lutomirski:
> rdtsc_barrier() needs this.
>
Thanks for doing this.
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/include/asm/vdso.h | 2 ++
> arch/x86/vdso/vdso32-setup.c | 25 +
> arch/x86/vdso/vma.c
>
> A quick grep reveals:
> mc13783.c:codec->control_data = dev_get_regmap(codec->dev->parent, NULL);
> si476x.c: codec->control_data = dev_get_regmap(codec->dev->parent, NULL);
> wm5102.c: codec->control_data = priv->core.arizona->regmap;
> wm5110.c: codec->control_data = priv->c
On 02/28/2014 08:08 AM, li.xi...@freescale.com wrote:
Subject: Re: [PATCH 2/3] ASoC: core: Set the default I/O up try regmap.
On Fri, Feb 28, 2014 at 04:00:38AM +, li.xi...@freescale.com wrote:
I'll send another patches to applied to use this for another CODEC
drivers.
And there almost 8
clean up checkpatch.pl error:
ERROR: that open brace { should be on the previous line
Signed-off-by: Daeseok Youn
---
drivers/staging/cxt1e1/hwprobe.c | 62 +++---
1 file changed, 25 insertions(+), 37 deletions(-)
diff --git a/drivers/staging/cxt1e1/hwprobe.c
checkpatch.pl error:
ERROR: do not use assignment in if condition
Signed-off-by: Daeseok Youn
---
drivers/staging/cxt1e1/hwprobe.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/cxt1e1/hwprobe.c b/drivers/staging/cxt1e1/hwprobe.c
index
clean up checkpatch.pl warnings:
WARNING: Line length over 80 characters
Signed-off-by: Daeseok Youn
---
drivers/staging/cxt1e1/hwprobe.c | 45
--
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git a/drivers/staging/cxt1e1/hwprobe.c
b/drivers/
clean up checkpatch.pl warnings:
WARNING: please no spaces at the start of a line in
Signed-off-by: Daeseok Youn
---
drivers/staging/cxt1e1/hwprobe.c | 585 +++---
1 file changed, 293 insertions(+), 292 deletions(-)
diff --git a/drivers/staging/cxt1e1/hwprobe.c
clean up checkpatch.pl warnings:
WARNING: space prohibited between function name
and open parenthesis '('
Signed-off-by: Daeseok Youn
---
drivers/staging/cxt1e1/hwprobe.c | 120 +++---
1 file changed, 60 insertions(+), 60 deletions(-)
diff --git a/drivers/sta
> Subject: Re: [PATCH 2/3] ASoC: core: Set the default I/O up try regmap.
>
> On Fri, Feb 28, 2014 at 04:00:38AM +, li.xi...@freescale.com wrote:
>
> > I'll send another patches to applied to use this for another CODEC
> drivers.
> > And there almost 80 files, Should
On 27/02/14 20:16, Randy Dunlap wrote:
> On 02/27/2014 03:54 AM, Tomi Valkeinen wrote:
>> Hi,
>>
>> This is a re-send of the series, with RFC removed from the subject, and a
>> bunch
>> of acks added.
>>
>> I'm cc'ing more people, to make sure this doesn't come as a surprise, and to
>> make sure t
On 02/28/2014 01:58 AM, Andi Kleen wrote:
The interesting part is: what problems did you find using it?
I listed some of these here along with the links to the bug reports:
http://code.google.com/p/kernel-strider/wiki/RacesFound
The hunt still continues though.
Besides the races listed there
On 02/28/2014 03:48 AM, Xiubo Li wrote:
For the snd_soc_cache_init(), the reg_size maybe zero and then the value
of codec->reg_cache, which is alloced via kzalloc, maybe equal to
ZERO_SIZE_PTR. If the reg parameter of snd_soc_cache_write() is large enough,
the cache[idx] = val maybe cause the ker
On 02/27/2014 06:52 PM, Sören Brinkmann wrote:
Hi Daniel, Michal,
On Wed, 2014-02-19 at 03:14PM -0800, Soren Brinkmann wrote:
Hi,
another iteration of this series. The patches are the same as in v3, but
the series shrank a bit. I rebased this series on tip/timers/core, hence
the two patches fo
On 2014/2/28 14:44, Matthew Garrett wrote:
> On Fri, Feb 28, 2014 at 02:39:56PM +0800, Li, Aubrey wrote:
>
>> Just let you know, Windows8.1 calls EFI on these boxes for reboot/shutdown.
>
> Ok, in that case we should add EFI reboot to the list once Matt's 1:1
> mapping support has landed. The ri
From: Mika Westerberg
Add support for Intel Low Power I/O subsystem PWM controllers found on
Intel BayTrail SoC.
Signed-off-by: Mika Westerberg
Signed-off-by: Chew, Kean Ho
Signed-off-by: Chang, Rebecca Swee Fun
Signed-off-by: Chew, Chiau Ee
---
drivers/pwm/Kconfig| 10 +++
drivers/pw
On 02/21/2014 03:21 AM, Ryan wrote:
Is there a way to trace suspend-resume without using ftrace and printk.
Thanks.
ryan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140227:
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The drm-tegra tree lost its build failure.
The wireless-next
On Fri, Feb 28, 2014 at 02:39:56PM +0800, Li, Aubrey wrote:
> Just let you know, Windows8.1 calls EFI on these boxes for reboot/shutdown.
Ok, in that case we should add EFI reboot to the list once Matt's 1:1
mapping support has landed. The right place to try it is probably after
the second atte
On 02/28/2014 07:40 AM, li.xi...@freescale.com wrote:
Subject: Re: [alsa-devel] [PATCH 2/3] ASoC: core: Set the default I/O up try
regmap.
On 02/28/2014 06:56 AM, li.xi...@freescale.com wrote:
Subject: Re: [PATCH 2/3] ASoC: core: Set the default I/O up try regmap.
On Fri, Feb 28, 2014 at 04:
> Subject: Re: [alsa-devel] [PATCH 2/3] ASoC: core: Set the default I/O up try
> regmap.
>
> On 02/28/2014 06:56 AM, li.xi...@freescale.com wrote:
> >> Subject: Re: [PATCH 2/3] ASoC: core: Set the default I/O up try regmap.
> >>
> >> On Fri, Feb 28, 2014 at 04:00:38AM +, li.xi...@freescale.co
On 2014/2/28 14:23, Matthew Garrett wrote:
> On Fri, Feb 28, 2014 at 02:20:41PM +0800, Li, Aubrey wrote:
>
>> Well, I already figured that out. Reset Register Supported flag is ZERO
>> in FACP table. I attached this table for your interesting.
>
> Ok, in that case we need to check how Windows dea
From: Liu ShuoX
In ramoops_pstore_read, a valid prz pointer with zero size buffer will
break traverse of all persistent ram buffers. The latter buffer might
be lost.
Signed-off-by: Liu ShuoX
---
fs/pstore/ram.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/p
From: Liu ShuoX
ftrace_read_cnt need to be reset in open to support mutli times
getting the records.
Signed-off-by: Liu ShuoX
---
fs/pstore/ram.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index fa8cef2..a5d0cab 100644
--- a/fs/pstore/ram.c
+++ b/fs/p
On 02/28/2014 06:56 AM, li.xi...@freescale.com wrote:
Subject: Re: [PATCH 2/3] ASoC: core: Set the default I/O up try regmap.
On Fri, Feb 28, 2014 at 04:00:38AM +, li.xi...@freescale.com wrote:
I'll send another patches to applied to use this for another CODEC drivers.
And there almost 80
On 2014/2/28 13:41, Florian Fainelli wrote:
> 2014-02-27 21:26 GMT-08:00 Ding Tianhong :
>> On 2014/2/28 11:45, John Fastabend wrote:
>>> On 2/27/2014 6:43 PM, Ding Tianhong wrote:
I run these steps:
modprobe 8021q
vconfig add eth2 20
vconfig add eth2.20 20
ifconfig et
On 02/27/2014 06:52 PM, Sören Brinkmann wrote:
> Hi Daniel, Michal,
>
> On Wed, 2014-02-19 at 03:14PM -0800, Soren Brinkmann wrote:
>> Hi,
>>
>> another iteration of this series. The patches are the same as in v3, but
>> the series shrank a bit. I rebased this series on tip/timers/core, hence
>> t
Bad idea:
[ 908.026136] [] rt_spin_lock_slowlock+0xaa/0x2c0
[ 908.026145] [] task_numa_free+0x31/0x130
[ 908.026151] [] finish_task_switch+0xce/0x100
[ 908.026156] [] thread_return+0x48/0x4ae
[ 908.026160] [] schedule+0x25/0xa0
[ 908.026163] [] rt_spin_lock_slowlock+0xd5/0x2c0
[ 908.0
On Fri, Feb 28, 2014 at 02:20:41PM +0800, Li, Aubrey wrote:
> Well, I already figured that out. Reset Register Supported flag is ZERO
> in FACP table. I attached this table for your interesting.
Ok, in that case we need to check how Windows deals with a FACP that has
this flag set to 0 but valid
On 2014/2/28 14:12, Matthew Garrett wrote:
> On Fri, Feb 28, 2014 at 02:07:58PM +0800, Li, Aubrey wrote:
>> On 2014/2/28 13:56, Matthew Garrett wrote:
>>> Probably, once we've got those patches landed (I've lost track of
>>> whether they're in 3.13 or aimed at 3.14)
>>
>> You didn't look the refer
On Thu, Feb 27, 2014 at 10:38:26PM +0900, Atsushi Nemoto wrote:
> I don't object to the whole patch. Validating in spi core is good of
> course, and "xfer->len % w_size" part looks no problem.
> I just want to keep ways to handle an odd device, for example, which
> requires long delay between ch
Now that all users have been converted to regmap and the config.reg_bits
and config.val_bits can be setted by each user through regmap core API.
So these two params are redundant here.
Signed-off-by: Xiubo Li
---
include/sound/soc.h | 1 -
sound/soc/codecs/wm5110.c | 2 +-
sound/soc/codecs
Signed-off-by: Xiubo Li
---
sound/soc/codecs/ad193x.c| 7 ---
sound/soc/codecs/adau1373.c | 6 --
sound/soc/codecs/adav80x.c | 6 --
sound/soc/codecs/ak4535.c| 6 --
sound/soc/codecs/ak4641.c| 6 --
sound/soc/codecs/ak4642.c| 6
Most of the CODECs' ASoC probe code could be simplified directly, while
for wm5110 and wm8997 CODEC drivers need much more research and examination.
Xiubo Li (2):
ASoC: codec: Simplify ASoC probe code.
ASoC: io: Remove reduntant params of snd_soc_codec_set_cache_io()
include/sound/soc.h
On Fri, Feb 28, 2014 at 02:07:58PM +0800, Li, Aubrey wrote:
> On 2014/2/28 13:56, Matthew Garrett wrote:
> > Probably, once we've got those patches landed (I've lost track of
> > whether they're in 3.13 or aimed at 3.14)
>
> You didn't look the reference I quoted in the patch.
>
> It's stable if
On 2014/2/28 13:56, Matthew Garrett wrote:
> On Fri, Feb 28, 2014 at 01:22:37PM +0800, Li, Aubrey wrote:
>> On 2014/2/28 12:56, Matthew Garrett wrote:
>>> EFI reboot is still somewhat unreliable - it may be safe after the
>>> recent patches to provide a 1:1 mapping.
>>
>> So it's acceptable to put
> Subject: Re: [PATCH 2/3] ASoC: core: Set the default I/O up try regmap.
>
> On Fri, Feb 28, 2014 at 04:00:38AM +, li.xi...@freescale.com wrote:
>
> > I'll send another patches to applied to use this for another CODEC drivers.
> > And there almost 80 files, Should I send them in one patch or
On Fri, Feb 28, 2014 at 01:22:37PM +0800, Li, Aubrey wrote:
> On 2014/2/28 12:56, Matthew Garrett wrote:
> > EFI reboot is still somewhat unreliable - it may be safe after the
> > recent patches to provide a 1:1 mapping.
>
> So it's acceptable to put EFI in the default list.
Probably, once we've
On 2/27/2014 2:17 PM, Shevchenko, Andriy wrote:
On Thu, 2014-02-27 at 10:44 +0530, George Cherian wrote:
Start the channel tear down only if the channel is busy, else just
bail out. In some cases its seen that by the time the tear down is
initiated the cppi completes the DMA, especially in ISOCH
On Fri, Feb 28, 2014 at 04:00:38AM +, li.xi...@freescale.com wrote:
> I'll send another patches to applied to use this for another CODEC drivers.
> And there almost 80 files, Should I send them in one patch or split them into
> individual patch for each CODEC driver ?
I'd suggest doing one pa
Hi Kumar,
I pulled this in to my 3.14 tree and gave it a spin. But I keep
hitting the case of unlock below telling me that someone else is
holding the lock.
On Wed, Aug 14, 2013 at 12:09 PM, Kumar Gala wrote:
[...]
> +
> +static int msm_hwspinlock_trylock(struct hwspinlock *lock)
> +{
> +
Hi Marc,
> -Original Message-
> From: Marc Kleine-Budde [mailto:m...@pengutronix.de]
> Sent: Wednesday, February 26, 2014 9:13 PM
> To: Appana Durga Kedareswara Rao; w...@grandegger.com; Michal Simek;
> grant.lik...@linaro.org; robh...@kernel.org; linux-...@vger.kernel.org
> Cc: net...@vg
2014-02-27 21:26 GMT-08:00 Ding Tianhong :
> On 2014/2/28 11:45, John Fastabend wrote:
>> On 2/27/2014 6:43 PM, Ding Tianhong wrote:
>>> I run these steps:
>>>
>>> modprobe 8021q
>>> vconfig add eth2 20
>>> vconfig add eth2.20 20
>>> ifconfig eth2 xx.xx.xx.xx
>>>
>>> then the Call Trace happened:
>
On 2014/2/27 7:50, Rafael J. Wysocki wrote:
> On Wednesday, February 26, 2014 10:46:37 AM Li, Aubrey wrote:
>> Sleep control and status registers need santity check before ACPI
>> install acpi_power_off to pm_power_off hook. The checking code in
>> acpi_enter_sleep_state() is too late, we should no
From: Liu Ping Fan
When doing some numa tests on powerpc, I triggered an oops bug. I find
it is caused by using page->_last_cpupid. It should be initialized as
"-1 & LAST_CPUPID_MASK", but not "-1". Otherwise, in task_numa_fault(),
we will miss the checking (last_cpupid == (-1 & LAST_CPUPID_MASK
On 2014/2/28 11:45, John Fastabend wrote:
> On 2/27/2014 6:43 PM, Ding Tianhong wrote:
>> I run these steps:
>>
>> modprobe 8021q
>> vconfig add eth2 20
>> vconfig add eth2.20 20
>> ifconfig eth2 xx.xx.xx.xx
>>
>> then the Call Trace happened:
>>
>
> [...]
>
>> ===
On 2014/2/28 12:56, Matthew Garrett wrote:
> On Fri, Feb 28, 2014 at 12:11:57PM +0800, Li, Aubrey wrote:
>> This patch is to introduce BOOT_EFI and BOOT_CF9 in the reboot sequence
>> loop, to fix the reboot problem on the known Intel Bay Trail-T based
>> platform, for example, ASUS-T100 and Dell Ve
Hi Marek,
Thank you very much for your suggestion.
> -Original Message-
> From: Marek Vasut [mailto:ma...@denx.de]
> Sent: Friday, February 28, 2014 4:40 AM
> To: linux-arm-ker...@lists.infradead.org
> Cc: Yuan Yao-B46683; w...@the-dreams.de; mark.rutl...@arm.com;
> shawn@linaro.org;
Recordmcount utility under scripts is run, after compiling each object,
to find out all the locations of calling _mcount() and put them into
specific seciton named __mcount_loc.
Then linker collects all such information into a table in the kernel image
(between __start_mcount_loc and __stop_mcount_
This patch allows system call entry or exit to be traced as ftrace events,
ie. sys_enter_*/sys_exit_*, if CONFIG_FTRACE_SYSCALLS is enabled.
Those events appear and can be controlled under
${sysfs}/tracing/events/syscalls/
Signed-off-by: AKASHI Takahiro
---
arch/arm64/Kconfig |
Since insn.h is indirectly included in asm/entry-ftrace.S,
we need to exclude some declarations by __ASSEMBLY__.
Signed-off-by: AKASHI Takahiro
---
arch/arm64/include/asm/insn.h |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/include/asm/insn.h b/arch/arm64/include/asm/insn.h
walk_stackframe() calls unwind_frame(), and if walk_stackframe() is
"notrace", unwind_frame() should be also "notrace".
Signed-off-by: AKASHI Takahiro
---
arch/arm64/kernel/stacktrace.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/stacktrace.c b/arch/a
This patch allows "dynamic ftrace" if CONFIG_DYNAMIC_FTRACE is enabled.
Here we can turn on and off tracing dynamically per-function base.
On arm64, this is done by patching single branch instruction to _mcount()
inserted by gcc -pg option. The branch is replaced to NOP initially at
kernel start u
CALLER_ADDRx returns caller's address at specified level in call stacks.
They are used for several tracers like irqsoff and preemptoff.
Strange to say, however, they are refered even without FTRACE.
Please note that this implementation assumes that we have frame pointers.
(which means kernel shoul
This patch implements arm64 specific part to support function tracers,
such as function (CONFIG_FUNCTION_TRACER), function_graph
(CONFIG_FUNCTION_GRAPH_TRACER) and function profiler
(CONFIG_FUNCTION_PROFILER).
With 'function' tracer, all the functions in the kernel are traced with
timestamps in ${
This patchset implements a function tracer on arm64.
There was another implementation from Cavium network, but both of us agreed
to use my patchset as future base. He is supposed to review this code, too.
The only issue that I had some concern on was "fault protection" code
in prepare_ftrace_retur
This patch adds auditing functions on entry to or exit from
every system call invocation.
Acked-by: Richard Guy Briggs
Signed-off-by: AKASHI Takahiro
---
arch/arm64/kernel/ptrace.c | 54 ++--
1 file changed, 32 insertions(+), 22 deletions(-)
diff --git
On AArch64, audit is supported through generic lib/audit.c and
compat_audit.c, and so this patch adds arch specific definitions required.
Acked-by Will Deacon
Acked-by: Richard Guy Briggs
Signed-off-by: AKASHI Takahiro
---
arch/arm64/Kconfig |1 +
arch/arm64/include/asm/sysca
This patchset adds system call audit support on arm64.
Both 32-bit (AUDIT_ARCH_ARM) and 64-bit tasks (AUDIT_ARCH_AARCH64)
are supported. Since arm64 has the exact same set of system calls
on LE and BE, we don't care about endianness (or more specifically
__AUDIT_ARCH_64BIT bit in AUDIT_ARCH_*).
Th
This patchset contains some patches commonly used by audit and ftrace.
Patch [1/2] defines system call related TIF_* flags to add syscall_trace()
hooks, including ftrace, audit and seccomp, later.
Those features will be implemented in separate patchsets, but it's safe to
check for all TIF_* now be
Currently syscall_trace() is called only for ptrace.
With additional TIF_xx flags defined, it is now called in all the cases
of audit, ftrace and seccomp in addition to ptrace.
Acked-by: Richard Guy Briggs
Signed-off-by: AKASHI Takahiro
---
arch/arm64/include/asm/thread_info.h | 13 ++
This macro, regs_return_value, is used mainly for audit to record system
call's results, but may also be used in test_kprobes.c.
Acked-by Will Deacon
Acked-by: Richard Guy Briggs
Signed-off-by: AKASHI Takahiro
---
arch/arm64/include/asm/ptrace.h |5 +
1 file changed, 5 insertions(+)
d
On Thu, 2014-02-27 at 17:27 -0800, Paul E. McKenney wrote:
> Hello, Thomas and Ingo,
>
> This pull request contains latency bandaids^Woptimizations to the
> timer-wheel code that are useful in conjunction with NO_HZ_FULL Kconfig
> option. These optimizations reduce the jiffy-by-jiffy looping in
Ganapatrao,
On 02/26/2014 12:38 AM, Kulkarni, Ganapatrao wrote:
From: AKASHI Takahiro
Sent: Tuesday, February 25, 2014 2:53 PM
To: rost...@goodmis.org; fweis...@gmail.com; mi...@redhat.com;
catalin.mari...@arm.com; will.dea...@arm.com; tim.b...@sonymob
On Fri, Feb 28, 2014 at 12:11:57PM +0800, Li, Aubrey wrote:
> This patch is to introduce BOOT_EFI and BOOT_CF9 in the reboot sequence
> loop, to fix the reboot problem on the known Intel Bay Trail-T based
> platform, for example, ASUS-T100 and Dell Venue 8/11 Pro. These
> platforms don't support AC
On Fri, 2014-02-28 at 14:03 +1100, James Morris wrote:
> Ok, which tree should take this? I'm happy to, although most of it is
> outside security/ .
Security might make the most sense - I don't think any of the additional
restrictions (beyond kexec, and I think we've hashed that argument out
no
On Thu, 2014-02-27 at 13:48 -0800, Davidlohr Bueso wrote:
> From: Davidlohr Bueso
> diff --git a/mm/nommu.c b/mm/nommu.c
> index 8740213..95c2bd9 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -768,16 +768,23 @@ static void add_vma_to_mm(struct mm_struct *mm, struct
> vm_area_struct *vma)
>
On Thu, Feb 27, 2014 at 09:08:01PM +0100, Linus Walleij wrote:
> On Thu, Feb 20, 2014 at 6:53 AM, Jenny TC wrote:
>
> > +++ b/include/linux/power/power_supply_charger.h
>
> > +#define MAX_CUR_VOLT_SAMPLES 3
> > +#define DEF_CUR_VOLT_SAMPLE_JIFF (30*HZ)
>
> Why are things defined in Jiffies like
From: Andi Kleen
With srcline key/sort'ing it's useful to have line numbers
in the annotate window. This patch implements this.
Use objdump -l to request the line numbers and
save them in the line structure. Then the browser
displays them for source lines.
The line numbers are not displayed by
From: Andi Kleen
For lbr-as-callgraph we need to see the line number in the history,
because many LBR entries can be in a single function, and just
showing the same function name many times is not useful.
When the history code is configured to sort by address, also try to
resolve the address to
From: Andi Kleen
When the source line is not found fall back to sym + offset.
This is generally much more useful than a raw address.
For this we need to pass in the symbol from the caller.
For some callers it's awkward to compute, so we stay
at the old behaviour.
Signed-off-by: Andi Kleen
---
From: Andi Kleen
The srcline sort output ignored the width, which caused
various problems with displaying srcline in the tui
browser. Just cut it off at width.
Signed-off-by: Andi Kleen
---
tools/perf/util/sort.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/ut
From: Andi Kleen
For perf report with --sort srcline only print the base source file
name. This makes the results generally fit much better to the
screen. The path is usually not that useful anyways because it is
often from different systems.
Signed-off-by: Andi Kleen
---
tools/perf/util/srcli
From: Andi Kleen
Add a --branch-history option to perf report that changes all
the settings necessary for using the branches in callstacks.
This is just a short cut to make this nicer to use, it does
not enable any functionality by itself.
v2: Change sort order. Rename option to --branch-histor
From: Andi Kleen
Currently branch stacks can be only shown as edge histograms for
individual branches. I never found this display particularly useful.
This implements an alternative mode that creates histograms over complete
branch traces, instead of individual branches, similar to how normal
ca
[All review feedback addressed.]
This patchkit implements lbr-as-callgraphs in per freport,
as an alternative way to present LBR information.
Current perf report does a histogram over the branch edges,
which is useful to look at basic blocks, but doesn't tell
you anything about the larger control
From: Andi Kleen
opensuse libbfd requires -lz -liberty to build. Add those
to the BFD feature detection.
Signed-off-by: Andi Kleen
---
tools/perf/config/Makefile| 2 +-
tools/perf/config/feature-checks/Makefile | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --gi
This patch is to introduce BOOT_EFI and BOOT_CF9 in the reboot sequence
loop, to fix the reboot problem on the known Intel Bay Trail-T based
platform, for example, ASUS-T100 and Dell Venue 8/11 Pro. These
platforms don't support ACPI reboot, we expect to call EFI runtime
service to handle this case
On 02/27/2014 07:45 PM, Jaegeuk Kim wrote:
Hi Al,
In the following configuration, I met a deadlock condition like below.
Kernel: 3.14-rc3
Workload: fsstress with 10 threads
Reproducible scenario: N/A
Is it related to this patch?
commit 1370e97bb2eb1ef2df7355204e5a4ba13e12b861
Author: Waiman Lo
> Subject: Re: [PATCH 2/3] ASoC: core: Set the default I/O up try regmap.
>
> On Thu, Feb 27, 2014 at 05:49:52PM +0800, Xiubo Li wrote:
> > For most CODEC drivers which the REGMAP is used, the soc_probe_codec()
> > will do the stuff work of snd_soc_codec_set_cache_io(), which the CODEC
> > driver
For the snd_soc_cache_init(), the reg_size maybe zero and then the value
of codec->reg_cache, which is alloced via kzalloc, maybe equal to
ZERO_SIZE_PTR. If the reg parameter of snd_soc_cache_write() is large enough,
the cache[idx] = val maybe cause the kernel crash...
So this patch fix this via d
On Thu, Feb 27, 2014 at 05:49:52PM +0800, Xiubo Li wrote:
> For most CODEC drivers which the REGMAP is used, the soc_probe_codec()
> will do the stuff work of snd_soc_codec_set_cache_io(), which the CODEC
> drivers' ASoC probe will do too, and almost at the same time.
Applied, thanks. I did a che
I think the psbfb case is just horribly broken; they probably want to populate
the entire VMA at mmap time rather than fault time. It'll be less code for
them.
ttm is more nuanced, and there're one or two other graphics drivers that have
similar requirements of "faulting around". But all of t
1 - 100 of 876 matches
Mail list logo
