On Friday 26 October 2012 05:40 PM, Felipe Balbi wrote:
> On Fri, Oct 26, 2012 at 05:33:16PM +0530, vineet.gup...@synopsys.com wrote:
>> +/*
>> + * Release the memory region(s) being used by 'port'.
>> + */
>> +static void arc_serial_release_port(struct uart_port *port)
>> +{
>> +}
>> +
>> +/*
>> +
On Fri, 26 Oct 2012 15:09:05 +0800, Hongbo Zhang wrote:
> From: "hongbo.zhang"
>
> Problem of using this list is that the cpufreq_get_max_state callback will be
> called when register cooling device by thermal_cooling_device_register, but
> this list isn't ready at this moment. What's more, there
Hello Sir/Mam:
Happy to contact you !
We would like to introudce our company.Our company is a large scale
pertrochemical enterprise with synthetic rubber as the main product. We
could supply SBR 1502 and 1712. It is manufactured by SINOPEC YANGZI.
The following is the SBR quotation :
* SB
On Sat, 2012-10-27 at 09:23 +0800, Ming Lei wrote:
> This patch introduces one module parameter of 'path' in firmware_class
> to support customizing firmware image search path, so that people can
> use its own firmware path if the default built-in paths can't meet their
> demand[1], and the typical
Once I realized that the original document have been updated, I will
update that translation immediately.
2012/10/25 Catalin Marinas :
> 2012/10/24 Tekkaman Ninja :
>> This is a Chinese translated version of
>> Documentation/arm64/memory.txt
>>
>> Signed-off-by: Fu Wei
>
> As long as you maintain
Hi, Catalin
I have a question about the original document.
what is the exact meaning about the "memory" in
"ffc0 256GB memory"
Can I treat it as "kernel logical address space" ? Or maybe It can be
modified to “kernel” ？
It's relevant to my Chines
On Fri, Oct 26, 2012 at 09:54:53PM -0400, Vladislav Bolkhovitin wrote:
> What different in our positions is that you are considering storage
> as something you can connect to your desktop, while in my view
> storage is something, which stores data and serves them the best
> possible way with the be
hi, Rob,
Thanks for your suggestion, and It can be decided by the maintainer.
My suggestion is that non-english translations in the kernel source
can help the developer who use that language as mother language join
the development of Linux kernel.
They can get info from kernel source, it's more c
We need to store thread info to these exception thread info like something
we already did for PPC32.
Signed-off-by: Tiejun Chen
---
This patch is followed on my three patches I send recently:
[PATCH 1/3] powerpc/book3e: load critical/machine/debug exception stack
[PATCH 2/3] powerpc/book3e: supp
OK, I will try my best to keep it up to date.
I hope that Catalin Marinas can Cc the patch to me, when the
Documentation/arm64 has got a patch.
Then I can translate it to Chinese immediately.
Now the info about AArch64 is limited. so maybe it have some translation errors.
When I realized that er
On 10/26/2012 05:12 PM, Alan Cox wrote:
On Fri, 26 Oct 2012 14:45:02 -0400
Rik van Riel wrote:
Intel has an architectural guarantee that the TLB entry causing
a page fault gets invalidated automatically. This means
we should be able to drop the local TLB invalidation.
Because of the way other
On 10/26/2012 06:37 PM, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
>> [...]
>>
>> So a sane series would introduce maybe two functions:
>> cpu_load() and task_load() and use those where we now use
>> rq->load.weight and p->se.load.weight for load balancing
>> purposes. Implement these f
On 10/26/2012 05:59 PM, Peter Zijlstra wrote:
> On Thu, 2012-10-25 at 23:42 +0530, Preeti U Murthy wrote:
> firstly, cfs_rq is the wrong place for a per-cpu load measure, secondly
> why add another load field instead of fixing the one we have?
Hmm..,rq->load.weight is the place.
>> So why didnt
On Fri, Oct 26, 2012 at 07:31:07PM +0100, Al Viro wrote:
> The situation got much better by now. More than a half of
> architectures are done - alpha arm arm64 c6x hexagon ia64 m68k mips openrisc
> parisc sparc tile um unicore32 and x86.
>
> Two more avait ACKs from maintainers - powe
Theodore Ts'o wrote:
The problem is this code isn't done yet, and journal_checksum is
really not ready for prime time. When it is ready, my plan is to wire
it up so it is enabled by default; at the moment, it was intended for
developer experimentation only. As I said, it's my fault for n
On Fri, Oct 26, 2012 at 7:39 PM, Cyberman Wu wrote:
> On Sat, Oct 27, 2012 at 12:28 AM, Bjorn Helgaas wrote:
>> On Fri, Oct 26, 2012 at 8:08 AM, Chris Metcalf wrote:
>>
>>> Cyberman: it seems like your bias hack is working for you. But, as Bjorn
>>> says, this sounds like a driver bug. What ha
Calling INIT_WORK in blinkm_led_common_set() means we init a workqueue every
time when brightness_set callback is called.
Move INIT_WORK to blinkm_probe() so we only need to init the workqueue once.
This patch also refactors the data structure of blinkm_data and blinkm_work.
Embedded struct blinkm
Theodore Ts'o, on 10/25/2012 09:50 AM wrote:
Yeah I don't buy that. One, flash is still too expensive. Two,
the capital costs to build enough Silicon foundries to replace the
current production volume of HDD's is way too expensive for any
company to afford (the cloud providers are buying
Theodore Ts'o, on 10/25/2012 01:14 AM wrote:
On Tue, Oct 23, 2012 at 03:53:11PM -0400, Vladislav Bolkhovitin wrote:
Yes, SCSI has full support for ordered/simple commands designed
exactly for that task: to have steady flow of commands even in case
when some of them are ordered.
SCSI does,
Nico Williams, on 10/24/2012 05:17 PM wrote:
Yes, SCSI has full support for ordered/simple commands designed exactly for
that task: [...]
[...]
But historically for some reason Linux storage developers were stuck with
"barriers" concept, which is obviously not the same as ORDERED commands,
hen
This patch updates pwm-vt8500.c to support devicetree probing and
make use of the common clock subsystem.
A binding document describing the PWM controller found on
arch-vt8500 is also included.
Signed-off-by: Tony Prisk
---
v4:
return err from clk_enable rather than -EBUSY
v5:
replace IS_ERR_OR_
On Sat, Oct 27, 2012 at 12:28 AM, Bjorn Helgaas wrote:
> On Fri, Oct 26, 2012 at 8:08 AM, Chris Metcalf wrote:
>
>> Cyberman: it seems like your bias hack is working for you. But, as Bjorn
>> says, this sounds like a driver bug. What happens if you just revert your
>> changes, but then in mvsas
This patch introduces one module parameter of 'path' in firmware_class
to support customizing firmware image search path, so that people can
use its own firmware path if the default built-in paths can't meet their
demand[1], and the typical usage is passing the below from kernel command
parameter w
On Fri, Oct 26, 2012 at 11:37:20AM +0900, Minchan Kim wrote:
[...]
> > > Of course, it's very flexible and potential to add new VM knob easily but
> > > the thing we is about to use now is only VMEVENT_ATTR_PRESSURE.
> > > Is there any other use cases for swap or free? or potential user?
> >
> > N
Hi folks,
This is a just friendly heads up that target-pending has been updated to
latest v3.7-rc2 mainline code. As usual, the for-next* branches have
been recreated from master and include in-flight target development
patches destined for upstream during the v3.8 merge window.
Also, a heads up
On Fri, Oct 26, 2012 at 10:19:21PM +0100, Nix wrote:
> > prevent unwary civilians from coming across the feature and saying,
> > "oooh, shiny!" and turning it on. :-(
>
> Or having it turned on by default either, which seems to be the case
> now.
Huh? It's not turned on by default. If you moun
I've bcc'ed sta...@vger.kernel.org, LKML, and greg-kh, since I suspect
they aren't interested in all of these details... we'll keep this on
linux-ext4 for sanity's sake.
On Sat, Oct 27, 2012 at 01:15:42AM +0200, Martin wrote:
>
> sorry for the repetition, but Theodore Ts'o asked me to re-post thi
Chris Friesen wrote:
On 10/26/2012 01:43 PM, Wallak wrote:
Chris Friesen wrote:
On 10/25/2012 04:49 PM, Wallak wrote:
I've a very annoying behavior with the linux-3.6.x kernels release,
and
a monolithic configuration. The USB 2.0 drives are mapped first with
/dev/sda, /dev/sdb... devices, and
On Fri, Oct 26, 2012 at 11:07:31AM +0100, Dimitris Papastamos wrote:
> On Thu, Oct 25, 2012 at 11:48:33AM -0700, Greg Kroah-Hartman wrote:
> > On Tue, Oct 23, 2012 at 01:52:55PM +0100, Dimitris Papastamos wrote:
> > > This patch provides the aforementioned procfs file that lists
> > > the default f
On Fri, Oct 26, 2012 at 01:46:38PM -0500, Seth Jennings wrote:
> On 10/26/2012 11:13 AM, Greg Kroah-Hartman wrote:
> > On Fri, Oct 26, 2012 at 10:49:01AM -0500, Seth Jennings wrote:
> >> debugfs currently lacks the ability to create attributes
> >> that set/get atomic_t values.
> >>
> >> This patch
On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote:
> Hi Guys,
>
> I am debugging a reported kmemleak involving a sierra wireless MC8705
> connected
> through isp1763 on powerpc linux-3.0.22
Does this also happen on 3.6.3?
thanks,
greg k-h
--
To unsubscribe from this list: send
On 10/26/2012 11:10 PM, Theodore Ts'o wrote:
This looks very different. The symptoms are quite different, and it's
most likely that an unclean shutdown is involved. In your case,
you're doing clean shutdowns, with some suspend/resume cycles thrown
in.
No no, the case I reported was triggered
memmap_init_zone() loops through every Page Frame Number (pfn),
including pfn values that are within the gaps between existing
memory sections. The unneeded looping will become a boot
performance issue when machines configure larger memory ranges
that will contain larger and more numerous gaps.
T
On Sat, Oct 27, 2012 at 1:08 AM, Thomas Gleixner wrote:
>
> Looks like CONFIG_NUMA=y exposes explosions. I just noticed that none
> of the machines which are in my basic set of test systems have that
> enabled.
>
> /me goes to do some homework
Try
https://github.com/torvalds/linux/commit/6b187d0
> Well, we could set a new attribute bit on the file which indicates
> that the file has been corrupted, and this could cause any attempts to
> open the file to return some error until the bit has been cleared.
That sounds a lot better than renaming/moving the file.
> This would persist across re
On 10/26/2012 02:51 PM, Shuah Khan wrote:
On 10/26/2012 09:01 AM, Shuah Khan wrote:
Add support for debug_dma_mapping_error() call to avoid warning from
debug_dma_unmap() interface when it checks for mapping error checked
status. Without this patch, device driver failed to check map error
warni
From: Thomas Gleixner
rcu_read_unlock_special() checks in_serving_softirq() and leaves early
when true. On RT this is obviously wrong as softirq processing context
can be preempted and therefor such a task can be on the gp_tasks
list. Leaving early here will leave the task on the list and therefo
From: Steven Rostedt
---
localversion-rt |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index b2111a2..792cb5f 100644
--- a/localversion-rt
+++ b/localversion-rt
@@ -1 +1 @@
--rt24
+-rt25-rc1
--
1.7.10.4
--
To unsubscribe from this lis
Dear RT Folks,
This is the RT stable review cycle of patch 3.4.15-rt25-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release cand
fixed below checkpatch warnings.
-WARNING: printk() should include KERN_ facility level
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/comedi/drivers/usbduxfast.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/comedi/drivers/usbduxfast.c
b/dri
The patch works around two UART interrupt bugs when the serial console is
flooded with inputs:
1. syslog shows "serial8250: too much works for irq"
2. serial console stops responding to key stroke
serial8250_handle_irq() checks UART_IIR_RDI before reading receive fifo
and clears bogus interrupt U
Hi Guys,
I am debugging a reported kmemleak involving a sierra wireless MC8705 connected
through isp1763 on powerpc linux-3.0.22
We are still isolating the exact trigger, but this is a pretty good one so far
send "at!reset" to the modem control tty, wait until it finishes rebooting
then try to
On Fri, 26 Oct 2012, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.6.3-rt7 release.
>
> Changes since 3.6.3-rt6:
>
>* Enable SLUB for RT
>
> Last time I looked at SLUB for RT (some years ago) it was just
> way more painful than dealing with SLAB, but C
On Fri, Oct 26, 2012 at 7:19 AM, Alan Cox wrote:
> So we only need to check this in serial8250_handle_irq when IIR indicates
> a data timeout interrupt ?
>
> Can we do
>
> if ((iir & 0x0F) == 0x0C) {
> /* Expensive RDI check */
> }
>
>
>
> Alan
Checking data timeo
Systems running with Yama enabled expect restrictions on various
potentially dangerous operations that could create backward-compaibility
issues with rare userspace corner-cases. Since 561ec64ae67e ("VFS:
don't do protected {sym,hard}links by default") has disabled VFS link
restrictions by default,
On Fri, 26 Oct 2012, Peter LaDow wrote:
> On Fri, Oct 26, 2012 at 2:05 PM, Eric Dumazet wrote:
> If this were safe, we wouldn't be seeing this lockup and your patch
> wouldn't be needed. So it seems that your patch doesn't really
> address the issue that we are not "sure a thread cannot be interr
On Fri, 2012-10-26 at 13:07 -0700, David Daney wrote:
> On 10/26/2012 10:06 AM, Shuah Khan wrote:
> > On Fri, 2012-10-26 at 09:45 -0700, David Daney wrote:
> >> On 10/26/2012 09:01 AM, Shuah Khan wrote:
> >>> Add support for debug_dma_mapping_error() call to avoid warning from
> >>> debug_dma_unmap
On 10/02/2012 01:17 PM, Dan Magenheimer wrote:
> If so, and move forward? What do you see as next steps?
I've been reviewing the changes between zcache and zcache2 and getting
a feel for the scope and direction of those changes.
- Getting the community engaged to review zcache1 at ~2300SLOC was
On Fri, 2012-10-26 at 13:49 -0700, Linus Torvalds wrote:
> On Fri, Oct 26, 2012 at 5:29 AM, Vinod Koul
> wrote:
> >
> > git://git.infradead.org/users/vkoul/slave-dma.git fixes
>
> git.infradead.org is sick, and is apparently not accepting
> connections...
>
> Can you check whether git-daemon i
[Issue]
A format of variable name has been updated to type, id, count and ctime
to support holding multiple logs.
Format of current variable name
dump-type0-1-2-12345678
type:0
id:1
count:2
ctime:12345678
On the other hand, if an old variable name before being updated
remains, users
[Issue]
A format of variable name has been updated to type, id, count and ctime
to support holding multiple logs.
Format of current variable name
dump-type0-1-2-12345678
type:0
id:1
count:2
ctime:12345678
On the other hand, if an old variable name before being updated
remains, users
[Issue]
Currently, a variable name, which identifies each entry, consists of type, id
and ctime.
But if multiple events happens in a short time, a second/third event may fail
to log because
efi_pstore can't distinguish each event with current variable name.
[Solution]
A reasonable way to ident
[Issue]
Currently, a variable name, which is used to identify each log entry, consists
of type,
id and ctime. But an erase callback does not use ctime.
If efi_pstore supported just one log, type and id were enough.
However, in case of supporting multiple logs, it doesn't work because
it can't di
On Fri, Oct 26, 2012 at 1:27 PM, Linus Torvalds
wrote:
> On Fri, Oct 26, 2012 at 1:23 PM, Kees Cook wrote:
>>
>> I'd like it to be the exception to turn it _off_, rather than the
>> exception to turn it on.
>
> Kees, you don't seem to understand.
>
> Breaking applications is unacceptable. End of
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and writes panic messages to NVRAM.
3. system reboots.
4. kernel panics again before a user checks the
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and writes panic messages to NVRAM.
3. system reboots.
4. kernel panics again before a user check
On Fri, 2012-10-26 at 15:10 -0400, David Miller wrote:
> From: David Miller
> Date: Fri, 26 Oct 2012 15:01:53 -0400 (EDT)
>
> > From: Shuah Khan
> > Date: Fri, 26 Oct 2012 10:13:09 -0600
> >
> >> Add support for debug_dma_mapping_error() call to avoid warning from
> >> debug_dma_unmap() interfa
[Issue]
As discussed in a thread below, Running out of space in EFI isn't a well-tested
scenario.
And we wouldn't expect all firmware to handle it gracefully.
http://marc.info/?l=linux-kernel&m=134305325801789&w=2
On the other hand, current efi_pstore doesn't check a remaining space of
storage
Changelog
v2 -> v3
- Create patches 6/7 and 7/7 to work with an existing format of variable name
v1 -> v2
- Separate into 5 patches in accordance with Mike's comment
- Erase an extra line of comment in patch 1/5
[Issue]
Currently, efi_pstore driver simply overwrites existing panic
This is what we usually expect at this stage of the game, lots of
little things, mostly in drivers. With the occaisional "oops didn't
mean to do that" kind of regressions in the core code.
1) Uninitialized data in __ip_vs_get_timeouts(), from Arnd Bergmann
2) Reject invalid ACK sequences in Fas
Hello,
On Fri, Oct 26, 2012 at 11:29:56PM +0200, Rafael J. Wysocki wrote:
> Actually, what tree is it supposed to apply to?
>
> The change in kernel/cgroup_freezer.c doesn't look like anything in
> the current Linus' tree to me.
Ooh, right. This depends on the earlier cgroup_freezer changes.
So
On Friday, October 26, 2012 11:14:17 PM Rafael J. Wysocki wrote:
> On Friday, October 26, 2012 08:01:49 PM Oleg Nesterov wrote:
> > On 10/26, Tejun Heo wrote:
> > >
> > > Acked-by: Tejun Heo
> >
> > Thanks!
> >
> > > Rafael, sorry that this one doesn't have pm cc'd
> >
> > Ah, sorry Rafael. Ye
On Fri, Oct 26, 2012 at 2:05 PM, Eric Dumazet wrote:
> Do you know what is per cpu data in linux kernel ?
I sorta did. But since your response, I did more reading, and now I
see what you mean. But I don't think this is a per cpu issue. More
below.
> Because its not needed. Really I dont know
On 10/26/2012 01:23 PM, Kees Cook wrote:
>
> Every distro will ship with this enabled (except perhaps Damn
> Vulnerable Linux), so why make it harder?
>
So please remind me why can't it be on by default in code.
And the normal sysctl to turn it off for these who want to
experiment with "filesyst
On 26 Oct 2012, Theodore Ts'o uttered the following:
> The plan is that eventually, we will have checksums on a
> per-journalled block basis, instead of a per-commit basis, and when we
> get a failed checksum, we skip the replay of that block,
But not of everything it implies, since that's quite
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
pm+acpi-for-3.7-rc3
to receive power management and ACPI fixes for v3.7-rc3 with top-most commit
879dca019dc43a1622edca3e7dde644b14b5acc5
ACPI: missing break
on top of commit
> This isn't the first time that journal_checksum has proven problematic.
> It's a shame that we're stuck between two error-inducing stools here...
The problem is that it currently bails out be aborting the entire
journal replay, and the file system will get left in a mess when it
does that. It's
On Friday 26 October 2012, Chris Brand wrote:
> > @@ -124,6 +156,12 @@ static int __devinit pwm_probe(struct
> > platform_device *pdev)
> > chip->chip.base = -1;
> > chip->chip.npwm = VT8500_NR_PWMS;
> >
> > + chip->clk = devm_clk_get(&pdev->dev, NULL);
> > + if (IS_ERR_OR_NULL
This looks very different. The symptoms are quite different, and it's
most likely that an unclean shutdown is involved. In your case,
you're doing clean shutdowns, with some suspend/resume cycles thrown
in. Also, kernel version 3.5.5 doesn't have the commits that were
added between 3.6.1 and 3.6
On Friday, October 26, 2012 08:01:49 PM Oleg Nesterov wrote:
> On 10/26, Tejun Heo wrote:
> >
> > Acked-by: Tejun Heo
>
> Thanks!
>
> > Rafael, sorry that this one doesn't have pm cc'd
>
> Ah, sorry Rafael. Yes, I have read you email, and I was going to
> add linux-pm but forgot.
>
> > but ca
On Fri, 26 Oct 2012 14:45:02 -0400
Rik van Riel wrote:
> Intel has an architectural guarantee that the TLB entry causing
> a page fault gets invalidated automatically. This means
> we should be able to drop the local TLB invalidation.
>
> Because of the way other areas of the page fault code wor
On Fri, 2012-10-26 at 11:51 -0700, Peter LaDow wrote:
> (I've added netfilter and linux-rt-users to try to pull in more help).
>
> On Fri, Oct 26, 2012 at 9:48 AM, Eric Dumazet wrote:
> > Upstream kernel is fine, there is no race, as long as :
> >
> > local_bh_disable() disables BH and preemption
On 26 Oct 2012, Theodore Ts'o stated:
> On Fri, Oct 26, 2012 at 09:37:08PM +0100, Nix wrote:
>>
>> I can reproduce this on a small filesystem and stick the image somewhere
>> if that would be of any use to anyone. (If I'm very lucky, merely making
>> this offer will make the problem go away. :} )
On 10/26/2012 01:05 AM, Daniel Vetter wrote:
On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
wrote:
No worries, it is another ILK hang similar to the ones reported earlier
- it just seems the ring stops advancing. Hopefully it is a missing w/a
from http://cgit.freedesktop.org/~danvet/drm/lo
On Fri, Oct 26, 2012 at 09:37:08PM +0100, Nix wrote:
>
> I can reproduce this on a small filesystem and stick the image somewhere
> if that would be of any use to anyone. (If I'm very lucky, merely making
> this offer will make the problem go away. :} )
I'm not sure the image is going to be that
On Thursday 25 October 2012, Nicolas Ferre wrote:
> ARM: at91: fix external interrupts in non-DT case
This patch now leads to build errors with at91x40_defconfig,
which I've fixed up by applying the patch below on top.
Please yell if this is not the right fix.
Arnd
commit 3a8852af
On Fri, 26 Oct 2012, Peter LaDow wrote:
> (I've added netfilter and linux-rt-users to try to pull in more help).
>
> On Fri, Oct 26, 2012 at 9:48 AM, Eric Dumazet wrote:
> > Upstream kernel is fine, there is no race, as long as :
> >
> > local_bh_disable() disables BH and preemption.
>
> Looking
Hi Tony,
> @@ -124,6 +156,12 @@ static int __devinit pwm_probe(struct
> platform_device *pdev)
> chip->chip.base = -1;
> chip->chip.npwm = VT8500_NR_PWMS;
>
> + chip->clk = devm_clk_get(&pdev->dev, NULL);
> + if (IS_ERR_OR_NULL(chip->clk)) {
> + dev_err(&pdev->dev,
On Fri, Oct 26, 2012 at 5:29 AM, Vinod Koul wrote:
>
> git://git.infradead.org/users/vkoul/slave-dma.git fixes
git.infradead.org is sick, and is apparently not accepting connections...
Can you check whether git-daemon is actually running there? The
machine is pinging ok.
Linus
--
To
On 26 Oct 2012, Martin said:
> On 10/26/2012 10:24 PM, Nix wrote:
>> On 26 Oct 2012, Martin spake thusly:
>>> Computer is booted again in order to copy a few files to memory stick.
>>> Unbeknownst to me, the following entries are logged in the
>>> system log:
>>>
>>> Oct 15 20:00:16 harold kernel
On 10/26/2012 10:24 PM, Nix wrote:
On 26 Oct 2012, Martin spake thusly:
[...]
I have studied my corruption problem more closely and can give you a
description of what happened below. Would you say this may be the same
bug?
No. You want to keep up with the thread. Ted's first educated guess is
From: Andi Kleen
Make perf report -j aware of the new intx,notx,abort branch qualifiers.
v2: ABORT -> ABORTTX
Signed-off-by: Andi Kleen
---
tools/perf/Documentation/perf-record.txt |3 +++
tools/perf/builtin-record.c |3 +++
2 files changed, 6 insertions(+), 0 deletions(-)
From: Andi Kleen
Haswell has two additional LBR from flags for TSX: intx and abort, implemented
as a new v4 version of the LBR format.
Handle those in and adjust the sign extension code to still correctly extend.
The flags are exported similarly in the LBR record to the existing misprediction
fl
From: Andi Kleen
So that the browser still shows the abort label
Signed-off-by: Andi Kleen
---
tools/perf/util/annotate.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
index f0a9103..a34a1ae 100644
--- a/tools/
From: Andi Kleen
In the PEBS handler report the transaction flags using the new
generic transaction flags facility. Most of them come from
the "tsx_tuning" field in PEBSv2, but the abort code is derived
from the RAX register reported in the PEBS record.
Signed-off-by: Andi Kleen
---
arch/x86/k
From: Andi Kleen
The --sort documentation for top and report was hopelessly out-of-date
Instead of having two more places that would need to be updated,
just point to --help.
Signed-off-by: Andi Kleen
---
tools/perf/Documentation/perf-report.txt |2 +-
tools/perf/Documentation/perf-top.txt
From: Andi Kleen
Extend the perf branch sorting code to support sorting by intx
or abort qualifiers. Also print out those qualifiers.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-report.c |3 +-
tools/perf/builtin-top.c|4 ++-
tools/perf/perf.h |4 ++-
tools/perf/
On 26 Oct 2012, Eric Sandeen outgrape:
> On 10/23/12 3:57 PM, Nix wrote:
>> The only unusual thing about the filesystems on this machine are that
>> they have hardware RAID-5 (using the Areca driver), so I'm mounting with
>> 'nobarrier': the full set of options for all my ext4 filesystems are:
>>
From: Andi Kleen
This is not arch perfmon, but older CPUs will just ignore it. This makes
it possible to do at least some TSX measurements from a KVM guest
Cc: a...@redhat.com
Cc: g...@redhat.com
v2: Various fixes to address review feedback
v3: Ignore the bits when no CPUID. No #GP. Force raw ev
From: Andi Kleen
I had some problems with spurious PMIs, so print the PMU state
on a spurious one. This will not interact well with other NMI users.
Disabled by default, has to be explicitely enabled through sysfs.
Optional, but useful for debugging.
v2: Move to /sys/devices/cpu
v3: Print in mo
From: Andi Kleen
Recent Intel CPUs have a new alternative MSR range for perfctrs that allows
writing the full counter width. Enable this range if the hardware reports it
using a new capability bit. This lowers overhead of perf stat slightly because
it has to do less interrupts to accumulate the c
From: Andi Kleen
Add support to perf stat to print the basic transactional execution statistics:
Total cycles, Cycles in Transaction, Cycles in aborted transsactions
using the intx and intx_checkpoint qualifiers.
Transaction Starts and Elision Starts, to compute the average transaction
length.
From: Andi Kleen
Add a precise qualifier, like cpu/event=0x3c,precise=1/
This is needed so that the kernel can request enabling PEBS
for TSX events. The parser bails out on any sysfs parse errors,
so this is needed in any case to handle any event on the TSX
perf kernel.
Signed-off-by: Andi Klee
From: Andi Kleen
The callers of parse_events usually have their own error handling.
Move the fprintf for a bad event to parse_events_options, which
is the only one who should need it.
Signed-off-by: Andi Kleen
---
tools/perf/util/parse-events.c | 10 +++---
1 files changed, 7 insertions(
From: Andi Kleen
Add a generic qualifier for transaction events, as a new sample
type that returns a flag word. This is particularly useful
for qualifying aborts: to distinguish aborts which happen
due to asynchronous events (like conflicts caused by another
CPU) versus instructions that lead to
From: Andi Kleen
Add infrastructure to generate event aliases in /sys/devices/cpu/events/
And use this to set up user friendly aliases for the common TSX events.
TSX tuning relies heavily on the PMU, so it's important to be user friendly.
This replaces the generic transaction events in an earli
On 10/23/12 3:57 PM, Nix wrote:
> [Bruce, Trond, I fear it may be hard for me to continue chasing this NFS
> lockd crash as long as ext4 on 3.6.3 is hosing my filesystems like
> this. Apologies.]
> The only unusual thing about the filesystems on this machine are that
> they have hardware RAID-
From: Andi Kleen
Add the glue in the user tools to record transaction flags with
--transaction (-T was already taken) and dump them.
Followon patches will use them.
Signed-off-by: Andi Kleen
---
tools/perf/Documentation/perf-record.txt |5 -
tools/perf/builtin-record.c |
From: Andi Kleen
With checkpointed counters there can be a situation where the counter
is overflowing, aborts the transaction, is set back to a non overflowing
checkpoint, causes interupt. The interrupt doesn't see the overflow
because it has been checkpointed. This is then a spurious PMI, typic
From: Andi Kleen
When a weighted sample is requested, first try to report the TSX abort cost
on Haswell. If that is not available report the memory latency. This
allows profiling both by abort cost and by memory latencies.
Memory latencies requires enabling a different PEBS mode (LL).
When both
1 - 100 of 600 matches
Mail list logo
