public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paraschiv, Andra-Irina" <andraprs@amazon.com>
To: Alexander Graf <graf@amazon.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Anthony Liguori <aliguori@amazon.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Colm MacCarthaigh <colmmacc@amazon.com>,
	"David Duncan" <davdunc@amazon.com>,
	Bjoern Doebel <doebel@amazon.de>,
	"David Woodhouse" <dwmw@amazon.co.uk>,
	Frank van der Linden <fllinden@amazon.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Karen Noel <knoel@redhat.com>,
	"Martin Pohlack" <mpohlack@amazon.de>,
	Matt Wilson <msw@amazon.com>, Paolo Bonzini <pbonzini@redhat.com>,
	Balbir Singh <sblbir@amazon.com>,
	Stefano Garzarella <sgarzare@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Stewart Smith <trawets@amazon.com>,
	Uwe Dannowski <uwed@amazon.de>,
	Vitaly Kuznetsov <vkuznets@redhat.com>, kvm <kvm@vger.kernel.org>,
	ne-devel-upstream <ne-devel-upstream@amazon.com>
Subject: Re: [PATCH v6 10/18] nitro_enclaves: Add logic for getting the enclave image load info
Date: Tue, 11 Aug 2020 13:17:31 +0300	[thread overview]
Message-ID: <0ef970b1-eea2-916c-3546-fdc4f2595e99@amazon.com> (raw)
In-Reply-To: <70ec8010-cb3b-50a8-5472-a96c5aa2cf8d@amazon.de>



On 10/08/2020 12:57, Alexander Graf wrote:
>
>
> On 05.08.20 11:10, Andra Paraschiv wrote:
>> Before setting the memory regions for the enclave, the enclave image
>> needs to be placed in memory. After the memory regions are set, this
>> memory cannot be used anymore by the VM, being carved out.
>>
>> Add ioctl command logic to get the offset in enclave memory where to
>> place the enclave image. Then the user space tooling copies the enclave
>> image in the memory using the given memory offset.
>>
>> Signed-off-by: Andra Paraschiv <andraprs@amazon.com>
>
> Reviewed-by: Alexander Graf <graf@amazon.com>

Thanks for review. I included the tag for this one and the next 2 patches.

Andra



Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.


  reply	other threads:[~2020-08-11 10:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05  9:09 [PATCH v6 00/18] Add support for Nitro Enclaves Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 01/18] nitro_enclaves: Add ioctl interface definition Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 02/18] nitro_enclaves: Define the PCI device interface Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 03/18] nitro_enclaves: Define enclave info for internal bookkeeping Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 04/18] nitro_enclaves: Init PCI device driver Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 05/18] nitro_enclaves: Handle PCI device command requests Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 06/18] nitro_enclaves: Handle out-of-band PCI device events Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 07/18] nitro_enclaves: Init misc device providing the ioctl interface Andra Paraschiv
2020-08-10  5:22   ` Alexander Graf
2020-08-11  7:58     ` Paraschiv, Andra-Irina
2020-08-05  9:10 ` [PATCH v6 08/18] nitro_enclaves: Add logic for creating an enclave VM Andra Paraschiv
2020-08-10  6:11   ` Alexander Graf
2020-08-11  8:16     ` Paraschiv, Andra-Irina
2020-08-05  9:10 ` [PATCH v6 09/18] nitro_enclaves: Add logic for setting an enclave vCPU Andra Paraschiv
2020-08-10  7:33   ` Alexander Graf
2020-08-11  8:52     ` Paraschiv, Andra-Irina
2020-08-05  9:10 ` [PATCH v6 10/18] nitro_enclaves: Add logic for getting the enclave image load info Andra Paraschiv
2020-08-10  9:57   ` Alexander Graf
2020-08-11 10:17     ` Paraschiv, Andra-Irina [this message]
2020-08-05  9:10 ` [PATCH v6 11/18] nitro_enclaves: Add logic for setting an enclave memory region Andra Paraschiv
2020-08-10  9:54   ` Alexander Graf
2020-08-05  9:10 ` [PATCH v6 12/18] nitro_enclaves: Add logic for starting an enclave Andra Paraschiv
2020-08-10 10:33   ` Alexander Graf
2020-08-05  9:10 ` [PATCH v6 13/18] nitro_enclaves: Add logic for terminating " Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 14/18] nitro_enclaves: Add Kconfig for the Nitro Enclaves driver Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 15/18] nitro_enclaves: Add Makefile " Andra Paraschiv
2020-08-05 14:23   ` kernel test robot
2020-08-06  5:22     ` Paraschiv, Andra-Irina
2020-08-05  9:10 ` [PATCH v6 16/18] nitro_enclaves: Add sample for ioctl interface usage Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 17/18] nitro_enclaves: Add overview documentation Andra Paraschiv
2020-08-05  9:10 ` [PATCH v6 18/18] MAINTAINERS: Add entry for the Nitro Enclaves driver Andra Paraschiv

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=0ef970b1-eea2-916c-3546-fdc4f2595e99@amazon.com \
    --to=andraprs@amazon.com \
    --cc=aliguori@amazon.com \
    --cc=benh@kernel.crashing.org \
    --cc=colmmacc@amazon.com \
    --cc=davdunc@amazon.com \
    --cc=doebel@amazon.de \
    --cc=dwmw@amazon.co.uk \
    --cc=fllinden@amazon.com \
    --cc=graf@amazon.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=knoel@redhat.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=pbonzini@redhat.com \
    --cc=sblbir@amazon.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=trawets@amazon.com \
    --cc=uwed@amazon.de \
    --cc=vkuznets@redhat.com \
    /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