All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrei Semenov <andrei.semenov@vates.fr>
Cc: xen-devel@lists.xenproject.org, "Jan Beulich" <jbeulich@suse.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"George Dunlap" <george.dunlap@citrix.com>,
	"Julien Grall" <julien@xen.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [PATCH v1 0/2] Starting AMD SEV work
Date: Thu, 11 Apr 2024 02:50:32 +0200	[thread overview]
Message-ID: <Zhcz2d4JsAl4J6vG@mail-itl> (raw)
In-Reply-To: <cover.1712759753.git.andrei.semenov@vates.fr>

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

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 for "Secure Encrypted Virtualization" and allows the memory contents
> of a VM to be encrypted with a key unique to this VM. In this way the neither
> other VMs nor hypervisor can't read the memory content of this "encrypted"
> VM.
> 
> In order to create and to run such a VM different layers of software must
> interact (bascally Xen hypevisor, Xen toolstack in dom0 and the encrypted VM
> itself).
> 
> In this work we start with discovering and enabling SEV feature on the platform.
> The second patch ports AMD Secure Processor driver on Xen. This AMD Secure
> Processor device (a.k.a PSP) is the way the different software layers interact
> with AMD firmware/hardware to manage and run the encrypted VM.

How will that interact with the PSP driver in dom0? AFAIK amdgpu driver
uses PSP for loading the GPU firmware. Does it mean one need to choose
either GPU in dom0 or encrypted VMs, or is it going to work somehow
together?

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2024-04-11  0:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 15:36 [PATCH v1 0/2] Starting AMD SEV work Andrei Semenov
2024-04-10 15:36 ` Andrei Semenov
2024-04-10 15:36   ` [PATCH v1 0/2] AMD SEV initial work Andrei Semenov
2024-04-10 15:36   ` [PATCH v1 1/2] Implemented AMD SEV discovery and enabling Andrei Semenov
2024-04-11 18:32     ` Andrew Cooper
2024-04-12 14:06       ` Andrei Semenov
2024-04-12 14:38         ` Vaishali Thakkar
2024-04-12 15:07           ` Andrew Cooper
2024-04-12 15:18             ` Vaishali Thakkar
2024-04-18  8:13     ` Jan Beulich
2024-04-18 13:29       ` Andrei Semenov
2024-04-10 15:36   ` [PATCH v1 2/2] Implemented Amd Secure Processor device driver Andrei Semenov
2024-04-11 18:42     ` Andrew Cooper
2024-04-12 14:49       ` Andrei Semenov
2024-04-12 14:56         ` Andrew Cooper
2024-04-18  8:31     ` Jan Beulich
2024-04-10 16:31   ` [PATCH v1 0/2] AMD SEV initial work Andrei Semenov
2024-04-11  0:50   ` Marek Marczykowski-Górecki [this message]
2024-04-11  7:48     ` [PATCH v1 0/2] Starting AMD SEV work Andrei Semenov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zhcz2d4JsAl4J6vG@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=andrei.semenov@vates.fr \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.