From: James Morse <james.morse@arm.com>
To: Rex Nie <rex.nie@jaguarmicro.com>
Cc: "fenghua.yu@intel.com" <fenghua.yu@intel.com>,
"reinette.chatre@intel.com" <reinette.chatre@intel.com>,
"rohit.mathew@arm.com" <rohit.mathew@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 答复: [PATCH] fs/resctrl: Uniform data type of component_id/domid/id/cache_id
Date: Mon, 18 Mar 2024 17:32:38 +0000 [thread overview]
Message-ID: <d0277225-199a-4175-a43b-a09c1445138a@arm.com> (raw)
In-Reply-To: <KL1PR0601MB577382D132A25E055856C543E62B2@KL1PR0601MB5773.apcprd06.prod.outlook.com>
Hi Rex,
On 12/03/2024 02:52, Rex Nie wrote:
> Thanks for your reply. Please check my inline reply.
> BTW, can I know the progress/roadmap of mpam driver upstream?
The series to change the monitor code in a way that allows MPAM to work, and split the
locks has been merged for rc1. I plan to post the next series shortly. Once that is
reviewed and merged the refactoring of resctrl will be finished and I can start posting
the MPAM driver. (it has a few small dependencies on cacheinfo and PPTT parsing code).
I anticipate the MPAM driver will be merged fairly quickly as it won't regress existing
systems.
Any help reviewing the x86 changes would be appreciated - these are the changes that can
affect existing systems. (Shall I CC you on the series?)
Thanks,
James
next prev parent reply other threads:[~2024-03-18 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 8:18 Rex Nie
2024-03-11 17:54 ` James Morse
2024-03-12 2:52 ` 答复: " Rex Nie
2024-03-18 17:32 ` James Morse [this message]
2024-03-19 3:21 ` 答复: " Rex Nie
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=d0277225-199a-4175-a43b-a09c1445138a@arm.com \
--to=james.morse@arm.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=rex.nie@jaguarmicro.com \
--cc=rohit.mathew@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®