[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c919928-00ed-beda-e984-35f7b6ca42fb@redhat.com>
Date: Thu, 30 Apr 2020 12:34:10 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Alexander Graf <graf@...zon.com>,
"Paraschiv, Andra-Irina" <andraprs@...zon.com>,
linux-kernel@...r.kernel.org
Cc: Anthony Liguori <aliguori@...zon.com>,
Benjamin Herrenschmidt <benh@...zon.com>,
Colm MacCarthaigh <colmmacc@...zon.com>,
Bjoern Doebel <doebel@...zon.de>,
David Woodhouse <dwmw@...zon.co.uk>,
Frank van der Linden <fllinden@...zon.com>,
Martin Pohlack <mpohlack@...zon.de>,
Matt Wilson <msw@...zon.com>, Balbir Singh <sblbir@...zon.com>,
Stewart Smith <trawets@...zon.com>,
Uwe Dannowski <uwed@...zon.de>, kvm@...r.kernel.org,
ne-devel-upstream@...zon.com
Subject: Re: [PATCH v1 00/15] Add support for Nitro Enclaves
On 28/04/20 17:07, Alexander Graf wrote:
>
> Why don't we build something like the following instead?
>
> vm = ne_create(vcpus = 4)
> ne_set_memory(vm, hva, len)
> ne_load_image(vm, addr, len)
> ne_start(vm)
>
> That way we would get the EIF loading into kernel space. "LOAD_IMAGE"
> would only be available in the time window between set_memory and start.
> It basically implements a memcpy(), but it would completely hide the
> hidden semantics of where an EIF has to go, so future device versions
> (or even other enclave implementers) could change the logic.
Can we add a file format argument and flags to ne_load_image, to avoid
having a v2 ioctl later?
Also, would you consider a mode where ne_load_image is not invoked and
the enclave starts in real mode at 0xffffff0?
Thanks,
Paolo
Powered by blists - more mailing lists