From: "tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>
To: James Morse <james.morse@arm.com>
Cc: 'Arnd Bergmann' <arnd@arndb.de>, Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Olof Johansson <olof@lixom.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
SoC Team <soc@kernel.org>,
"misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>
Subject: RE: [PATCH RFC] soc: fujitsu: Add cache driver code
Date: Wed, 31 Mar 2021 08:52:16 +0000 [thread overview]
Message-ID: <OSAPR01MB21463C735D4A07344F35E7CC8B7C9@OSAPR01MB2146.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAK8P3a2pFcNTw9NpRtQfYr7A5OcZ=As2kM0D_sbfFcGQ_J2Q+Q@mail.gmail.com>
Dear James Morse
> > Given that all of this is outside of the scope of the architecture, I
> > don't think that arch/arm64/ is the right place for it. Perhaps this
> > would fit into the resctrl rework that James has been doing for MPAM?
>
> Indeed, that sounds like a good starting point. I don't understand enough about
> either of the two to be sure, but it sounds like there is some overlap in
> functionality, and ideally we would have one user interface that can deal with
> all the hardware implementations (intel, arm, fujitsu and any future ones).
According to my study, it seems possible to add A64FX's sector cache function
to resctrl. I heard you are working on resctrl rework for MPAM ,
but I cannot find related patches on ML archive. Therefore,
I would like to know the status about MPAM support.
(1) I think the first step is to support resctrl for ARM arch.
Have you finished the work of arm support and when will you release it?
(2) When will you release MPAM patch?
Best regards
Tan Shaopeng
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-31 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 9:38 [PATCH RFC] Upstream A64FX cache driver tan.shaopeng
2021-03-03 9:38 ` [PATCH RFC] soc: fujitsu: Add cache driver code tan.shaopeng
2021-03-03 11:24 ` Arnd Bergmann
2021-03-04 10:34 ` tan.shaopeng
2021-03-04 10:46 ` Will Deacon
2021-03-04 10:58 ` Arnd Bergmann
2021-03-05 7:48 ` tan.shaopeng
2021-03-31 8:52 ` tan.shaopeng [this message]
2021-04-01 16:15 ` James Morse
2021-04-02 8:44 ` tan.shaopeng
2021-03-04 10:54 ` Arnd Bergmann
2021-03-05 8:10 ` tan.shaopeng
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=OSAPR01MB21463C735D4A07344F35E7CC8B7C9@OSAPR01MB2146.jpnprd01.prod.outlook.com \
--to=tan.shaopeng@fujitsu.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=misono.tomohiro@fujitsu.com \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).