Hi Jaegeuk,
On Wed, Feb 25, 2015 at 10:35:23AM -0800, Jaegeuk Kim wrote:
>Hi Wanpeng,
>
>On Wed, Feb 25, 2015 at 12:53:37PM +0800, Wanpeng Li wrote:
>> recover_orphan_inodes is used to recover orphan inodes, the meta pages
>> which readahead should be orphan_blkaddr - start_blk instead of
>>
Michael Ellerman writes:
> Anton has a busy ppc64le KVM box where guests sometimes hit the infamous
> "kernel BUG at kernel/smpboot.c:134!" issue during boot:
>
> BUG_ON(td->cpu != smp_processor_id());
>
> Basically a per CPU hotplug thread scheduled on the wrong CPU. The oops
> output
On Wednesday, February 25, 2015 02:39:17 PM Lorenzo Pieralisi wrote:
> On Wed, Feb 25, 2015 at 02:13:23PM +, Daniel Lezcano wrote:
> > On 02/24/2015 06:58 PM, Lorenzo Pieralisi wrote:
> > > On return from cpuidle_enter_freeze() irqs are re-enabled by the function
> > > caller (ie
On Wed, Jan 21, 2015 at 08:29:55AM +0800, Yijing Wang wrote:
> v1->v2:
> Split pci_host_bridge_list into a new patch, remove .phb_probe_mode
> and rework powerpc .phb_of_scan_bus() for simpilicty suggested by
> Arnd. Refresh some patch description log, and add a new patch to fix
On Wed, Feb 25, 2015 at 01:00:16AM +0100, Denys Vlasenko wrote:
> After TEST insn, JE actually performs "jump if zero",
> let's use JZ mnemonic instead.
>
> No code changes, but less confusion.
>
> Signed-off-by: Denys Vlasenko
> CC: Linus Torvalds
> CC: Steven Rostedt
> CC: Ingo Molnar
>
On Wed, Feb 25, 2015 at 02:32:07PM -0800, Stephen Boyd wrote:
> The ahbix clock can never be turned off. To switch the rates we
> need to switch the mux off the M/N counter to an always on source
> (XO), reprogram the M/N counter to get the rate we want and
> finally switch back to the M/N
On Wed, Feb 25, 2015 at 12:18:14PM -0800, Bjorn Helgaas wrote:
> Why are we worrying about byte order here at all? I'd think we could
> just print t->dw0 directly with %08x.
Right, my only concern is since this is user-facing, someone/something
might depend on its format/byte order. But since no
From: Guenter Roeck
Date: Tue, 24 Feb 2015 23:02:02 -0800
> To avoid race conditions when using the ds->ports[] array,
> we need to check if the accessed port has been initialized.
> Introduce and use helper function dsa_is_port_initialized
> for that purpose and use it where needed.
>
>
Gregory,
I instantiated both configurations and verified I get essentially the
same temperature from both, with the original register having a
slightly larger spread. I didn't reproduce any outliers in this run,
but I'll keep it running for a while to see if any occur.
I'm running this to gather
2015-02-25, 13:59:06 -0800, Andy Lutomirski wrote:
> On Wed, Feb 25, 2015 at 1:28 PM, Denys Vlasenko wrote:
> > On 02/25/2015 09:10 PM, Andy Lutomirski wrote:
> >> On Wed, Feb 25, 2015 at 11:59 AM, Andrey Wagin wrote:
> >>> 2015-02-25 21:42 GMT+03:00 Denys Vlasenko :
> On 02/25/2015 01:37
On 02/25/2015 02:26 PM, Radim Krčmář wrote:
> 2015-02-24 15:25-0600, Joel Schopp:
- clr_cr_intercept(svm, INTERCEPT_CR0_WRITE);
} else {
set_cr_intercept(svm, INTERCEPT_CR0_READ);
>>> (There is no point in checking fpu_active if cr0s are equal.)
>>>
-
I've hosted my timekeeping tests on github for the last few years:
https://github.com/johnstultz-work/timetests
but I suspect not too many folks have actually used them.
I've been meaning to get them reworked and submitted into the
selftest infrastructure, but haven't had much time until
On Wednesday, February 25, 2015 03:01:08 PM Scot Doyle wrote:
> On Wed, 25 Feb 2015, Zheng, Lv wrote:
> ...
> > > I was using "+"/"#"/"*" to filter different EC log entries
> > > which makes debugging easier.
> > > And, if we changed this from pr_info into pr_debug, then we will have
The posix_timers.c test has a loop that tries to keep it in
kernel space, repeatedly calling brk(). Since its noise, and
a failure won't change what the test would do, add a unused
value to quiet the warning.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Try to streamline the makefile so its easier to add timer/timekeeping
tests.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff
This adds my inconsistency-test from my timetests suite,
which checks for (single threaded) time inconsistencies
across the various clockids.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile
Add the threaded time inconsistency test from the timetest suite.
This checks for time inconsistencies between cpus, usually associated
with clock skew as sometimes found w/ TSCs.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
This adds a adjtimex validation test which checks the behavior
for a set of valida and invalid inputs. So far this only tests
ADJ_FREQUENCY, but hopefully will grow.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
This adds the alarmtimer-suspend test from the timetests suite,
which tests that the alarmtimers wake the system up from suspend
shortly after the time they were set to fire.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
Adds my nanosleep latency test from the timetest suite.
This checks to make sure we don't see "unreasonable"
latencies (> 40ms) when calling nanosleep.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
Add test to validate mqueue timeout latency from the timetest suite
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile | 3 +-
tools/testing/selftests/timers/mqueue-lat.c | 113
Add my set-timer-lat test from the timetest suite. This
test checks the latency from set_timer and reports if
any are unreasonable (>40ms).
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile
This change adds the skew_consistency test, which twists the
ADJ_FREQUENCY knob back and forth and watches for timekeeping
inconsistencies.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile
This adds my clock skew estimation test from the timetest suite.
It measures the drift between CLOCK_MONOTONIC and CLOCK_MONOTONIC_RAW
and compares it with the current frequency value from adjtimex.
It sometimes can trigger false failures when ntpd isn't in a
steady state, but its a useful too
This patch adds the change_skew test which validates the
adjtimex freq can be set to various values and then using
the inconsistency-check, raw_skew, and nanosleep tests
ensures time behaves properly.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by:
This change adds the leap-a-day test which sets STA_INS and
STA_DEL each day to trigger leapseconds each day. It also
has a mode to jump the time to right before the end of the
day each iteration.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John
This change adds the leapcrash test which tests to see if a
leapsecond deadlock which was observed from 2.6.26 to 3.3
is present on this system.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile
On Wed, 25 Feb 2015 11:32:18 +0200 Tomi Valkeinen
wrote:
> Yep, I don't think so. In any case, all this is to be deprecated, and as
> soon as omapdrm driver works reliably that should be the driver to use.
How close is that? Is it worth experimenting yet? Is there an xorg driver
available?
Adds the clocksource-switch tests which continually switches the
current clocksource between all the available ones, watching for
any timekeeping inconsistencies.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
Adds the set-2038 test which sets the time to near-edge cases
like the start and end of the 32 bit epoch and checks that
time behaves properly. There is also a dangerous mode, which
lets the clock roll over past 2038 on 32bit systems, which
on some older kernels will cause system hangs.
Cc: Shuah
Since I'm adding a bunch of tests to selftests/timers, put me
on the hook in the maintainers file.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS
Add my basic nanosleep test from my timetest suite.
This test validates that nanosleep dosen't return early
against a number of clockids.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile|
This patch adds the set-tai test which ensures the tai offset
can be set properly from adjtimex.
Cc: Shuah Khan
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Cc: Richard Cochran
Signed-off-by: John Stultz
---
tools/testing/selftests/timers/Makefile | 3 +-
The ahbix clock can never be turned off. To switch the rates we
need to switch the mux off the M/N counter to an always on source
(XO), reprogram the M/N counter to get the rate we want and
finally switch back to the M/N counter. Add a new ops structure
for this type of clock so that we can set
On Fri, Feb 20, 2015 at 08:21:36AM -0500, Kevin Mulvey wrote:
> Better alignment of loop using tabs rather than spaces, this
> makes checkpatch.pl happier.
>
> Signed-off-by: Kevin Mulvey
> ---
> virt/kvm/kvm_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied both, thanks.
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Wednesday, February 25, 2015 8:56 AM
> To: KY Srinivasan
> Cc: de...@linuxdriverproject.org; Haiyang Zhang; linux-
> ker...@vger.kernel.org; Dexuan Cui
> Subject: Re: [PATCH 1/2] Drivers: hv: hv_balloon:
On 02/25/2015 11:36 PM, Benjamin Tissoires wrote:
On Feb 25 2015 or thereabouts, Nikolai Kondrashov wrote:
On 02/25/2015 02:05 AM, Benjamin Tissoires wrote:
We append "Pen", "Pad", "Mouse" or "Keyboard" suffix to the appropriate
input node to match what the Wacom driver does and be more
On Wed, 25 Feb 2015 12:03:36 +0200 Tomi Valkeinen
wrote:
> On 25/02/15 11:37, NeilBrown wrote:
> >
> > These devices do not need to return to non-graphic console
> > for suspend, so disable that option.
> > This means there is less work to do in the suspend/resume cycle,
> > making it smoother
Hi Sudeep,
Thank you for the patch.
On Tuesday 24 February 2015 17:53:42 Sudeep Holla wrote:
> As per the ISP1761 data sheet, the DcChipID register represents
> the hardware version number (0015h) and the chip ID (8210h) for the
> Peripheral Controller.
>
> This patch fixes the chip ID value
On Sat, Feb 21, 2015 at 12:21:16AM +0100, Borislav Petkov wrote:
> On Fri, Feb 20, 2015 at 04:02:10PM -0600, Joel Schopp wrote:
> > From: David Kaplan
> >
> > KVM has nice wrappers to access the register values, clean up a few places
> > that should use them but currently do not.
> >
> >
On 02/25/2015 11:28 PM, Benjamin Tissoires wrote:
On Feb 25 2015 or thereabouts, Nikolai Kondrashov wrote:
On 02/25/2015 02:05 AM, Benjamin Tissoires wrote:
Reviewed-by: Nikolai Kondrashov
Could I have your Signed-off-by here, it's mainly your patch, and so I
kept your From.
Sure:
On Thu, Feb 05, 2015 at 04:52:52PM -0500, Murali Karicheri wrote:
> This patch add an important capability to PCI driver on Keystone. I hope to
> have this merged to the upstream branch so that it is available for v3.20.
> Also would like thank everyone for the contribution.
>
> PCI devices on
On Wednesday, February 25, 2015 06:03:56 PM Dave Airlie wrote:
> > * v3.19 ignored [io 0x0cf8-0x0cff], but v4.0 includes it. I think
> > it's wrong to include it because that's the configuration space
> > address/data registers, so it's consumed by the host bridge and not
> > produced on the
Hi Alexandre,
On Sun, Feb 22, 2015 at 03:08:31PM +0100, Alexandre Belloni wrote:
> Add support for bq27510 to the bq27x00 driver.
>
> Signed-off-by: Alexandre Belloni
patch looks mostly fine to me, I have two comments (inline).
-- Sebastian
> ---
> drivers/power/bq27x00_battery.c | 50
>
On Wed, Feb 25, 2015 at 2:14 PM, Laura Abbott wrote:
> Hi,
>
> CONFIG_DEBUG_SET_MODULE_RONX is currently non-functional on arm and arm64
> because of changes in behavior of is_module_addr. This series fixes
> both arm and arm64 to work correctly and corrects a minor bug
> related to section
When CONFIG_DEBUG_SET_MODULE_RONX is enabled, the sizes of
module sections are aligned up so appropriate permissions can
be applied. Adjusting for the symbol table may cause them to
become unaligned. Make sure to re-align the sizes afterward.
Signed-off-by: Laura Abbott
---
kernel/module.c | 2
Hi,
CONFIG_DEBUG_SET_MODULE_RONX is currently non-functional on arm and arm64
because of changes in behavior of is_module_addr. This series fixes
both arm and arm64 to work correctly and corrects a minor bug
related to section alignment in modules.
Laura Abbott (3):
arm64: Don't use
The set_memory_* functions currently only support module
addresses. The addresses are validated using is_module_addr.
That function is special though and relies on internal state
in the module subsystem to work properly. At the time of
module initialization and calling set_memory_*, it's too
The set_memory_* functions currently only support module
addresses. The addresses are validated using is_module_addr.
That function is special though and relies on internal state
in the module subsystem to work properly. At the time of
module initialization and calling set_memory_*, it's too
The "break" statements are missing by intention.
On Wed, 25 Feb 2015, Ameen Ali wrote:
> Redundant bitwise operation on 'pm' in 'switch' statement.
Why do you say the operations are redundant?
> Signed-off-by : Ameen Ali
> ---
> drivers/usb/host/ohci-tmio.c | 3 +++
> 1 file changed, 3
On 02/04/15 16:55, Ray Jui wrote:
> Sometimes a clock needs to know the rate of its parent before itself is
> registered to the framework. An example is that a PLL may need to
> initialize itself to a specific VCO frequency, before registering to the
> framework. The parent rate needs to be known,
Whenever there is a division it is usually worthwhile to
add some belt'n'braces code to ensure that cnt != 0, otherwise
a machine signal can occur.
Signed-off-by : Ameen Ali
---
drivers/net/ethernet/qlogic/qlcnic/qlcnic_dcb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wednesday 25 February 2015 22:44:42 Sebastian Reichel wrote:
> Hi Pavel,
>
> On Sat, Jan 31, 2015 at 10:39:19PM +0100, Pavel Machek wrote:
> > So we have multiple values in one sysfs file:
> >
> > root@n900:/sys/class/power_supply# cat bq24150a-0/registers
> > 0x00=0x50
> > 0x01=0xc8
> >
On Wed, Feb 25, 2015 at 10:49:51PM +0100, Pavel Machek wrote:
> Hi!
>
> > > >Is one tag per directory sufficient? Is one tag per file sufficient?
> > > >How about one tag per package? If package, then isn't a single tag for
> > > >the whole kernel source tree sufficient, as we all know the
In the future mm->exe_file will be done without mmap_sem
serialization, thus isolate and reorganize the related
code to make the transition easier. Good users will, make
use of the more standard get_mm_exe_file(), requiring only
holding the mmap_sem to read the value, and relying on reference
In the future mm->exe_file will be done without mmap_sem
serialization, thus isolate and reorganize the tile elf
code to make the transition easier. Good users will, make
use of the more standard get_mm_exe_file(), requiring only
holding the mmap_sem to read the value, and relying on reference
From: Ameen Ali
Date: Wed, 25 Feb 2015 23:56:43 +0200
> @@ -822,7 +822,7 @@ qlcnic_dcb_get_pg_tc_cfg_tx(struct net_device *netdev,
> int tc, u8 *prio,
> if (temp->valid && (pg == temp->pgid))
> cnt++;
> }
> -
> + if(cnt != 0)
>
we will remove the need for mmap_sem when dealing with
exe_file.
Applies on top of linux-next (-20150225). The arch bits are entirely
100% untested, so I apologize if there are any stupid build issues.
Thanks!
Davidlohr Bueso (3):
tile/elf: reorganize notify_exec()
oprofile: reduce mmap_sem hold for
sync_buffer() needs the mmap_sem for two distinct operations,
both only occurring upon user context switch handling:
1) Dealing with the exe_file.
2) Adding the dcookie data as we need to lookup the vma that
backs it. This is done via add_sample() and add_data().
This patch isolates 1),
On Wed, Feb 25, 2015 at 1:28 PM, Denys Vlasenko wrote:
> On 02/25/2015 09:10 PM, Andy Lutomirski wrote:
>> On Wed, Feb 25, 2015 at 11:59 AM, Andrey Wagin wrote:
>>> 2015-02-25 21:42 GMT+03:00 Denys Vlasenko :
On 02/25/2015 01:37 PM, Andrey Wagin wrote:
> 2015-02-13 0:54 GMT+03:00 Denys
This patch removes obsolete code in which summary variable is not needed.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/recovery.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
index 188a034..b2a92d4 100644
--- a/fs/f2fs/recovery.c
+++
From: Arnaldo Carvalho de Melo
When printing just events, i.e. '--no-sys --ev some:events' it makes no
sense to waste screen space.
Before:
# trace --no-sys --ev probe:*
84481.704 ( ): probe:vfs_getname:(811ed023)
pathname="/etc/services")
84481.892 ( ):
From: Arnaldo Carvalho de Melo
When tracing in X we get event loops due to the tracing activity, i.e.
updates to a gnome-terminal that generate syscalls for X.org, etc.
To get a more useful view of what is happening, syscall wise, system
wide, we need to filter those, like in:
# ps ax|egrep
Whenever there is a division it is usually worthwhile to
add some belt'n'braces code to ensure that cnt != 0, otherwise
a machine signal can occur.
Signed-off-by : Ameen Ali
---
drivers/net/ethernet/qlogic/qlcnic/qlcnic_dcb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Jaegeuk Kim
During the roll-forward recovery, -ENOENT for f2fs_iget can be skipped.
So, this error value should not be propagated.
Change-Id: I230ad2371e3fb4b9df42059c4a61f92c1f9838de
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/recovery.c | 4 +++-
1 file changed, 3 insertions(+), 1
From: Arnaldo Carvalho de Melo
Forgot to do it when adding the feature.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
Link:
From: "Michael S. Tsirkin"
Date: Tue, 24 Feb 2015 17:31:10 +0100
> The 2 that we use for copy_to_iter comes from sizeof(u16),
> it used to be that way before the iov iter update.
> Fix it up, making it obvious the size of stack access
> is right.
>
> Signed-off-by: Michael S. Tsirkin
Michael,
On Fri, Dec 12, 2014 at 11:14:58PM +0800, Feng Wu wrote:
> This patch updates the Posted-Interrupts Descriptor when vCPU
> is blocked.
>
> pre-block:
> - Add the vCPU to the blocked per-CPU list
> - Clear 'SN'
> - Set 'NV' to POSTED_INTR_WAKEUP_VECTOR
>
> post-block:
> - Remove the vCPU from the
Hi,
On Wed, Feb 11, 2015 at 12:36:51PM +0100, Mike Looijmans wrote:
> The driver reported 30% less than actually measured. This turned out to
> be caused by a simple typo in the formula to calculate the LSB quantity.
This is in my for-next queue since some time already and will be
send to
Hi Pavel,
On Wed, Feb 11, 2015 at 11:47:16AM +0100, Pavel Machek wrote:
> Cleanup comments for bq2415x_charger, bq27x00_battery.c.
Thanks, added to battery-2.6.git.
-- Sebastian
signature.asc
Description: Digital signature
From: Arnaldo Carvalho de Melo
To use in stdio based tools, like 'trace'.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Stephane Eranian
Link:
Bummer, the subject should've been:
[GIT PULL 00/21] perf/core improvements and fixes
;-\
- Arnaldo
--
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
Hi,
On Mon, Feb 09, 2015 at 12:20:45PM -0500, Nicholas Mc Guire wrote:
> return type of wait_for_completion_timeout is unsigned long not int. as
> timeout is used for wait_for_completion_timeout exclusively here its
> type is simply changed to unsigned long.
thanks, applied to battery-2.6.git.
From: Arnaldo Carvalho de Melo
All it wants is session->evlist.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
Link:
On Feb 25 2015 or thereabouts, Ping Cheng wrote:
> On Wed, Feb 25, 2015 at 8:43 AM, Benjamin Tissoires
> wrote:
> > The stylus of this device works just fine out of the box.
> > The touch is seen by default as a mouse with relative events and some
> > gestures.
> > The wireless and the wired
Hi,
On Mon, Feb 09, 2015 at 12:21:05PM -0500, Nicholas Mc Guire wrote:
> Converting jiffies to milliseconds by "val * 1000 / HZ" is technically
> OK but jiffies_to_msecs(val) is the cleaner solution and handles all
> corner cases correctly. This is a minor API consolidation only and
> should make
From: Arnaldo Carvalho de Melo
[root@ssdandy ~]# perf trace --filter-pids 16348
0.000 ( 0.000 ms): tuned/1027 ... [continued]: select()) = 0 Timeout
793.770 ( 0.000 ms): lsmd/895 ... [continued]: select()) = 0 Timeout
793.775 (793.724 ms): tuned/1027 select(tvp: 0x7f766e50)
Michael Ellerman writes:
> Anton has a busy ppc64le KVM box where guests sometimes hit the infamous
> "kernel BUG at kernel/smpboot.c:134!" issue during boot:
>
> BUG_ON(td->cpu != smp_processor_id());
>
> Basically a per CPU hotplug thread scheduled on the wrong CPU. The oops
> output confirms
Hi!
> During the testing period of about 5 months I have concluded:
>
> 1) There are 3 identical Fujitsu RX200 S6 test servers which all show the
> same problem, but I also reproduced it on some Sun Fire and Dell server.
>
> 2) The problem happens with both HW RAID (MegaRAID SAS 2108) and when
Hi!
> > >Is one tag per directory sufficient? Is one tag per file sufficient?
> > >How about one tag per package? If package, then isn't a single tag for
> > >the whole kernel source tree sufficient, as we all know the overall
> > >license for the kernel source tree.
> >
> > We really need one
Em Thu, Feb 19, 2015 at 11:31:13PM +0900, Masami Hiramatsu escreveu:
> Recent linux kernel provides a blacklist of the functions which
> can not be probed. perf probe can now check this blacklist before
> setting new events and indicate better error message for users.
>
> Without this patch,
>
On Mon 2015-02-02 18:08:06, Serge Hallyn wrote:
> Quoting Casey Schaufler (ca...@schaufler-ca.com):
> > I'm game to participate in such an effort. The POSIX scheme
> > is workable, but given that it's 20 years old and hasn't
> > developed real traction it's hard to call it successful.
>
> Over
Hi!
> > A key concept behind posix capabilities is that the privilege comes from
> > both the person and the file being executed. As you say below basically
> > anything can be executed by the program so that is completely violated.
>
> Well this patch does not change that. Its just that the
From: Jiri Olsa
Adding new 'perf data' command to provide operations over data files.
The 'perf data convert' sub command is coming in following patch, but
there's possibility for other useful commands like 'perf data ls' (to
display perf data file in directory in ls style).
Signed-off-by:
Em Fri, Feb 20, 2015 at 11:17:02PM +0100, Jiri Olsa escreveu:
> From: Sebastian Andrzej Siewior
> Adding support to convert tracepoint event fields into CTF
> event fields.
> We parse each tracepoint event for CTF conversion and add
> tracepoint fields as regular CTF event fields, so they
>
On Mon 2015-02-23 16:58:36, Felipe Balbi wrote:
> On Mon, Feb 23, 2015 at 11:34:57PM +0100, Pavel Machek wrote:
> > On Thu 2015-02-19 15:14:24, Felipe Balbi wrote:
> > > Hi,
> > >
> > > Do we have support for LED controllers which can handle patterns of
> > > different kinds ? I mean, currently,
From: Jiri Olsa
Adding 'perf data convert' to convert perf data file into different
format. This patch adds support for CTF format conversion.
To convert perf.data into CTF run:
$ perf data convert --to-ctf=./ctf-data/
[ perf data convert: Converted 'perf.data' into CTF data './ctf-data/' ]
From: Jiri Olsa
Adding feature check for babeltrace library [1], which will be used for
perf data file CTF [2] conversion in following patches.
The babeltrace library is now automatically detected as standard
feature. It's possible to specify LIBBABELTRACE_DIR make variable to
specify location
From: Arnaldo Carvalho de Melo
To figure out if ordered_events are being used when doing a flush
operation, it is enough to check if there were in fact some events
queued, i.e. look at oe->nr_events.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic
From: Arnaldo Carvalho de Melo
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Stephane Eranian
Link: http://lkml.kernel.org/n/tip-fmto8ft6jrtwz09dxn5d4...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de
From: Andi Kleen
Add an option to perf record to record running/enabled time for read
events, similar to what stat does.
This is useful to understand multiplexing problems.
Right now the report support is not great, but at least report -D
already supports it.
Signed-off-by: Andi Kleen
From: Arnaldo Carvalho de Melo
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
Link:
From: Arnaldo Carvalho de Melo
To avoid tracing the tracer.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
Link:
From: Sebastian Andrzej Siewior
Some of the tracers bring their own id or pid fields and we can end up
having two of them. This patch adds a "perf_" prefix to the 'generic'
fields so we avoid a clash of the member names.
The change is visible in the babeltrace output:
Before:
$ babeltrace
From: Arnaldo Carvalho de Melo
We need to filter multiple pids in trace, i.e. trace itself,
gnome-terminal, X.org, etc.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc:
From: Arnaldo Carvalho de Melo
Further untangling perf_session from plain event delivery routines.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
From: Arnaldo Carvalho de Melo
Because we need to use ordered_events in some cases, so we will need to
first have them in a queue, order that queue, and then process the
event.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc:
From: Arnaldo Carvalho de Melo
For tools that don't deal with perf.data files, thus do not need to
use perf_session.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc:
From: Arnaldo Carvalho de Melo
Start to untangle session from delivering samples, as there are
tools that want to use ordered_events and don't use perf_session at all.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike
From: Arnaldo Carvalho de Melo
To filter out events for a certain pid, for instance, when tracing
system wide, so that the tracer itself doesn't creates an event loop.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike
201 - 300 of 1756 matches
Mail list logo
