Namazu: a Full-Text Search Engine

This index contains 0 documents and 0 keywords.

Last modified: date


Query: [How to search]

Display: Description: Sort:

Results:

References: [ amd: 6092 ] [ sev: 1033 ]

Total 514 documents matching your query.

1. Re: [Qemu-devel] [RFC PATCH v1 00/10] Add AMD SEV guest live migration support (score: 578)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Thu, 25 Apr 2019 02:15:49 +0000
It's megabits/sec. The QMP query-migration command shows the throughput in Mbits/s. It includes PSP command execution and the network write. Most of the time is spent in PSP FW. I have not performed
/archive/html/qemu-devel/2019-04/msg04181.html (6,858 bytes)

2. Re: [Qemu-devel] [RFC PATCH v1 00/10] Add AMD SEV guest live migration support (score: 603)
Author: Steve Rutherford <srutherford@google.com>
Date: Wed, 24 Apr 2019 17:18:38 -0700
Do you mean MiB/s, MB/s or Mb/s? Since you are talking about network speeds, sometimes these get conflated. I'm guessing you mean MB/s since you are also using 4kb for page size. On Wed, Apr 24, 2019
/archive/html/qemu-devel/2019-04/msg04179.html (13,053 bytes)

3. Re: [Qemu-devel] [RFC PATCH v1 00/10] Add AMD SEV guest live migration support (score: 657)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 21:32:39 +0000
I have not done a complete performance analysis yet! From the qemu QMP prompt (query-migration) I am getting ~8mbps throughput from one host to another (this is with 4kb regions). I have been told th
/archive/html/qemu-devel/2019-04/msg04176.html (12,177 bytes)

4. Re: [Qemu-devel] [RFC PATCH v1 00/10] Add AMD SEV guest live migration support (score: 603)
Author: Steve Rutherford <srutherford@google.com>
Date: Wed, 24 Apr 2019 12:15:12 -0700
What's the back-of-the-envelope marginal cost of transferring a 16kB region from one host to another? I'm interested in what the end to end migration perf changes look like for this. If you have meas
/archive/html/qemu-devel/2019-04/msg04172.html (10,985 bytes)

5. [Qemu-devel] [RFC PATCH v1 08/10] KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall (score: 194)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:09 +0000
The hypercall can be used by the SEV guest to notify the page encryption status to the hypervisor. The hypercall should be invoked only when the encryption attribute is changed from encrypted -> decr
/archive/html/qemu-devel/2019-04/msg04111.html (13,044 bytes)

6. [Qemu-devel] [RFC PATCH v1 07/10] KVM: x86: Add AMD SEV specific Hypercall3 (score: 613)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:07 +0000
KVM hypercall framework relies on alternative framework to patch the VMCALL -> VMMCALL on AMD platform. If a hypercall is made before apply_alternative() is called then it defaults to VMCALL. The app
/archive/html/qemu-devel/2019-04/msg04110.html (8,140 bytes)

7. [Qemu-devel] [RFC PATCH v1 03/10] KVM: SVM: Add KVM_SEV_SEND_FINISH command (score: 73)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:02 +0000
The command is used to finailize the encryption context created with KVM_SEV_SEND_START command. Cc: Thomas Gleixner <address@hidden> Cc: Ingo Molnar <address@hidden> Cc: "H. Peter Anvin" <address@hi
/archive/html/qemu-devel/2019-04/msg04109.html (8,816 bytes)

8. [Qemu-devel] [RFC PATCH v1 05/10] KVM: SVM: Add KVM_SEV_RECEIVE_UPDATE_DATA command (score: 92)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:05 +0000
The command is used for copying the incoming buffer into the SEV guest memory space. Cc: Thomas Gleixner <address@hidden> Cc: Ingo Molnar <address@hidden> Cc: "H. Peter Anvin" <address@hidden> Cc: Pa
/archive/html/qemu-devel/2019-04/msg04108.html (12,316 bytes)

9. [Qemu-devel] [RFC PATCH v1 06/10] KVM: SVM: Add KVM_SEV_RECEIVE_FINISH command (score: 82)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:06 +0000
The command finalize the guest receiving process and make the SEV guest ready for the execution. Cc: Thomas Gleixner <address@hidden> Cc: Ingo Molnar <address@hidden> Cc: "H. Peter Anvin" <address@hi
/archive/html/qemu-devel/2019-04/msg04107.html (8,893 bytes)

10. [Qemu-devel] [RFC PATCH v1 02/10] KVM: SVM: Add KVM_SEND_UPDATE_DATA command (score: 101)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:01 +0000
The command is used for encrypting the guest memory region using the encryption context created with KVM_SEV_SEND_START. Cc: Thomas Gleixner <address@hidden> Cc: Ingo Molnar <address@hidden> Cc: "H.
/archive/html/qemu-devel/2019-04/msg04105.html (14,550 bytes)

