[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TYAPR01MB6330974317488E525DBA4E2E8BD29@TYAPR01MB6330.jpnprd01.prod.outlook.com>
Date: Mon, 6 Sep 2021 06:19:07 +0000
From: "tan.shaopeng@...itsu.com" <tan.shaopeng@...itsu.com>
To: 'James Morse' <james.morse@....com>
CC: "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"'linux-arm-kernel@...ts.infradead.org'"
<linux-arm-kernel@...ts.infradead.org>,
"'soc@...nel.org'" <soc@...nel.org>,
"'tony.luck@...el.com'" <tony.luck@...el.com>,
"'arnd@...db.de'" <arnd@...db.de>,
"'will@...nel.org'" <will@...nel.org>,
"'catalin.marinas@....com'" <catalin.marinas@....com>,
"'olof@...om.net'" <olof@...om.net>,
"misono.tomohiro@...itsu.com" <misono.tomohiro@...itsu.com>
Subject: RE: About resctrl code rebase
Hi, James Morse
Thanks for your reply.
> On 01/09/2021 09:35, tan.shaopeng@...itsu.com wrote:
> >> As you known, Fujitsu is implementing a feature that add A64FX's
> >> cache control function into resctrl.
>
> >> Fujitsu will implement this feature base on your rebased code. I
> >> think the commit of refactoring arch/x86 implementation of resctrl
> >> has been merged into the x86/cache branch.
> >> https://lore.kernel.org/lkml/162871088112.395.12879267279872673224.ti
> >> p-bot2@...-bot2/
>
> I'm afraid this was only a small part of it.
>
> I've also posted the next series here:
> https://lore.kernel.org/lkml/20210729223610.29373-1-james.morse@arm.com
> /
>
> and there are a couple more after that.
I understand.
> >> I would like to know whether you have rebased these codes that move
> >> the common parts of multiple architectures to somewhere.
> >> And where is the rebase code?
> >> In addition, when will you release the latest MPAM patch?
>
> I will keep posting 'the next part' of the x86 changes once the earlier part is
> reviewed.
> (please help!)
I will check these patches.
And I'm going to test these patches on machine with x86.
Best regards,
Tan Shaopeng
> I can't push the latest branch until the ACPI spec is published, but I hope that
> will happen this month.
>
>
> > I'm afraid that my message may not have reached you.
>
> Yes, I'm horribly behind with email!
Powered by blists - more mailing lists