From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Andrey Borzenkov <arvidjaar@gmail.com>
Cc: "M A Young" <m.a.young@durham.ac.uk>,
"The development of GNU GRUB" <grub-devel@gnu.org>,
fabio.fantoni@m2r.biz,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Subject: Re: [Xen-devel] pvgrub2 is merged
Date: Tue, 26 Nov 2013 19:16:13 +0000 [thread overview]
Message-ID: <5294F37D.805@citrix.com> (raw)
In-Reply-To: <20131126221221.3fe316e3@opensuse.site>
On 26/11/13 18:12, Andrey Borzenkov wrote:
> В Tue, 26 Nov 2013 18:58:47 +0100
> Fabio Fantoni <fabio.fantoni@m2r.biz> пишет:
>
>> I have also another question:
>> Is possible specify multiple path where search the grub.cfg for support
>> all mainly distributions and add a custom cfg path support taking it
>> from arguments?
>>
> You can do something like
>
> if search --set root --file /boot/grub2/grub.cfg ; then
> configfile /boot/grub2/grub.cfg
> elif search --set root --file /boot/grub/grub.cfg ; then
> configfile /boot/grub/grub.cfg
> elif ...
> ...
> fi
>
> If xen provides way to pass arguments to kernel, it sure could be
> implemented as arguments to grub. Actually someone asked for a way to
> pass arguments to grub on EFI, so this could share implementation.
The way PV guests get a command line from the toolstack is via the
start_info.cmd_line, which is up to 1024 bytes.
This will be available to anything which gets its hand on the start info
page.
~Andrew
next prev parent reply other threads:[~2013-11-26 20:16 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 20:52 pvgrub2 is merged Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-09 21:01 ` [Xen-devel] " Samuel Thibault
2013-11-10 4:47 ` Andrey Borzenkov
2013-11-11 11:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-13 19:06 ` [Xen-devel] " M A Young
2013-11-13 20:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-14 12:27 ` M A Young
2013-11-14 17:03 ` M A Young
2013-11-14 17:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-14 18:48 ` M A Young
2013-11-14 18:57 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-14 18:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-14 21:11 ` M A Young
2013-11-14 21:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-25 15:56 ` Fabio Fantoni
2013-11-25 19:35 ` M A Young
2013-11-26 17:58 ` Fabio Fantoni
2013-11-26 18:12 ` Andrey Borzenkov
2013-11-26 19:16 ` Andrew Cooper [this message]
2013-11-27 11:32 ` Fabio Fantoni
2013-11-27 11:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-27 15:59 ` Fabio Fantoni
2013-11-27 16:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-27 16:24 ` Fabio Fantoni
2013-11-27 17:35 ` Andrey Borzenkov
2013-11-28 13:07 ` Fabio Fantoni
2013-11-28 14:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-28 14:17 ` Fabio Fantoni
2013-11-29 11:28 ` Fabio Fantoni
[not found] ` <52987D7F.3050006@gmail.com>
[not found] ` <52988F86.6050008@m2r.biz>
2013-12-03 10:31 ` Fabio Fantoni
2013-12-03 10:33 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-03 11:22 ` Fabio Fantoni
[not found] ` <529DC07E.8000201@gmail.com>
[not found] ` <529DE3FD.90002@m2r.biz>
2013-12-03 15:33 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-03 16:16 ` Fabio Fantoni
2013-12-06 11:11 ` Fabio Fantoni
2013-12-06 11:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-06 14:44 ` Fabio Fantoni
2013-12-06 14:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-06 15:22 ` Fabio Fantoni
2013-12-07 10:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-09 10:06 ` Fabio Fantoni
2013-12-17 10:44 ` Fabio Fantoni
2013-12-17 11:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-17 13:11 ` Fabio Fantoni
2013-12-17 13:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-17 13:55 ` Fabio Fantoni
2013-12-17 14:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-17 14:10 ` Fabio Fantoni
2013-12-17 14:35 ` Fabio Fantoni
2013-12-18 14:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-18 19:39 ` Stefano Stabellini
2013-12-18 20:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 11:54 ` Stefano Stabellini
2013-12-20 12:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-06 12:23 ` Stefano Stabellini
2014-11-07 15:20 ` Stefano Stabellini
2013-12-17 11:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 15:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:04 ` Fabio Fantoni
2013-11-27 16:10 ` M A Young
2013-11-11 10:10 ` Ian Campbell
2013-11-11 11:54 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-11 12:06 ` Ian Campbell
2013-11-11 12:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-14 9:48 ` Dario Faggioli
2013-11-13 16:36 ` Ian Campbell
2013-11-13 18:25 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-14 8:37 ` Ian Campbell
2013-12-11 11:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-11 11:51 ` Ian Campbell
2013-12-11 11:54 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-11 14:34 ` Dario Faggioli
2013-12-14 17:13 ` Leif Lindholm
2014-01-06 15:35 ` Lars Kurth
2013-11-29 13:24 ` Colin Watson
2013-11-29 17:44 ` Andrey Borzenkov
2013-11-29 18:16 ` Colin Watson
2013-12-02 9:48 ` [Xen-devel] " Ian Campbell
2013-12-02 10:37 ` Samuel Thibault
2013-12-02 10:46 ` Ian Campbell
2013-12-03 17:27 ` Colin Watson
2013-12-03 17:41 ` Ian Campbell
2013-11-30 10:36 ` 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=5294F37D.805@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=arvidjaar@gmail.com \
--cc=fabio.fantoni@m2r.biz \
--cc=grub-devel@gnu.org \
--cc=m.a.young@durham.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).