This is a collection of Intel®’ IA32® Software Developer's Manuals (URL of the day) and AMD' AMD64 Architecture Programmer's Manual together with the related specifications, application notes, white papers, and change logs. The collection aims to keep all available revisions. It was originally created by Michal Necasek, see OS/2 Museum.

If you have a public document, related to the IA32® specifications and missing from the collection, please mail it to me. The content of this URL and all sub-ULRs is available for convenient bulk download by rsync x86docs password "" (empty).

MPAMCFG_EN, MPAM Partition Configuration Enable Register

The MPAMCFG_EN characteristics are:

Purpose

Enables a PARTID configuration as set in other MPAMCFG registers.

Configuration

The power domain of MPAMCFG_EN is IMPLEMENTATION DEFINED.

This register is present only when (FEAT_MPAMv0p1 is implemented or FEAT_MPAMv1p1 is implemented) and MPAMF_IDR.HAS_ENDIS == '1'. Otherwise, direct accesses to MPAMCFG_EN are RES0.

If FEAT_MPAMv0p1 or FEAT_MPAMv1p1 is implemented, the following statements apply:

• MPAMCFG_EN_s enables a Secure PARTID.

• MPAMCFG_EN_ns enables a Non-secure PARTID.

• If FEAT_RME is implemented, the following statements also apply:

  • MPAMCFG_EN_rl enables a Realm PARTID.

  • MPAMCFG_EN_rt enables a Root PARTID.

The power and reset domain of each MSC component is specific to that component.

Attributes

MPAMCFG_EN is a 32-bit register.

Field descriptions

Bits [31:16]

PARTID, bits [15:0]

Accessing MPAMCFG_EN

If both FEAT_MPAM and FEAT_RME are implemented, the following statements apply:

• In a system that supports Secure, Non-secure, Root, and Realm memory maps, there must be MPAM feature pages in all four address maps:

• MPAMCFG_EN_s must only be accessible from the Secure MPAM feature page.

• MPAMCFG_EN_ns must only be accessible from the Non-secure MPAM feature page.

• MPAMCFG_EN_rt must only be accessible from the Root MPAM feature page.

• MPAMCFG_EN_rl must only be accessible from the Realm MPAM feature page.

• MPAMCFG_EN_s, MPAMCFG_EN_ns, MPAMCFG_EN_rt, and MPAMCFG_EN_rl must be separate registers:

• The Secure instance (MPAMCFG_EN_s) accesses the PARTID enable used for Secure PARTIDs.

• The Non-secure instance (MPAMCFG_EN_ns) accesses the PARTID enable used for Non-secure PARTIDs.

• The Root instance (MPAMCFG_EN_rt) accesses the PARTID enable used for Root PARTIDs.

• The Realm instance (MPAMCFG_EN_rl) accesses the PARTID enable used for Realm PARTIDs.

When RIS is implemented, loads and stores to MPAMCFG_EN access the PARTID enable configuration settings for the PARTID enable resource instance selected by MPAMCFG_PART_SEL.RIS and the PARTID selected by MPAMCFG_PART_SEL.PARTID_SEL.

When RIS is not implemented, loads and stores to MPAMCFG_EN access the PARTID enable configuration settings for the PARTID selected by MPAMCFG_PART_SEL.PARTID_SEL.

When PARTID narrowing is implemented, loads and stores to MPAMCFG_EN access the PARTID enable configuration settings for the internal PARTID selected by MPAMCFG_PART_SEL.PARTID_SEL, and MPAMCFG_PART_SEL.INTERNAL must be 1.

When PARTID narrowing is not implemented, loads and stores to MPAMCFG_EN access the PARTID enable configuration settings for the request PARTID selected by MPAMCFG_PART_SEL.PARTID_SEL, and MPAMCFG_PART_SEL.INTERNAL must be 0.

MPAMCFG_EN can be accessed through the memory-mapped interfaces:

When FEAT_MPAMv1p1 is implemented or FEAT_MPAMv0p1 is implemented, accesses to this register are WO/RAZ.

When FEAT_MPAMv1p1 is implemented or FEAT_MPAMv0p1 is implemented, accesses to this register are WO/RAZ.

When FEAT_RME is implemented and (FEAT_MPAMv1p1 is implemented or FEAT_MPAMv0p1 is implemented), accesses to this register are WO/RAZ.

When FEAT_RME is implemented and (FEAT_MPAMv1p1 is implemented or FEAT_MPAMv0p1 is implemented), accesses to this register are WO/RAZ.

2026-03-26 20:27:25, 2026-03_rel

Copyright © 2010-2026 Arm Limited or its affiliates. All rights reserved. This document is Non-Confidential.