From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Remaining EFI Xen on ARM issues (on Juno at least) Date: Wed, 22 Oct 2014 11:45:00 +0100 Message-ID: <1413974700.18118.5.camel@citrix.com> References: <1413863725-27630-1-git-send-email-roy.franz@linaro.org> <1413879444.20604.29.camel@citrix.com> <1413901026.23337.48.camel@citrix.com> <1413967660.20604.47.camel@citrix.com> <54479A3A0200007800040ECF@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54479A3A0200007800040ECF@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Roy Franz , Stefano Stabellini , xen-devel List-Id: xen-devel@lists.xenproject.org On Wed, 2014-10-22 at 10:51 +0100, Jan Beulich wrote: > >>> On 22.10.14 at 10:47, wrote: > > Since http://xenbits.xenproject.org/docs/unstable/misc/efi.html doesn't > > mention any need to qualify paths with a disk: prefix I suppose x86 > > doesn't require anything like this. Jan can you confirm? > > According to my own experience, the path used to invoke xen.efi > (no matter whether from the shell of a boot manager entry) is > sufficient to access all other files (which are getting resolved > relative to xen.efi's location). However, I don't think I ever tried > running something from the root of a file system. And of course I > have no idea how similar the code bases are your and my firmware > got built from. You are always running from (/boot/)EFI/$vendor/ or similar I suppose. > > I'm a bit confused why -cfg=fs2:cfg (or fs2:/cfg or fs2:\cfg) doesn't > > Out of those, afaik only the variant using a backslash is valid (the > first one being valid only if the current directory is the root of the > fs; I don't recall whether EFI maintains per-FS CWDs or just a > single global one). OK, that makes sense. > Did you verify that your EFI binary got control passed at all (i.e. > whether it really is an issue with reading the config file)? It prints: Xen 4.5-unstable (c/s Mon Oct 20 20:55:25 2014 -0700 git:91086d0) EFI loader No configuration file found. So I'm pretty sure xen.efi has been called. > > work, since they specify the disk directly, but maybe I just don't > > understand this aspect of EFI and the application/stub needs to parse > > that if it wants to support loading things from other volumes (and > > doesn't, which is fine). > > > > It's interesting that Linux on juno is correctly able to load the > > dtb=juno from its command line. Is there some difference here between > > the interfaces used by the Linux stub vs the Xen one? > > Quite possible - ours is derived from code we had been using for an > abandoned OS project over ten years ago. OK, so it probably is worth investigating what Xen does differently a little then. Ian.