Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760345AbcLPMWK (ORCPT ); Fri, 16 Dec 2016 07:22:10 -0500 Received: from mga05.intel.com ([192.55.52.43]:19625 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759890AbcLPMWC (ORCPT ); Fri, 16 Dec 2016 07:22:02 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,357,1477983600"; d="scan'208";a="912888004" Message-ID: <1481890738.9552.70.camel@linux.intel.com> Subject: Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel From: Andy Shevchenko To: Dave Young , Jean Delvare Cc: kexec@lists.infradead.org, Mika Westerberg , Eric Biederman , linux-kernel@vger.kernel.org Date: Fri, 16 Dec 2016 14:18:58 +0200 In-Reply-To: <20161216023213.GA4505@dhcp-128-65.nay.redhat.com> References: <20161202195416.58953-1-andriy.shevchenko@linux.intel.com> <20161202195416.58953-3-andriy.shevchenko@linux.intel.com> <20161215122856.7d24b7a8@endymion> <20161216023213.GA4505@dhcp-128-65.nay.redhat.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 959 Lines: 29 On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > Hi Andy, > > > > On Fri,  2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > > > Until now kexec'ed kernel has no clue where to look for DMI entry > > > point. > > > > > > Pass it via kernel command line parameter in the same way as it's > > > done for ACPI > > > RSDP. > > > > I am no kexec expert but this confuses me. Shouldn't the second > > kernel > > have access to the EFI systab as the first kernel does? It includes > > many more pointers than just ACPI and DMI tables, and it would seem > > inconvenient to have to pass all these addresses individually > > explicitly. > > Yes, in modern linux kernel, kexec has the support for EFI, I think it > should work naturally at least in x86_64. Thanks for this good news! Unfortunately Intel Galileo is 32-bit platform. -- Andy Shevchenko Intel Finland Oy