swiotlb: Adjust SWIOTBL bounce buffer size for SEV guests.
Subsystems (3)
PATCH v6 1/1 swiotlb: Adjust SWIOTBL bounce buffer size for SEV guests.
From: Ashish Kalra <[email protected]>
For SEV, all DMA to and from guest has to use shared (un-encrypted) pages. SEV uses SWIOTLB to make this happen without requiring changes to device drivers. However, depending on workload being run, the default 64MB of SWIOTLB might not be enough and SWIOTLB may run out of buffers to use for DMA, resulting in I/O errors and/or performance degradation for high I/O workloads.
Increase the default size of SWIOTLB for SEV guests using a minimum value of 128MB and a maximum value of 512MB, determining on amount of provisioned guest memory.
Using late_initcall() interface to invoke swiotlb_adjust() does not work as the size adjustment needs to be done before mem_encrypt_init() and reserve_crashkernel() which use the allocated SWIOTLB buffer size, hence calling it explicitly from setup_arch().
The SWIOTLB default size adjustment is added as an architecture specific interface/callback to allow architectures such as those supporting memory encryption to adjust/expand SWIOTLB size for their use.
v5 fixed build errors and warnings as
--- arch/x86/kernel/setup.c | 2 ++ arch/x86/mm/mem_encrypt.c | 32 ++++++++++++++++++++++++++++++++ include/linux/swiotlb.h | 6 ++++++ kernel/dma/swiotlb.c | 24 ++++++++++++++++++++++++ 4 files changed, 64 insertions(+)
arch/x86/kernel/setup.c +2 -0
@@ -1166,6 +1166,8 @@ void __init setup_arch(char **cmdline_p)if (boot_cpu_has (X86_FEATURE_GBPAGES ))hugetlb_cma_reserve (PUD_SHIFT -PAGE_SHIFT ); +swiotlb_adjust (); +/* * Reserve memory for crash kernel after SRAT is parsed so that it * won't consume hotpluggable memory.
arch/x86/mm/mem_encrypt.c +32 -0
@@ -490,6 +490,38 @@ static void print_mem_encrypt_feature_info(void) }/* Architecture __weak replacement functions */ +unsigned long __init arch_swiotlb_adjust (unsigned long iotlb_default_size) +{ +unsigned long size =0 ; + +/* +* For SEV, all DMA has to occur via shared/unencrypted pages. +* SEV uses SWOTLB to make this happen without changing device +* drivers. However, depending on the workload being run, the +* default 64MB of SWIOTLB may not be enough & SWIOTLB may +* run out of buffers for DMA, resulting in I/O errors and/or +* performance degradation especially with high I/O workloads. +* Increase the default size of SWIOTLB for SEV guests using +* a minimum value of 128MB and a maximum value of 512MB, +* depending on amount of provisioned guest memory. +*/ +if (sev_active ()) { +phys_addr_t total_mem =memblock_phys_mem_size (); + +if (total_mem <=SZ_1G ) + size =max (iotlb_default_size, (unsigned long )SZ_128M ); +else if (total_mem <=SZ_4G ) + size =max (iotlb_default_size, (unsigned long )SZ_256M ); +else + size =max (iotlb_default_size, (unsigned long )SZ_512M ); + +pr_info ("SWIOTLB bounce buffer size adjusted to %luMB for SEV platform" , + size >>20 ); + } + +return size; +} +void __init mem_encrypt_init (void ) {if (!sme_me_mask)
include/linux/swiotlb.h +6 -0
@@ -33,6 +33,7 @@ extern void swiotlb_init(int verbose);int swiotlb_init_with_tbl (char *tlb,unsigned long nslabs,int verbose);extern unsigned long swiotlb_nr_tbl (void );unsigned long swiotlb_size_or_default (void ); +unsigned long __init arch_swiotlb_adjust (unsigned long size);extern int swiotlb_late_init_with_tbl (char *tlb,unsigned long nslabs);extern void __init swiotlb_update_mem_attributes (void );
@@ -80,6 +81,7 @@ void __init swiotlb_exit(void);unsigned int swiotlb_max_segment (void );size_t swiotlb_max_mapping_size (struct device *dev);bool is_swiotlb_active (void ); +void __init swiotlb_adjust (void );#else #define swiotlb_force SWIOTLB_NO_FORCEstatic inline bool is_swiotlb_buffer (phys_addr_t paddr)
@@ -102,6 +104,10 @@ static inline bool is_swiotlb_active(void) {return false; } + +static inline void swiotlb_adjust (void ) +{ +}#endif /* CONFIG_SWIOTLB */ extern void swiotlb_print_info (void );
kernel/dma/swiotlb.c +24 -0
@@ -163,6 +163,30 @@ unsigned long swiotlb_size_or_default(void)return size ? size : (IO_TLB_DEFAULT_SIZE ); } +unsigned long __init __weak arch_swiotlb_adjust (unsigned long size) +{ +return 0 ; +} + +void __init swiotlb_adjust (void ) +{ +unsigned long size; + +/* +* If swiotlb parameter has not been specified, give a chance to +* architectures such as those supporting memory encryption to +* adjust/expand SWIOTLB size for their use. +*/ +if (!io_tlb_nslabs) { + size =arch_swiotlb_adjust (IO_TLB_DEFAULT_SIZE ); +if (size) { + size =ALIGN (size,1 <<IO_TLB_SHIFT ); + io_tlb_nslabs = size >>IO_TLB_SHIFT ; + io_tlb_nslabs =ALIGN (io_tlb_nslabs,IO_TLB_SEGSIZE ); + } + } +} +void swiotlb_print_info (void ) {unsigned long bytes = io_tlb_nslabs <<IO_TLB_SHIFT ;
Signature · 6 lines
2.17.1 _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
Borislav Petkov
maintainerQuoted 9 lines · Ashish Kalra
From: Ashish Kalra <[email protected]>
For SEV, all DMA to and from guest has to use shared (un-encrypted) pages. SEV uses SWIOTLB to make this happen without requiring changes to device drivers. However, depending on workload being run, the default 64MB of SWIOTLB might not be enough and SWIOTLB may run out of buffers to use for DMA, resulting in I/O errors and/or performance degradation for high I/O workloads.
Quoted 3 lines
Increase the default size of SWIOTLB for SEV guests using a minimum value of 128MB and a maximum value of 512MB, determining on amount of provisioned guest memory.
That sentence needs massaging.
Quoted 4 lines
Using
late_initcall()interface to invokeswiotlb_adjust()does not work as the size adjustment needs to be done beforemem_encrypt_init()andreserve_crashkernel()which use the allocated SWIOTLB buffer size, hence calling it explicitly fromsetup_arch().
"hence call it ... "
Quoted 2 lines
The SWIOTLB default size adjustment is added as an architecture specific
"... is added... " needs to be "Add ..."
Quoted 32 lines
interface/callback to allow architectures such as those supporting memory encryption to adjust/expand SWIOTLB size for their use.
v5 fixed build errors and warnings as
Reported-by kbuild test robot <[email protected]>Signed-off-by Ashish Kalra <[email protected]>--- arch/x86/kernel/setup.c | 2 ++ arch/x86/mm/mem_encrypt.c | 32 ++++++++++++++++++++++++++++++++ include/linux/swiotlb.h | 6 ++++++ kernel/dma/swiotlb.c | 24 ++++++++++++++++++++++++ 4 files changed, 64 insertions(+)arch/x86/kernel/setup.c +2
-0@@ -1166,6 +1166,8 @@ void __init setup_arch(char **cmdline_p)if (boot_cpu_has (X86_FEATURE_GBPAGES ))hugetlb_cma_reserve (PUD_SHIFT -PAGE_SHIFT ); +swiotlb_adjust (); +/* * Reserve memory for crash kernel after SRAT is parsed so that it * won't consume hotpluggable memory. arch/x86/mm/mem_encrypt.c +0
-0
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 495
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +3
-0@@ -490,6 +490,38 @@ static void print_mem_encrypt_feature_info(void) }/* Architecture __weak replacement functions */ +unsigned long __init arch_swiotlb_adjust (unsigned long iotlb_default_size) +{ +unsigned long size =0 ;
unsigned long size = iotlb_default_size;
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 501
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +6
-0+ +/* +* For SEV, all DMA has to occur via shared/unencrypted pages. +* SEV uses SWOTLB to make this happen without changing device +* drivers. However, depending on the workload being run, the +* default 64MB of SWIOTLB may not be enough & SWIOTLB may
^
Use words pls, not "&".
Quoted 7 lines
arch/x86/mm/mem_encrypt.c +7
-0+* run out of buffers for DMA, resulting in I/O errors and/or +* performance degradation especially with high I/O workloads. +* Increase the default size of SWIOTLB for SEV guests using +* a minimum value of 128MB and a maximum value of 512MB, +* depending on amount of provisioned guest memory. +*/ +if (sev_active ()) {
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 518
Quoted 10 lines
arch/x86/mm/mem_encrypt.c +10
-0+phys_addr_t total_mem =memblock_phys_mem_size (); + +if (total_mem <=SZ_1G ) + size =max (iotlb_default_size, (unsigned long )SZ_128M ); +else if (total_mem <=SZ_4G ) + size =max (iotlb_default_size, (unsigned long )SZ_256M ); +else + size =max (iotlb_default_size, (unsigned long )SZ_512M ); + + pr_info("SWIOTLB bounce buffer size adjusted to %luMB for SEV platform",
just "... for SEV" - no need for "platform".
...
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 168
Quoted 11 lines
kernel/dma/swiotlb.c +3
-0@@ -163,6 +163,30 @@ unsigned long swiotlb_size_or_default(void)return size ? size : (IO_TLB_DEFAULT_SIZE ); } +unsigned long __init __weak arch_swiotlb_adjust (unsigned long size) +{ +return 0 ;
That, of course, needs to return size, not 0.
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 179
Quoted 11 lines
kernel/dma/swiotlb.c +11
-0+} + +void __init swiotlb_adjust (void ) +{ +unsigned long size; + +/* +* If swiotlb parameter has not been specified, give a chance to +* architectures such as those supporting memory encryption to +* adjust/expand SWIOTLB size for their use. +*/
And when you preset the function-local argument "size" with the size coming in as the size argument of arch_swiotlb_adjust()...
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 182
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+if (!io_tlb_nslabs) { + size =arch_swiotlb_adjust (IO_TLB_DEFAULT_SIZE ); +if (size) {
... you don't have to do if (size) here either but simply use size to compute io_tlb_nslabs, I'd say.
Thx.
Signature · 8 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommuQuoted 80 lines · Borislav Petkov
Quoted 9 lines · Ashish Kalra
From: Ashish Kalra <[email protected]>
For SEV, all DMA to and from guest has to use shared (un-encrypted) pages. SEV uses SWIOTLB to make this happen without requiring changes to device drivers. However, depending on workload being run, the default 64MB of SWIOTLB might not be enough and SWIOTLB may run out of buffers to use for DMA, resulting in I/O errors and/or performance degradation for high I/O workloads.
Quoted 3 lines
Increase the default size of SWIOTLB for SEV guests using a minimum value of 128MB and a maximum value of 512MB, determining on amount of provisioned guest memory.
That sentence needs massaging.
Quoted 4 lines
Using
late_initcall()interface to invokeswiotlb_adjust()does not work as the size adjustment needs to be done beforemem_encrypt_init()andreserve_crashkernel()which use the allocated SWIOTLB buffer size, hence calling it explicitly fromsetup_arch()."hence call it ... "
Quoted 2 lines
The SWIOTLB default size adjustment is added as an architecture specific
"... is added... " needs to be "Add ..."
Quoted 32 lines
interface/callback to allow architectures such as those supporting memory encryption to adjust/expand SWIOTLB size for their use.
v5 fixed build errors and warnings as
Reported-by kbuild test robot <[email protected]>Signed-off-by Ashish Kalra <[email protected]>--- arch/x86/kernel/setup.c | 2 ++ arch/x86/mm/mem_encrypt.c | 32 ++++++++++++++++++++++++++++++++ include/linux/swiotlb.h | 6 ++++++ kernel/dma/swiotlb.c | 24 ++++++++++++++++++++++++ 4 files changed, 64 insertions(+)arch/x86/kernel/setup.c +2
-0@@ -1166,6 +1166,8 @@ void __init setup_arch(char **cmdline_p)if (boot_cpu_has (X86_FEATURE_GBPAGES ))hugetlb_cma_reserve (PUD_SHIFT -PAGE_SHIFT ); +swiotlb_adjust (); +/* * Reserve memory for crash kernel after SRAT is parsed so that it * won't consume hotpluggable memory. arch/x86/mm/mem_encrypt.c +0
-0arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 495
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +3
-0@@ -490,6 +490,38 @@ static void print_mem_encrypt_feature_info(void) }/* Architecture __weak replacement functions */ +unsigned long __init arch_swiotlb_adjust (unsigned long iotlb_default_size) +{ +unsigned long size =0 ;unsigned long size = iotlb_default_size;arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 501
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +6
-0+ +/* +* For SEV, all DMA has to occur via shared/unencrypted pages. +* SEV uses SWOTLB to make this happen without changing device +* drivers. However, depending on the workload being run, the +* default 64MB of SWIOTLB may not be enough & SWIOTLB may ^Use words pls, not "&".
Quoted 13 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 514
Quoted 13 lines
arch/x86/mm/mem_encrypt.c +13
-0+* run out of buffers for DMA, resulting in I/O errors and/or +* performance degradation especially with high I/O workloads. +* Increase the default size of SWIOTLB for SEV guests using +* a minimum value of 128MB and a maximum value of 512MB, +* depending on amount of provisioned guest memory. +*/ +if (sev_active ()) { +phys_addr_t total_mem =memblock_phys_mem_size (); + +if (total_mem <=SZ_1G ) + size =max (iotlb_default_size, (unsigned long )SZ_128M ); +else if (total_mem <=SZ_4G ) + size =max (iotlb_default_size, (unsigned long )SZ_256M );
That is eating 128MB for 1GB, aka 12% of the guest memory allocated statically for this.
And for guests that are 2GB, that is 12% until it gets to 3GB when it is 8% and then 6% at 4GB.
I would prefer this to be based on your memory count, that is 6% of total memory. And then going forward we can allocate memory _after_ boot and then stich the late SWIOTLB pool and allocate on demand.
Quoted 17 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 518
Quoted 4 lines
arch/x86/mm/mem_encrypt.c +4
-0+else + size =max (iotlb_default_size, (unsigned long )SZ_512M ); + + pr_info("SWIOTLB bounce buffer size adjusted to %luMB for SEV platform",just "... for SEV" - no need for "platform".
...
Quoted 8 lines
kernel/dma/swiotlb.c +0
-0@@ -163,6 +163,30 @@ unsigned long swiotlb_size_or_default(void)return size ? size : (IO_TLB_DEFAULT_SIZE ); }
Quoted 5 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 168
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+unsigned long __init __weak arch_swiotlb_adjust (unsigned long size) +{ +return 0 ;That, of course, needs to return size, not 0.
This is not going to work for TDX. I think having a registration to SWIOTLB to have this function would be better going forward.
As in there will be a swiotlb_register_adjuster() which AMD SEV code can call at start, also TDX can do it (and other platforms).
Quoted 16 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 179
Quoted 12 lines
kernel/dma/swiotlb.c +11
-0+} + +void __init swiotlb_adjust (void ) +{ +unsigned long size; + +/* +* If swiotlb parameter has not been specified, give a chance to +* architectures such as those supporting memory encryption to +* adjust/expand SWIOTLB size for their use. +*/ And when you preset the function-local argument "size" with the size coming in as the size argument of
arch_swiotlb_adjust()...
Quoted 14 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 182
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+if (!io_tlb_nslabs) { + size =arch_swiotlb_adjust (IO_TLB_DEFAULT_SIZE ); +if (size) {... you don't have to do if (size) here either but simply use size to compute
io_tlb_nslabs, I'd say.Thx.
Signature · 4 lines
Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
Borislav Petkov
maintainerQuoted 5 lines · Konrad Rzeszutek Wilk
This is not going to work for TDX. I think having a registration to SWIOTLB to have this function would be better going forward.
As in there will be a
swiotlb_register_adjuster()which AMD SEV code can call at start, also TDX can do it (and other platforms).
Oh do tell. It doesn't need to adjust size?
Signature · 8 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommuQuoted 8 lines · Borislav Petkov
Quoted 5 lines · Konrad Rzeszutek Wilk
This is not going to work for TDX. I think having a registration to SWIOTLB to have this function would be better going forward.
As in there will be a
swiotlb_register_adjuster()which AMD SEV code can call at start, also TDX can do it (and other platforms).Oh do tell. It doesn't need to adjust size?
I am assuming that TDX is going to have the same exact issue that AMD SEV will have.
Are you recommending to have an unified x86 specific callback where we check if it:
- CPUID_AMD_SEV or CPUID_INTEL_TDX is set, and
- No vIOMMU present, then we adjust the size?
Quoted 6 lines
Signature · 5 lines
-- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
Borislav Petkov
maintainerQuoted 8 lines · Konrad Rzeszutek Wilk
I am assuming that TDX is going to have the same exact issue that AMD SEV will have.
Are you recommending to have an unified x86 specific callback where we check if it:
-
CPUID_AMD_SEVorCPUID_INTEL_TDXis set, and
- No vIOMMU present, then we adjust the size?
I'm thinking do it correct right now and when TDX appears on the horizon requesting this adjusted to TDX, then change it. Like we always do.
Signature · 8 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommuHello Konrad,
Quoted 97 lines · Konrad Rzeszutek Wilk
Quoted 80 lines · Borislav Petkov
Quoted 9 lines · Ashish Kalra
From: Ashish Kalra <[email protected]>
For SEV, all DMA to and from guest has to use shared (un-encrypted) pages. SEV uses SWIOTLB to make this happen without requiring changes to device drivers. However, depending on workload being run, the default 64MB of SWIOTLB might not be enough and SWIOTLB may run out of buffers to use for DMA, resulting in I/O errors and/or performance degradation for high I/O workloads.
Quoted 3 lines
Increase the default size of SWIOTLB for SEV guests using a minimum value of 128MB and a maximum value of 512MB, determining on amount of provisioned guest memory.
That sentence needs massaging.
Quoted 4 lines
Using
late_initcall()interface to invokeswiotlb_adjust()does not work as the size adjustment needs to be done beforemem_encrypt_init()andreserve_crashkernel()which use the allocated SWIOTLB buffer size, hence calling it explicitly fromsetup_arch()."hence call it ... "
Quoted 2 lines
The SWIOTLB default size adjustment is added as an architecture specific
"... is added... " needs to be "Add ..."
Quoted 32 lines
interface/callback to allow architectures such as those supporting memory encryption to adjust/expand SWIOTLB size for their use.
v5 fixed build errors and warnings as
Reported-by kbuild test robot <[email protected]>Signed-off-by Ashish Kalra <[email protected]>--- arch/x86/kernel/setup.c | 2 ++ arch/x86/mm/mem_encrypt.c | 32 ++++++++++++++++++++++++++++++++ include/linux/swiotlb.h | 6 ++++++ kernel/dma/swiotlb.c | 24 ++++++++++++++++++++++++ 4 files changed, 64 insertions(+)arch/x86/kernel/setup.c +2
-0@@ -1166,6 +1166,8 @@ void __init setup_arch(char **cmdline_p)if (boot_cpu_has (X86_FEATURE_GBPAGES ))hugetlb_cma_reserve (PUD_SHIFT -PAGE_SHIFT ); +swiotlb_adjust (); +/* * Reserve memory for crash kernel after SRAT is parsed so that it * won't consume hotpluggable memory. arch/x86/mm/mem_encrypt.c +0
-0arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 495
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +3
-0@@ -490,6 +490,38 @@ static void print_mem_encrypt_feature_info(void) }/* Architecture __weak replacement functions */ +unsigned long __init arch_swiotlb_adjust (unsigned long iotlb_default_size) +{ +unsigned long size =0 ;unsigned long size = iotlb_default_size;arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 501
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +6
-0+ +/* +* For SEV, all DMA has to occur via shared/unencrypted pages. +* SEV uses SWOTLB to make this happen without changing device +* drivers. However, depending on the workload being run, the +* default 64MB of SWIOTLB may not be enough & SWIOTLB may ^Use words pls, not "&".
Quoted 13 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 514
Quoted 13 lines
arch/x86/mm/mem_encrypt.c +13
-0+* run out of buffers for DMA, resulting in I/O errors and/or +* performance degradation especially with high I/O workloads. +* Increase the default size of SWIOTLB for SEV guests using +* a minimum value of 128MB and a maximum value of 512MB, +* depending on amount of provisioned guest memory. +*/ +if (sev_active ()) { +phys_addr_t total_mem =memblock_phys_mem_size (); + +if (total_mem <=SZ_1G ) + size =max (iotlb_default_size, (unsigned long )SZ_128M ); +else if (total_mem <=SZ_4G ) + size =max (iotlb_default_size, (unsigned long )SZ_256M );That is eating 128MB for 1GB, aka 12% of the guest memory allocated statically for this.
Quoted 8 lines
And for guests that are 2GB, that is 12% until it gets to 3GB when it is 8% and then 6% at 4GB.
I would prefer this to be based on your memory count, that is 6% of total memory. And then going forward we can allocate memory _after_ boot and then stich the late SWIOTLB pool and allocate on demand.
Ok.
As i mentioned earlier, the patch was initially based on using a % of guest memory, as below:
+#define SEV_ADJUST_SWIOTLB_SIZE_PERCENT 5
+#define SEV_ADJUST_SWIOTLB_SIZE_MAX (1UL << 30)
...
...
+ if (sev_active() && !io_tlb_nslabs) {
+ unsigned long total_mem = get_num_physpages() <<
+ PAGE_SHIFT;
+
+ default_size = total_mem *
+ SEV_ADJUST_SWIOTLB_SIZE_PERCENT / 100;
+
+ default_size = ALIGN(default_size, 1 << IO_TLB_SHIFT);
+
+ default_size = clamp_val(default_size, IO_TLB_DEFAULT_SIZE,
+ SEV_ADJUST_SWIOTLB_SIZE_MAX);
+ }
So a similar logic can be applied here.
Quoted 24 lines
Quoted 18 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 518
Quoted 5 lines
arch/x86/mm/mem_encrypt.c +4
-0+else + size =max (iotlb_default_size, (unsigned long )SZ_512M ); + + pr_info("SWIOTLB bounce buffer size adjusted to %luMB for SEV platform",just "... for SEV" - no need for "platform".
...
Quoted 8 lines
kernel/dma/swiotlb.c +0
-0@@ -163,6 +163,30 @@ unsigned long swiotlb_size_or_default(void)return size ? size : (IO_TLB_DEFAULT_SIZE ); }Quoted 5 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 168
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+unsigned long __init __weak arch_swiotlb_adjust (unsigned long size) +{ +return 0 ;That, of course, needs to return size, not 0.
Quoted 6 lines
This is not going to work for TDX. I think having a registration to SWIOTLB to have this function would be better going forward.
As in there will be a
swiotlb_register_adjuster()which AMD SEV code can call at start, also TDX can do it (and other platforms).
The question is how does mem_encrypt_init() work ?
That uses a similar logic as arch_swiotlb_adjust() as a "__weak" function and i am sure it will also need to have added support for TDX, can't both arch_swiotlb_adjust() and mem_encrypt_init() have specific checks for active AMD/INTEL memory encryption technology and accordingly perform actions, as mem_encrypt_init() currently checks for sev_active().
init/main.c:
void __init __weak mem_encrypt_init(void) { }
start_kernel()
{
..
mem_encrypt_init();
..
}
arch/x86/mm/mem_encrypt.c:
/* Architecture __weak replacement functions */
void __init mem_encrypt_init(void)
{
if (!sme_me_mask)
return;
/* Call into SWIOTLB to update the SWIOTLB DMA buffers */
swiotlb_update_mem_attributes();
/*
* With SEV, we need to unroll the rep string I/O instructions.
*/
if (sev_active())
static_branch_enable(&sev_enable_key);...
...
Thanks,
Ashish
Quoted 23 lines
Quoted 23 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 179
Quoted 12 lines
kernel/dma/swiotlb.c +11
-0+} + +void __init swiotlb_adjust (void ) +{ +unsigned long size; + +/* +* If swiotlb parameter has not been specified, give a chance to +* architectures such as those supporting memory encryption to +* adjust/expand SWIOTLB size for their use. +*/ And when you preset the function-local argument "size" with the size coming in as the size argument of
arch_swiotlb_adjust()...kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 182
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+if (!io_tlb_nslabs) { + size =arch_swiotlb_adjust (IO_TLB_DEFAULT_SIZE ); +if (size) {... you don't have to do if (size) here either but simply use size to compute
io_tlb_nslabs, I'd say.
Quoted 7 lines
Quoted 7 lines
Thx.
Signature · 4 lines
Regards/Gruss, Boris. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeople.kernel.org%2Ftglx%2Fnotes-about-netiquette&data=04%7C01%7CAshish.Kalra%40amd.com%7Cebd4a85f98f44bdfcb5408d88fd8dfac%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637417508926083910%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ub9PjAPzhDWr7K2iQggTAXwgg4VbORxP%2F%2Fcg6gQreCc%3D&reserved=0
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
Borislav Petkov
maintainerQuoted 2 lines · Ashish Kalra
As i mentioned earlier, the patch was initially based on using a % of guest memory,
Can you figure out how much the guest memory is and then allocate a percentage?
Signature · 8 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommuQuoted 10 lines · Borislav Petkov
Quoted 2 lines · Ashish Kalra
As i mentioned earlier, the patch was initially based on using a % of guest memory,
Can you figure out how much the guest memory is and then allocate a percentage?
But what will be the criteria to figure out this percentage?
As I mentioned earlier, this can be made as complicated as possible by adding all kind of heuristics but without any predictable performance gain.
Or it can be kept simple by using a static percentage value.
Thanks,
Ashish
Quoted 5 lines
Signature · 4 lines
Regards/Gruss, Boris. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeople.kernel.org%2Ftglx%2Fnotes-about-netiquette&data=04%7C01%7Cashish.kalra%40amd.com%7C0766422bcee64d2eb57208d89057f620%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637418054797950694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2FEFuRGOMOu4BZUkPOd9rxam%2BBA3nXj4tdRFFj3nQ47U%3D&reserved=0
Borislav Petkov
maintainerQuoted 7 lines · Ashish
But what will be the criteria to figure out this percentage?
As I mentioned earlier, this can be made as complicated as possible by adding all kind of heuristics but without any predictable performance gain.
Or it can be kept simple by using a static percentage value.
Yes, static percentage number based on the guest memory. X% of the guest memory is used for SWIOTLB.
Since you use sev_active(), it means the size computation is done in the guest so that SWIOTLB size is per-guest. Yes?
If so, you can simply take, say, 5% of the guest memory's size and use that for SWIOTLB buffers. Or 6 or X or whatever.
Makes sense?
Signature · 8 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommuQuoted 11 lines · Borislav Petkov
Quoted 6 lines · Ashish
But what will be the criteria to figure out this percentage?
As I mentioned earlier, this can be made as complicated as possible by adding all kind of heuristics but without any predictable performance gain.
Quoted 7 lines
Quoted 1 line
Or it can be kept simple by using a static percentage value.
Yes, static percentage number based on the guest memory. X% of the guest memory is used for SWIOTLB.
Since you use
sev_active(), it means the size computation is done in the guest so that SWIOTLB size is per-guest. Yes?
Yes
Quoted 5 lines
If so, you can simply take, say, 5% of the guest memory's size and use that for SWIOTLB buffers. Or 6 or X or whatever.
Makes sense?
Sure it does.
Thanks,
Ashish
Quoted 6 lines
Signature · 5 lines
-- Regards/Gruss, Boris. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeople.kernel.org%2Ftglx%2Fnotes-about-netiquette&data=04%7C01%7CAshish.Kalra%40amd.com%7C91b611b21d3049d70ca908d8905cbc37%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637418075284000564%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JvnUfskyd9xdsal4oYkSYW5ouL2b4cs%2Fo2oYi9KrkFo%3D&reserved=0
Hello Konrad,
Quoted 200 lines · Ashish Kalra
Hello Konrad,
Quoted 97 lines · Konrad Rzeszutek Wilk
Quoted 80 lines · Borislav Petkov
Quoted 9 lines · Ashish Kalra
From: Ashish Kalra <[email protected]>
For SEV, all DMA to and from guest has to use shared (un-encrypted) pages. SEV uses SWIOTLB to make this happen without requiring changes to device drivers. However, depending on workload being run, the default 64MB of SWIOTLB might not be enough and SWIOTLB may run out of buffers to use for DMA, resulting in I/O errors and/or performance degradation for high I/O workloads.
Quoted 3 lines
Increase the default size of SWIOTLB for SEV guests using a minimum value of 128MB and a maximum value of 512MB, determining on amount of provisioned guest memory.
That sentence needs massaging.
Quoted 4 lines
Using
late_initcall()interface to invokeswiotlb_adjust()does not work as the size adjustment needs to be done beforemem_encrypt_init()andreserve_crashkernel()which use the allocated SWIOTLB buffer size, hence calling it explicitly fromsetup_arch()."hence call it ... "
Quoted 2 lines
The SWIOTLB default size adjustment is added as an architecture specific
"... is added... " needs to be "Add ..."
Quoted 32 lines
interface/callback to allow architectures such as those supporting memory encryption to adjust/expand SWIOTLB size for their use.
v5 fixed build errors and warnings as
Reported-by kbuild test robot <[email protected]>Signed-off-by Ashish Kalra <[email protected]>--- arch/x86/kernel/setup.c | 2 ++ arch/x86/mm/mem_encrypt.c | 32 ++++++++++++++++++++++++++++++++ include/linux/swiotlb.h | 6 ++++++ kernel/dma/swiotlb.c | 24 ++++++++++++++++++++++++ 4 files changed, 64 insertions(+)arch/x86/kernel/setup.c +2
-0@@ -1166,6 +1166,8 @@ void __init setup_arch(char **cmdline_p)if (boot_cpu_has (X86_FEATURE_GBPAGES ))hugetlb_cma_reserve (PUD_SHIFT -PAGE_SHIFT ); +swiotlb_adjust (); +/* * Reserve memory for crash kernel after SRAT is parsed so that it * won't consume hotpluggable memory. arch/x86/mm/mem_encrypt.c +0
-0arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 495
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +3
-0@@ -490,6 +490,38 @@ static void print_mem_encrypt_feature_info(void) }/* Architecture __weak replacement functions */ +unsigned long __init arch_swiotlb_adjust (unsigned long iotlb_default_size) +{ +unsigned long size =0 ;unsigned long size = iotlb_default_size;arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 501
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +6
-0+ +/* +* For SEV, all DMA has to occur via shared/unencrypted pages. +* SEV uses SWOTLB to make this happen without changing device +* drivers. However, depending on the workload being run, the +* default 64MB of SWIOTLB may not be enough & SWIOTLB may ^Use words pls, not "&".
Quoted 13 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 514
Quoted 13 lines
arch/x86/mm/mem_encrypt.c +13
-0+* run out of buffers for DMA, resulting in I/O errors and/or +* performance degradation especially with high I/O workloads. +* Increase the default size of SWIOTLB for SEV guests using +* a minimum value of 128MB and a maximum value of 512MB, +* depending on amount of provisioned guest memory. +*/ +if (sev_active ()) { +phys_addr_t total_mem =memblock_phys_mem_size (); + +if (total_mem <=SZ_1G ) + size =max (iotlb_default_size, (unsigned long )SZ_128M ); +else if (total_mem <=SZ_4G ) + size =max (iotlb_default_size, (unsigned long )SZ_256M );That is eating 128MB for 1GB, aka 12% of the guest memory allocated statically for this.
Quoted 8 lines
And for guests that are 2GB, that is 12% until it gets to 3GB when it is 8% and then 6% at 4GB.
I would prefer this to be based on your memory count, that is 6% of total memory. And then going forward we can allocate memory _after_ boot and then stich the late SWIOTLB pool and allocate on demand.
Ok.
As i mentioned earlier, the patch was initially based on using a % of guest memory, as below:
(quoted diff) +14
-0+#define SEV_ADJUST_SWIOTLB_SIZE_PERCENT 5 +#define SEV_ADJUST_SWIOTLB_SIZE_MAX (1UL << 30) + if (sev_active() && !io_tlb_nslabs) { + unsigned long total_mem = get_num_physpages() << + PAGE_SHIFT; + + default_size = total_mem * + SEV_ADJUST_SWIOTLB_SIZE_PERCENT / 100; + + default_size = ALIGN(default_size, 1 << IO_TLB_SHIFT); + + default_size = clamp_val(default_size, IO_TLB_DEFAULT_SIZE, + SEV_ADJUST_SWIOTLB_SIZE_MAX); + }So a similar logic can be applied here.
Quoted 24 lines
Quoted 18 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 518
Quoted 5 lines
arch/x86/mm/mem_encrypt.c +4
-0+else + size =max (iotlb_default_size, (unsigned long )SZ_512M ); + + pr_info("SWIOTLB bounce buffer size adjusted to %luMB for SEV platform",just "... for SEV" - no need for "platform".
...
Quoted 8 lines
kernel/dma/swiotlb.c +0
-0@@ -163,6 +163,30 @@ unsigned long swiotlb_size_or_default(void)return size ? size : (IO_TLB_DEFAULT_SIZE ); }Quoted 5 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 168
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+unsigned long __init __weak arch_swiotlb_adjust (unsigned long size) +{ +return 0 ;That, of course, needs to return size, not 0.
Quoted 6 lines
This is not going to work for TDX. I think having a registration to SWIOTLB to have this function would be better going forward.
As in there will be a
swiotlb_register_adjuster()which AMD SEV code can call at start, also TDX can do it (and other platforms).The question is how does
mem_encrypt_init()work ?That uses a similar logic as
arch_swiotlb_adjust()as a "__weak" function and i am sure it will also need to have added support for TDX, can't botharch_swiotlb_adjust()andmem_encrypt_init()have specific checks for active AMD/INTEL memory encryption technology and accordingly perform actions, asmem_encrypt_init()currently checks forsev_active().
init/main.c:void
__init__weakmem_encrypt_init(void){ }
start_kernel(){ .. mem_encrypt_init(); .. }
arch/x86/mm/mem_encrypt.c:/* Architecture
__weakreplacement functions */void
__initmem_encrypt_init(void){ if (!sme_me_mask) return; /* Call into SWIOTLB to update the SWIOTLB DMA buffers */ swiotlb_update_mem_attributes(); /* * With SEV, we need to unroll the rep string I/O instructions. */ if (sev_active()) static_branch_enable(&sev_enable_key);
Quoted 3 lines
...
...
Your thoughts on this ?
Thanks,
Ashish
Quoted 24 lines
Quoted 24 lines
Quoted 24 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 179
Quoted 13 lines
kernel/dma/swiotlb.c +11
-0+} + +void __init swiotlb_adjust (void ) +{ +unsigned long size; + +/* +* If swiotlb parameter has not been specified, give a chance to +* architectures such as those supporting memory encryption to +* adjust/expand SWIOTLB size for their use. +*/ And when you preset the function-local argument "size" with the size coming in as the size argument of
arch_swiotlb_adjust()...kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 182
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+if (!io_tlb_nslabs) { + size =arch_swiotlb_adjust (IO_TLB_DEFAULT_SIZE ); +if (size) {... you don't have to do if (size) here either but simply use size to compute
io_tlb_nslabs, I'd say.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Thx.
Signature · 4 lines
Regards/Gruss, Boris. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeople.kernel.org%2Ftglx%2Fnotes-about-netiquette&data=04%7C01%7CAshish.Kalra%40amd.com%7Cebd4a85f98f44bdfcb5408d88fd8dfac%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637417508926083910%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ub9PjAPzhDWr7K2iQggTAXwgg4VbORxP%2F%2Fcg6gQreCc%3D&reserved=0
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
Quoted 207 lines · Ashish Kalra
Hello Konrad,
Quoted 200 lines · Ashish Kalra
Hello Konrad,
Quoted 97 lines · Konrad Rzeszutek Wilk
Quoted 80 lines · Borislav Petkov
Quoted 9 lines · Ashish Kalra
From: Ashish Kalra <[email protected]>
For SEV, all DMA to and from guest has to use shared (un-encrypted) pages. SEV uses SWIOTLB to make this happen without requiring changes to device drivers. However, depending on workload being run, the default 64MB of SWIOTLB might not be enough and SWIOTLB may run out of buffers to use for DMA, resulting in I/O errors and/or performance degradation for high I/O workloads.
Quoted 3 lines
Increase the default size of SWIOTLB for SEV guests using a minimum value of 128MB and a maximum value of 512MB, determining on amount of provisioned guest memory.
That sentence needs massaging.
Quoted 4 lines
Using
late_initcall()interface to invokeswiotlb_adjust()does not work as the size adjustment needs to be done beforemem_encrypt_init()andreserve_crashkernel()which use the allocated SWIOTLB buffer size, hence calling it explicitly fromsetup_arch()."hence call it ... "
Quoted 2 lines
The SWIOTLB default size adjustment is added as an architecture specific
"... is added... " needs to be "Add ..."
Quoted 32 lines
interface/callback to allow architectures such as those supporting memory encryption to adjust/expand SWIOTLB size for their use.
v5 fixed build errors and warnings as
Reported-by kbuild test robot <[email protected]>Signed-off-by Ashish Kalra <[email protected]>--- arch/x86/kernel/setup.c | 2 ++ arch/x86/mm/mem_encrypt.c | 32 ++++++++++++++++++++++++++++++++ include/linux/swiotlb.h | 6 ++++++ kernel/dma/swiotlb.c | 24 ++++++++++++++++++++++++ 4 files changed, 64 insertions(+)arch/x86/kernel/setup.c +2
-0@@ -1166,6 +1166,8 @@ void __init setup_arch(char **cmdline_p)if (boot_cpu_has (X86_FEATURE_GBPAGES ))hugetlb_cma_reserve (PUD_SHIFT -PAGE_SHIFT ); +swiotlb_adjust (); +/* * Reserve memory for crash kernel after SRAT is parsed so that it * won't consume hotpluggable memory. arch/x86/mm/mem_encrypt.c +0
-0arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 495
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +3
-0@@ -490,6 +490,38 @@ static void print_mem_encrypt_feature_info(void) }/* Architecture __weak replacement functions */ +unsigned long __init arch_swiotlb_adjust (unsigned long iotlb_default_size) +{ +unsigned long size =0 ;unsigned long size = iotlb_default_size;arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 501
Quoted 6 lines
arch/x86/mm/mem_encrypt.c +6
-0+ +/* +* For SEV, all DMA has to occur via shared/unencrypted pages. +* SEV uses SWOTLB to make this happen without changing device +* drivers. However, depending on the workload being run, the +* default 64MB of SWIOTLB may not be enough & SWIOTLB may ^Use words pls, not "&".
Quoted 13 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 514
Quoted 13 lines
arch/x86/mm/mem_encrypt.c +13
-0+* run out of buffers for DMA, resulting in I/O errors and/or +* performance degradation especially with high I/O workloads. +* Increase the default size of SWIOTLB for SEV guests using +* a minimum value of 128MB and a maximum value of 512MB, +* depending on amount of provisioned guest memory. +*/ +if (sev_active ()) { +phys_addr_t total_mem =memblock_phys_mem_size (); + +if (total_mem <=SZ_1G ) + size =max (iotlb_default_size, (unsigned long )SZ_128M ); +else if (total_mem <=SZ_4G ) + size =max (iotlb_default_size, (unsigned long )SZ_256M );That is eating 128MB for 1GB, aka 12% of the guest memory allocated statically for this.
Quoted 8 lines
And for guests that are 2GB, that is 12% until it gets to 3GB when it is 8% and then 6% at 4GB.
I would prefer this to be based on your memory count, that is 6% of total memory. And then going forward we can allocate memory _after_ boot and then stich the late SWIOTLB pool and allocate on demand.
Ok.
As i mentioned earlier, the patch was initially based on using a % of guest memory, as below:
(quoted diff) +14
-0+#define SEV_ADJUST_SWIOTLB_SIZE_PERCENT 5 +#define SEV_ADJUST_SWIOTLB_SIZE_MAX (1UL << 30) + if (sev_active() && !io_tlb_nslabs) { + unsigned long total_mem = get_num_physpages() << + PAGE_SHIFT; + + default_size = total_mem * + SEV_ADJUST_SWIOTLB_SIZE_PERCENT / 100; + + default_size = ALIGN(default_size, 1 << IO_TLB_SHIFT); + + default_size = clamp_val(default_size, IO_TLB_DEFAULT_SIZE, + SEV_ADJUST_SWIOTLB_SIZE_MAX); + }So a similar logic can be applied here.
Quoted 24 lines
Quoted 18 lines
arch/x86/mm/mem_encrypt.c static void print_mem_encrypt_feature_info(void) · line 518
Quoted 5 lines
arch/x86/mm/mem_encrypt.c +4
-0+else + size =max (iotlb_default_size, (unsigned long )SZ_512M ); + + pr_info("SWIOTLB bounce buffer size adjusted to %luMB for SEV platform",just "... for SEV" - no need for "platform".
...
Quoted 8 lines
kernel/dma/swiotlb.c +0
-0@@ -163,6 +163,30 @@ unsigned long swiotlb_size_or_default(void)return size ? size : (IO_TLB_DEFAULT_SIZE ); }Quoted 5 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 168
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+unsigned long __init __weak arch_swiotlb_adjust (unsigned long size) +{ +return 0 ;That, of course, needs to return size, not 0.
Quoted 6 lines
This is not going to work for TDX. I think having a registration to SWIOTLB to have this function would be better going forward.
As in there will be a
swiotlb_register_adjuster()which AMD SEV code can call at start, also TDX can do it (and other platforms).The question is how does
mem_encrypt_init()work ?That uses a similar logic as
arch_swiotlb_adjust()as a "__weak" function and i am sure it will also need to have added support for TDX, can't botharch_swiotlb_adjust()andmem_encrypt_init()have specific checks for active AMD/INTEL memory encryption technology and accordingly perform actions, asmem_encrypt_init()currently checks forsev_active().
init/main.c:void
__init__weakmem_encrypt_init(void){ }
start_kernel(){ .. mem_encrypt_init(); .. }
arch/x86/mm/mem_encrypt.c:/* Architecture
__weakreplacement functions */void
__initmem_encrypt_init(void){ if (!sme_me_mask) return; /* Call into SWIOTLB to update the SWIOTLB DMA buffers */ swiotlb_update_mem_attributes(); /* * With SEV, we need to unroll the rep string I/O instructions. */ if (sev_active()) static_branch_enable(&sev_enable_key);Quoted 3 lines
...
...
Quoted 1 line
Your thoughts on this ?
That looks quite sensible.
Quoted 35 lines
Thanks,
AshishQuoted 31 lines
Quoted 31 lines
Quoted 31 lines
kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 179
Quoted 13 lines
kernel/dma/swiotlb.c +11
-0+} + +void __init swiotlb_adjust (void ) +{ +unsigned long size; + +/* +* If swiotlb parameter has not been specified, give a chance to +* architectures such as those supporting memory encryption to +* adjust/expand SWIOTLB size for their use. +*/ And when you preset the function-local argument "size" with the size coming in as the size argument of
arch_swiotlb_adjust()...kernel/dma/swiotlb.c unsigned long swiotlb_size_or_default(void) · line 182
Quoted 3 lines
kernel/dma/swiotlb.c +3
-0+if (!io_tlb_nslabs) { + size =arch_swiotlb_adjust (IO_TLB_DEFAULT_SIZE ); +if (size) {... you don't have to do if (size) here either but simply use size to compute
io_tlb_nslabs, I'd say.Thx.
Signature · 4 lines
Regards/Gruss, Boris. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeople.kernel.org%2Ftglx%2Fnotes-about-netiquette&data=04%7C01%7CAshish.Kalra%40amd.com%7Cebd4a85f98f44bdfcb5408d88fd8dfac%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637417508926083910%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ub9PjAPzhDWr7K2iQggTAXwgg4VbORxP%2F%2Fcg6gQreCc%3D&reserved=0
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu