Skip to contentSkip to conversation

SUPPORT.md: extend security support for hosts to 12 TiB of memory

PATCH Superseded Jan Beulich 2 participants 5 messages Apr 6, 2022 – Apr 27, 2022

v1 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 SUPPORT.md: extend security support for hosts to 12 TiB of memory

c49ee0329ff3 ("SUPPORT.md: limit security support for hosts with very much memory"), as a result of XSA-385, restricted security support to 8 TiB of host memory. Extend this to 12 TiB, putting in place a guest restriction to 8 TiB in exchange.

A 12 TiB host was certified successfully for use with Xen 4.14 as per
https://www.suse.com/nbswebapp/yesBulletin.jsp?bulletinNumber=150753.
This in particular included running as many guests (2 TiB each) as possible in parallel, to actually prove that all the memory can be used like this. It may be relevant to note that the Optane memory there was used in memory-only mode, with DRAM acting as cache.

SUPPORT.md +9 -1
@@ -50,7 +50,7 @@ For the Cortex A57 r0p0 - r1p1, see Erra
 
 ### Physical Memory
 
-    Status: Supported up to 8 TiB
+    Status: Supported up to 12 TiB
 
 Hosts with more memory are supported, but not security supported.
 
@@ -121,6 +121,14 @@ ARM only has one guest type at the momen
 
     Status: Supported
 
+## Guest Limits
+
+### Memory
+
+    Status: Supported up to 8 TiB
+
+Guests with more memory are supported, but not security supported.
+
 ## Hypervisor file system
 
 ### Build info
#1 lore raw

Hi,

Quoted 4 lines · Jan Beulich

c49ee0329ff3 ("SUPPORT.md: limit security support for hosts with very much memory"), as a result of XSA-385, restricted security support to 8 TiB of host memory. Extend this to 12 TiB, putting in place a guest restriction to 8 TiB in exchange.

And this is even without CONFIG_BIGMEM?

Quoted 13 lines

A 12 TiB host was certified successfully for use with Xen 4.14 as per
https://www.suse.com/nbswebapp/yesBulletin.jsp?bulletinNumber=150753.
This in particular included running as many guests (2 TiB each) as possible in parallel, to actually prove that all the memory can be used like this. It may be relevant to note that the Optane memory there was used in memory-only mode, with DRAM acting as cache.

SUPPORT.md For the Cortex A57 r0p0 - r1p1, see Erra · line 53

Quoted 5 lines
SUPPORT.md +1 -1
@@ -50,7 +50,7 @@ For the Cortex A57 r0p0 - r1p1, see Erra
 
  ### Physical Memory
 
-    Status: Supported up to 8 TiB
+    Status: Supported up to 12 TiB

I am afraid this limit is going to be too high for Arm. Even the previous one was technically incorrect. From [1], it should be:
- 5TB for arm64
- 16GB for arm32

SUPPORT.md ARM only has one guest type at the momen · line 128

Quoted 12 lines
SUPPORT.md +5 -0
  Hosts with more memory are supported, but not security supported.
 
@@ -121,6 +121,14 @@ ARM only has one guest type at the momen
 
      Status: Supported
 
+## Guest Limits
+
+### Memory
+
+    Status: Supported up to 8 TiB

For Arm, this should be limited to 1TB for arm64 and 16GB for arm32.

SUPPORT.md ARM only has one guest type at the momen · line 130

Quoted 2 lines
SUPPORT.md +2 -0
+
+Guests with more memory are supported, but not security supported.

d->max_pages is a 32-bit value. So Xen can effectively only support up to 16TB of memory. AFAICT, it would require quite a bit rework to lift that limit. So I think it would be better to spell out the upper limit.

Cheers,

[1] https://wiki.xenproject.org/wiki/Xen_Project_Release_Features

Signature · 1 line
Julien Grall
#2 lore raw
Quoted 7 lines · Julien Grall
Quoted 4 lines · Jan Beulich

c49ee0329ff3 ("SUPPORT.md: limit security support for hosts with very much memory"), as a result of XSA-385, restricted security support to 8 TiB of host memory. Extend this to 12 TiB, putting in place a guest restriction to 8 TiB in exchange.

And this is even without CONFIG_BIGMEM?

Yes. BIGMEM only matters when memory extends past the 16 TiB boundary (i.e. when frame numbers with ore than 32 significant bits appear).

Quoted 6 lines
Quoted 6 lines
SUPPORT.md +0 -0
@@ -50,7 +50,7 @@ For the Cortex A57 r0p0 - r1p1, see Erra
 
  ### Physical Memory
 
Quoted 7 lines

