From: "Moger, Babu" <Babu.Moger@amd.com>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, H Peter Anvin <hpa@zytor.com>,
Tony Luck <tony.luck@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
James Morse <james.morse@arm.com>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
Arshiya Hayatkhan Pathan <arshiya.hayatkhan.pathan@intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] selftests/resctrl: Add resctrl selftest
Date: Wed, 17 Oct 2018 18:23:14 +0000 [thread overview]
Message-ID: <64115578-930b-e9a6-6908-921ba27ca066@amd.com> (raw)
In-Reply-To: <9c99a95d-de9a-6b33-a4c4-074b31515a7e@amd.com>
On 10/17/2018 01:03 PM, Moger, Babu wrote:
> Hi Fenghua,
> My few comments.
>
> On 10/17/2018 09:40 AM, Moger, Babu wrote:
>>
>>
>> On 10/16/2018 03:32 PM, Fenghua Yu wrote:
>>>> From: Moger, Babu [mailto:Babu.Moger@amd.com]
>>>> On 10/16/2018 11:56 AM, Fenghua Yu wrote:
>>>>> With more and more resctrl features are being added by Intel, AMD and
>>>>> ARM, a test tool is becoming more and more useful to validate that
>>>>> both hardware and software functionalities work as expected.
>>>>
>>>> I like the initiative here. It is always good to have a single code base.
>>>>
>>>> One question. I see that there is a tool at https://github.com/intel/intel-cmt-cat to test and verify the functionality of resctrl feature. I also see some of the distros have this tool already.
>>>> Is this tool going to replace intel-cmt-cat? I have not looked at the
>>>> patches closely yet.
>>>
>>> No, the selftest in this patch set will not replace intel-cmt-cat or
>>> vice versa.
>>>
>>> The selftest in this patch set has a different purpose from intel-cmt-cat:
>>> the selftest is a test tool which validates resctrl functionalities while
>>> intel-cmt-cat is mainly a utility that provides base library for higher
>>> level applications including performance analysis tools, benchmark measurement
>>> tools, and potential resctrl tests. For example, running MBA test in the
>>> selftests tells MBA working or not working (fail/pass) right way. The
>>
>> Ok. Sure. Let me take a look at selftest closely. Will send my feedback soon.
>>
>>> intel-cmt-cat doesn't have this testing capability unless we extend the
>>> tool.
>>>
>>> And intel-cmt-cat is maintained and developed by Intel. I don't think it's
>>> easy to extend it to AMD and ARM features. The selftest will be maintained
>>
>> We1l.. We were hoping to have a common tool across. It makes it easy for
>> distros. Probably, we can have a separate discussion on this.
>>
>>> and developed by the community and will hopefully cover all architectures.
>>>
>>> We have seen a few issues recently in resctrl and may see more issues
>>> while expending the features. A convevient selftest may be useful to help
>>> identify and fix those potential issues.
>
> I don't know the rules for selftest. Here are my general comments.
>
> 1. File names are not consistent.
> # ls *.c
> fill_buf.c mba.c mbm.c resctrl.c resctrl_membw.c resctrl_tests.c
> Few files start with resctrl_ prefix and others don't.
>
> 2. Do we need README(or USAGE) here? I had too
>
Correction..
2. Do we need README(or USAGE) here? I had too look at the code to check
on "usage options" to run this utility.
> 3. I saw lots of these errors.
> "mba.c:111:2: error: ‘for’ loop initial declarations are only allowed
> in C99 mode"
> for (int i = 0; i < 10; i++) {
> ^
>
> I had to change it to
> int i;
> for (i = 0; i < 10; i++) {
>
>
>
>>>
>>> Thanks.
>>>
>>> -Fenghua
>>>
>>>
next prev parent reply other threads:[~2018-10-17 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 16:56 [PATCH 0/7] selftests/resctrl: Add resctrl selftest Fenghua Yu
2018-10-16 16:56 ` [PATCH 1/7] selftests/resctrl: Add basic resctrl file system operations and data Fenghua Yu
2018-10-16 16:56 ` [PATCH 2/7] selftests/resctrl: Read memory bandwidth from perf IMC counter and from resctrl file system Fenghua Yu
2018-10-16 16:56 ` [PATCH 3/7] selftests/resctrl: Add callback to start a benchmark Fenghua Yu
2018-10-16 16:56 ` [PATCH 4/7] selftests/resctrl: Add built in benchmark Fenghua Yu
2018-10-16 16:56 ` [PATCH 5/7] selftests/resctrl: Add mbm test Fenghua Yu
2018-10-16 16:56 ` [PATCH 6/7] selftests/resctrl: Add mba test Fenghua Yu
2018-10-16 16:56 ` [PATCH 7/7] selftests/resctrl: Add the test in MAINTAINERS Fenghua Yu
2018-10-16 17:40 ` [PATCH 0/7] selftests/resctrl: Add resctrl selftest Moger, Babu
[not found] ` <FFF73D592F13FD46B8700F0A279B802F485D47DE@ORSMSX114.amr.corp.intel.com>
2018-10-16 20:32 ` Fenghua Yu
2018-10-17 14:40 ` Moger, Babu
2018-10-17 17:28 ` Prakhya, Sai Praneeth
2018-10-17 18:28 ` Moger, Babu
2018-10-17 18:31 ` Prakhya, Sai Praneeth
2018-10-17 18:03 ` Moger, Babu
2018-10-17 18:23 ` Moger, Babu [this message]
[not found] ` <CALBSrqBXdXfNdZ1yJ_-zUSkk_2m_8R-VHNqk8DH3HmxCti4hhA@mail.gmail.com>
2018-10-17 20:24 ` Fenghua Yu
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=64115578-930b-e9a6-6908-921ba27ca066@amd.com \
--to=babu.moger@amd.com \
--cc=arshiya.hayatkhan.pathan@intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=reinette.chatre@intel.com \
--cc=sai.praneeth.prakhya@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).