Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp1375329imd; Sat, 27 Oct 2018 07:52:41 -0700 (PDT) X-Google-Smtp-Source: AJdET5d7YvvJ4JDFrD9xSs8SaX6KYUardOMDcn54h+02xu9TpyqloB5dHJDRKffLedM3vHDSgIYt X-Received: by 2002:a63:dc0c:: with SMTP id s12mr7494518pgg.398.1540651961719; Sat, 27 Oct 2018 07:52:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540651961; cv=none; d=google.com; s=arc-20160816; b=bBkDr3LJcul/Xq1HFvcm6CNMBmJTcnCdV9njsPxY4P+MVHbr39ubbzHSEpN0HaU8fi t0QXVCeDfDZ5S4X6sv4numl1rV0jb5FfW7sDlPgXbJna4e3Py990atSfmm15DI/oPVEA CLXKJ/ehOM/1gu6uQWOyd42mEko7ytBcaRAzKkKMzshHv0fA+2/YevO75f3V0cK5Cgcj o1p9YqSE2r927zvnEZVw3ooN+a6o5gfT/5tNVW4xXyF7VfBrMfBun5x1mYCBeAnWxYhu 5kjwyNm59ONOONvvAtHW/y18nT55H6uQPyZxnebTmvW8qssfJkChDRONOlZL9PRM+nJ0 BkcA== 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; bh=YhLNRePVqk5HKtcjJF2WHRsDBsyQP9HP3lrAEvyRW8c=; b=F9qcWi/wOaa9ediA0BaiIbyQoe5BKhMkiqGdvy5U2fjUGHJlLs8keIiGDj7Ch0HJpi cpBQR/hI+qPlA62hAGpMk19sIeTc4Q3dHyPjQ+h4/TT29PH0N4yIDxZ6AuHJwCSXzY3k UmAeJRA6x+yFGUI5ZsDKhAj6jYiFpndIfdAV8KUog3X3++tDRBqnxRn3mKY39fdnhEOI yIG+29Dg9UOKYBbly8y2KpKn2fjGx+61EEClFG6By7Yug5TRxdvTfccLnjWxI/rQHwsG aQG5fxXjb2n74Q82Gjsx7Ayl+hmllHGQLirTvuted9+25Gsx68zeby1HazWeVqxYkpsa ja3Q== 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 n6-v6si14632718pla.99.2018.10.27.07.52.26; Sat, 27 Oct 2018 07:52:41 -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 S1728745AbeJ0XdA (ORCPT + 99 others); Sat, 27 Oct 2018 19:33:00 -0400 Received: from mail.skyhub.de ([5.9.137.197]:39252 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728629AbeJ0XdA (ORCPT ); Sat, 27 Oct 2018 19:33:00 -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 BiYLkZVQrnPA; Sat, 27 Oct 2018 16:51:44 +0200 (CEST) Received: from nazgul.tnic (x2f7f1ca.dyn.telefonica.de [2.247.241.202]) (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 1855C1EC0496; Sat, 27 Oct 2018 16:51:43 +0200 (CEST) Date: Sat, 27 Oct 2018 16:51:51 +0200 From: Borislav Petkov To: lijiang Cc: Baoquan He , Petr Tesarik , linux-kernel@vger.kernel.org, x86@kernel.org, kexec@lists.infradead.org, mingo@redhat.com, tglx@linutronix.de, dyoung@redhat.com Subject: Re: [PATCH] kdump, vmcoreinfo: Export sme_me_mask value to vmcoreinfo Message-ID: <20181027145151.GA7338@nazgul.tnic> References: <1263471c-a27d-a698-15f0-b5947f13ea93@redhat.com> <20181026182440.20a4b107@ezekiel.suse.cz> <20181026222517.GB26927@nazgul.tnic> <20181027081343.GA1884@MiWiFi-R3L-srv> <20181027091007.GB1046@nazgul.tnic> <20181027093917.GA14493@MiWiFi-R3L-srv> <20181027101221.GC1046@nazgul.tnic> <20181027110858.GB14493@MiWiFi-R3L-srv> 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 Sat, Oct 27, 2018 at 10:41:56PM +0800, lijiang wrote: > Actually, the value of 'sme_me_mask' is 0x800000000000 when SME is > enabled, otherwise it is 0. That is to say, if the bit 47 is set, the > bit number is also 0x800000000000 (1 << 47UL); Yes, and you can simply copy the mask into your variable and export that. Thinking about it more, though, it might be better if you instead export a smaller value - not an u64 - and construct the mask in userspace. I.e., a u8 which should be enough for your current purposes. I say current because if it turns out we need to export more SME-related info to userspace, exporting an u64 and then OR-ing in more information in it would allow that. u8 not so much. So doing something like: [ misc ][ enc bit ][ other misc SME info ] 0000_0000_0000_0000_1000_0000_0000_0000_0000_0000_0000_0000_0000_0000_0000_0000 63 59 55 51 47 43 39 35 31 27 23 19 15 11 7 3 would allow for exporting that additional info. Especially if we want to use VMCOREINFO for more than kexec things. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --