From: "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>
To: "Moger, Babu" <Babu.Moger@amd.com>, "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H Peter Anvin" <hpa@zytor.com>,
"Luck, Tony" <tony.luck@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
James Morse <james.morse@arm.com>,
"Pathan, Arshiya Hayatkhan" <arshiya.hayatkhan.pathan@intel.com>,
"Shankar, Ravi V" <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:31:44 +0000 [thread overview]
Message-ID: <FFF73D592F13FD46B8700F0A279B802F485D4DB7@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <feb572ec-4495-c52c-0127-213417a67c3c@amd.com>
> > For (Intel) Memory Bandwidth features like MBA and MBM, perf iMC
> > (Integrated Memory Controller) is used for validation. As a part of
> > test, we run a benchmark (eg: fill_buf) and get memory bandwidth
> > values from MBM and iMC and verify if the difference between both the
> reported values are in a reasonable range.
> >
> > To make this common across x86, could you please let us know if
> > similar things (i.e. perf iMC) exist on AMD? If so, you could add it in. The same
> applies for ARM.
>
> We dont have iMC. You can go ahead with what you have right now. We can
> add those details later if required.
Sure! Makes sense to me.
Regards,
Sai
next prev parent reply other threads:[~2018-10-17 18:31 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 [this message]
2018-10-17 18:03 ` Moger, Babu
2018-10-17 18:23 ` Moger, Babu
[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=FFF73D592F13FD46B8700F0A279B802F485D4DB7@ORSMSX114.amr.corp.intel.com \
--to=sai.praneeth.prakhya@intel.com \
--cc=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=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).