From: "Longpeng(Mike)" <longpeng2@huawei.com>
To: <andraprs@amazon.com>, <lexnv@amazon.com>, <alcioa@amazon.com>
Cc: <linux-kernel@vger.kernel.org>, <arei.gonglei@huawei.com>,
<gregkh@linuxfoundation.org>, <kamal@canonical.com>,
<pbonzini@redhat.com>, <sgarzare@redhat.com>,
<stefanha@redhat.com>, <vkuznets@redhat.com>,
<ne-devel-upstream@amazon.com>,
"Longpeng(Mike)" <longpeng2@huawei.com>
Subject: [PATCH v2 0/4] merge contiguous physical memory regions
Date: Tue, 21 Sep 2021 23:10:35 +0800 [thread overview]
Message-ID: <20210921151039.1502-1-longpeng2@huawei.com> (raw)
Hi guys,
This patchset try to merge the contiguous physical memory regions when
set user memory regions, you can see message in PATCH 1 for details.
Please review when you free, thank!
Changes v1 -> v2:
- update the commit message as Andra's suggestion [Andra]
- remove TODO completely in ne_set_user_memory_region_ioctl [Andra]
- extract the physical memory regions setup into individual
function
- add kunit tests [Andra]
Longpeng(Mike) (4):
nitro_enclaves: merge contiguous physical memory regions
nitro_enclaves: sanity check the physical region during setting
nitro_enclaves: add test framework for the misc functionality
nitro_enclaves: add kunit tests for physical contiguous region merging
drivers/virt/nitro_enclaves/Kconfig | 8 ++
drivers/virt/nitro_enclaves/ne_misc_dev.c | 160 ++++++++++++++++++++---------
drivers/virt/nitro_enclaves/ne_misc_test.c | 63 ++++++++++++
3 files changed, 182 insertions(+), 49 deletions(-)
create mode 100644 drivers/virt/nitro_enclaves/ne_misc_test.c
--
1.8.3.1
next reply other threads:[~2021-09-21 15:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 15:10 Longpeng(Mike) [this message]
2021-09-21 15:10 ` [PATCH v2 1/4] nitro_enclaves: " Longpeng(Mike)
2021-09-21 15:20 ` Greg KH
2021-09-22 1:09 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-09-21 15:20 ` Greg KH
2021-09-22 0:27 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-10-03 13:00 ` Paraschiv, Andra-Irina
2021-10-05 13:54 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-10-06 11:11 ` Paraschiv, Andra-Irina
2021-09-21 15:10 ` [PATCH v2 2/4] nitro_enclaves: sanity check the physical region during setting Longpeng(Mike)
2021-10-03 13:29 ` Paraschiv, Andra-Irina
2021-09-21 15:10 ` [PATCH v2 3/4] nitro_enclaves: add test framework for the misc functionality Longpeng(Mike)
2021-09-21 15:20 ` Greg KH
2021-09-22 0:33 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-09-22 5:55 ` Greg KH
2021-10-03 13:49 ` Paraschiv, Andra-Irina
2021-10-07 2:05 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-10-07 15:37 ` Paraschiv, Andra-Irina
2021-09-21 15:10 ` [PATCH v2 4/4] nitro_enclaves: add kunit tests for physical contiguous region merging Longpeng(Mike)
2021-10-03 14:14 ` Paraschiv, Andra-Irina
2021-09-27 7:00 ` [PATCH v2 0/4] merge contiguous physical memory regions 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=20210921151039.1502-1-longpeng2@huawei.com \
--to=longpeng2@huawei.com \
--cc=alcioa@amazon.com \
--cc=andraprs@amazon.com \
--cc=arei.gonglei@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=kamal@canonical.com \
--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
all inboxes | Powered by JetHome®