From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <graf@amazon.com>,
"Paraschiv, Andra-Irina" <andraprs@amazon.com>,
linux-kernel@vger.kernel.org
Cc: Anthony Liguori <aliguori@amazon.com>,
Benjamin Herrenschmidt <benh@amazon.com>,
Colm MacCarthaigh <colmmacc@amazon.com>,
Bjoern Doebel <doebel@amazon.de>,
David Woodhouse <dwmw@amazon.co.uk>,
Frank van der Linden <fllinden@amazon.com>,
Martin Pohlack <mpohlack@amazon.de>, Matt Wilson <msw@amazon.com>,
Balbir Singh <sblbir@amazon.com>,
Stewart Smith <trawets@amazon.com>,
Uwe Dannowski <uwed@amazon.de>,
kvm@vger.kernel.org, ne-devel-upstream@amazon.com
Subject: Re: [PATCH v1 00/15] Add support for Nitro Enclaves
Date: Thu, 23 Apr 2020 23:18:15 +0200 [thread overview]
Message-ID: <0467ce02-92f3-8456-2727-c4905c98c307@redhat.com> (raw)
In-Reply-To: <80489572-72a1-dbe7-5306-60799711dae0@amazon.com>
On 23/04/20 22:56, Alexander Graf wrote:
>>
>> CPL3 is how the user application run, but does the enclave's Linux boot
>> process start in real mode at the reset vector (0xfffffff0), in 16-bit
>> protected mode at the Linux bzImage entry point, or at the ELF entry
>> point?
>
> There is no "entry point" per se. You prepopulate at target bzImage into
> the enclave memory on boot which then follows the standard boot
> protocol. Everything
There's still a "where" missing in that sentence. :) I assume you put
it at 0x10000 (and so the entry point at 0x10200)? That should be
documented because that is absolutely not what the KVM API looks like.
> before that (enclave firmware, etc.) is provided by
> the enclave environment.
>
> Think of it like a mechanism to launch a second QEMU instance on the
> host, but all you can actually control are the -smp, -m, -kernel and
> -initrd parameters.
Are there requirements on how to populate the memory to ensure that the
host firmware doesn't crash and burn? E.g. some free memory right below
4GiB (for the firmware, the LAPIC/IOAPIC or any other special MMIO
devices you have, PCI BARs, and the like)?
> The only I/O channel you have between your VM and
> that new VM is a vsock channel which is configured by the host on your
> behalf.
Is this virtio-mmio or virtio-pci, and what other emulated devices are
there and how do you discover them? Are there any ISA devices
(RTC/PIC/PIT), and are there SMBIOS/RSDP/MP tables in the F segment?
Thanks,
Paolo
next prev parent reply other threads:[~2020-04-23 21:18 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 18:41 [PATCH v1 00/15] Add support for Nitro Enclaves Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 01/15] nitro_enclaves: Add ioctl interface definition Andra Paraschiv
2020-04-21 18:47 ` Randy Dunlap
2020-04-21 21:45 ` Paolo Bonzini
2020-04-22 15:49 ` Paraschiv, Andra-Irina
2020-04-21 18:41 ` [PATCH v1 02/15] nitro_enclaves: Define the PCI device interface Andra Paraschiv
2020-04-21 21:22 ` Paolo Bonzini
2020-04-23 13:37 ` Paraschiv, Andra-Irina
2020-04-24 15:10 ` Paraschiv, Andra-Irina
2020-04-21 18:41 ` [PATCH v1 03/15] nitro_enclaves: Define enclave info for internal bookkeeping Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 04/15] nitro_enclaves: Init PCI device driver Andra Paraschiv
2020-04-25 14:25 ` Liran Alon
2020-04-29 16:31 ` Paraschiv, Andra-Irina
2020-04-21 18:41 ` [PATCH v1 05/15] nitro_enclaves: Handle PCI device command requests Andra Paraschiv
2020-04-25 14:52 ` Liran Alon
2020-04-29 17:00 ` Paraschiv, Andra-Irina
2020-04-21 18:41 ` [PATCH v1 06/15] nitro_enclaves: Handle out-of-band PCI device events Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 07/15] nitro_enclaves: Init misc device providing the ioctl interface Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 08/15] nitro_enclaves: Add logic for enclave vm creation Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 09/15] nitro_enclaves: Add logic for enclave vcpu creation Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 10/15] nitro_enclaves: Add logic for enclave memory region set Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 11/15] nitro_enclaves: Add logic for enclave start Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 12/15] nitro_enclaves: Add logic for enclave termination Andra Paraschiv
2020-04-21 18:41 ` [PATCH v1 13/15] nitro_enclaves: Add Kconfig for the Nitro Enclaves driver Andra Paraschiv
2020-04-21 18:50 ` Randy Dunlap
2020-04-22 14:35 ` Paraschiv, Andra-Irina
2020-04-21 18:41 ` [PATCH v1 14/15] nitro_enclaves: Add Makefile " Andra Paraschiv
2020-04-23 8:12 ` kbuild test robot
2020-04-24 17:00 ` Paraschiv, Andra-Irina
2020-04-23 8:43 ` kbuild test robot
2020-04-24 15:27 ` Paraschiv, Andra-Irina
2020-04-21 18:41 ` [PATCH v1 15/15] MAINTAINERS: Add entry " Andra Paraschiv
2020-04-21 21:46 ` [PATCH v1 00/15] Add support for Nitro Enclaves Paolo Bonzini
2020-04-23 13:19 ` Paraschiv, Andra-Irina
2020-04-23 13:42 ` Paolo Bonzini
2020-04-23 17:42 ` Paraschiv, Andra-Irina
2020-04-23 17:51 ` Paolo Bonzini
2020-04-23 20:56 ` Alexander Graf
2020-04-23 21:18 ` Paolo Bonzini [this message]
2020-04-24 12:56 ` Alexander Graf
2020-04-24 16:27 ` Paolo Bonzini
2020-04-24 19:11 ` Alexander Graf
2020-04-25 16:05 ` Paolo Bonzini
2020-04-27 9:15 ` Paraschiv, Andra-Irina
2020-04-27 9:22 ` Paraschiv, Andra-Irina
2020-04-27 9:46 ` Paolo Bonzini
2020-04-27 10:00 ` Paraschiv, Andra-Irina
2020-04-28 15:07 ` Alexander Graf
2020-04-29 13:20 ` Paolo Bonzini
2020-04-30 13:59 ` Paraschiv, Andra-Irina
2020-04-30 10:34 ` Paolo Bonzini
2020-04-30 11:21 ` Alexander Graf
2020-04-30 11:38 ` Paolo Bonzini
2020-04-30 11:47 ` Alexander Graf
2020-04-30 11:58 ` Paolo Bonzini
2020-04-30 12:19 ` Alexander Graf
2020-05-07 17:44 ` Pavel Machek
2020-05-08 7:00 ` Paraschiv, Andra-Irina
2020-05-09 19:21 ` Pavel Machek
2020-05-10 11:02 ` Herrenschmidt, Benjamin
2020-05-11 10:49 ` Paraschiv, Andra-Irina
2020-05-11 13:49 ` Stefan Hajnoczi
2020-04-24 3:04 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-04-24 8:19 ` Paraschiv, Andra-Irina
2020-04-24 9:54 ` Paraschiv, Andra-Irina
2020-04-26 1:55 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-04-27 18:39 ` Paraschiv, Andra-Irina
2020-04-24 9:59 ` Tian, Kevin
2020-04-24 13:59 ` Paraschiv, Andra-Irina
2020-04-26 8:16 ` Tian, Kevin
2020-04-27 19:05 ` Paraschiv, Andra-Irina
[not found] ` <CAKXe6SLonLQLAOY9Q_2AzTeg4uJxiknsAWnJpTF0hMcXEG5Tew@mail.gmail.com>
2020-05-11 12:05 ` Paraschiv, Andra-Irina
2020-04-25 15:25 ` Liran Alon
2020-04-27 7:56 ` Paraschiv, Andra-Irina
2020-04-27 11:44 ` Liran Alon
2020-04-28 15:25 ` Alexander Graf
2020-04-28 16:01 ` Liran Alon
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=0467ce02-92f3-8456-2727-c4905c98c307@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@amazon.com \
--cc=andraprs@amazon.com \
--cc=benh@amazon.com \
--cc=colmmacc@amazon.com \
--cc=doebel@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=fllinden@amazon.com \
--cc=graf@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpohlack@amazon.de \
--cc=msw@amazon.com \
--cc=ne-devel-upstream@amazon.com \
--cc=sblbir@amazon.com \
--cc=trawets@amazon.com \
--cc=uwed@amazon.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).