From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: EFI GetNextVariableName crashes when running under
 Xen, but not under Linux. efi-rs=0 works. No memmap issues
Date: Wed, 28 Jan 2015 14:02:02 +0000
Message-ID: <54C8F9EA020000780005A55E@mail.emea.novell.com>
References: <20150126162753.GA1812@l.oracle.com>
	<54C680C90200007800059907@mail.emea.novell.com>
	<20150127000247.GU3473@olila.local.net-space.pl>
	<54C6DCB7.3060206@citrix.com>
	<54C752460200007800059B8B@mail.emea.novell.com>
	<20150127201858.GY3473@olila.local.net-space.pl>
	<54C8AF37020000780005A330@mail.emea.novell.com>
	<20150128125703.GA3473@olila.local.net-space.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <JBeulich@suse.com>) id 1YGTC1-0000UD-2f
	for xen-devel@lists.xenproject.org; Wed, 28 Jan 2015 14:02:05 +0000
In-Reply-To: <20150128125703.GA3473@olila.local.net-space.pl>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel <xen-devel@lists.xenproject.org>
List-Id: xen-devel@lists.xenproject.org

>>> On 28.01.15 at 13:57, <daniel.kiper@oracle.com> wrote:
> On Wed, Jan 28, 2015 at 08:43:19AM +0000, Jan Beulich wrote:
>> >>> On 27.01.15 at 21:18, <daniel.kiper@oracle.com> wrote:
>> > I am going to align EFI early command line parser to legacy
>> > BIOS early boot path parser (I think about vga command line
>> > option). So, I think that this EFI "bug" work could be based
>> > on it.
>>
>> The vga option is completely meaningless under EFI. And any such
> 
> Yep, I know that we have GOP there. I meant that user should have
> a chance to choose arbitrary mode like in case of VGA. Currently,
> he or she could only rely on automatic mode detection or just disable
> this mechanism. So, I think we should implement vga option (or rename
> it to gop) as is (maybe with some minor changes) in early EFI code.

Sounds like you haven't seen the video= config file option...

>> workaround implementation would ideally be done in a backportable
>> way, i.e. without depending on a huge pile of other changes.
> 
> We add more and more early options, so, maybe we could workout
> something generic, easily reusable in other cases.

Early options are different from the need to control the bootloader
part of xen.efi.

Jan