From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: James Morse <james.morse@arm.com>
Cc: "itaru.kitayama@fujitsu.com" <itaru.kitayama@fujitsu.com>,
'Rob Herring' <robh@kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>
Subject: Re: mpam/snapshot/v5.17
Date: Wed, 15 Jun 2022 17:44:32 +0100 [thread overview]
Message-ID: <20220615174432.00006951@Huawei.com> (raw)
In-Reply-To: <71500d44-e318-ba0d-4e0f-079d338940e7@arm.com>
On Wed, 15 Jun 2022 11:26:27 +0100
James Morse <james.morse@arm.com> wrote:
> Hi Itaru,
>
> On 6/13/22 22:59, itaru.kitayama@fujitsu.com wrote:
> > Rob,
> > Indeed my colleague pointed that out to me as well. In the meantime, what's the best way
> > to test the MPAM feature (8.4 optional)?
>
> I do my testing with the Fixed Virtual Platform from arm[0].
> Its a bit of a pain to set up, but it configured correctly it presents MPAM MSC - although
> they don't do anything as its not a performance model.
>
> There are a ton of options, but the main two to try and enable are something like:
> | cluster0.has_mpam=1
> | cluster0.l3cache-mpamf_base=0x30000000
>
> Let me know off list if you want a hand setting it up.
>
>
> One day there will be hardware!
There is (and has been for several years... :)
https://chowdera.com/2021/05/20210504023631776n.html
openEuler is carrying code for it.
https://gitee.com/openeuler/kernel/tree/openEuler-22.03-LTS/arch/arm64/kernel/mpam
>
>
> Thanks,
>
> James
>
> [0] https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-06-15 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 7:55 mpam/snapshot/v5.17 itaru.kitayama
2022-06-13 16:44 ` mpam/snapshot/v5.17 Rob Herring
2022-06-13 21:59 ` mpam/snapshot/v5.17 itaru.kitayama
2022-06-15 10:26 ` mpam/snapshot/v5.17 James Morse
2022-06-15 16:44 ` Jonathan Cameron [this message]
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=20220615174432.00006951@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=itaru.kitayama@fujitsu.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=tan.shaopeng@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.