Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932427AbbHYOXO (ORCPT ); Tue, 25 Aug 2015 10:23:14 -0400 Received: from mail-io0-f169.google.com ([209.85.223.169]:32990 "EHLO mail-io0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754038AbbHYOXL (ORCPT ); Tue, 25 Aug 2015 10:23:11 -0400 MIME-Version: 1.0 In-Reply-To: <20150825141819.GA3013@codeblueprint.co.uk> References: <1440090902-15157-1-git-send-email-izumi.taku@jp.fujitsu.com> <1440090952-15211-1-git-send-email-izumi.taku@jp.fujitsu.com> <20150825141819.GA3013@codeblueprint.co.uk> Date: Tue, 25 Aug 2015 16:23:10 +0200 Message-ID: Subject: Re: [PATCH 1/2] efi: Add EFI_MEMORY_MORE_RELIABLE support to efi_md_typeattr_format() From: Ard Biesheuvel To: Matt Fleming Cc: Taku Izumi , "linux-kernel@vger.kernel.org" , "linux-efi@vger.kernel.org" , "x86@kernel.org" , Matt Fleming , "tglx@linutronix.de" , "mingo@redhat.com" , "hpa@zytor.com" , Tony Luck , qiuxishi@huawei.com, kamezawa.hiroyu@jp.fujitsu.com, Laszlo Ersek , Borislav Petkov Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2547 Lines: 54 On 25 August 2015 at 16:18, Matt Fleming wrote: > On Fri, 21 Aug, at 02:15:52AM, Taku Izumi wrote: >> UEFI spec 2.5 introduces new Memory Attribute Definition named >> EFI_MEMORY_MORE_RELIABLE. This patch adds this new attribute >> support to efi_md_typeattr_format(). >> >> Signed-off-by: Taku Izumi >> --- >> drivers/firmware/efi/efi.c | 6 ++++-- >> 1 file changed, 4 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c >> index d6144e3..aadc1c4 100644 >> --- a/drivers/firmware/efi/efi.c >> +++ b/drivers/firmware/efi/efi.c >> @@ -589,12 +589,14 @@ char * __init efi_md_typeattr_format(char *buf, size_t size, >> attr = md->attribute; >> if (attr & ~(EFI_MEMORY_UC | EFI_MEMORY_WC | EFI_MEMORY_WT | >> EFI_MEMORY_WB | EFI_MEMORY_UCE | EFI_MEMORY_WP | >> - EFI_MEMORY_RP | EFI_MEMORY_XP | EFI_MEMORY_RUNTIME)) >> + EFI_MEMORY_RP | EFI_MEMORY_XP | EFI_MEMORY_RUNTIME | >> + EFI_MEMORY_MORE_RELIABLE)) >> snprintf(pos, size, "|attr=0x%016llx]", >> (unsigned long long)attr); >> else >> - snprintf(pos, size, "|%3s|%2s|%2s|%2s|%3s|%2s|%2s|%2s|%2s]", >> + snprintf(pos, size, "|%3s|%4s|%2s|%2s|%2s|%3s|%2s|%2s|%2s|%2s]", >> attr & EFI_MEMORY_RUNTIME ? "RUN" : "", >> + attr & EFI_MEMORY_MORE_RELIABLE ? "RELY" : "", >> attr & EFI_MEMORY_XP ? "XP" : "", >> attr & EFI_MEMORY_RP ? "RP" : "", >> attr & EFI_MEMORY_WP ? "WP" : "", > > I'm not keen on using "RELY" because I don't think it's at all obvious > what it means. "RELI" would be closer, but still could use some > improvement. > > Since we turned off this kernel output by default (at least on x86) > because the line length had grown quite long, maybe we should just > embrace it and print "RELIABLE" in full? > Since its meaning is not at all obvious even when printing RELIABLE in full, couldn't we simply use 'MR' instead? You need the UEFI spec to make sense of this anyway ... (Same goes for RUN btw, perhaps RT would even be clearer there) -- Ard. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/