All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Khalid Aziz <khalid.aziz@hp.com>
Cc: kexec@lists.infradead.org, horms@verge.net.au,
	Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH]kdump: pass noefi and acpi_rsdp= to 2nd kernel
Date: Thu, 13 Sep 2012 09:38:27 -0400	[thread overview]
Message-ID: <20120913133827.GB4396@redhat.com> (raw)
In-Reply-To: <1347028634.20255.79.camel@lyra>

On Fri, Sep 07, 2012 at 08:37:14AM -0600, Khalid Aziz wrote:
> On Fri, 2012-09-07 at 16:56 +0800, Dave Young wrote:
> > Actually in x86 setup code if bootloader do not pass correct efi_info in
> > boot_params efi_enabled will be set to 0 automaticlly.
> > 
> 
> When we kexec a kernel, the EFI signature is missing in the bootloader
> signature in boot_params, so kexec'd kernels currently disable EFI
> automatically even without noefi in this code:
> 
> arch/x86/kernel/setup.c:
> 
> 733         if (!strncmp((char *)&boot_params.efi_info.efi_loader_signature,
> 734                      "EL32", 4)) {
> 735                 efi_enabled = 1;
> 736                 efi_64bit = false;
> 737         } else if (!strncmp((char *)&boot_params.efi_info.efi_loader_signatu     re,             
> 738                      "EL64", 4)) {
> 739                 efi_enabled = 1;
> 740                 efi_64bit = true;
> 741         }
> 
> efi_enabled is initialized to 0.

Hi Khalid,

So what does this mean? Second kernel assumes the regular BIOS and tries
to initialize that way? That sounds broken or is it just fine given
the fact we are anyway not planning to call into any of the efi services.
But what about memory maps, ACPI tables etc.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2012-09-13 13:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  5:44 [PATCH]kdump: pass noefi and acpi_rsdp= to 2nd kernel Dave Young
2012-09-05  7:45 ` Simon Horman
2012-09-06  2:48   ` Dave Young
2012-09-05 13:18 ` Vivek Goyal
2012-09-06  2:58   ` Dave Young
2012-09-06 20:46     ` Vivek Goyal
2012-09-05 23:09 ` Khalid Aziz
2012-09-06  3:18   ` Dave Young
2012-09-06 17:57     ` Khalid Aziz
2012-09-07  8:56       ` Dave Young
2012-09-07 14:37         ` Khalid Aziz
2012-09-13 13:38           ` Vivek Goyal [this message]
2012-09-14 20:32             ` Khalid Aziz
2012-09-20  7:49               ` Eric W. Biederman
2012-09-21 22:50                 ` Khalid Aziz
2012-09-12  2:35         ` Dave Young
2012-10-18  3:12           ` Dave Young
2012-10-18 14:59             ` Khalid Aziz
2012-10-22  2:05               ` Dave Young
2012-09-06 20:24   ` Vivek Goyal
2012-09-07 14:32     ` Khalid Aziz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120913133827.GB4396@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=khalid.aziz@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.