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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 28 Oct 2015 11:03:36 +0530
From:	Anju T <anju@...ux.vnet.ibm.com>
To:	Denis Kirjanov <kda@...ux-powerpc.org>
Cc:	linux-kernel@...r.kernel.org, maddy@...ux.vnet.ibm.com,
	acme@...hat.com, hemant@...ux.vnet.ibm.com, dsahern@...il.com,
	naveen.n.rao@...ux.vnet.ibm.com, sukadev@...ux.vnet.ibm.com,
	jolsa@...hat.com, khandual@...ux.vnet.ibm.com, mpe@...erman.id.au,
	anju@...ux.vnet.ibm.com
Subject: Re: [PATCH V2 0/3] perf/powerpc:Add ability to sample intr machine
 state in powerpc

Hi Denis,
On Monday 26 October 2015 06:47 PM, Denis Kirjanov wrote:
> On 10/26/15, Anju T <anju@...ux.vnet.ibm.com> wrote:
>> This short patch series add the ability to sample the interrupted
>> machine state for each hardware sample
> Hi,
> how can we check your patch series without testing details?

I have mentioned about the commands to test this feature in the 3rd 
patch of this series,but not detailed.

To test this patch,
Eg:

$perf record -I ls   // record machine state at interrupt
$perf script -D      //read the perf.data file

Sample output obtained for this patch / output looks like as follows:

179614739048 0xb90 [0x190]: PERF_RECORD_SAMPLE(IP, 0x1): 4130/4130: 
0xc0000000001dde88 period: 1 addr: 0

... intr regs: mask 0xfffffffffff ABI 64-bit

.... gpr0 0xc0000000001e6974

.... gpr1 0xc000001e48ad79a0

.... gpr2 0xc000000001523400

.... gpr3 0x1

.... gpr4 0xc000000fd7c76600

.... gpr5 0x29d1df51d8

.... gpr6 0x1e000000

.... gpr7 0x0

.... gpr8 0x0

.... gpr9 0x0

.... gpr10 0x1

.... gpr11 0x0

.... gpr12 0x24022822

.... gpr13 0xc00000000fee4c80

.... gpr14 0x0

.... gpr15 0xc0000000fcab3800

.... gpr16 0x0

.... gpr17 0xc000000ffa445000

.... gpr18 0xc000001e48ad78a0

.... gpr19 0xc000000001523400

.... gpr20 0xc0000000000a09bc

.... gpr21 0xc000001e3c11d100

.... gpr22 0xc0000000001e54a8

.... gpr23 0xc000000001523400

.... gpr24 0xc000001e48ad7850

.... gpr25 0xc000001e3c11d100

.... gpr26 0xc000001e48a71790

.... gpr27 0xfffffffffffffead

.... gpr28 0x0

.... gpr29 0xc000001e3c11d100

.... gpr30 0x1

.... gpr31 0x0

.... nip 0xc00000000000fe8c

.... msr 0x9000000000009032

.... orig_r3 0xc0000000001e6978

.... ctr 0xc00000000009e1f0

.... link 0xc0000000001e697c

.... xer 0x0

.... ccr 0x84022884

.... softe 0x1

.... trap 0xf01

.... dar 0x0

.... dsisr 0x300040060000004

.... result 0x0

... thread: :4130:4130

...... dso: /root/.debug/.build-id/82/8d2c7bac560dc9aac8bf6289f26504e22d6883

:4130 4130 179.614739: 1 cycles: c0000000001dde88 .perf_ctx_unlock 
(/boot/vmlinux)


0xd20 [0x190]: event: 9


>
>> Anju (3):
>>    perf/powerpc:add ability to sample intr machine state in power
>>    tools/perf:Map the ID values with register names
>>    perf/powerpc:add support for sampling intr machine state
>>
>>
>>   arch/powerpc/Kconfig                        |   1 +
>>   arch/powerpc/include/uapi/asm/perf_regs.h   |  55 +++++++++++++
>>   arch/powerpc/perf/Makefile                  |   1 +
>>   arch/powerpc/perf/perf_regs.c               |  87 ++++++++++++++++++++
>>   tools/perf/arch/powerpc/include/perf_regs.h | 118
>> ++++++++++++++++++++++++++++
>>   tools/perf/config/Makefile                  |   5 ++
>>   6 files changed, 267 insertions(+)
>>   create mode 100644 arch/powerpc/include/uapi/asm/perf_regs.h
>>   create mode 100644 arch/powerpc/perf/perf_regs.c
>>   create mode 100644 tools/perf/arch/powerpc/include/perf_regs.h
>>
>> --
>> 2.1.0
>>
>> _______________________________________________
>>
Thanks and regards
Anju

--
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