[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <X/iOtPo7/EoB6ban@google.com>
Date: Fri, 8 Jan 2021 08:56:20 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Steve Rutherford <srutherford@...gle.com>
Cc: Ashish Kalra <ashish.kalra@....com>,
"Dr. David Alan Gilbert" <dgilbert@...hat.com>,
"Singh, Brijesh" <brijesh.singh@....com>,
Paolo Bonzini <pbonzini@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Joerg Roedel <joro@...tes.org>,
Borislav Petkov <bp@...e.de>,
"Lendacky, Thomas" <Thomas.Lendacky@....com>,
X86 ML <x86@...nel.org>, KVM list <kvm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
"dovmurik@...ux.vnet.ibm.com" <dovmurik@...ux.vnet.ibm.com>,
"tobin@....com" <tobin@....com>,
"jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
"frankeh@...ibm.com" <frankeh@...ibm.com>,
"Grimm, Jon" <jon.grimm@....com>
Subject: Re: [PATCH v2 1/9] KVM: x86: Add AMD SEV specific Hypercall3
On Thu, Jan 07, 2021, Steve Rutherford wrote:
> Supporting merging of consecutive entries (or not) is less important
> to get right since it doesn't change any of the APIs. If someone runs
> into performance issues, they can loop back and fix this then. I'm
> slightly concerned with the behavior for overlapping regions.
I'm assuming merging entries will be a near-trivial effort once everything else
is implemented, e.g. KVM will need to traverse the list to remove entries when
address are converted back to private. Piling on merging functionality at that
point should not be all that hard, especially if the list is sorted and entries
are merged on insertion.
Powered by blists - more mailing lists