Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp328253imm; Mon, 9 Jul 2018 02:30:21 -0700 (PDT) X-Google-Smtp-Source: AAOMgpehREhdfhThFQ2aI4brjEfP5ocp4u/LuZALJSen+65MYmEISrrZ34X4scqbi74jmNc01DLm X-Received: by 2002:a17:902:8a95:: with SMTP id p21-v6mr19896592plo.91.1531128621915; Mon, 09 Jul 2018 02:30:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531128621; cv=none; d=google.com; s=arc-20160816; b=pz77l1ai5Ythcu/XIaoClQyGky9pOqzGN+5LMe8IerHA6O/PP4ZyEeXmTMkgD6hotp 33IM4Hh0TZ61ztbJY1QPC077S0oJyeQt3wN3797tyeRvHgIQ+A5t824EczPMct8eJSxb 31F1Fye1mi4XlLsQhAn3yJybVq/PfcK8VyawFXZsEAxi2b2EKzVvQsLmqm+V2UBZXCbL Ycb+/Ej1rkoAj2t7HvkAP3SWCYwQUNijY6AFh1WTb/HkN5ZNbyNr6/p8xamL6YEMiUcP FqltXCgnD68WZ5QbWLjo3f8q8svQxY020ti7kQaAQPEFxOWmflnVy/oFie4Zr9+vO1it v3Vw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=MhojFsnozRn7g9EfQ1GAjB9eAZUahTSkg1uptf8pb30=; b=xIdmtzitVhc3QcG4u+IjJr7Zo2PgHXifiEkYlAuR2paT7Omcvlgvh+Hyp4mkVWOZpG ZI1ot74qGOfx1QfTua1GheKVQiEKzGw5Osw2dmbk6TBzHyzA3qeplz6/XgCrKyO/MIh5 ZaUFnXLwdiLqUDoVqDNiiS9lGlWIiMn+tWTgEyYSqE9vZL70+BWoHw9IFFHc/3QWlS7n b11g0sK5BZmekazq9B0S394ODf2JFmhNmD0BvAWIbSK/WbIcJ+yeT9Td4+8uJOPP0ay2 L2qqZD6gNOusGiYi6dAPoY9/zwB9OtVfF0/N6mk2nQgO/Z8hByY6wB70VVqcuR8VM0wY IWPw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f5-v6si13733041plr.56.2018.07.09.02.30.07; Mon, 09 Jul 2018 02:30:21 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932632AbeGIJ3O (ORCPT + 99 others); Mon, 9 Jul 2018 05:29:14 -0400 Received: from mail.skyhub.de ([5.9.137.197]:41160 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754404AbeGIJ3L (ORCPT ); Mon, 9 Jul 2018 05:29:11 -0400 X-Virus-Scanned: Nedap ESD1 at mail.skyhub.de Received: from mail.skyhub.de ([127.0.0.1]) by localhost (blast.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id s89sPC2jAeDW; Mon, 9 Jul 2018 11:29:10 +0200 (CEST) Received: from nazgul.tnic (unknown [78.130.214.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 44A8C1EC0559; Mon, 9 Jul 2018 11:29:10 +0200 (CEST) Date: Mon, 9 Jul 2018 11:29:01 +0200 From: Borislav Petkov To: lijiang Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com, ebiederm@xmission.com, joro@8bytes.org, thomas.lendacky@amd.com, dyoung@redhat.com, kexec@lists.infradead.org, iommu@lists.linux-foundation.org, bhe@redhat.com Subject: Re: [PATCH 1/5 V5] Add a function(ioremap_encrypted) for kdump when AMD sme enabled Message-ID: <20180709092901.GA22182@nazgul.tnic> References: <20180702072639.10110-1-lijiang@redhat.com> <20180702072639.10110-2-lijiang@redhat.com> <20180702101451.GB28730@zn.tnic> <4ae1cfb5-0a4b-2aac-2575-024e2c74826f@redhat.com> <895db996-febd-d50c-91af-4f1ef3d27bd8@redhat.com> <20180703111428.GB5748@zn.tnic> <4fbb843b-9597-a48b-8b6f-00e354b91950@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 09, 2018 at 02:28:11PM +0800, lijiang wrote: > Last week, I had tried many ways to do this work, but it looks > like that the ways of deducing address is not suitable to another > scenarios, such as mapping some devices mmio space, which are > unencrypted, and the device mmio space is outside kdump kernel like > the old memory, but the old memory is encrypted, we can't find the > general rules to decide when to encrypt or not. If we can't find the "general rules" how is the caller supposed to know how to access the memory? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --