From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by kanga.kvack.org (Postfix) with ESMTP id E351E6B049D for ; Mon, 29 Oct 2018 15:22:53 -0400 (EDT) Received: by mail-wm1-f70.google.com with SMTP id y185-v6so7824362wmg.6 for ; Mon, 29 Oct 2018 12:22:53 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id r17sor3542365wrx.38.2018.10.29.12.22.52 for (Google Transport Security); Mon, 29 Oct 2018 12:22:52 -0700 (PDT) MIME-Version: 1.0 References: <20181026075900.111462-1-marcorr@google.com> <20181029164813.GH28520@bombadil.infradead.org> In-Reply-To: From: Marc Orr Date: Mon, 29 Oct 2018 19:22:40 +0000 Message-ID: Subject: Re: [kvm PATCH v4 0/2] use vmalloc to allocate vmx vcpus Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Jim Mattson Cc: willy@infradead.org, Wanpeng Li , kvm@vger.kernel.org, David Rientjes , Konrad Rzeszutek Wilk , linux-mm@kvack.org, akpm@linux-foundation.org, pbonzini@redhat.com, rkrcmar@redhat.com, sean.j.christopherson@intel.com On Mon, Oct 29, 2018 at 12:16 PM Marc Orr wrote: > > Thanks for all the discussion on this. Give me a bit to investigate > Dave's suggestions around refactoring the fpu state, and I'll report > back with what I find. > Thanks, > Marc Also, sorry for top-posting on my last email!