From: "Luck, Tony" <tony.luck@intel.com>
To: "Chatre, Reinette" <reinette.chatre@intel.com>,
"tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
'James Morse' <james.morse@arm.com>,
"misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>
Subject: RE: About add an A64FX cache control function into resctrl
Date: Thu, 29 Apr 2021 17:50:20 +0000 [thread overview]
Message-ID: <49cdd0b707194148915e2efe2ab5d707@intel.com> (raw)
In-Reply-To: <14ddf86b-89e1-ba26-b684-f3d5d5f8ade7@intel.com>
>>>> [Sector cache function]
>>>> The sector cache function split cache into multiple sectors and
>>>> control them separately. It is implemented on the L1D cache and
>>>> L2 cache in the A64FX processor and can be controlled individually
>>>> for L1D cache and L2 cache. A64FX has no L3 cache. Each L1D cache and
>>>> L2 cache has 4 sectors. Which L1D sector is used is specified by the
>>>> value of [57:56] bits of address, how many ways of sector are
>>>> specified by the value of register (IMP_SCCR_L1_EL0).
>>>> Which L2 sector is used is specified by the value of [56] bits of
>>>> address, and how many ways of sector are specified by value of
>>>> register (IMP_SCCR_ASSIGN_EL1, IMP_SCCR_SET0_L2_EL1,
>>>> IMP_SCCR_SET1_L2_EL1).
Are A64FX binaries position independent? I.e. could the OS reassign
a running task to a different sector by remapping it to different virtual
addresses during a context switch?
Or is this a static property at task launch?
-Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: "Chatre, Reinette" <reinette.chatre@intel.com>,
"tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
'James Morse' <james.morse@arm.com>,
"misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>
Subject: RE: About add an A64FX cache control function into resctrl
Date: Thu, 29 Apr 2021 17:50:20 +0000 [thread overview]
Message-ID: <49cdd0b707194148915e2efe2ab5d707@intel.com> (raw)
In-Reply-To: <14ddf86b-89e1-ba26-b684-f3d5d5f8ade7@intel.com>
>>>> [Sector cache function]
>>>> The sector cache function split cache into multiple sectors and
>>>> control them separately. It is implemented on the L1D cache and
>>>> L2 cache in the A64FX processor and can be controlled individually
>>>> for L1D cache and L2 cache. A64FX has no L3 cache. Each L1D cache and
>>>> L2 cache has 4 sectors. Which L1D sector is used is specified by the
>>>> value of [57:56] bits of address, how many ways of sector are
>>>> specified by the value of register (IMP_SCCR_L1_EL0).
>>>> Which L2 sector is used is specified by the value of [56] bits of
>>>> address, and how many ways of sector are specified by value of
>>>> register (IMP_SCCR_ASSIGN_EL1, IMP_SCCR_SET0_L2_EL1,
>>>> IMP_SCCR_SET1_L2_EL1).
Are A64FX binaries position independent? I.e. could the OS reassign
a running task to a different sector by remapping it to different virtual
addresses during a context switch?
Or is this a static property at task launch?
-Tony
next prev parent reply other threads:[~2021-04-29 17:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 5:46 About add an A64FX cache control function into resctrl tan.shaopeng
2021-04-09 5:46 ` tan.shaopeng
2021-04-21 8:37 ` tan.shaopeng
2021-04-21 8:37 ` tan.shaopeng
2021-04-21 16:39 ` Reinette Chatre
2021-04-21 16:39 ` Reinette Chatre
2021-04-23 8:10 ` tan.shaopeng
2021-04-23 8:10 ` tan.shaopeng
2021-04-28 8:16 ` tan.shaopeng
2021-04-28 8:16 ` tan.shaopeng
2021-04-29 17:42 ` Reinette Chatre
2021-04-29 17:42 ` Reinette Chatre
2021-04-29 17:50 ` Luck, Tony [this message]
2021-04-29 17:50 ` Luck, Tony
2021-04-30 11:46 ` Catalin Marinas
2021-04-30 11:46 ` Catalin Marinas
2021-05-17 8:29 ` tan.shaopeng
2021-05-17 8:29 ` tan.shaopeng
2021-05-17 8:31 ` tan.shaopeng
2021-05-17 8:31 ` tan.shaopeng
2021-05-21 17:44 ` Reinette Chatre
2021-05-21 17:44 ` Reinette Chatre
2021-05-25 8:45 ` tan.shaopeng
2021-05-25 8:45 ` tan.shaopeng
2021-05-26 17:36 ` Reinette Chatre
2021-05-26 17:36 ` Reinette Chatre
2021-05-27 8:45 ` tan.shaopeng
2021-05-27 8:45 ` tan.shaopeng
2021-07-07 11:26 ` tan.shaopeng
2021-07-07 11:26 ` tan.shaopeng
2021-07-16 0:49 ` tan.shaopeng
2021-07-16 0:49 ` tan.shaopeng
2021-07-19 23:25 ` Reinette Chatre
2021-07-19 23:25 ` Reinette Chatre
2021-07-21 8:10 ` tan.shaopeng
2021-07-21 8:10 ` tan.shaopeng
2021-07-21 23:39 ` Reinette Chatre
2021-07-21 23:39 ` Reinette Chatre
2021-05-17 8:37 ` tan.shaopeng
2021-05-17 8:37 ` 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=49cdd0b707194148915e2efe2ab5d707@intel.com \
--to=tony.luck@intel.com \
--cc=fenghua.yu@intel.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=reinette.chatre@intel.com \
--cc=tan.shaopeng@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.