From: James Morse <james.morse@arm.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Amit Singh Tomar <amitsinght@marvell.com>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
George Cherian <gcherian@marvell.com>,
"robh@kernel.org" <robh@kernel.org>,
"peternewman@google.com" <peternewman@google.com>,
Drew Fustini <dfustini@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [EXT] Re: resctrl2 - status
Date: Fri, 15 Sep 2023 18:16:43 +0100 [thread overview]
Message-ID: <6682c765-9d7f-dd21-af85-e83cee435a89@arm.com> (raw)
In-Reply-To: <20230830114731.00003590@Huawei.com>
Hi guys,
On 30/08/2023 11:47, Jonathan Cameron wrote:
> On Tue, 29 Aug 2023 17:18:53 +0000
> Amit Singh Tomar <amitsinght@marvell.com> wrote:
>> From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
>> James probably also has views on this, but I wouldn't expect userspace to go anywhere near ACPI parsing.
I agree wholeheartedly! Parsing the ACPI tables also wouldn't work: the firmware tables
describe where the MPAM hardware is, but the features that are supported are described by
the hardware, then grouped to find the common features we can make use of.
>> If the description of what MPAM features are supported (before resctrl is running) is necessary, then we
>> should add it to the existing description of the various caches etc. Maybe somewhere in
>> /sys/bus/node/devices/nodeX/cpuY/cache/indexZ/
>> for the caches
>> and
>> /sys/bus/node/devices/nodeX for the DRAM controllers.
>> [>>] Or may be all the MPAM features list is unified at one place, something like this ?
>> https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git/commit/?h=mpam/snapshot/v6.5-rc1&id=c32874cd1d68241c481a9d0c32c8c65d019c247e
>
> Fine for debug, not for generic tooling.
Yeah, this is really just for folk reporting bugs to me so we can work out what their
firmware table described, and what the driver found.
Thanks,
James
prev parent reply other threads:[~2023-09-15 17:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 18:10 Luck, Tony
2023-08-25 17:47 ` Reinette Chatre
2023-08-25 18:09 ` Luck, Tony
2023-08-25 18:58 ` Reinette Chatre
2023-08-25 19:44 ` Luck, Tony
2023-08-25 20:20 ` Reinette Chatre
2023-08-25 20:54 ` Tony Luck
2023-08-25 23:08 ` Reinette Chatre
2023-08-26 1:11 ` Tony Luck
2023-08-28 14:50 ` Reinette Chatre
2023-09-06 18:21 ` Tony Luck
2023-09-08 18:08 ` Moger, Babu
2023-09-08 18:51 ` Luck, Tony
2023-09-08 21:35 ` Moger, Babu
2023-09-08 23:13 ` Tony Luck
2023-09-15 17:55 ` Drew Fustini
2023-09-18 10:44 ` Jonathan Cameron
2023-09-28 8:47 ` Peter Newman
2023-09-28 14:47 ` Luck, Tony
2023-09-29 9:38 ` Jonathan Cameron
2023-09-29 14:49 ` Drew Fustini
2023-09-15 17:16 ` James Morse
2023-09-15 20:38 ` Tony Luck
2023-09-21 0:21 ` Tony Luck
2023-09-19 12:53 ` Peter Newman
2023-09-19 16:40 ` Tony Luck
2023-08-29 10:23 ` Jonathan Cameron
2023-08-29 17:18 ` [EXT] " Amit Singh Tomar
2023-08-30 10:47 ` Jonathan Cameron
2023-09-15 17:16 ` James Morse [this message]
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=6682c765-9d7f-dd21-af85-e83cee435a89@arm.com \
--to=james.morse@arm.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=amitsinght@marvell.com \
--cc=dfustini@baylibre.com \
--cc=fenghua.yu@intel.com \
--cc=gcherian@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=reinette.chatre@intel.com \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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®