All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-efi@vger.kernel.org, Toshi Kani <toshi.kani@hp.com>,
	Greg KH <greg@kroah.com>,
	x86@kernel.org, kexec@lists.infradead.org,
	James.Bottomley@HansenPartnership.com, horms@verge.net.au,
	bp@alien8.de, ebiederm@xmission.com,
	"H. Peter Anvin" <hpa@zytor.com>,
	dyoung@redhat.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: [patch 1/3 v2] Add function get_bootparam
Date: Tue, 12 Nov 2013 09:26:52 -0500	[thread overview]
Message-ID: <20131112142652.GA24980@redhat.com> (raw)
In-Reply-To: <aa0ccca4-b27b-41b6-8adb-3c969eb29bf7@email.android.com>

On Tue, Nov 12, 2013 at 04:58:50PM +1300, Matthew Garrett wrote:
> Well, there's one alternative - don't export this at all and only support UEFI kernels that have an in-kernel loader, then just pass the data internally. 

Hi Matthew,

I am still writing that in-kernel support for kexec/kdump. I guess in
next 2 weeks I might be able to post a basic RFC version. (no EFI support
in this version though).

Having said that, I think that it is good to export these values to
user space and make existing code work with UEFI. New code (if it gets
in at all) will slowly mature over a period of time and transition to it
will be slow. I think initially it will be used only if secureboot is
enabled. And in the mean time we need a good solution for kexec/kdump
with UEFI. 

Thanks
Vivek

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

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Toshi Kani <toshi.kani-VXdhtT5mjnY@public.gmane.org>,
	Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>,
	x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org,
	horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org,
	bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org,
	ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org,
	"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [patch 1/3 v2] Add function get_bootparam
Date: Tue, 12 Nov 2013 09:26:52 -0500	[thread overview]
Message-ID: <20131112142652.GA24980@redhat.com> (raw)
In-Reply-To: <aa0ccca4-b27b-41b6-8adb-3c969eb29bf7-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>

On Tue, Nov 12, 2013 at 04:58:50PM +1300, Matthew Garrett wrote:
> Well, there's one alternative - don't export this at all and only support UEFI kernels that have an in-kernel loader, then just pass the data internally. 

Hi Matthew,

I am still writing that in-kernel support for kexec/kdump. I guess in
next 2 weeks I might be able to post a basic RFC version. (no EFI support
in this version though).

Having said that, I think that it is good to export these values to
user space and make existing code work with UEFI. New code (if it gets
in at all) will slowly mature over a period of time and transition to it
will be slow. I think initially it will be used only if secureboot is
enabled. And in the mean time we need a good solution for kexec/kdump
with UEFI. 

Thanks
Vivek

  parent reply	other threads:[~2013-11-12 14:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  8:29 [patch 0/3 v2] kexec-tools: efi runtime support dyoung
2013-11-05  8:29 ` dyoung-H+wXaHxf7aLQT0dZR+AlfA
2013-11-05  8:29 ` [patch 1/3 v2] Add function get_bootparam dyoung
2013-11-05  8:29   ` dyoung-H+wXaHxf7aLQT0dZR+AlfA
2013-11-12  1:27   ` Toshi Kani
2013-11-12  1:27     ` Toshi Kani
2013-11-12  2:14     ` Dave Young
2013-11-12  2:14       ` Dave Young
2013-11-12  3:20     ` H. Peter Anvin
2013-11-12  3:20       ` H. Peter Anvin
2013-11-12  3:53       ` Ingo Molnar
2013-11-12  3:53         ` Ingo Molnar
     [not found]         ` <aa0ccca4-b27b-41b6-8adb-3c969eb29bf7@email.android.com>
2013-11-12 14:26           ` Vivek Goyal [this message]
2013-11-12 14:26             ` Vivek Goyal
2013-11-12  7:58       ` Greg KH
2013-11-12  7:58         ` Greg KH
2013-11-12  8:08         ` Dave Young
2013-11-12  8:08           ` Dave Young
2013-11-12  8:30           ` Greg KH
2013-11-12  8:30             ` Greg KH
2013-11-12  8:50             ` Dave Young
2013-11-12  8:50               ` Dave Young
2013-11-12  9:37             ` H. Peter Anvin
2013-11-12  9:37               ` H. Peter Anvin
2013-11-12  9:51               ` Greg KH
2013-11-12  9:51                 ` Greg KH
2013-11-13  0:50                 ` Dave Young
2013-11-13  0:50                   ` Dave Young
2013-11-18  2:22                   ` Dave Young
2013-11-18  2:22                     ` Dave Young
2013-11-18  3:29                     ` H. Peter Anvin
2013-11-18  3:29                       ` H. Peter Anvin
2013-11-18  5:29                       ` Dave Young
2013-11-18  5:29                         ` Dave Young
2013-11-18  5:36                         ` H. Peter Anvin
2013-11-18  5:36                           ` H. Peter Anvin
2013-11-05  8:29 ` [patch 2/3 v2] Add efi_info in x86 setup header dyoung
2013-11-05  8:29   ` dyoung-H+wXaHxf7aLQT0dZR+AlfA
2013-11-05  8:29 ` [patch 3/3 v2] Passing efi related data via setup_data dyoung
2013-11-05  8:29   ` dyoung-H+wXaHxf7aLQT0dZR+AlfA

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=20131112142652.GA24980@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bp@alien8.de \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=greg@kroah.com \
    --cc=horms@verge.net.au \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=toshi.kani@hp.com \
    --cc=x86@kernel.org \
    /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.