From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, ak@linux.intel.com,
eranian@google.com, irogers@google.com
Subject: Re: [PATCH V3 3/3] perf test: Support the retire_lat check
Date: Mon, 6 Feb 2023 11:25:03 -0500 [thread overview]
Message-ID: <32d7df47-6d7e-6b7c-f444-9f31e6425ff2@linux.intel.com> (raw)
In-Reply-To: <30bc05e4-a479-ad53-22b1-4afca4fa7ec2@linux.intel.com>
On 2023-02-06 10:49 a.m., Liang, Kan wrote:
>
>
> On 2023-02-06 10:34 a.m., Arnaldo Carvalho de Melo wrote:
>> Em Mon, Feb 06, 2023 at 12:32:54PM -0300, Arnaldo Carvalho de Melo escreveu:
>>> Em Mon, Feb 06, 2023 at 10:17:46AM -0500, Liang, Kan escreveu:
>>>>
>>>>
>>>> On 2023-02-06 10:01 a.m., Arnaldo Carvalho de Melo wrote:
>>>>> Em Thu, Feb 02, 2023 at 11:22:09AM -0800, kan.liang@linux.intel.com escreveu:
>>>>>> From: Kan Liang <kan.liang@linux.intel.com>
>>>>>>
>>>>>> Add test for the new field for Retire Latency in the X86 specific test.
>>>>>
>>>>> Is this passing 'perf test' for you?
>>>>
>>>> Ah, it should be the original V2 missed the below change.
>>>
>>> Can you please send this as a separate patch as I already merged
>>> torvalds/master and added more csets on top, so to just fix it and
>>> force push now would be bad.
>>>
>>> Please use what is in my perf/core branch and add a Fixes for that v2
>>> patch.
>>
>> BTW, the 3rd patch with the test is already on the tmp.perf/core branch,
>> that will move to perf/core after the next round of container build
>> tests.
>>
>
> Thanks. I will sent a V4 to fix the 'perf test' issue.
>
The V4 is here. It includes a fix for the 'perf test' issue and a fix
for the perf script document.
https://lore.kernel.org/lkml/20230206162100.3329395-1-kan.liang@linux.intel.com/
Sorry again for the inconvenience.
Thanks,
Kan
> Thanks,
> Kan
>> - Arnaldo
>>
>>> Thanks,
>>>
>>> - Arnaldo
>>>
>>>> @@ -100,5 +101,25 @@ void arch_perf_synthesize_sample_weight(const
>>>> struct perf_sample *data,
>>>> if (type & PERF_SAMPLE_WEIGHT_STRUCT) {
>>>> *array &= 0xffffffff;
>>>> *array |= ((u64)data->ins_lat << 32);
>>>> + *array |= ((u64)data->retire_lat << 48);
>>>> }
>>>> }
>>>>
>>>> Could you please remove the V2 and re-apply the V3?
>>>
>>>> $ sudo ./perf test -v "x86 sample parsing"
>>>> 74: x86 Sample parsing :
>>>> --- start ---
>>>> test child forked, pid 3316797
>>>> test child finished with 0
>>>> ---- end ----
>>>> x86 Sample parsing: Ok
>>>>
>>>>
>>>> Thanks,
>>>> Kan
>>>>
>>>>>
>>>>> [root@quaco ~]# perf test -v "x86 sample parsing"
>>>>> 74: x86 Sample parsing :
>>>>> --- start ---
>>>>> test child forked, pid 72526
>>>>> Samples differ at 'retire_lat'
>>>>> parsing failed for sample_type 0x1000000
>>>>> test child finished with -1
>>>>> ---- end ----
>>>>> x86 Sample parsing: FAILED!
>>>>> [root@quaco ~]#
>>>>>
>>>>> - Arnaldo
>>>>>
>>>>>> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
>>>>>> ---
>>>>>>
>>>>>> New patch since V2
>>>>>>
>>>>>> tools/perf/arch/x86/tests/sample-parsing.c | 5 ++++-
>>>>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/tools/perf/arch/x86/tests/sample-parsing.c b/tools/perf/arch/x86/tests/sample-parsing.c
>>>>>> index 690c7c07e90d..a061e8619267 100644
>>>>>> --- a/tools/perf/arch/x86/tests/sample-parsing.c
>>>>>> +++ b/tools/perf/arch/x86/tests/sample-parsing.c
>>>>>> @@ -27,8 +27,10 @@ static bool samples_same(const struct perf_sample *s1,
>>>>>> const struct perf_sample *s2,
>>>>>> u64 type)
>>>>>> {
>>>>>> - if (type & PERF_SAMPLE_WEIGHT_STRUCT)
>>>>>> + if (type & PERF_SAMPLE_WEIGHT_STRUCT) {
>>>>>> COMP(ins_lat);
>>>>>> + COMP(retire_lat);
>>>>>> + }
>>>>>>
>>>>>> return true;
>>>>>> }
>>>>>> @@ -48,6 +50,7 @@ static int do_test(u64 sample_type)
>>>>>> struct perf_sample sample = {
>>>>>> .weight = 101,
>>>>>> .ins_lat = 102,
>>>>>> + .retire_lat = 103,
>>>>>> };
>>>>>> struct perf_sample sample_out;
>>>>>> size_t i, sz, bufsz;
>>>>>> --
>>>>>> 2.35.1
>>>>>>
>>>>>
>>>
>>> --
>>>
>>> - Arnaldo
>>
next prev parent reply other threads:[~2023-02-06 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 19:22 [PATCH V3 1/3] perf report: Support Retire Latency kan.liang
2023-02-02 19:22 ` [PATCH V3 2/3] perf script: " kan.liang
2023-02-02 19:22 ` [PATCH V3 3/3] perf test: Support the retire_lat check kan.liang
2023-02-06 15:01 ` Arnaldo Carvalho de Melo
2023-02-06 15:17 ` Liang, Kan
2023-02-06 15:32 ` Arnaldo Carvalho de Melo
2023-02-06 15:34 ` Arnaldo Carvalho de Melo
2023-02-06 15:49 ` Liang, Kan
2023-02-06 16:25 ` Liang, Kan [this message]
2023-02-06 15:23 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32d7df47-6d7e-6b7c-f444-9f31e6425ff2@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®