From: "tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>
To: "'james.morse@arm.com'" <james.morse@arm.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"'soc@kernel.org'" <soc@kernel.org>,
"'tony.luck@intel.com'" <tony.luck@intel.com>,
"'arnd@arndb.de'" <arnd@arndb.de>,
"'will@kernel.org'" <will@kernel.org>,
"'catalin.marinas@arm.com'" <catalin.marinas@arm.com>,
"'olof@lixom.net'" <olof@lixom.net>,
"misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>
Subject: About resctrl code rebase
Date: Thu, 19 Aug 2021 05:14:29 +0000 [thread overview]
Message-ID: <TYAPR01MB6330F88A234F98FEF239EDD28BC09@TYAPR01MB6330.jpnprd01.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
Hi, James Morse
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.tip-bot2@tip-bot2/
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?
Best regards,
Tan Shaopeng
[-- Attachment #2: Type: text/html, Size: 3895 bytes --]
next reply other threads:[~2021-08-19 5:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 5:14 tan.shaopeng [this message]
[not found] <20210901083516.Qzs5LSr3ZkgfJT5t1XFyf14HW7R1F3jCzWy7uCnDETY@z>
2021-09-01 8:35 ` About resctrl code rebase tan.shaopeng
[not found] ` <20210901170420.65KFdDatm7mKlrWIB5eDJIuh9nXnVk_MIyBoAWWLMxs@z>
2021-09-01 17:04 ` James Morse
2021-09-01 17:04 ` James Morse
[not found] ` <20210906061907.zRxgWS4hpDpFAJYpGB0XapTra9BTfiqCe1FFEmEIhlc@z>
2021-09-06 6:19 ` tan.shaopeng
2021-09-06 6:19 ` tan.shaopeng
2021-11-24 11:17 ` 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=TYAPR01MB6330F88A234F98FEF239EDD28BC09@TYAPR01MB6330.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=linux-kernel@vger.kernel.org \
--cc=misono.tomohiro@fujitsu.com \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=tony.luck@intel.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).