From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BD3ECC43381 for ; Fri, 1 Mar 2019 14:01:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9372C20850 for ; Fri, 1 Mar 2019 14:01:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388246AbfCAOBe (ORCPT ); Fri, 1 Mar 2019 09:01:34 -0500 Received: from mx2.suse.de ([195.135.220.15]:57506 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728098AbfCAOBe (ORCPT ); Fri, 1 Mar 2019 09:01:34 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C1719B00E; Fri, 1 Mar 2019 14:01:32 +0000 (UTC) Date: Fri, 01 Mar 2019 15:01:32 +0100 Message-ID: From: Takashi Iwai To: Ard Biesheuvel Cc: "Lee, Chun-Yi" , linux-efi , Linux Kernel Mailing List Subject: Re: [PATCH] efi: Downgrade "EFI_MEMMAP is not enabled" message In-Reply-To: References: <20190301134033.2100-1-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 01 Mar 2019 14:53:39 +0100, Ard Biesheuvel wrote: > > On Fri, 1 Mar 2019 at 14:40, Takashi Iwai wrote: > > > > Since 38ac0287b7f4 ("fbdev/efifb: Honour UEFI memory map attributes > > when mapping the FB"), efifb_probe() checks its memory range via > > efi_mem_desc_lookup(), and this leads to a spurious error message > > "EFI_MEMMAP is not enabled" at every boot on KVM. This is quite > > annoying since the error message appears even if you set "quiet" boot > > option. > > > > Actually there are only a few places that call efi_mem_desc_lookup() > > function, and the other callers do give the explicit error messages > > when the function returns an error in anyway. That is, the error > > message in the function is more or less moot. > > > > So let's downgrade the error message for stop annoying users. > > > > Fixes: 38ac0287b7f4 ("fbdev/efifb: Honour UEFI memory map attributes when mapping the FB") > > Bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1127339 > > Signed-off-by: Takashi Iwai > > --- > > drivers/firmware/efi/efi.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c > > index 55b77c576c42..50ac33097458 100644 > > --- a/drivers/firmware/efi/efi.c > > +++ b/drivers/firmware/efi/efi.c > > @@ -409,7 +409,7 @@ int efi_mem_desc_lookup(u64 phys_addr, efi_memory_desc_t *out_md) > > efi_memory_desc_t *md; > > > > if (!efi_enabled(EFI_MEMMAP)) { > > - pr_err_once("EFI_MEMMAP is not enabled.\n"); > > + pr_debug("EFI_MEMMAP is not enabled.\n"); > > return -EINVAL; > > } > > > > efifb_probe() only calls efi_mem_desc_lookup() if > screen_info.orig_video_isVGA == VIDEO_TYPE_EFI, which only gets > assigned on a EFI boot. > > So even though I don't object to the patch as is, I would like to > understand where this error message is coming from, given that it > means that you are running on a UEFI system without the EFI memory > map. > > Is this system booting via GRUB in EFI mode? No, it's booted in legacy boot mode. But the primary fb is efifb, and that's why the message appears. thanks, Takashi