SUPPORT.md For the Cortex A57 r0p0 - r1p1, see Erra · line 53

Quoted 2 lines
SUPPORT.md +1 -1
-    Status: Supported up to 8 TiB
+    Status: Supported up to 12 TiB

I am afraid this limit is going to be too high for Arm. Even the previous one was technically incorrect. From [1], it should be:
- 5TB for arm64
- 16GB for arm32

May I ask that you submit a patch correcting this, and I'll rebase on top of that? I can't really fit such an adjustment under the umbrella of the title and purpose of this change.

Quoted 11 lines

SUPPORT.md ARM only has one guest type at the momen · line 128

Quoted 9 lines
SUPPORT.md +5 -0
@@ -121,6 +121,14 @@ ARM only has one guest type at the momen
 
      Status: Supported
 
+## Guest Limits
+
+### Memory
+
+    Status: Supported up to 8 TiB

For Arm, this should be limited to 1TB for arm64 and 16GB for arm32.

Sure, will do.

Quoted 6 lines

SUPPORT.md ARM only has one guest type at the momen · line 130

Quoted 2 lines
SUPPORT.md +2 -0
+
+Guests with more memory are supported, but not security supported.

d->max_pages is a 32-bit value. So Xen can effectively only support up to 16TB of memory. AFAICT, it would require quite a bit rework to lift that limit. So I think it would be better to spell out the upper limit.

Same here.

Jan

#3 lore raw

Hi Jan,

Quoted 11 lines · Jan Beulich
Quoted 7 lines · Julien Grall
Quoted 4 lines · Jan Beulich

c49ee0329ff3 ("SUPPORT.md: limit security support for hosts with very much memory"), as a result of XSA-385, restricted security support to 8 TiB of host memory. Extend this to 12 TiB, putting in place a guest restriction to 8 TiB in exchange.

And this is even without CONFIG_BIGMEM?

Yes. BIGMEM only matters when memory extends past the 16 TiB boundary (i.e. when frame numbers with ore than 32 significant bits appear).

Thanks for the confirmation!

Quoted 15 lines
Quoted 7 lines
Quoted 7 lines
SUPPORT.md +0 -0
@@ -50,7 +50,7 @@ For the Cortex A57 r0p0 - r1p1, see Erra
 
   ### Physical Memory
 
Quoted 7 lines

SUPPORT.md For the Cortex A57 r0p0 - r1p1, see Erra · line 53

Quoted 2 lines
SUPPORT.md +1 -1
-    Status: Supported up to 8 TiB
+    Status: Supported up to 12 TiB

I am afraid this limit is going to be too high for Arm. Even the previous one was technically incorrect. From [1], it should be:
- 5TB for arm64
- 16GB for arm32

Quoted 3 lines

May I ask that you submit a patch correcting this, and I'll rebase on top of that? I can't really fit such an adjustment under the umbrella of the title and purpose of this change.

Sure. I will submit one soon.

Cheers,

Signature · 1 line
Julien Grall
#4 lore raw

Hi,

Quoted 28 lines · Julien Grall
Quoted 11 lines · Jan Beulich
Quoted 7 lines · Julien Grall
Quoted 4 lines · Jan Beulich

c49ee0329ff3 ("SUPPORT.md: limit security support for hosts with very much memory"), as a result of XSA-385, restricted security support to 8 TiB of host memory. Extend this to 12 TiB, putting in place a guest restriction to 8 TiB in exchange.

And this is even without CONFIG_BIGMEM?

Yes. BIGMEM only matters when memory extends past the 16 TiB boundary (i.e. when frame numbers with ore than 32 significant bits appear).

Thanks for the confirmation!

Quoted 13 lines
Quoted 12 lines

SUPPORT.md For the Cortex A57 r0p0 - r1p1, see Erra · line 51

Quoted 7 lines
SUPPORT.md +1 -1
@@ -50,7 +50,7 @@ For the Cortex A57 r0p0 - r1p1, see Erra
    ### Physical Memory
-    Status: Supported up to 8 TiB
+    Status: Supported up to 12 TiB

I am afraid this limit is going to be too high for Arm. Even the previous one was technically incorrect. From [1], it should be:
    - 5TB for arm64
    - 16GB for arm32

Quoted 5 lines
Quoted 3 lines

May I ask that you submit a patch correcting this, and I'll rebase on top of that? I can't really fit such an adjustment under the umbrella of the title and purpose of this change.

Sure. I will submit one soon.

I have submitted a patch: https://lore.kernel.org/xen-devel/[email protected]/T/#u

Cheers,

Signature · 1 line
Julien Grall