summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorMatt Turner <mattst88@gmail.com>2026-10-07 23:24:06 -0400
committerMagnus Lindholm <linmag7@gmail.com>2026-10-18 00:44:44 +0200
commit5cea79aacfcf677fd9e62e4efad0413be51665c9 (patch)
treecb6a478cc3cfe89288038cd4da3e2db65f859efc /tools/perf/scripts/python
parent4bef20bbb9e02568a009efa4d404ce2621289be5 (diff)
downloadlinux-5cea79aacfcf677fd9e62e4efad0413be51665c9.tar.gz
linux-5cea79aacfcf677fd9e62e4efad0413be51665c9.zip
alpha: describe the PTE read and write enable bits
The comments on _PAGE_KRE and _PAGE_URE said only "xxx". Describe the four enable bits as the Alpha Linux PTE defines them, in Table 22-3 of the Alpha Architecture Reference Manual: kernel and user read enable in bits 8 and 9, kernel and user write enable in bits 12 and 13, with bits <11:10> and <15:14> reserved. There are only two processor modes, user and kernel (section 22.5.1). Linux uses the read enables as its accessed bit and the write enables as its dirty bit, so say which of __ACCESS_BITS and __DIRTY_BITS each one belongs to. The names differ from what the hardware calls those bits on the 21264. Its PALcode loads the PTE unchanged into DTB_PTE (21264/EV67 Hardware Reference Manual, section 6.9), where bits 9 and 13 are the Executive read and write enables (Figure 5-27), Executive being mode 1 of the four the processor implements (Table 5-5). That is a detail below the PALcode interface, and it is also the layout of the OpenVMS PTE in Table 11-2, which is not the one Linux uses. No functional change. Suggested-by: Magnus Lindholm <linmag7@gmail.com> Signed-off-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Magnus Lindholm <linmag7@gmail.com> Link: https://lore.kernel.org/r/20261007-alpha-hugepages-v2-3-8e108af2d961@gmail.com Signed-off-by: Magnus Lindholm <linmag7@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions