From: James Morse <james.morse@arm.com>
To: "tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.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: Thu, 1 Apr 2021 17:15:09 +0100 [thread overview]
Message-ID: <edaea436-d94e-d862-1136-66e9f881e0cc@arm.com> (raw)
In-Reply-To: <OSAPR01MB21463C735D4A07344F35E7CC8B7C9@OSAPR01MB2146.jpnprd01.prod.outlook.com>
Hi Tan Shaopeng,
On 31/03/2021 09:52, tan.shaopeng@fujitsu.com wrote:
>>> 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 think this depends on whether it maps to one of Intel RDT's existing schema.
While adding new ones looks easy, it is bad for user-space as they are not portable
between machines that support 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.
Its about five or six series that refactor resctrl inside arch/x86 to have a clear
boundary between arch-specific code and the resctrl code that implements the filesystem,
then pull it out to /fs/ and build the MPAM driver to make it work for arm64.
Unfortunately, its rather large (>100 patches), so will take some time to be reviewed.
> (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?
No-one wants a second copy of the code to implement resctrl, as this will introduce subtle
bugs that user-space would have to work around, and make it harder to merge later.
The first step is to refactor the arch/x86 implementation of resctrl so that the parts
that are visible to user-space can be moved somewhere that is common to multiple
architectures.
I've posted the next chunk of that work here:
https://lore.kernel.org/lkml/20210312175849.8327-1-james.morse@arm.com/
> (2) When will you release MPAM patch?
The latest complete version of the tree is here:
https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git/log/?h=mpam/snapshot/feb
It is over a year old, and has plenty of bugs.
I hope to push a newer version of the branch once I have a complete copy of the tree that
has been tested, and is based on the current version of the ACPI table.
Thanks,
James
_______________________________________________
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-04-01 16:31 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
2021-04-01 16:15 ` James Morse [this message]
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=edaea436-d94e-d862-1136-66e9f881e0cc@arm.com \
--to=james.morse@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=misono.tomohiro@fujitsu.com \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=tan.shaopeng@fujitsu.com \
--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).