[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c177d918-7421-9441-fb24-45ffe46f8298@redhat.com>
Date: Thu, 28 Jan 2021 16:09:53 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Borislav Petkov <bp@...e.de>,
Sean Christopherson <seanjc@...gle.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Tom Lendacky <thomas.lendacky@....com>,
Brijesh Singh <brijesh.singh@....com>
Subject: Re: [PATCH v2 04/14] x86/cpufeatures: Assign dedicated feature word
for AMD mem encryption
On 14/01/21 18:16, Borislav Petkov wrote:
> On Thu, Jan 14, 2021 at 09:09:28AM -0800, Sean Christopherson wrote:
>> Hmm, patch 05/14 depends on the existence of the new word. That's a non-issue
>> if you're planning on taking this for 5.11. If it's destined for 5.12, maybe
>> get an ack from Paolo on patch 05 and take both through tip?
>
> Yeah, I guess that. Both are not urgent 5.11 material to take 'em now.
> So I guess I'll wait for Paolo's ACK.
If you think this patch is valuable go ahead and pick it. I can wait
until after the merge window to queue patch 5. It is independent from
the others and I had questions, so I am just queuing the others for 5.12.
Paolo
>> I can drop them from this series when I send v3. In hindsight, I
>> should have split these two patches into a separate mini-series from
>> the get-go.
>
> Nah, no worries. We do patch acrobatics on a daily basis. :-)
Powered by blists - more mailing lists