11. [Qemu-devel] [RFC PATCH v1 04/10] KVM: SVM: Add support for KVM_SEV_RECEIVE_START command (score: 120)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:03 +0000
The command is used to create encryption context for the incoming SEV guest. The encryption context can be later unused by the hypervisor to import the incoming data into the SEV guest memory space.
/archive/html/qemu-devel/2019-04/msg04106.html (12,363 bytes)

12. [Qemu-devel] [RFC PATCH v1 10/10] mm: x86: Invoke hypercall when page encryption status is changed (score: 64)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:11 +0000
Invoke a hypercall when a memory region is changed from encrypted -> decrypted and vice versa. Hypervisor need to know the page encryption status during the guest migration. Cc: Thomas Gleixner <addr
/archive/html/qemu-devel/2019-04/msg04104.html (11,723 bytes)

13. [Qemu-devel] [RFC PATCH v1 09/10] KVM: x86: Introduce KVM_GET_PAGE_ENC_BITMAP ioctl (score: 92)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:10:10 +0000
The ioctl can be used to retrieve page encryption bitmap for a given kvm memory slot. Cc: Thomas Gleixner <address@hidden> Cc: Ingo Molnar <address@hidden> Cc: "H. Peter Anvin" <address@hidden> Cc: P
/archive/html/qemu-devel/2019-04/msg04103.html (11,609 bytes)

14. [Qemu-devel] [RFC PATCH v1 01/10] KVM: SVM: Add KVM_SEV SEND_START command (score: 89)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:09:59 +0000
The command is used to create an outgoing SEV guest encryption context. Cc: Thomas Gleixner <address@hidden> Cc: Ingo Molnar <address@hidden> Cc: "H. Peter Anvin" <address@hidden> Cc: Paolo Bonzini <
/archive/html/qemu-devel/2019-04/msg04102.html (12,692 bytes)

15. [Qemu-devel] [RFC PATCH v1 00/10] Add AMD SEV guest live migration support (score: 657)
Author: "Singh, Brijesh" <brijesh.singh@amd.com>
Date: Wed, 24 Apr 2019 16:09:58 +0000
The series add support for AMD SEV guest live migration commands. To protect the confidentiality of an SEV protected guest memory while in transit we need to use the SEV commands defined in SEV API s
/archive/html/qemu-devel/2019-04/msg04101.html (9,569 bytes)

16. [Qemu-devel] [PULL 09/12] pc-bios: document the edk2 firmware images; add firmware descriptors (score: 33)
Author: Laszlo Ersek <lersek@redhat.com>
Date: Tue, 23 Apr 2019 19:15:17 +0200
Update the README file with information on the images added previously, and provide firmware descriptor documents that conform to "docs/interop/firmware.json". Signed-off-by: Laszlo Ersek <address@hi
/archive/html/qemu-devel/2019-04/msg03808.html (16,486 bytes)

17. Re: [Qemu-devel] [PATCH v3] i386: Add new Hygon 'Dhyana' CPU model (score: 44)
Author: Pavel Hrdina <phrdina@redhat.com>
Date: Thu, 18 Apr 2019 16:27:04 +0200
Just for the reference, this discussion happened last year and AMD developer Brijesh agreed [1] that the microarchitecture name would be better, one of the reasons I've objected again. Pavel [1] <htt
/archive/html/qemu-devel/2019-04/msg03162.html (14,378 bytes)

18. Re: [Qemu-devel] [PATCH v3] i386: Add new Hygon 'Dhyana' CPU model (score: 37)
Author: Eduardo Habkost <ehabkost@redhat.com>
Date: Thu, 18 Apr 2019 11:05:20 -0300
It is an issue. The fact that features are missing has huge importance for most virtualization management software that supports live migration. Not having the "enforce" flag enabled by default was a
/archive/html/qemu-devel/2019-04/msg03153.html (12,683 bytes)

19. Re: [Qemu-devel] [PATCH v3] i386: Add new Hygon 'Dhyana' CPU model (score: 37)
Author: Pavel Hrdina <phrdina@redhat.com>
Date: Thu, 18 Apr 2019 11:59:35 +0200
Fair enough, still the point stands that we should use the name of the microarchitecture. Pavel Attachment: signature.asc Description: PGP signature
/archive/html/qemu-devel/2019-04/msg03083.html (10,782 bytes)

20. Re: [Qemu-devel] [PATCH v3] i386: Add new Hygon 'Dhyana' CPU model (score: 37)
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Thu, 18 Apr 2019 09:48:25 +0100
I don't think this is a good idea. AFAICT, Dhyana and EPYC should not be thought of as the same microarchitecture. Dhyana is a fork of the Zen microarchitecture as illustrated by the dropping of a nu
/archive/html/qemu-devel/2019-04/msg03074.html (10,339 bytes)


This search system is powered by Namazu v

foobar@namazu.org