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=-11.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 8D78CC48BCF for ; Wed, 9 Jun 2021 11:56:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 716C861263 for ; Wed, 9 Jun 2021 11:56:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239655AbhFIL6B (ORCPT ); Wed, 9 Jun 2021 07:58:01 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:38497 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239571AbhFIL57 (ORCPT ); Wed, 9 Jun 2021 07:57:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623239764; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=QsYYuHrua3D0nwfbXiXkP8WpKTH3SeSa8f6XqnxLdhM=; b=IdbAaP1W1rUf4m9PaTGB2hvdgn0reHmmU7Llj3KRnTzMY5hQTa8u0KUsWFKgg9zD3g+RwG kxtM7HUPI/GaLjAQNCsAGN3eZ5/hu3M6p53Pf0zEfUKgEKpxLj/GZvK7oFWdPSDvl1hfUf 2juzW4x28u0a1XXEstk4NuNM6/ycPg4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-318-gJ5uh2mDNlChH6Z5_WPjqA-1; Wed, 09 Jun 2021 07:56:03 -0400 X-MC-Unique: gJ5uh2mDNlChH6Z5_WPjqA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 89D17100A8EB; Wed, 9 Jun 2021 11:56:01 +0000 (UTC) Received: from dhcp-128-65.nay.redhat.com (ovpn-12-35.pek2.redhat.com [10.72.12.35]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 853AD60877; Wed, 9 Jun 2021 11:55:57 +0000 (UTC) Date: Wed, 9 Jun 2021 19:55:54 +0800 From: Dave Young To: Andy Shevchenko Cc: Andy Shevchenko , Jean Delvare , Linux Kernel Mailing List , Mika Westerberg , Javier =?iso-8859-1?B?VGnh?= , kexec@lists.infradead.org, Eric Biederman , linux-efi , Matt Fleming , Ard Biesheuvel Subject: Re: [PATCH v1 0/2] firmware: dmi_scan: Make it work in kexec'ed kernel Message-ID: References: <20161202195416.58953-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/08/21 at 03:38pm, Andy Shevchenko wrote: > On Tue, Jun 8, 2021 at 3:29 PM Dave Young wrote: > > On 06/07/21 at 08:18pm, Andy Shevchenko wrote: > > > On Mon, Jun 07, 2021 at 07:22:21PM +0300, Andy Shevchenko wrote: > > > > On Sat, Jun 05, 2021 at 03:51:05PM +0800, Dave Young wrote: > > > > > On 06/02/21 at 11:53am, Andy Shevchenko wrote: > > > > > > On Wed, Jun 02, 2021 at 11:42:14AM +0300, Andy Shevchenko wrote: > > > > > > > On Fri, Dec 02, 2016 at 09:54:14PM +0200, Andy Shevchenko wrote: > > > > > > > > Until now DMI information is lost when kexec'ing. Fix this in the same way as > > > > > > > > it has been done for ACPI RSDP. > > > > > > > > > > > > > > > > Series has been tested on Galileo Gen2 where DMI is used by drivers, in > > > > > > > > particular the default I2C host speed is choosen based on DMI system > > > > > > > > information and now gets it correct. > > > > > > > > > > > > > > Still nothing happens for a while and problem still exists. > > > > > > > Can we do something about it, please? > > > > > > > > > > Seems I totally missed this thread. Old emails lost. > > > > > > > > You can always access to it via lore :-) > > > > https://lore.kernel.org/linux-efi/20161217105721.GB6922@dhcp-128-65.nay.redhat.com/T/#u > > > > Thanks. Hmm, this is for 32bit efi. kexec efi boot support was only > > added for 64bit. So if 32bit dmidecode does not work I'm not surprise. > > > > > > > > > > (Okay, it's not full, but contains main parts anyway) > > > > > > > > > > > > > The question Ard asked is to confirm if the firmware converted the > > > > > SMBIOS3 addr to a virtual address after exit boot service. I do not > > > > > remember some easy way to check it due to lost the context of the code. > > > > > But you can try to check it via dmesg|grep SMBIOS both in normal boot > > > > > and kexeced boot log. And then compare if those addresses are > > > > > identical. > > > > > > > > > > If the SMBIOS3 addr in kexec kernel is different then it should have > > > > > been modified by firmware. Then we need patch kernel and kexec-tools to > > > > > support it. > > > > > > > > > > You can try below patch to see if it works: > > > > > > > > So, AFAIU I have to apply patch to kexec tools for the fist kernel + userspace > > > > and apply kernel patch for the second kernel? Or it's all for the first one? > > > > > > > > > apply a kexec-tools patch to kexec-tools if you do not use kexec -s > > > > > (kexec_file_load): > > > > > > > > Here is how we are using it: > > > > https://github.com/andy-shev/buildroot/blob/intel/board/intel/common/netboot/udhcpc-script.sh#L54 > > > > > > Okay, thanks for the patches. I have applied them to both kernels, so the first > > > one and second one are the same and kexec tools have a patch provided in the > > > user space of the both kernels (only first one in use though). > > > > > > Before applying your patch, I have reverted my hacks (as per this series). > > > > > > Result is: > > > > > > # uname -a > > > Linux buildroot 5.13.0-rc5+ #1 SMP Mon Jun 7 19:49:40 EEST 2021 i586 GNU/Linux > > > # dmidecode > > > # dmidecode 3.3 > > > Scanning /dev/mem for entry point. > > > # No SMBIOS nor DMI entry point found, sorry. > > > > > > I.o.w. it does NOT fix the issue. My patches do (with a hint from user space). > > > > As I said, since it is 32bit efi, so your test results are expected, > > also no need to check the kernel log about SMBIOS3 address changed or > > not. > > So, what shall I do? It's already 5 years passed without any progress > while my patches definitely help here. > Should I rebase and resubmit? Probably it is doable to have kexec on 32bit efi working without runtime service support, that means no need the trick of fixed mapping. If I can restore my vm to boot 32bit efi on this weekend then I may provide some draft patches for test. > > -- > With Best Regards, > Andy Shevchenko > Thanks Dave From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1lqwoZ-00DUIQ-Uo for kexec@lists.infradead.org; Wed, 09 Jun 2021 11:56:09 +0000 Date: Wed, 9 Jun 2021 19:55:54 +0800 From: Dave Young Subject: Re: [PATCH v1 0/2] firmware: dmi_scan: Make it work in kexec'ed kernel Message-ID: References: <20161202195416.58953-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Andy Shevchenko Cc: Andy Shevchenko , Jean Delvare , Linux Kernel Mailing List , Mika Westerberg , Javier =?iso-8859-1?B?VGnh?= , kexec@lists.infradead.org, Eric Biederman , linux-efi , Matt Fleming , Ard Biesheuvel On 06/08/21 at 03:38pm, Andy Shevchenko wrote: > On Tue, Jun 8, 2021 at 3:29 PM Dave Young wrote: > > On 06/07/21 at 08:18pm, Andy Shevchenko wrote: > > > On Mon, Jun 07, 2021 at 07:22:21PM +0300, Andy Shevchenko wrote: > > > > On Sat, Jun 05, 2021 at 03:51:05PM +0800, Dave Young wrote: > > > > > On 06/02/21 at 11:53am, Andy Shevchenko wrote: > > > > > > On Wed, Jun 02, 2021 at 11:42:14AM +0300, Andy Shevchenko wrote: > > > > > > > On Fri, Dec 02, 2016 at 09:54:14PM +0200, Andy Shevchenko wrote: > > > > > > > > Until now DMI information is lost when kexec'ing. Fix this in the same way as > > > > > > > > it has been done for ACPI RSDP. > > > > > > > > > > > > > > > > Series has been tested on Galileo Gen2 where DMI is used by drivers, in > > > > > > > > particular the default I2C host speed is choosen based on DMI system > > > > > > > > information and now gets it correct. > > > > > > > > > > > > > > Still nothing happens for a while and problem still exists. > > > > > > > Can we do something about it, please? > > > > > > > > > > Seems I totally missed this thread. Old emails lost. > > > > > > > > You can always access to it via lore :-) > > > > https://lore.kernel.org/linux-efi/20161217105721.GB6922@dhcp-128-65.nay.redhat.com/T/#u > > > > Thanks. Hmm, this is for 32bit efi. kexec efi boot support was only > > added for 64bit. So if 32bit dmidecode does not work I'm not surprise. > > > > > > > > > > (Okay, it's not full, but contains main parts anyway) > > > > > > > > > > > > > The question Ard asked is to confirm if the firmware converted the > > > > > SMBIOS3 addr to a virtual address after exit boot service. I do not > > > > > remember some easy way to check it due to lost the context of the code. > > > > > But you can try to check it via dmesg|grep SMBIOS both in normal boot > > > > > and kexeced boot log. And then compare if those addresses are > > > > > identical. > > > > > > > > > > If the SMBIOS3 addr in kexec kernel is different then it should have > > > > > been modified by firmware. Then we need patch kernel and kexec-tools to > > > > > support it. > > > > > > > > > > You can try below patch to see if it works: > > > > > > > > So, AFAIU I have to apply patch to kexec tools for the fist kernel + userspace > > > > and apply kernel patch for the second kernel? Or it's all for the first one? > > > > > > > > > apply a kexec-tools patch to kexec-tools if you do not use kexec -s > > > > > (kexec_file_load): > > > > > > > > Here is how we are using it: > > > > https://github.com/andy-shev/buildroot/blob/intel/board/intel/common/netboot/udhcpc-script.sh#L54 > > > > > > Okay, thanks for the patches. I have applied them to both kernels, so the first > > > one and second one are the same and kexec tools have a patch provided in the > > > user space of the both kernels (only first one in use though). > > > > > > Before applying your patch, I have reverted my hacks (as per this series). > > > > > > Result is: > > > > > > # uname -a > > > Linux buildroot 5.13.0-rc5+ #1 SMP Mon Jun 7 19:49:40 EEST 2021 i586 GNU/Linux > > > # dmidecode > > > # dmidecode 3.3 > > > Scanning /dev/mem for entry point. > > > # No SMBIOS nor DMI entry point found, sorry. > > > > > > I.o.w. it does NOT fix the issue. My patches do (with a hint from user space). > > > > As I said, since it is 32bit efi, so your test results are expected, > > also no need to check the kernel log about SMBIOS3 address changed or > > not. > > So, what shall I do? It's already 5 years passed without any progress > while my patches definitely help here. > Should I rebase and resubmit? Probably it is doable to have kexec on 32bit efi working without runtime service support, that means no need the trick of fixed mapping. If I can restore my vm to boot 32bit efi on this weekend then I may provide some draft patches for test. > > -- > With Best Regards, > Andy Shevchenko > Thanks Dave _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec