* Namhyung Kim wrote:
> Hello,
>
> This is a new version of callchain improvement patchset. Basically
> it's almost same as v4 but rebased on current acme/perf/core and some
> functions are renamed as Frederic requested.
>
> Now I'm hunting down a bug in 'perf report -s sym' which was found
On Fri, 2013-10-11 at 16:49 +1100, Ryan Mallon wrote:
> It doesn't matter what the value of kptr_restrict happens to be, the
> code is still broken. So, with your patch, values 0 and 2 of
> kptr_restrict will print a seemingly correct value, but when
> kptr_restrict is 1 then it will print
On 10/10/13 09:30, Michal Simek wrote:
> s/op/pdev/ in xilinxfb_of_probe().
> No functional chagnes.
>
> Signed-off-by: Michal Simek
> ---
> Changes in v3: None
> Changes in v2: None
>
> drivers/video/xilinxfb.c | 18 +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
On Fri, 2013-09-06 at 14:30 -0600, Bjorn Helgaas wrote:
> On Thu, Sep 05, 2013 at 03:55:27PM +0800, Yijing Wang wrote:
> > Use pci_is_pcie() to simplify code.
> >
> > Acked-by: Kumar Gala
> > Reviewed-by: Gavin Shan
> > Signed-off-by: Yijing Wang
> > Cc: Gavin Shan
> > Cc: Benjamin
No real reason to do this.
"K. Y. Srinivasan" wrote:
>The variable hv_lapic_frequency is only used when CONFIG_X86_LOCAL_APIC
>is defined. Make the necessary adjustment.
>
>Signed-off-by: K. Y. Srinivasan
>---
> arch/x86/kernel/cpu/mshyperv.c |2 +-
> 1 files changed, 1 insertions(+), 1
* Kirill A. Shutemov wrote:
> I've missed that we preallocate few pmds on pgd_alloc() if X86_PAE
> enabled. Let's add missed constructor/destructor calls.
>
> I haven't noticed it during testing since prep_new_page() clears
> page->mapping and therefore page->ptl. It's effectively equal to
>
On 11/10/13 16:38, Joe Perches wrote:
> On Fri, 2013-10-11 at 16:31 +1100, Ryan Mallon wrote:
>> On 11/10/13 16:25, Joe Perches wrote:
>>> Printing kernel pointers via %pK has a minor defect when
>>> kptr_restrict is set to 2: the pointer may be emitted
>>> as "pK-error" instead of all 0's when
* Fengguang Wu wrote:
> > Indeed. Something like the updated version below?
> >
> > [ I kept the asm_volatile_goto() naming to make sure the implicit volatile
> > is visible. ]
>
> Ingo, I applied this patch (as commit c015a7f0b746) on top of
> tip/sched/core
>
> 3354781a2184
On Fri, 2013-10-11 at 16:31 +1100, Ryan Mallon wrote:
> On 11/10/13 16:25, Joe Perches wrote:
> > Printing kernel pointers via %pK has a minor defect when
> > kptr_restrict is set to 2: the pointer may be emitted
> > as "pK-error" instead of all 0's when in an interrupt.
>
> NAK. This is not a
On Thu, Oct 10, 2013 at 06:03:01PM -0300, Marcelo Tosatti wrote:
> On Thu, Oct 10, 2013 at 10:16:46PM +0300, Gleb Natapov wrote:
> > On Thu, Oct 10, 2013 at 01:42:22PM -0300, Marcelo Tosatti wrote:
> > > On Thu, Oct 10, 2013 at 03:08:45PM +0300, Gleb Natapov wrote:
> > > > On Wed, Oct 09, 2013 at
On 11/10/13 16:25, Joe Perches wrote:
> Printing kernel pointers via %pK has a minor defect when
> kptr_restrict is set to 2: the pointer may be emitted
> as "pK-error" instead of all 0's when in an interrupt.
NAK. This is not a defect, as I explained earlier. It is really a defect
that it
On Fri, 2013-10-11 at 16:19 +1100, Ryan Mallon wrote:
> Yeah, that is probably the best solution. I'll try to put together a
> patch series doing this. It will obviously be more involved though, so I
> think it is still worth merging the original patch in the interm.
I just submitted a patch
Hi Linus,
all over the map,
nouveau: disable MSI, needs more work, will try again next merge window,
radeon: audio + uvd regression fixes, dpm fixes, reset fixes
i915: dpms one might fix your haswell,
and one pain in the ass revert, so we have VGA arbitration that when
implemented 4-5 years
Remove a few coding style nits:
o Leading spaces for tabs
o case indentation depth
o else and brace locations
o logical continuation placement
Several checkpatch bleats still exist,
mostly not worth changing.
Signed-off-by: Joe Perches
---
lib/vsprintf.c | 83
Printing kernel pointers via %pK has a minor defect when
kptr_restrict is set to 2: the pointer may be emitted
as "pK-error" instead of all 0's when in an interrupt.
Fix this defect, neaten the code, and correct the sysctl
documentation.
Add missing documentation for 2 other uses: %pNF and %pV.
On 11/10/13 15:42, George Spelvin wrote:
> ebied...@xmission.com (Eric W. Biederman) wrote:
>> Sigh. This is all wrong. The only correct thing to test is
>> file->f_cred. Aka the capabilities of the program that opened the
>> file.
>>
>> Which means that the interface to %pK in the case of
From: Frederic Weisbecker
This way we can later delimit a lifecycle for the comm and map a hist to
a precise comm:timeslice couple.
Comm and fork events that don't have PERF_SAMPLE_TIME samples can only
send 0 value as a timestamp and thus should overwrite any previous comm
on a given thread
Hi Mark, Jean-Christophe,
On 10/10/13 20:50, Mark Brown wrote:
> Today's linux-next merge of the omap_dss2 tree got conflicts in
> drivers/video/omap2/dss/hdmi4_core.[ch] caused by ef26958a (omapdss:
> HDMI: Rename hdmi driver files to nicer names) interacting with a range
> of commits from
From: Frederic Weisbecker
As the thread comm is going to be implemented by way of a more
complicated data structure than just a pointer to a string from the
thread struct, convert the readers of comm to use an accessor instead
of accessing it directly. The accessor will be later overriden to
From: Frederic Weisbecker
This new comm infrastructure provides two features:
1) It keeps track of all comms lifecycle for a given thread. This
way we can associate a timeframe to any thread comm, as long as
PERF_SAMPLE_TIME samples are joined to comm and fork events.
As a result we should
From: Namhyung Kim
It can take quite amount of time so add progress bar UI to inform user.
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-annotate.c | 2 +-
tools/perf/builtin-diff.c | 2 +-
tools/perf/builtin-report.c | 10 +-
From: Frederic Weisbecker
Now that comm strings are allocated only once and refcounted to be shared
among threads, these can now be safely compared by addresses. This
should remove most hists collapses on post processing.
Signed-off-by: Frederic Weisbecker
Cc: Jiri Olsa
Cc: David Ahern
Cc:
From: Namhyung Kim
At insert time, a hist entry should reference comm at the time
otherwise it'll get the last comm anyway.
Signed-off-by: Namhyung Kim
Cc: Frederic Weisbecker
Link: http://lkml.kernel.org/n/tip-n6pykiiymtgmcjs834go2...@git.kernel.org
[ Fixed up const pointer issues ]
From: Namhyung Kim
Introduce ui_progress_setup() and ui_progress__advance() to separate
out from the session logic. It'll be used by other places in the
upcoming patch.
Cc: Jiri Olsa
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/ui/progress.c | 18 ++
From: Namhyung Kim
Current collapse stage has a scalability problem which can be
reproduced easily with parallel kernel build. This is because it
needs to traverse every children of callchain linearly during the
collapse/merge stage. Convert it to rbtree reduced the overhead
significantly.
On
Hello,
This is a new version of callchain improvement patchset. Basically
it's almost same as v4 but rebased on current acme/perf/core and some
functions are renamed as Frederic requested.
Now I'm hunting down a bug in 'perf report -s sym' which was found
during the test, but I think it's not
> I think something like the below may address the issue - I've only build
> tested this so far.
>
> We have another case where DRM does the wrong thing here too - a similar
> thing goes on with connectors as well. I've not yet looked into this,
> but I'll take a look later today.
>
> Fengguang
The variable hv_lapic_frequency is only used when CONFIG_X86_LOCAL_APIC
is defined. Make the necessary adjustment.
Signed-off-by: K. Y. Srinivasan
---
arch/x86/kernel/cpu/mshyperv.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/cpu/mshyperv.c
ebied...@xmission.com (Eric W. Biederman) wrote:
> Sigh. This is all wrong. The only correct thing to test is
> file->f_cred. Aka the capabilities of the program that opened the
> file.
>
> Which means that the interface to %pK in the case of kptr_restrict is
> broken as it has no way to be
On 10/10/13 21:58, Lars-Peter Clausen wrote:
> According to the datasheet the the panel as a dedicated dout pin. Maybe
> you did not connect it in your design, which means you won't be able to
> read any data from the panel at all.
I don't see a dedicated dout in the datasheet...
From: Wei Yongjun
Use free_bch() instead of kfree() to free init_bch()
allocated data.
Signed-off-by: Wei Yongjun
---
drivers/mtd/devices/docg3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/devices/docg3.c b/drivers/mtd/devices/docg3.c
index
From: Wei Yongjun
Use vfree() instead of kfree() to free vmalloc()
allocated data.
Signed-off-by: Wei Yongjun
---
drivers/staging/crystalhd/crystalhd_lnx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/crystalhd/crystalhd_lnx.c
On Thu, Oct 10, 2013 at 05:12:19PM +0200, Ingo Molnar wrote:
>
> * Jakub Jelinek wrote:
>
> > On Thu, Oct 10, 2013 at 07:04:18AM -0700, Richard Henderson wrote:
> > > On 10/10/2013 01:31 AM, Jakub Jelinek wrote:
> > > > Also, for the bitops patch, you probably want an asm_volatile_goto
> > > >
> Damn gmail screwed up my reply-all,
>
> anyhoo I get the feeling I'd rather do this like fbdev does and stop using
> an embedded kdev for this if I can. The lifetime of the minor and the sysfs
> objects aren't necessarily that tied together esp with hot unplug of
> USB devices.
>
> e.g. when a
Sorry for the very late reply, finally got some time to look at other
peoples code.
On Tue, 3 Sep 2013 14:05:08 +0900
Namhyung Kim wrote:
> From: Namhyung Kim
>
> The set_graph_notrace filter is analogous to set_ftrace_notrace and
> can be used for eliminating uninteresting part of function
the capacity calculation is obvious buggy.
Signed-off-by: Shaohua Li
---
drivers/block/null_blk.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: master/drivers/block/null_blk.c
===
---
On Sun, Oct 06, 2013 at 08:14:10PM -0400, Mike Snitzer wrote:
> On Fri, Oct 04 2013 at 1:07pm -0400,
> Mike Snitzer wrote:
>
> > With your latest fix I was able to create a thin device and format with
> > XFS. Unfortunately, when I tried to run the thinp-test-suite the very
> > first
If a tag is freed, the request might be used very soon. There is a short window
rq->q is null, so cache it.
Signed-off-by: Shaohua Li
---
block/blk-mq.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: master/block/blk-mq.c
On Thu, Oct 10, 2013 at 8:53 PM, Russell King - ARM Linux
wrote:
> On Thu, Oct 10, 2013 at 10:19:20AM +0100, Russell King - ARM Linux wrote:
>> On Thu, Oct 10, 2013 at 03:23:45AM +0100, Dave Airlie wrote:
>> >
>> > > I think David Arlie also needs a quiet talking to about how to use the
>> > >
1. Add new supporting declarations to option.c, to support Huawei new devices
with new bInterfaceSubClass value.
Signed-off-by: fangxiaozhi
--- linux-3.11.4-orig/drivers/usb/serial/option.c 2013-10-10 16:13:25.443072876
+0800
+++
Ryan Mallon writes:
> On 11/10/13 13:20, Eric W. Biederman wrote:
>> Joe Perches writes:
>>
>>> Some setuid binaries will allow reading of files which have read
>>> permission by the real user id. This is problematic with files which
>>> use %pK because the file access permission is checked at
On 10/10/2013 03:07 PM, Matt Porter wrote:
On 10/10/2013 01:57 PM, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, October 10, 2013 10:46 AM
On Thu, Oct 10, 2013 at 12:54:40PM -0400, Matt Porter wrote:
On 10/10/2013 11:29 AM, Felipe Balbi wrote:
On Mon, Oct 07,
On 11/10/13 13:20, Eric W. Biederman wrote:
> Joe Perches writes:
>
>> Some setuid binaries will allow reading of files which have read
>> permission by the real user id. This is problematic with files which
>> use %pK because the file access permission is checked at open() time,
>> but the
On Mon, Oct 07, 2013 at 07:19:58PM -0300, Geyslan G. Bem wrote:
> Free memory allocated to edma_desc when failing to allocate slot.
>
> Signed-off-by: Geyslan G. Bem
Applied thanks
~Vinod
> ---
> drivers/dma/edma.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/dma/edma.c
On Thu, Sep 26, 2013 at 02:28:37AM +0400, Sergei Shtylyov wrote:
> Commit c1c63a14f4f2419d093acd7164eccdff315baa86 (DMA: shdma: switch to managed
> resource allocation) got rid of shdma_free_irq() but unfortunately got merged
> later than commit c4f6c41ba790bbbfcebb4c47a709ac8ff1fe1af9 (dma: add
On Thu, Oct 10, 2013 at 08:23:13PM -0600, Jens Axboe wrote:
> On Thu, Oct 10 2013, Kent Overstreet wrote:
> > Linus, please apply - the last fix in the bugfix series I sent you had an
> > embarassing screwup...
> >
> > For 3.13, shall I start sending you pull requests directly?
>
> Sorry I
From: Hyunhee Kim
Date: Wed, 9 Oct 2013 16:21:36 +0900
Subject: [PATCH] Input: add regulator haptic driver
The regulator haptic driver function can be used to control motor by on/off
regulator.
User can control the haptic driver by using force feedback framework.
Signed-off-by: Hyunhee Kim
Thanks, Seth
On Thu, Oct 10, 2013 at 10:26 AM, Seth Jennings
wrote:
> On Thu, Oct 10, 2013 at 09:29:07AM +0800, Bob Liu wrote:
>> On 10/09/2013 10:40 PM, Seth Jennings wrote:
>> >
>> > The reason we never noticed this for zswap is that zswap has no
>> > dynamically allocated per-type resources.
On Thu, Oct 10 2013, Kent Overstreet wrote:
> Linus, please apply - the last fix in the bugfix series I sent you had an
> embarassing screwup...
>
> For 3.13, shall I start sending you pull requests directly?
Sorry I dropped the ball on that one, it's the first time ever I've
missed a deadline.
From: Hyunhee Kim
Date: Wed, 9 Oct 2013 16:21:36 +0900
Subject: [PATCH] Input: add regulator haptic driver
The regulator haptic driver function can be used to control motor by on/off
regulator.
User can control the haptic driver by using force feedback framework.
Signed-off-by: Hyunhee Kim
Hi Jin,
On 10/11/2013 07:54 AM, Jin Xu wrote:
>> Date: Thu, 10 Oct 2013 16:11:53 +0800
>> From: guz.f...@cn.fujitsu.com
>> To: jinuxst...@live.com
>> CC: yuan.mark.zh...@samsung.com; jaegeuk@samsung.com;
>> linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel.org;
>>
Joe Perches writes:
> Some setuid binaries will allow reading of files which have read
> permission by the real user id. This is problematic with files which
> use %pK because the file access permission is checked at open() time,
> but the kptr_restrict setting is checked at read() time. If a
On Thu, 2013-10-10 at 17:22 -0600, David Ahern wrote:
> Running 3.12-rc3 just hit BUG in autofs4_expire_wait
It doesn't look like this could be due to Al's change to the locking in
autos4_wait() and that the only change to autofs that I'm aware of.
Could you do a bisect please?
>
>
Signed-off-by: Jingchang Lu
---
arch/arm/boot/dts/vf610.dtsi | 49 +
include/dt-bindings/dma/vf610-edma.h | 103 +++
2 files changed, 152 insertions(+)
create mode 100644 include/dt-bindings/dma/vf610-edma.h
diff --git
Signed-off-by: Jingchang Lu
---
arch/arm/mach-imx/clk-vf610.c | 5 +
include/dt-bindings/clock/vf610-clock.h | 6 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/clk-vf610.c b/arch/arm/mach-imx/clk-vf610.c
index b169a39..29f88a2 100644
---
On Thu, Oct 10, 2013 at 09:21:36PM +0200, Arokux X wrote:
> Hi,
>
> recently I have been working on mainlining a simple bus glue driver
> for the USB EHCI for the Allwinner family of the ARM SoCs aka sunxi.
> The patches are almost ready and can be found at [1] and will be
> submitted once
From: Lan Tianyu
SBS's proc directory isn't useded and so remove it. Prepare for removing
/proc/acpi directory.
Signed-off-by: Lan Tianyu
---
drivers/acpi/sbs.c | 325 +
1 file changed, 4 insertions(+), 321 deletions(-)
diff --git
From: Lan Tianyu
There is no user of cm_sbs.c and CONFIG_ACPI_PROCFS_POWER. So remove
them. Prepare for removing /proc/acpi
Signed-off-by: Lan Tianyu
---
drivers/acpi/Kconfig | 17
drivers/acpi/Makefile | 1 -
drivers/acpi/cm_sbs.c | 105
From: Lan Tianyu
Alarm proc file provides the info and control of RTC-CMOS alarm and
RTC CMOS driver provides wakealarm sysfs attribute for the same
purpose. The alarm file isn't compiled into kernel when RTC CMOS
driver is selected. The driver is default to be selected for x86
platform. So
From: Lan Tianyu
The battery's proc directory isn't useded and remove it.
Signed-off-by: Lan Tianyu
---
drivers/acpi/battery.c | 328 +
1 file changed, 1 insertion(+), 327 deletions(-)
diff --git a/drivers/acpi/battery.c
From: Lan Tianyu
AC's proc directory is not used and so remove it. Prepare for removing
/proc/acpi directory.
Signed-off-by: Lan Tianyu
---
drivers/acpi/ac.c | 128 +-
1 file changed, 2 insertions(+), 126 deletions(-)
diff --git
On Thu, Oct 10, 2013 at 8:47 PM, Dan Murphy wrote:
>
> Is there a board that has 2 built in smsc devices?
I don't know, maybe there isn't, but driver should be generic enough, and
as I said it is a generic problem, and people are discussing it, so suggest
to read previous discussions first
This patchset is to remove AC/Battery directories and alarm file under
/proc/acpi
drivers/acpi/Kconfig | 17 --
drivers/acpi/Makefile| 1 -
drivers/acpi/ac.c| 128 +
drivers/acpi/battery.c
Hi Will,
Maybe I know your meaning ,
If it use spinlock to protected the shared data,
The bug will not happen, because spinlock will
Use DSB( ) to sync .
Unluckily, here, it use a special seqcount_t( ) (see get_counters( ) function)
To make sure there is no others using the old data,
Before
On Fri, 11 Oct 2013 10:39:35 +0900
Yoshihiro YUNOMAE wrote:
> Hi Steven,
>
> Would you review this patch set?
Yeah, I've been really busy lately and now I'm back to reviewing
patches. I should be able to get to it next week.
-- Steve
>
> Thanks,
> Yoshihiro YUNOMAE
>
--
To unsubscribe from
For atomic_clear_mask(), 'v->counter' is 'int', so it is better to use
'unsigned int' instead of 'unsigned long' for parameter 'mask' to make
atomic_clear_mask() itself consistency.
And atomic_[set/clear]_mask() are pairs, the modification can also let
them consistent with each other.
Although
On Thu, Oct 10, 2013 at 6:45 PM, Rafael J. Wysocki wrote:
>
> /* Register slots for ejectable funtions only. */
> - if (acpi_pci_check_ejectable(pbus, handle) ||
> is_dock_device(handle)) {
> + if ((acpi_pci_check_ejectable(pbus, handle) || is_dock_device(handle))
> +
From: Michael Davidson
The "gold" linker doesn't seem to put some additional per-cpu cases in
the right place. Add these to the per-cpu check. Without this, the kASLR
patch series fails to correctly apply relocations, and fails to boot.
Signed-off-by: Michael Davidson
Signed-off-by: Kees Cook
Hi Steven,
Would you review this patch set?
Thanks,
Yoshihiro YUNOMAE
(2013/09/13 11:06), Yoshihiro YUNOMAE wrote:
Hi Steven,
This is a v2 patch set for realizing a part of "Integrated trace" feature which
is a trace merging system for a virtualization environment. Currently, trace-cmd
does
The err variable is intended to receive the timer_create() return before
checking it
Signed-off-by: Felipe Pena
---
tools/testing/selftests/timers/posix_timers.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/timers/posix_timers.c
Hi.
The following reproducer causes auditd daemon hang up.
(But the hang up is released after the audit_backlog_wait_time passes.)
# auditctl -a exit,always -S all
# reboot
I reproduced the hangup on KVM, and then got a crash dump.
After I analyzed the dump, I found auditd daemon hung up in
On Friday, October 11, 2013 01:09:33 AM Rafael J. Wysocki wrote:
> On Thursday, October 10, 2013 02:37:15 PM Linus Torvalds wrote:
> > On Thu, Oct 10, 2013 at 2:35 PM, Rafael J. Wysocki
> > wrote:
> > >
> > > Well, I must have overlooked the original report. Is it available
> > > anywhere
> >
Add REGULATOR_LINEAR_RANGE macro and convert regulator drivers to use it.
Signed-off-by: Axel Lin
Cc: Yi Zhang
Cc: Chao Xie
Cc: Guennadi Liakhovetski
Cc: Laxman Dewangan
Cc: Eric Miao
Cc: Margarita Olaya
---
drivers/regulator/88pm800.c| 10 --
linear ranges means each range has linear voltage settings.
So we can calculate max_uV for each linear range in regulator core rather than
set the max_uV field in drivers.
Signed-off-by: Axel Lin
Cc: Yi Zhang
Cc: Chao Xie
Cc: Guennadi Liakhovetski
Cc: Laxman Dewangan
Cc: Eric Miao
Cc:
Dear Boaz,
On Thu, Oct 10, 2013 at 01:41:23PM -0700, Boaz Harrosh wrote:
> On 10/10/2013 02:02 AM, Fengguang Wu wrote:
> > Greetings,
> >
> > I got the below dmesg and the first bad commit is
> >
>
> Dear Wu
>
> This 20545536cd8ea949c61527b6395ec8c0d2c237b1 is from my tree at
>
Fix for a memory leak on tracing_data_get() function when returning NULL
explicitly
Signed-off-by: Felipe Pena
---
tools/perf/util/trace-event-info.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/trace-event-info.c
On 10/10/2013 10:23 PM, Will Deacon wrote:
> On Thu, Oct 10, 2013 at 12:03:52PM +0100, Chen Gang wrote:
>> On 10/10/2013 06:07 PM, Will Deacon wrote:
>>> On Thu, Oct 10, 2013 at 03:35:21AM +0100, Chen Gang wrote:
In current kernel wide source, for arm64, only s390 scsi drivers use
On Thu, Oct 10, 2013 at 06:49:30PM +0200, Toralf Förster wrote:
> On 10/10/2013 12:33 AM, Richard Weinberger wrote:
> > Am 09.10.2013 23:47, schrieb Jan Kara:
> >> On Wed 09-10-13 20:43:50, Richard Weinberger wrote:
> >>> CC'ing mm folks.
> >>> Please see below.
> >> Added Fenguang to CC since
On 10/10/2013 08:59 PM, Rafael J. Wysocki wrote:
> On Thursday, October 10, 2013 09:02:55 AM Aaron Lu wrote:
>> On 10/10/2013 08:29 AM, Rafael J. Wysocki wrote:
>>> On Tuesday, October 08, 2013 02:40:00 PM Aaron Lu wrote:
According to Matthew Garrett, "Windows 8 leaves backlight control up
On 10/10/2013 09:54 PM, zhangfei gao wrote:
On Wed, Oct 9, 2013 at 1:40 PM, Qiao Zhou wrote:
add multiple burst size support for 910-squ.
Signed-off-by: Qiao Zhou
---
drivers/dma/mmp_tdma.c | 25 -
1 files changed, 24 insertions(+), 1 deletions(-)
diff --git
On Thu, 2013-10-10 at 18:00 -0700, Linus Torvalds wrote:
> the first step is to realize you have a problem.
Says the guy that can only send patches to the list
as attachments not plain text because he uses gmail.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
add multiple burst size support for 910-squ.
Signed-off-by: Qiao Zhou
---
drivers/dma/mmp_tdma.c | 30 +-
1 files changed, 29 insertions(+), 1 deletions(-)
diff --git a/drivers/dma/mmp_tdma.c b/drivers/dma/mmp_tdma.c
index 38cb517..f6b9ec7 100644
---
v1: add multiple burst size support. remove previous fixed 32-byte setting.
v2: correct some missing definition.
Qiao Zhou (1):
dma: mmp_tdma: add multiple burst size support for 910-squ
drivers/dma/mmp_tdma.c | 25 -
1 files changed, 24 insertions(+), 1 deletions(-)
On Thu, Oct 10, 2013 at 6:06 PM, Joe Perches wrote:
> On Thu, 2013-10-10 at 18:00 -0700, Linus Torvalds wrote:
>> the first step is to realize you have a problem.
>
> Says the guy that can only send patches to the list
> as attachments not plain text because he uses gmail.
Yeah. I fire up pine
On Thu, Oct 10, 2013 at 5:19 PM, Steven Rostedt wrote:
>
> This may have been my fault, as I cut and pasted Rafael's email from
> the git log, and did not add the quotes myself.
Well, it is your fault, but only because you use a buggy mailer from hell.
> Perhaps claws should force names with
* Ralf Baechle [2013-10-09 14:08:09]:
> declares arch_uprobe_skip_sstep() as a weak function.
> But as there is no definition of generic version so when trying to build
> uprobes for an architecture that doesn't yet have a arch_uprobe_skip_sstep()
> implementation, the vmlinux will try to call
Add a 'trigger' file for each trace event, enabling 'trace event
triggers' to be set for trace events.
'trace event triggers' are patterned after the existing 'ftrace
function triggers' implementation except that triggers are written to
per-event 'trigger' files instead of to a single file such
Hi,
Sorry for the delay on this - I had other things come up and am just
now getting back to it..
This is v10 of the trace event triggers patchset. This version
addresses the comments and feedback from Steve Rostedt on v9. It also
adds a couple new but trivial patches for things I noticed
The original SOFT_DISABLE patches didn't add support for soft disable
of syscall events; this adds it and paves the way for future patches
allowing triggers to be added to syscall events, since triggers are
built on top of SOFT_DISABLE.
Add an array of ftrace_event_file pointers indexed by
Add 'stacktrace' event_command. stacktrace event triggers are added
by the user via this command in a similar way and using practically
the same syntax as the analogous 'stacktrace' ftrace function command,
but instead of writing to the set_ftrace_filter file, the stacktrace
event trigger is
Add 'snapshot' event_command. snapshot event triggers are added by
the user via this command in a similar way and using practically the
same syntax as the analogous 'snapshot' ftrace function command, but
instead of writing to the set_ftrace_filter file, the snapshot event
trigger is written to
Add 'enable_event' and 'disable_event' event_command commands.
enable_event and disable_event event triggers are added by the user
via these commands in a similar way and using practically the same
syntax as the analagous 'enable_event' and 'disable_event' ftrace
function commands, but instead of
Add 'traceon' and 'traceoff' event_command commands. traceon and
traceoff event triggers are added by the user via these commands in a
similar way and using practically the same syntax as the analagous
'traceon' and 'traceoff' ftrace function commands, but instead of
writing to the
The trace event filters are still tied to event calls rather than
event files, which means you don't get what you'd expect when using
filters in the multibuffer case:
Before:
# echo 'count > 65536' >
/sys/kernel/debug/tracing/events/syscalls/sys_enter_read/filter
# cat
register/unregister_ftrace_command() are only ever called from __init
functions, so can themselves be made __init.
Also make register_snapshot_cmd() __init for the same reason.
Signed-off-by: Tom Zanussi
---
include/linux/ftrace.h | 4 ++--
kernel/trace/ftrace.c | 12 ++--
If CONFIG_STACKTRACE is turned off, trace_dump_stack() isn't defined,
resulting in an 'undefined reference' error - define a stub to remedy
that.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
Add a generic event_command.set_trigger_filter() op implementation and
have the current set of trigger commands use it - this essentially
gives them all support for filters.
Syntactically, filters are supported by adding 'if ' just
after the command, in which case only events matching the filter
Provide a basic overview of trace event triggers and document the
available trigger commands, along with a few simple examples.
Signed-off-by: Tom Zanussi
---
Documentation/trace/events.txt | 207 +
1 file changed, 207 insertions(+)
diff --git
The names of the functions are tracing_snapshot_*, not
trace_snapshot_* - fix up the kerneldoc to avoid confusion.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index
Now squashfs have used for only one stream buffer for decompression
so it hurts concurrent read performance so this patch supprts
multiple decompressor to enhance performance concurrent I/O.
Four 1G file dd read on KVM machine which has 2 CPU and 4G memory.
dd if=test/test1.dat of=/dev/null &
dd
1 - 100 of 1604 matches
Mail list logo
