From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 2B3A6986405 for ; Thu, 12 Aug 2021 13:32:09 +0000 (UTC) From: David Hildenbrand Date: Thu, 12 Aug 2021 15:31:50 +0200 Message-Id: <20210812133150.36146-3-david@redhat.com> In-Reply-To: <20210812133150.36146-1-david@redhat.com> References: <20210812133150.36146-1-david@redhat.com> MIME-Version: 1.0 Subject: [virtio-comment] [PATCH v1 2/2] virtio-mem: describe interaction with memory properties Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable To: virtio-comment@lists.oasis-open.org Cc: David Hildenbrand List-ID: Let's describe how we expect the interaction with memory properties that might be available on a specific platform for ordinary system RAM. This is primarily a preparation for s390x support, which provides storage keys and may provide storage attributes, depending on the system configuration. Signed-off-by: David Hildenbrand --- virtio-mem.tex | 71 ++++++++++++++++++++++++++++++++++---------------- 1 file changed, 49 insertions(+), 22 deletions(-) diff --git a/virtio-mem.tex b/virtio-mem.tex index c4dd0d0..a1057cd 100644 --- a/virtio-mem.tex +++ b/virtio-mem.tex @@ -32,6 +32,16 @@ \section{Memory Device}\label{sec:Device Types / Memory = Device} expose plugged memory blocks to the operating system as system RAM, available for the page allocator. =20 +Some platforms provide memory properties for system RAM that are usually +queried and modified using special CPU instructions. Memory properties mig= ht +be implicitly queried or modified on memory access. Memory properties can +include advanced memory protection, access and change indication, or memor= y +usage indication relevant in virtualized environments. \footnote{For examp= le, +s390x provides storage keys for each 4 KiB page and may, depending on the +configuration, provide storage attributes for each 4 KiB page.} The device +provides the exact same properties with the exact same semantics for +plugged device memory as available for ordinary RAM in the same configurat= ion. + \subsection{Device ID}\label{sec:Device Types / Memory Device / Device ID} 24 =20 @@ -47,7 +57,8 @@ \subsection{Feature bits}\label{sec:Device Types / Memory= Device / Feature bits} \item[VIRTIO_MEM_F_ACPI_PXM (0)] The field \field{node_id} in the device configuration is valid and corresponds to an ACPI PXM. \item[VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE (1)] The driver MUST NOT access -unplugged memory. +unplugged memory. \footnote{This feature is expected to be enabled on plat= forms +with memory properties that might get modified implicitly on memory access= .} \end{description} =20 \subsection{Device configuration layout}\label{sec:Device Types / Memory D= evice / Device configuration layout} @@ -159,8 +170,8 @@ \subsection{Device Initialization}\label{Device Types /= Memory Device / Device I =20 The device MUST NOT change the state of memory blocks during device reset. =20 -The device MUST NOT change the content of plugged memory blocks during -device reset. +The device MUST NOT modify memory or memory properties of plugged memory +blocks during device reset. =20 \subsection{Device Operation}\label{sec:Device Types / Memory Device / Dev= ice Operation} =20 @@ -223,23 +234,30 @@ \subsection{Device Operation}\label{sec:Device Types = / Memory Device / Device Op =20 \drivernormative{\subsubsection}{Device Operation}{Device Types / Memory D= evice / Device Operation} =20 -The driver MUST NOT write to unplugged memory blocks. +The driver MUST NOT write memory or modify memory properties of +unplugged memory blocks. =20 -The driver MUST NOT read from unplugged memory blocks outside -\field{usable_region_size}. +The driver MUST NOT read memory or query memory properties of unplugged +memory blocks outside \field{usable_region_size}. =20 Without VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE, the driver SHOULD NOT read -memory of unplugged memory blocks inside \field{usable_region_size}. +memory or query memory properties of unplugged memory blocks inside +\field{usable_region_size}. =20 -With VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE, the driver MUST NOT read memory = of -unplugged memory blocks. +With VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE, the driver MUST NOT read memory +or query memory properties of unplugged memory blocks inside +\field{usable_region_size}. =20 -The driver MUST NOT request to unplug memory blocks while the memory is -still in use. +The driver MUST NOT request unplug of memory blocks while corresponding me= mory +or memory properties are still in use. =20 The driver SHOULD initialize memory blocks after plugging them, the conten= t is undefined. =20 +The driver SHOULD initialize memory properties of memory blocks after plug= ging +them if it cannot deal with either the default settings or the previous +setting. + The driver SHOULD react to resize requests from the device (\field{requested_size} in the device configuration changed) by (un)plugging memory blocks. @@ -253,25 +271,34 @@ \subsection{Device Operation}\label{sec:Device Types = / Memory Device / Device Op =20 \devicenormative{\subsubsection}{Device Operation}{Device Types / Memory D= evice / Device Operation} =20 -The device MAY change the content of unplugged memory blocks at any time. +The device MUST provide the exact same memory properties with the exact sa= me +semantics for device memory the platform provides in the same configuratio= n for +ordinary RAM. + +The device MAY modify memory or reset memory properties to defaults of unp= lugged +memory blocks at any time. =20 -The device MUST NOT change the content of plugged memory blocks. +The device MUST NOT modify memory or memory properties of plugged memory +blocks. =20 Without VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE, the device MUST allow the CPU= to -read memory of unplugged memory blocks inside \field{usable_region_size}. -\footnote{To allow for simplified dumping of memory. The CPU is expected t= o -copy such memory to another location before starting DMA.} +read memory or query memory properties of unplugged memory blocks inside +\field{usable_region_size}. \footnote{To allow for simplified dumping of +memory. The CPU is expected to copy such memory to another location before +starting DMA.} =20 With VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE, the device MAY allow the CPU to -read memory of unplugged memory blocks inside \field{usable_region_size}. +read memory or query memory properties of unplugged memory blocks inside +\field{usable_region_size}. =20 -The device MAY allow to read from unplugged memory blocks inside the -usable device-managed region via DMA. +The device MAY allow to read memory or query memory properties of unplugge= d +memory blocks inside \field{usable_region_size} via DMA. =20 -The device MAY allow to read from unplugged memory blocks outside -the usable device-managed region. +The device MAY allow to read memory or query memory properties of unplugge= d +memory blocks outside \field{usable_region_size} via DMA. =20 -The device MAY allow to write to unplugged memory blocks. +The device MAY allow to write memory or modify memory properties of unplug= ged +memory blocks. =20 The device MAY change the state of memory blocks during system resets. =20 --=20 2.31.1 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lis= ts Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/