Messages in this thread | | | From | "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" <> | Subject | RE: [PATCH v2 1/4] nitro_enclaves: merge contiguous physical memory regions | Date | Wed, 22 Sep 2021 00:27:44 +0000 |
| |
> -----Original Message----- > From: Greg KH [mailto:gregkh@linuxfoundation.org] > Sent: Tuesday, September 21, 2021 11:21 PM > To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) > <longpeng2@huawei.com> > Cc: andraprs@amazon.com; lexnv@amazon.com; alcioa@amazon.com; > linux-kernel@vger.kernel.org; Gonglei (Arei) <arei.gonglei@huawei.com>; > kamal@canonical.com; pbonzini@redhat.com; sgarzare@redhat.com; > stefanha@redhat.com; vkuznets@redhat.com; ne-devel-upstream@amazon.com > Subject: Re: [PATCH v2 1/4] nitro_enclaves: merge contiguous physical memory > regions > > On Tue, Sep 21, 2021 at 11:10:36PM +0800, Longpeng(Mike) wrote: > > There can be cases when there are more memory regions that need to be > > set for an enclave than the maximum supported number of memory regions > > per enclave. One example can be when the memory regions are backed by 2 > > MiB hugepages (the minimum supported hugepage size). > > > > Let's merge the adjacent regions if they are physical contiguous. This > > way the final number of memory regions is less than before merging and > > could potentially avoid reaching maximum. > > > > Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com> > > --- > > drivers/virt/nitro_enclaves/ne_misc_dev.c | 87 > ++++++++++++++++++++----------- > > 1 file changed, 58 insertions(+), 29 deletions(-) > > > > What changed from v1?
It seems you missed the cover letter ?
| |