All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>,
	The development of GNU GRUB <grub-devel@gnu.org>
Cc: Vladimir Serbinenko <phcoder@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Uniform commands for booting xen
Date: Fri, 13 Nov 2015 09:50:36 +0000	[thread overview]
Message-ID: <1447408236.18450.117.camel__33296.8227834955$1447408340$gmane$org@citrix.com> (raw)
In-Reply-To: <CAA91j0Wz++uchzCDwDEPBSf+k2kYy7iMEuPJfWBSap-ZQq_X2A@mail.gmail.com>

On Fri, 2015-11-13 at 12:04 +0300, Andrei Borzenkov wrote:
> > How do you express modules other than kernel+initrd in that
> > scheme, without grub needing to be aware of any new addition we
> > may find necessary going forward?
> > 
> 
> Are modules used by Xen self-identifying? Is it enough to simply pass
> Xen kernel list of binary blobs or Xen kernel must be told what these
> binary blobs are? If they are self identifying, why arm needs to be
> passed module type in the first place?

At first Xen/ARM required the bootloader to identify, but that was since
identified as causing madness and fixed by having Xen/ARM do as Xen/x86
does and figure things out for itself, but I failed to communicate this
clearly and things got implemented on the grub side under the old
assumptions.

I just replied in more detail about that to Jan's mail, so I won't repeat
myself further here.

Ian.

  reply	other threads:[~2015-11-13  9:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 13:41 Uniform commands for booting xen Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-12 15:44 ` [Xen-devel] " Jan Beulich
2015-11-12 16:46   ` Andrew Cooper
2015-11-12 16:46   ` Andrew Cooper
2015-11-12 16:58   ` Andrei Borzenkov
2015-11-12 16:58   ` [Xen-devel] " Andrei Borzenkov
2015-11-12 17:08     ` Jan Beulich
2015-11-12 17:11       ` Andrei Borzenkov
2015-11-12 17:11       ` Andrei Borzenkov
2015-11-12 17:08     ` Jan Beulich
2015-11-12 17:09   ` Ian Campbell
2015-11-12 17:09   ` [Xen-devel] " Ian Campbell
2015-11-13  7:48     ` Jan Beulich
2015-11-13  9:04       ` Andrei Borzenkov
2015-11-13  9:04       ` [Xen-devel] " Andrei Borzenkov
2015-11-13  9:50         ` Ian Campbell [this message]
2015-11-13  9:50         ` Ian Campbell
2016-01-11 14:06           ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-11 14:06           ` [Xen-devel] " Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-11 14:32             ` Jan Beulich
2016-01-11 14:32             ` [Xen-devel] " Jan Beulich
2016-01-11 14:58               ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-11 15:36                 ` Jan Beulich
2016-01-11 15:36                   ` [Xen-devel] " Jan Beulich
2016-01-11 14:58               ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-18 10:28             ` Ian Campbell
2016-01-18 10:28             ` [Xen-devel] " Ian Campbell
2016-01-22  9:14               ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-22  9:14               ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-13  9:48       ` Ian Campbell
2015-11-13  9:48       ` [Xen-devel] " Ian Campbell
2015-11-13  7:48     ` Jan Beulich
2015-11-12 15:44 ` Jan Beulich
2015-11-12 13:41 Vladimir 'φ-coder/phcoder' Serbinenko

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='1447408236.18450.117.camel__33296.8227834955$1447408340$gmane$org@citrix.com' \
    --to=ian.campbell@citrix.com \
    --cc=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.com \
    --cc=xen-devel@lists.xen.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.