(2013/07/30 1:41), Tom Zanussi wrote:
> +
> +static int
> +event_enable_trigger_func(struct event_command *cmd_ops, void *cmd_data,
> + char *glob, char *cmd, char *param, int enabled)
> +{
> + struct trace_array *tr = top_trace_array();
OK, here is the problem.
On 08/08/13 00:59, David Ahern wrote:
> Commit b55ae0a9 added code-reading.c which fails to compile on Fedora 16
> with compiler version:
> $ gcc --version
> gcc (GCC) 4.6.3 20120306 (Red Hat 4.6.3-2)
>
> Failure message is:
>
> tests/code-reading.c: In function ‘do_sort_something’:
>
On Thu, 2013-08-08 at 07:29 +0200, Mike Galbraith wrote:
> On Thu, 2013-08-08 at 12:31 +0800, ethan.zhao wrote:
>
> > diff --git a/arch/x86/include/asm/smp.h b/arch/x86/include/asm/smp.h
> > index 4137890..c27f04f 100644
> > --- a/arch/x86/include/asm/smp.h
> > +++ b/arch/x86/include/asm/smp.h
>
Le 26/06/2013 01:04, Scott Wood a écrit :
On Thu, Feb 28, 2013 at 09:52:22AM +0100, LEROY Christophe wrote:
This patch modifies the behaviour of the MPC8xx/8xxx watchdog. On the MPC8xx,
at 133Mhz, the maximum timeout of the watchdog timer is 1s, which means it must
be pinged twice a second.
On Wed, Aug 07, 2013 at 12:02:44PM +0300, Dan Aloni wrote:
> When my 'ifup eth' script was fired multiple times and ran concurrent on
> my laptop, for some obscure /etc scripting reason, it was revealed
> that the store_enabled() function in netconsole doesn't handle it nicely,
> as recorded by
Hi Simon,
Today's linux-next merge of the renesas tree got a conflict in
drivers/leds/leds-renesas-tpu.c between commit 33d693e59c42 ("leds: use
dev_get_platdata()") from the leds tree and commit ae3e4c277669 ("leds:
Remove leds-renesas-tpu driver") from the renesas tree.
I fixed it up (the
At Wed, 7 Aug 2013 17:45:09 +0100,
Mark Brown wrote:
>
> On Fri, Aug 02, 2013 at 12:59:24AM -0700, Felipe F. Tonello wrote:
>
> > +int jack_ctl_integer_info(struct snd_kcontrol *kcontrol,
> > + struct snd_ctl_elem_info *uinfo)
> > +{
> > + uinfo->type =
Hi all,
Today's linux-next merge of the mvebu tree got a conflict in
Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt between
commit f480adaf1b71 ("i2c: mv64xxx: Document the newly introduced
allwinner compatible") from the i2c tree and commit e7c4a1e9f937 ("ARM:
dts: mvebu: Introduce a new
On 08/08/2013 02:55 AM, Divy Le ray wrote:
> On 08/05/2013 11:41 AM, Jay Fenlason wrote:
>> On Mon, Aug 05, 2013 at 12:59:04PM +1000, Alexey Kardashevskiy wrote:
>>> Hi!
>>>
>>> Recently I started getting multiple errors like this:
>>>
>>> cxgb3 0006:01:00.0: iommu_alloc failed, tbl
This patch adds a new macro file for PMC macros.
This macro file includes the definitions of SR (status register) bit
offsets and will be use to reference PMC irqs.
Signed-off-by: Boris BREZILLON
---
include/dt-bindings/clk/at91/common/pmc.h | 20
1 file changed, 20
(I got several copies of that, one would have been plenty. Some people
get all grumpy when they get repeats, and at least one, who shall remain
unnamed, gets even grumpier when folks don't trim their replies, so be
careful;)
On Thu, 2013-08-08 at 12:31 +0800, ethan.zhao wrote:
> diff --git
On Thu, 2013-08-08 at 13:03 +0800, Tang Chen wrote:
> Change it to the style like other macros:
>
> #define INVALID_TABLE(x, path, name)\
> do { pr_err("ACPI OVERRIDE: " x " [%s%s]\n", path, name); } while (0)
Single statement macros do _not_ need
This patch adds new at91 main oscillator clock implementation using common
clk framework.
If rate is not provided during clock registration it is calculated using
the slow clock (main clk parent in this case) rate and MCFR register.
Signed-off-by: Boris BREZILLON
---
drivers/clk/at91/Makefile
On 08/08/2013 12:18 PM, Paul E. McKenney wrote:
> On Thu, Aug 08, 2013 at 11:10:47AM +0800, Lai Jiangshan wrote:
>> On 08/08/2013 10:33 AM, Paul E. McKenney wrote:
>>> On Thu, Aug 08, 2013 at 10:33:15AM +0800, Lai Jiangshan wrote:
On 08/08/2013 10:12 AM, Steven Rostedt wrote:
> On Thu,
On Wed, 2013-08-07 at 11:30 -0700, Alexander Duyck wrote:
> On 08/06/2013 07:56 PM, Alex Williamson wrote:
> > On Tue, 2013-08-06 at 16:27 -0700, Alexander Duyck wrote:
> >> On 08/05/2013 12:37 PM, Alex Williamson wrote:
> >>> The PCI spec indicates that with stable power, reset needs to be
> >>>
This patch adds at91 PMC (Power Management Controller) base support.
All at91 clocks managed by the PMC unit will use this framework.
This framework provides the following fonctionalities:
- define a new struct at91_pmc to hide PMC internals (lock, PMC memory
mapping, irq domain, ...)
-
Hi Doung
On 08/07/2013 06:37 AM, Doug Anderson wrote:
> The dw_mmc driver keeps a cache of the current slot->clock in order to
> avoid doing a whole lot of work every time set_ios() is called.
> However, after suspend/resume the register values are bogus so we need
> to ensure that the cached
The Hot-Pluggable field in SRAT suggests if the memory could be
hotplugged while the system is running. Print it as well when
parsing SRAT will help users to know which memory is hotpluggable.
Signed-off-by: Tang Chen
Reviewed-by: Wanpeng Li
Reviewed-by: Zhang Yanfei
Acked-by: Tejun Heo
---
In acpi_initrd_override(), it checks several things to ensure the
table it found is valid. In later patches, we need to do these check
somewhere else. So this patch introduces a common function
acpi_verify_table() to do all these checks, and reuse it in different
places. The function will be used
The comments of find_cpio_data() says:
* @offset: When a matching file is found, this is the offset to the
* beginning of the cpio. ..
But according to the code,
dptr = PTR_ALIGN(p + ch[C_NAMESIZE], 4);
nptr = PTR_ALIGN(dptr + ch[C_FILESIZE], 4);
*offset =
On Wed, Aug 7, 2013 at 9:29 PM, Aruna Balakrishnaiah
wrote:
> When we preallocate, we can use the same big_buf for compression as well as
> decompression.
> Also workspace will be one for both. By allocating max of inflate workspace
> size and deflate
> workspace size. We can save memory here.
This patch-set does some trivial fix and improving in ACPI code
for memory hotplug.
Patch 1,3,4 have been acked.
Tang Chen (4):
acpi: Print Hot-Pluggable Field in SRAT.
earlycpio.c: Fix the confusing comment of find_cpio_data().
acpi: Remove "continue" in macro INVALID_TABLE().
acpi:
The macro INVALID_TABLE() is defined like this:
#define INVALID_TABLE(x, path, name)\
{ pr_err("ACPI OVERRIDE: " x " [%s%s]\n", path, name); continue; }
And it is used like this:
for (...) {
...
if (...)
On Thu, Aug 08, 2013 at 12:08:56AM -0400, Steven Rostedt wrote:
> I went to do some benchmarks on the jump label code, and ran:
>
>
> perf stat -r 100 ./hackbench 50
>
> It ran twice, and then would die with:
>
> [ 65.785108] hackbench invoked oom-killer: gfp_mask=0x200da, order=0,
>
This patch adds the following Kconfig options to prepare the transition to
common clk framework:
- AT91_USE_OLD_CLK: this option is selected by every SoC which does not
support new at91 clks based on common clk framework (SoC which does not
define the clock tree in its device tree).
This
This patch moves at91_pmc.h header from machine specific directory
(arch/arm/mach-at91/include/mach/at91_pmc.h) to clk include directory
(include/linux/clk/at91_pmc.h).
We need this to avoid reference to machine specific headers in clk
drivers.
Signed-off-by: Boris BREZILLON
---
Hello,
This patch series is the 3rd version of the new at91 clock implementation
(using common clk framework).
Most of the clock provided by the PMC (Power Management Controller) are
implemented :
- main clock (main oscillator)
- pll clocks
- master clock
- programmable clocks
- utmi clock
-
On Wed, Aug 07, 2013 at 04:54:21PM -0700, Andrew Morton wrote:
> On Mon, 5 Aug 2013 15:09:35 -0700 Andi Kleen wrote:
>
> > From: Andi Kleen
> >
> > Use standard gcc __attribute__((alias(foo))) to define
> > the syscall aliases instead of custom assembler macros.
> >
> > This is far cleaner,
On 07/08/2013 20:59, Linus Walleij wrote:
On Sat, Jul 20, 2013 at 4:51 PM, Boris BREZILLON
wrote:
The current implementation handle both edge and level interrupts with the
'handle_simple_irq' handler.
Level interrupts are active as long as the pin stays at the configured
level (low or high).
Hi, perter and Mike,
Some other test to verify the regression causes etc.
On an 4 core intel i5 Asus pc.
The pipe test.
1. default Bios configuration and default 3.11-rc3 kernel.
[root@localhost ~]# time ./pip1m
real0m10.683s
user0m0.204s
sys 0m6.597s
[root@localhost ~]# time
On Wednesday 07 August 2013 11:00 PM, Tony Luck wrote:
Oh - one more thing - and my apologies for not spotting this before:
dst = allocate_buf_for_compression(big_buf_sz);
No - you may not call kmalloc() in oops/panic context. Please pre-allocate
everything you need in some
Arnaldo Carvalho de Melo wrote:
> Can you check how is this in the current perf/core branch so that we can
> move forward while I process some other patches?
This series (except this part) was merged into perf/completion of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux 3 weeks ago,
so
On Thu, Aug 08, 2013 at 11:10:47AM +0800, Lai Jiangshan wrote:
> On 08/08/2013 10:33 AM, Paul E. McKenney wrote:
> > On Thu, Aug 08, 2013 at 10:33:15AM +0800, Lai Jiangshan wrote:
> >> On 08/08/2013 10:12 AM, Steven Rostedt wrote:
> >>> On Thu, 2013-08-08 at 09:47 +0800, Lai Jiangshan wrote:
> >>>
On Wed, Aug 07, 2013 at 11:37:43AM -0400, Johannes Weiner wrote:
> On Wed, Aug 07, 2013 at 03:58:28PM +0100, Mel Gorman wrote:
> > On Fri, Aug 02, 2013 at 11:37:26AM -0400, Johannes Weiner wrote:
> > > @@ -352,6 +352,7 @@ struct zone {
> > >* free areas of different sizes
> > >*/
> > >
Hello Arnd,
On 07/08/2013 22:24, Arnd Bergmann wrote:
On Thursday 01 August 2013, Boris BREZILLON wrote:
This patch moves peripheral id definitions from machine specific include
dir (arch/arm/mach-at91/include/mach/'soc-name'.h) to dt-bindinds include
dir
Commit-ID: a02150610776f66b40257624822a879311592bb2
Gitweb: http://git.kernel.org/tip/a02150610776f66b40257624822a879311592bb2
Author: Kees Cook
AuthorDate: Mon, 8 Jul 2013 09:15:17 -0700
Committer: H. Peter Anvin
CommitDate: Wed, 7 Aug 2013 21:00:04 -0700
x86, relocs: Move ELF
Hi Greg,
Could you queue this commit for 3.0 and 3.4? It has been acked by Ingo.
On 2013/8/2 19:14, Ingo Molnar wrote:
>
> * Li Zefan wrote:
>
>> commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
>> Author: Zhu Yanhai
>> Date: Tue Jan 8 12:56:52 2013 +0800
>>
>> sched: Fix the broken
Hi Tony,
On Thursday 08 August 2013 03:52 AM, Tony Luck wrote:
On Tue, Aug 6, 2013 at 10:35 PM, Tony Luck wrote:
ERST is at the whim of the BIOS writer (the ACPI standard doesn't provide any
suggestions on record sizes). My systems support ~6K record size.
Off by a little - 7896 bytes on my
I went to do some benchmarks on the jump label code, and ran:
perf stat -r 100 ./hackbench 50
It ran twice, and then would die with:
[ 65.785108] hackbench invoked oom-killer: gfp_mask=0x200da, order=0,
oom_score_adj=0
[ 65.792921] hackbench cpuset=/ mems_allowed=0
[ 65.797286] CPU: 6
[2.6.34.x longterm stable status] On 05/08/2013 (Mon 22:32) Aaro Koskinen wrote:
> Hi,
>
> There hasn't been 2.6.34.x stable tree releases for a
> while. Also, in some mails you have mentioned EOLing this tree (e.g.
> http://marc.info/?l=linux-doc=137393133817894=2). I have two questions
>
On Wed, 2013-08-07 at 10:25 +0200, Mike Galbraith wrote:
> E5620 (2.4 GHz Westmere) throttle
>
> v3.11-rc4-27-ge4ef108 v3.11-rc4-27-ge4ef108+peterz
> 6.76% [k] __schedule 7.68% [k]
> reschedule_interrupt (find this little bastard)
On 08/07/2013 06:34 PM, Kees Cook wrote:
>
> Hi Peter,
>
> Can this get added to tip?
>
> Thanks,
>
> -Kees
>
Sorry, missed the 7/8 update...
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Tue, 6 Aug 2013, Alex Thorlton wrote:
> I've gotten my hands on some of the benchmarks/code that were used to
> originally uncover the performance issues we're seeing. I'm currently
> trying to separate out the performance issues that are being caused by
> the kernel code from issues
[Problem]
The current Linux cannot migrate pages used by the kerenl because
of the kernel direct mapping. In Linux kernel space, va = pa + PAGE_OFFSET.
When the pa is changed, we cannot simply update the pagetable and
keep the va unmodified. So the kernel pages are not migratable.
There are also
The previous patch introduced two new functions:
acpi_tb_install_table_firmware() and acpi_tb_install_table_override().
They are the same as acpi_tb_install_table() if they are called in sequence.
In order to split acpi_tb_parse_root_table(), we call these two functions
instead of
[Problem]
The current Linux cannot migrate pages used by the kerenl because
of the kernel direct mapping. In Linux kernel space, va = pa + PAGE_OFFSET.
When the pa is changed, we cannot simply update the pagetable and
keep the va unmodified. So the kernel pages are not migratable.
There are also
Hi Linus,
On Thu, Aug 8, 2013 at 12:23 AM, Linus Walleij wrote:
> On Wed, Jul 17, 2013 at 7:31 AM, Sonic Zhang wrote:
>
> I'd like Stephen and Axel to have a look at this as well...
>
>> From: Sonic Zhang
>>
>> in pinmux_disable_setting after current device fails to request
>> the same pins.
The previous patch introduces two new functions:
acpi_tb_root_table_install() and acpi_tb_root_table_override(),
which work just the same as acpi_tb_parse_root_table() if they are
called in sequence.
In order to split acpi_initialize_tables(), call thes two functions
in
This patch splits acpi_initialize_tables() into two steps, and
introduces two new functions:
acpi_initialize_tables_firmware() and acpi_tb_root_table_override(),
which work just the same as acpi_initialize_tables() if they are called
in sequence.
Signed-off-by: Tang Chen
Reviewed-by: Zhang
This patch splits acpi_tb_parse_root_table() into two steps, and
introduces two new functions:
acpi_tb_root_table_install() and acpi_tb_root_table_override().
They are just the same as acpi_tb_parse_root_table() if they are
called in sequence.
Signed-off-by: Tang Chen
Reviewed-by: Zhang
Hi Stephen,
On Thu, Aug 8, 2013 at 1:09 AM, Stephen Warren wrote:
> On 08/07/2013 10:23 AM, Linus Walleij wrote:
>> On Wed, Jul 17, 2013 at 7:31 AM, Sonic Zhang wrote:
>>
>> I'd like Stephen and Axel to have a look at this as well...
>>
>>> From: Sonic Zhang
>>>
>>> in pinmux_disable_setting
On 08/08/2013 02:38 AM, Eric W. Biederman wrote:
> Chen Gang writes:
>
>> Firstly, sorry for replying late, and also thank you for your detail
>> patient reply.
>>
>> On 08/07/2013 03:45 PM, Eric W. Biederman wrote:
>>> Chen Gang writes:
>>>
On 08/07/2013 05:46 AM, Eric W. Biederman wrote:
On 08/08/2013 10:33 AM, Paul E. McKenney wrote:
> On Thu, Aug 08, 2013 at 10:33:15AM +0800, Lai Jiangshan wrote:
>> On 08/08/2013 10:12 AM, Steven Rostedt wrote:
>>> On Thu, 2013-08-08 at 09:47 +0800, Lai Jiangshan wrote:
>>>
> [ 393.641012]CPU0
> [ 393.641012]
>
Hi Linus,
On Thu, Aug 8, 2013 at 2:56 AM, Linus Walleij wrote:
> On Thu, Aug 1, 2013 at 9:31 AM, Sonic Zhang wrote:
>> On Tue, Jul 30, 2013 at 12:47 AM, Linus Walleij
>> wrote:
>>> On Fri, Jul 26, 2013 at 6:57 AM, Sonic Zhang wrote:
>>>
Could you please comment on this patch set? It is
On 8 August 2013 00:25, Stephen Warren wrote:
> On 08/07/2013 12:06 PM, Viresh Kumar wrote:
>> On 7 August 2013 23:12, Stephen Warren wrote:
>>> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
cpufreq-cpu0 driver needs OPPs to be present in DT which can be probed by
it to
get
Occassionally events (e.g., context-switch, sched tracepoints) are losing
the conversion of sample data associated with a thread. For example:
$ perf record -e sched:sched_switch -c 1 -a -- sleep 5
$ perf script
ls 30482 [000] 1379727.583037: sched:sched_switch: prev_comm=ls
prev_pid=30482
Avoid walking the list of idle symbols more than once by setting a
flag in the symbol struct.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/util/symbol.c | 44
The PERF_RECORD_FORK event is already collected as part of the use of
cmd_record and those events are analyzed as part of the libperf machinery.
Using the fork tracepoint as well just duplicates the event load.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc:
Not used in the function, so no sense in doing the lookup here. Thread look
up will be done in the timehist command, and no sense in doing it twice.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
On 08/07/2013 12:15 PM, Raghavendra K T wrote:
On 08/07/2013 10:18 AM, H. Peter Anvin wrote:
tip:master is not a stable branch; it is more like linux-next. We need
to figure out which topic branches are dependencies for this set.
Okay. I 'll start looking at the branches that would get
Allows user to specify a list of symbols not interested in. One use case is
the upcoming timehist command.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/util/symbol.c | 20
Leverage new exclude symbol list to allow user to not see certain functions
in a backtrace. For example repeating patterns like:
do_select core_sys_select sys_select
can be reduced to just sys_select when dumping callchains, consuming less
real estate on the screen while still conveying the
>> If somebody needs a notification interface (and there is no one available
>> right now) then you cannot prevent from such a pointless work anyway...
>
> I'm gonna add one for freezer state transitions. It'll be simple
> "this file changed" thing and will probably apply that to at least oom
>
Make print options based on flags. Simplifies addition of more print
options which is the subject of upcoming patches.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/builtin-script.c
Option is used by upcoming timehist command.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/util/session.c |8 ++--
tools/perf/util/session.h |1 +
2 files changed, 7
Save vmlinux or kallsyms path loaded using embedded default lookup (ie.,
not a user specified path). Upcoming perf sched timehist command requires
kernel symbols for properly computing idle times and prints a warning
if the kernel symbols are not loaded.
Signed-off-by: David Ahern
Cc: Ingo
Event is not needed nor analyzed. Since perf-sched leverages perf-record
to capture the sched data, we already capture task events like EXIT.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
Context switch events are 64 bytes; sched_switch events are 136 bytes.
Both indicate scheduling changes, so allow user to leverage the smaller
event. If both events exist in a data file, then context-switch event is
ignored.
Signed-off-by: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
By default 'perf sched timehist' dumps a run-time summary for each task. The
summary includes the number of times the process was scheduled and the min, max
and average run times when scheduled (ie., a measure of how CPU time the task
wanted). Summary of idle times per cpu is also shown.
Example
Upcoming timehist command needs access to the event. Use the existing
handler.data element to do that.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/builtin-sched.c |3 ++-
1
Option is used by upcoming timehist command.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/builtin-script.c |6 --
tools/perf/util/session.c |6 --
Useful for debugging and correlating extra events in a file with
the scheduling events collected.
Signed-off-by: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/builtin-sched.c |
Allows analysis of individual tasks within a file collected for the
entire system.
Signed-off-by: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/builtin-sched.c | 50
Any event can have RAW data attribute set. The intent of the function is
to determine if the session has tracepoints, so check for the type of each
event explicitly.
Signed-off-by: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc:
Avoids strcmp processing each sample.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/builtin-top.c | 25 ++---
1 file changed, 2 insertions(+), 23 deletions(-)
Destroy argument is not necessary. If session is not returned to caller,
then clean it up.
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Stephane Eranian
---
tools/perf/builtin-sched.c | 16 +---
1
Ingo/Arnaldo:
I have a lot of patches queued up on top of this set. Before I go much farther
and the queue grows longer I wanted to throw out this set for comments, review
and inclusion where possible. Most of the patches are cleanups and re-workings
leading up to the new command. The patches I
On 8 August 2013 00:21, Stephen Warren wrote:
> On 08/07/2013 11:59 AM, Viresh Kumar wrote:
>> On 7 August 2013 23:23, Stephen Warren wrote:
>>> That link only describes why we shouldn't have a dedicated compatible
>>> value for cpufreq. I certainly agree with that. However, I think it's
>>>
On Wed, 7 Aug 2013, Vince Weaver wrote:
> On Wed, 7 Aug 2013, Stephen Boyd wrote:
>
> > ---8<
> >
> > diff --git a/arch/arm/kernel/perf_event.c b/arch/arm/kernel/perf_event.c
> > index d9f5cd4..21f7790 100644
> > --- a/arch/arm/kernel/perf_event.c
> > +++ b/arch/arm/kernel/perf_event.c
> >
On 8 August 2013 00:20, Stephen Warren wrote:
> Right, and that's *exactly* what having a cpufreq driver is for; to
> implement the details of CPU clock management.
cpufreq drivers used to keep such information since a long time,
probably because there wasn't another place to keep them and
On 08/08/2013 10:12 AM, Steven Rostedt wrote:
> On Thu, 2013-08-08 at 09:47 +0800, Lai Jiangshan wrote:
>
>>> [ 393.641012]CPU0
>>> [ 393.641012]
>>> [ 393.641012] lock(>wait_lock);
>>> [ 393.641012]
>>> [ 393.641012] lock(>wait_lock);
>>
>> Patch2 causes it!
>>
On 08/08/2013 12:03 AM, Stephen Warren wrote:
> On 08/07/2013 12:52 AM, Wei Ni wrote:
>> Enable thermal sensor nct1008 for t114 dalmore.
>
> Wei, I assume this patch doesn't depend on any of the other LM90-related
> patches you've sent; I can simply apply it right away?
In my [PATCH 1/2], I add
memcg requires the cgroup id to be smaller than 65536.
This is a preparation to kill css id.
Signed-off-by: Li Zefan
Acked-by: Michal Hocko
---
mm/memcontrol.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 3189f70..c0bb83c 100644
---
Now memcg uses cgroup id instead of css id. Update some comments and
set mem_cgroup_subsys->use_id to 0.
Signed-off-by: Li Zefan
Acked-by: Michal Hocko
---
mm/memcontrol.c | 24
1 file changed, 8 insertions(+), 16 deletions(-)
diff --git a/mm/memcontrol.c
The only user of css_id was memcg, and it has been convered to use
cgroup->id, so kill css_id.
Signed-off-by: Li Zefan
Reviewed-by: Michal Hocko
Acked-by: Tejun Heo
---
include/linux/cgroup.h | 37
kernel/cgroup.c| 252 +
2
On Thu, Aug 08, 2013 at 10:33:15AM +0800, Lai Jiangshan wrote:
> On 08/08/2013 10:12 AM, Steven Rostedt wrote:
> > On Thu, 2013-08-08 at 09:47 +0800, Lai Jiangshan wrote:
> >
> >>> [ 393.641012]CPU0
> >>> [ 393.641012]
> >>> [ 393.641012] lock(>wait_lock);
> >>> [
Use cgroup id instead of css id. This is a preparation to kill css id.
Note, as memcg treat 0 as an invalid id, while cgroup id starts with 0,
we define memcg_id == cgroup_id + 1.
Signed-off-by: Li Zefan
Acked-by: Michal Hocko
---
mm/memcontrol.c | 34 --
1
On 8 August 2013 04:55, Rafael J. Wysocki wrote:
> It looks like it would require us to redefine .target() to take next_state
> instead of target_freq (at least in the acpi-cpufreq case), wouldn't it?
If we don't do it, then atleast for few drivers, like acpi-cpufreq, which
use index more than
Hi Andrew,
All the cgroup preparation patches are in cgroup tree now, and these
remaining patches can be routed by mm tree.
===
This patchset converts memcg to use cgroup->id, and then we can remove
cgroup css_id.
As we've removed memcg's own refcnt, converting memcg to use cgroup->id
This is a preparation to kill css_id.
Signed-off-by: Li Zefan
Acked-by: Michal Hocko
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 6f292b8..87a2537 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1353,7
On 08/08/2013 10:12 AM, Steven Rostedt wrote:
> On Thu, 2013-08-08 at 09:47 +0800, Lai Jiangshan wrote:
>
>>> [ 393.641012]CPU0
>>> [ 393.641012]
>>> [ 393.641012] lock(>wait_lock);
>>> [ 393.641012]
>>> [ 393.641012] lock(>wait_lock);
>>
>> Patch2 causes it!
>>
On Wed, 7 Aug 2013, Stephen Boyd wrote:
> ---8<
>
> diff --git a/arch/arm/kernel/perf_event.c b/arch/arm/kernel/perf_event.c
> index d9f5cd4..21f7790 100644
> --- a/arch/arm/kernel/perf_event.c
> +++ b/arch/arm/kernel/perf_event.c
> @@ -53,7 +53,12 @@ armpmu_map_cache_event(const unsigned
How much does this matter?
"Yu, Fenghua" wrote:
>> From: Yu, Fenghua
>> Sent: Wednesday, August 07, 2013 3:46 PM
>>
>> > From: Borislav Petkov [mailto:b...@alien8.de]
>> > Sent: Wednesday, July 24, 2013 6:33 AM
>> > On Tue, Jul 23, 2013 at 11:00:26PM +0200, Torsten Kaiser wrote:
>> > > Extract
> -Original Message-
> From: grund...@google.com [mailto:grund...@google.com] On Behalf Of Grant
> Grundler
> Sent: Thursday, August 08, 2013 1:21 AM
>
> On Wed, Aug 7, 2013 at 5:07 AM, Cho KyongHo wrote:
> ...
> >> I don't understand how this is possible. Can someone explain this
> >>
On Thu, 2013-08-08 at 11:02 +0900, Masami Hiramatsu wrote:
> # mkdir instances/hoge
> # echo 'enable_event:mce:mce_record' >
> instances/hoge/events/syscalls/sys_enter_symlink/trigger
> # cat instances/hoge/events/syscalls/sys_enter_symlink/enable
> 0*
> # cat
Hello Rob:
Maybe I misunderstand what you said (if so, I am sorry for it).
At least for me, what you said is valuable to get additional discussion,
but it seems better to start a new thread for it and also cc to
linux-doc mail list.
If so better include me in cc list, thanks. ;-)
If you think
On Thu, 2013-08-08 at 09:47 +0800, Lai Jiangshan wrote:
> > [ 393.641012]CPU0
> > [ 393.641012]
> > [ 393.641012] lock(>wait_lock);
> > [ 393.641012]
> > [ 393.641012] lock(>wait_lock);
>
> Patch2 causes it!
> When I found all lock which can (chained) nested in
Hi,
(2013/07/30 1:40), Tom Zanussi wrote:
> Hi,
>
> This is v4 of the trace event triggers patchset, addressing more
> comments from Masami Hiramatsu (thanks for the review and comments).
>
> One of Masami's comments was on event_trigger_regex_open's use of
> inode->i_private and that the same
On Wed, 7 Aug 2013, Stephen Boyd wrote:
> Is config some really big value? It looks like config (or more
> specifically event->attr.config) is ecececec which is larger than 9
> (PERF_COUNT_HW_MAX). I'm fairly certain r4 is event->attr.type
> (PERF_TYPE_HARDWARE) and so we're out of bounds on that
This is useful to spot high latency blips. It is normal for HLT
reasons to have long exit times, so strip those from the duration
check.
v2: changed threshold to duration per acme's request
Signed-off-by: David Ahern
Cc: Arnaldo Carvalho de Melo
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc:
1 - 100 of 1724 matches
Mail list logo
