From: "Paraschiv, Andra-Irina" <andraprs@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Alexandru Ciobotaru <alcioa@amazon.com>,
Kamal Mostafa <kamal@canonical.com>,
Alexandru Vasile <lexnv@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
kvm <kvm@vger.kernel.org>,
ne-devel-upstream <ne-devel-upstream@amazon.com>
Subject: Re: [PATCH v1 1/3] nitro_enclaves: Enable Arm support
Date: Fri, 27 Aug 2021 13:19:46 +0300 [thread overview]
Message-ID: <7bed3e99-d69a-bf9b-b33a-acc3e3726fb0@amazon.com> (raw)
In-Reply-To: <YSilmGyvEAc46ujH@kroah.com>
On 27/08/2021 11:43, Greg KH wrote:
> On Thu, Aug 26, 2021 at 08:34:49PM +0300, Andra Paraschiv wrote:
>> Update the kernel config to enable the Nitro Enclaves kernel driver for
>> Arm support.
>>
>> Signed-off-by: Andra Paraschiv <andraprs@amazon.com>
>> ---
>> drivers/virt/nitro_enclaves/Kconfig | 8 ++------
>> 1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/virt/nitro_enclaves/Kconfig b/drivers/virt/nitro_enclaves/Kconfig
>> index 8c9387a232df8..f53740b941c0f 100644
>> --- a/drivers/virt/nitro_enclaves/Kconfig
>> +++ b/drivers/virt/nitro_enclaves/Kconfig
>> @@ -1,17 +1,13 @@
>> # SPDX-License-Identifier: GPL-2.0
>> #
>> -# Copyright 2020 Amazon.com, Inc. or its affiliates. All Rights Reserved.
>> +# Copyright 2020-2021 Amazon.com, Inc. or its affiliates. All Rights Reserved.
>>
>> # Amazon Nitro Enclaves (NE) support.
>> # Nitro is a hypervisor that has been developed by Amazon.
>>
>> -# TODO: Add dependency for ARM64 once NE is supported on Arm platforms. For now,
>> -# the NE kernel driver can be built for aarch64 arch.
>> -# depends on (ARM64 || X86) && HOTPLUG_CPU && PCI && SMP
>> -
>> config NITRO_ENCLAVES
>> tristate "Nitro Enclaves Support"
>> - depends on X86 && HOTPLUG_CPU && PCI && SMP
>> + depends on (ARM64 || X86) && HOTPLUG_CPU && PCI && SMP
> So no code change needed? If not, they why do we have a cpu type at all
> here?
Yes, no codebase changes needed so far.
I've looked during the initial phase of the upstreaming process to also
check the ARM64 build and use / implement functionality that would not
be x86 specific, if possible. And it worked good, for now no necessary
updates.
The supported architectures for the Nitro Enclaves overall project will
be x86 and ARM64 (x86 support has been released, ARM64 support is to be
released), so mentioning these explicitly here. No other architectures
have been considered so far.
Thanks,
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.
next prev parent reply other threads:[~2021-08-27 10:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 17:34 [PATCH v1 0/3] nitro_enclaves: Add support for Arm64 Andra Paraschiv
2021-08-26 17:34 ` [PATCH v1 1/3] nitro_enclaves: Enable Arm support Andra Paraschiv
2021-08-27 7:06 ` Stefano Garzarella
2021-08-27 8:43 ` Greg KH
2021-08-27 10:19 ` Paraschiv, Andra-Irina [this message]
2021-08-26 17:34 ` [PATCH v1 2/3] nitro_enclaves: Update documentation for " Andra Paraschiv
2021-08-27 7:21 ` Stefano Garzarella
2021-08-27 9:35 ` Paraschiv, Andra-Irina
2021-08-26 17:34 ` [PATCH v1 3/3] nitro_enclaves: Add fixes for checkpatch and docs reports Andra Paraschiv
2021-08-26 17:51 ` Vitaly Kuznetsov
2021-08-26 18:22 ` Paraschiv, Andra-Irina
2021-08-27 8:43 ` Greg KH
2021-08-27 10:22 ` Paraschiv, Andra-Irina
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=7bed3e99-d69a-bf9b-b33a-acc3e3726fb0@amazon.com \
--to=andraprs@amazon.com \
--cc=alcioa@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=kamal@canonical.com \
--cc=kvm@vger.kernel.org \
--cc=lexnv@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ne-devel-upstream@amazon.com \
--cc=pbonzini@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--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