Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751988AbdFSRSd (ORCPT ); Mon, 19 Jun 2017 13:18:33 -0400 Received: from mail.skyhub.de ([5.9.137.197]:47026 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750780AbdFSRSa (ORCPT ); Mon, 19 Jun 2017 13:18:30 -0400 Date: Mon, 19 Jun 2017 19:18:20 +0200 From: Borislav Petkov To: Tom Lendacky , =?utf-8?B?SsO2cmcgUsO2ZGVs?= Cc: linux-arch@vger.kernel.org, linux-efi@vger.kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org, x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, iommu@lists.linux-foundation.org, Rik van Riel , Radim =?utf-8?B?S3LEjW3DocWZ?= , Toshimitsu Kani , Arnd Bergmann , Jonathan Corbet , Matt Fleming , "Michael S. Tsirkin" , Joerg Roedel , Konrad Rzeszutek Wilk , Paolo Bonzini , Larry Woodman , Brijesh Singh , Ingo Molnar , Andy Lutomirski , "H. Peter Anvin" , Andrey Ryabinin , Alexander Potapenko , Dave Young , Thomas Gleixner , Dmitry Vyukov Subject: Re: [PATCH v6 26/34] iommu/amd: Allow the AMD IOMMU to work with memory encryption Message-ID: <20170619171820.tq4htttamb52pyx5@pd.tnic> References: <20170607191309.28645.15241.stgit@tlendack-t1.amdoffice.net> <20170607191745.28645.81756.stgit@tlendack-t1.amdoffice.net> <20170614174208.p2yr5exs4b6pjxhf@pd.tnic> <0611d01a-19f8-d6ae-2682-932789855518@amd.com> <20170615094111.wga334kg2bhxqib3@pd.tnic> <921153f5-1528-31d8-b815-f0419e819aeb@amd.com> <20170615153322.nwylo3dzn4fdx6n6@pd.tnic> <3db2c52d-5e63-a1df-edd4-975bce7f29c2@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3db2c52d-5e63-a1df-edd4-975bce7f29c2@amd.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 510 Lines: 18 On Thu, Jun 15, 2017 at 11:33:41AM -0500, Tom Lendacky wrote: > Changing the signature back reverts to the original way, so this can be > looked at separate from this patchset then. Right, the patch which added the volatile thing was this one: 4bf5beef578e ("iommu/amd: Don't put completion-wait semaphore on stack") and the commit message doesn't say why the thing needs to be volatile at all. Joerg? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.