[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c628c2a2-4d85-ccae-6de1-79d259209212@linux.intel.com>
Date: Wed, 15 May 2019 10:15:42 -0400
From: "Liang, Kan" <kan.liang@...ux.intel.com>
To: Ravi Bangoria <ravi.bangoria@...ux.ibm.com>, acme@...nel.org
Cc: jolsa@...nel.org, mingo@...hat.com, linux-kernel@...r.kernel.org,
ak@...ux.intel.com
Subject: Re: [PATCH V2 1/3] perf parse-regs: Split parse_regs
On 5/15/2019 2:49 AM, Ravi Bangoria wrote:
>
> On 5/15/19 1:49 AM, kan.liang@...ux.intel.com wrote:
>> From: Kan Liang <kan.liang@...ux.intel.com>
>>
>> The available registers for --int-regs and --user-regs may be different,
>> e.g. XMM registers.
>>
>> Split parse_regs into two dedicated functions for --int-regs and
>> --user-regs respectively.
>>
>> Modify the warning message. "--user-regs=?" should be applied to show
>> the available registers for --user-regs.
>>
>> Signed-off-by: Kan Liang <kan.liang@...ux.intel.com>
>> ---
>
> For patch 1 and 2,
> Tested-by: Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
>
> Minor neat. Should we update document as well? May be something like:
>
> tools/perf/Documentation/perf-record.txt
>
> --user-regs::
> Similar to -I, but capture user registers at sample time. To list the available
> user registers use --user-regs=\?.
>
Hi Ravi,
Thanks for test.
The change of document looks good.
Thanks,
Kan
Powered by blists - more mailing lists