From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH v3 4/4] KVM: VMX: Simplify segment_base Date: Tue, 21 Feb 2017 09:03:32 +0100 Message-ID: <20170221080332.GB3125@gmail.com> References: <20170214194259.75960-1-thgarnie@google.com> <20170214194259.75960-4-thgarnie@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Sender: Ingo Molnar Content-Disposition: inline In-Reply-To: To: Thomas Garnier , Paolo Bonzini Cc: Andy Lutomirski , Jim Mattson , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Kees Cook , Andy Lutomirski , Borislav Petkov , Paul Gortmaker , "Rafael J . Wysocki" , Len Brown , Pavel Machek , Jiri Kosina , Matt Fleming , Ard Biesheuvel , Boris Ostrovsky , Juergen Gross , Rusty Russell , Peter Zijlstra , Christian Borntraeger , Lui List-Id: linux-pm@vger.kernel.org * Thomas Garnier wrote: > > Okay, I guess I will have to wait for it to be integrated to > > linux-next then. Or would you rather to it after this patch set is > > added? > > Read your summary for the patchset of KVM cleanup, I will wait for it to reach > linux-next to rebase and send the new iteration. Note that to be able to apply your readonly-GDT series to the x86 tree I'll need a stable SHA1 to base it on. Paolo, how stable, non-rebasing are the KVM tree commits? Once Andy's patches hit the KVM tree I could pull from you and order it so that I'd send it to Linus only after you sent your bits upstream. That would save us 3 months of patch propagation latency. Or should we keep Andy's KVM patches together with the GDT patches? Either workflow works for me - it's your call as these are predominantly KVM changes. Thanks, Ingo