Re: [PATCH v1 1/2] Implemented AMD SEV discovery and enabling.

2024-04-18 Thread Andrei Semenov
lich wrote: On 10.04.2024 17:36, Andrei Semenov wrote: Signed-off-by: Andrei Semenov A couple more nits on top of what Andrew said. First: Please no patches (which aren't blindingly trivial) without description. @@ -1030,6 +1031,54 @@ static void amd_check_erratum_1485(void) wrmsrl(MSR_AM

Re: [PATCH v1 2/2] Implemented Amd Secure Processor device driver

2024-04-12 Thread Andrei Semenov
On 4/11/24 20:42, Andrew Cooper wrote: On 10/04/2024 4:36 pm, Andrei Semenov wrote: Signed-off-by: Andrei Semenov --- xen/arch/x86/include/asm/psp-sev.h | 655 +++ xen/drivers/Kconfig| 2 + xen/drivers/Makefile | 1 + xen/drivers

Re: [PATCH v1 1/2] Implemented AMD SEV discovery and enabling.

2024-04-12 Thread Andrei Semenov
On 4/11/24 20:32, Andrew Cooper wrote: On 10/04/2024 4:36 pm, Andrei Semenov wrote: diff --git a/xen/arch/x86/cpu/amd.c b/xen/arch/x86/cpu/amd.c index ab92333673..a5903613f0 100644 --- a/xen/arch/x86/cpu/amd.c +++ b/xen/arch/x86/cpu/amd.c @@ -1030,6 +1031,54 @@ static void

Re: [PATCH v1 0/2] Starting AMD SEV work

2024-04-11 Thread Andrei Semenov
ential PSP interfaces for priveleged guests. Best regards, Andrei Semenov Le jeudi 11/04/2024 02:50, Marek Marczykowski-Górecki a écrit : On Wed, Apr 10, 2024 at 05:36:34PM +0200, Andrei Semenov wrote: This patch series initiate work on AMD SEV technology implementation in Xen. SEV stands f

Re: [PATCH v1 0/2] AMD SEV initial work

2024-04-10 Thread Andrei Semenov
Also sent emacs ~ file. To ignore, sorry Le mercredi 10/04/2024 17:39, Andrei Semenov a écrit : ///HERE YOU GO Andrei Semenov (2): Implemented AMD SEV discovery and enabling. Implemented Amd Secure Processor device driver xen/arch/x86/cpu/amd.c | 53 ++ xen/arch/x86/hvm

[PATCH v1 1/2] Implemented AMD SEV discovery and enabling.

2024-04-10 Thread Andrei Semenov
Signed-off-by: Andrei Semenov --- xen/arch/x86/cpu/amd.c | 53 ++ xen/arch/x86/hvm/svm/Makefile | 1 + xen/arch/x86/hvm/svm/sev.c | 4 ++ xen/arch/x86/include/asm/cpufeature.h | 3 ++ xen/arch/x86/include/asm/cpufeatures.h | 2

[PATCH v1 2/2] Implemented Amd Secure Processor device driver

2024-04-10 Thread Andrei Semenov
Signed-off-by: Andrei Semenov --- xen/arch/x86/include/asm/psp-sev.h | 655 +++ xen/drivers/Kconfig| 2 + xen/drivers/Makefile | 1 + xen/drivers/crypto/Kconfig | 10 + xen/drivers/crypto/Makefile| 1 + xen/drivers/crypto

[PATCH v1 0/2] AMD SEV initial work

2024-04-10 Thread Andrei Semenov
///HERE YOU GO Andrei Semenov (2): Implemented AMD SEV discovery and enabling. Implemented Amd Secure Processor device driver xen/arch/x86/cpu/amd.c | 53 ++ xen/arch/x86/hvm/svm/Makefile | 1 + xen/arch/x86/hvm/svm/sev.c | 4 + xen/arch/x86/include

[PATCH v2 1/2] live migration: do not use deffered bitmap when inappropriate

2022-09-06 Thread Andrei Semenov
Use deffered bitmap only in PV guests context as it not used for HVM guests. This allow to reduce memory pressure on domain0 while migrating very large (memory wise) HVM guests. Signed-off-by: Andrei Semenov --- tools/libs/guest/xg_sr_common.h | 26 -- tools/libs/guest

[PATCH v2 2/2] live migration: use superpages for physmap population on restore when possible

2022-09-06 Thread Andrei Semenov
Implement an heuristic for X86 HVM guests which tries to use superpages while populating guest physmap on live migration. This should impove memory accesses performances for these guests. Signed-off-by: Andrei Semenov --- tools/include/xen-tools/libs.h | 4 ++ tools/libs/guest

[PATCH v2 0/2] live migration: optimisations

2022-09-06 Thread Andrei Semenov
This 2 patches implement some optimisations for guests live migraiton. Andrei Semenov (2): live migration: do not use deffered bitmap when inappropriate live migration: use superpages for physmap population on restore when possible tools/include/xen-tools/libs.h | 4

[Xen-devel] out of memory issue on dom0_hvm start

2018-11-27 Thread andrei . semenov
Hi all, I have some troubles to start xen when using dom0 in HVM mode on X86 Intel nuc7i5bnh  board. After some investigation it seems that  "domheap" memory allocator is out of memory while  constructing the p2m mapping  (pvh_setup_p2m).   This misbehavior, from my understanding, is the