lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 31 Mar 2015 21:46:27 +0800
From:	Yunlong Song <yunlong.song@...wei.com>
To:	<a.p.zijlstra@...llo.nl>, <paulus@...ba.org>, <mingo@...hat.com>,
	<acme@...nel.org>
CC:	<linux-kernel@...r.kernel.org>, <wangnan0@...wei.com>
Subject: [PATCH 0/9] perf sched replay: Make some improvements and fixes

Hi,
  Found some functions to improve and bugs to fix in perf sched replay.

Yunlong Song (9):
  perf sched replay: Use struct task_desc instead of struct task_task
    for     correct meaning
  perf sched replay: Increase the MAX_PID value to fix assertion failure
        problem
  perf sched replay: Alloc the memory of pid_to_task dynamically to
    adapt     to the unexpected change of pid_max
  perf sched replay: Realloc the memory of pid_to_task stepwise to adapt
        to the different pid_max configurations
  perf sched replay: Fix the segmentation fault problem caused by pr_err
        in threads
  perf sched replay: Handle the dead halt of sem_wait when
    create_tasks()     fails for any task
  perf sched replay: Fix the EMFILE error caused by the limitation of
    the     maximum open files
  perf sched replay: Support using -f to override perf.data file
    ownership
  perf sched replay: Use replay_repeat to calculate the runavg of cpu   
     usage instead of the default value 10

 tools/perf/builtin-sched.c | 67 +++++++++++++++++++++++++++++++++++-----------
 1 file changed, 52 insertions(+), 15 deletions(-)

-- 
1.8.5.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