grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Fu Wei <fu.wei@linaro.org>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Vladimir Serbinenko <phcoder@gmail.com>,
	Julien Grall <julien.grall@linaro.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Linaro UEFI Mailman List <linaro-uefi@lists.linaro.org>,
	Jon Masters <jcm@redhat.com>
Subject: Re: [PATCH v2 4/4] arm64: update the introduction of xen boot commands in docs/grub.texi
Date: Fri, 26 Feb 2016 13:59:57 +0800	[thread overview]
Message-ID: <CADyBb7sETqYE5xztcRHie_dpbQJGJHb95fRNvoM9DiZ214M6Ew@mail.gmail.com> (raw)
In-Reply-To: <B746781A-CAF2-44EA-A4FC-6EA962AD3172@gmail.com>

Hi Andrei

On 26 February 2016 at 13:24, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>
>
> Отправлено с iPhone
>
>> 26 февр. 2016 г., в 7:48, Fu Wei <fu.wei@linaro.org> написал(а):
>>
>> Hi Andrei
>>
>>> On 26 February 2016 at 01:34, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>>> 25.02.2016 09:39, fu.wei@linaro.org пишет:
>>>> From: Fu Wei <fu.wei@linaro.org>
>>>>
>>>> delete: xen_linux, xen_initrd, xen_xsm
>>>> add: xen_module
>>>>
>>>> This update bases on
>>>>    commit 0edd750e50698854068358ea53528100a9192902
>>>>    Author: Vladimir Serbinenko <phcoder@gmail.com>
>>>>    Date:   Fri Jan 22 10:18:47 2016 +0100
>>>>
>>>>        xen_boot: Remove obsolete module type distinctions.
>>>>
>>>> Signed-off-by: Fu Wei <fu.wei@linaro.org>
>>>> ---
>>>> docs/grub.texi | 32 +++++++++-----------------------
>>>> 1 file changed, 9 insertions(+), 23 deletions(-)
>>>>
>>>> diff --git a/docs/grub.texi b/docs/grub.texi
>>>> index 82f6fa4..0f99c50 100644
>>>> --- a/docs/grub.texi
>>>> +++ b/docs/grub.texi
>>>> @@ -3861,9 +3861,7 @@ you forget a command, you can run the command @command{help}
>>>> * videoinfo::                   List available video modes
>>>> @comment * xen_*::              Xen boot commands
>>>> * xen_hypervisor::              Load xen hypervisor binary
>>>> -* xen_linux::                   Load dom0 kernel for xen hypervisor
>>>> -* xen_initrd::                  Load dom0 initrd for dom0 kernel
>>>> -* xen_xsm::                     Load xen security module for xen hypervisor
>>>> +* xen_module::                  Load xen modules for xen hypervisor
>>>> @end menu
>>>>
>>>>
>>>> @@ -5141,30 +5139,18 @@ verbatim as the @dfn{kernel command-line}. Any other binaries must be
>>>> reloaded after using this command.
>>>> @end deffn
>>>>
>>>> -@node xen_linux
>>>> -@subsection xen_linux
>>>> +@node xen_module
>>>> +@subsection xen_module
>>>>
>>>> -@deffn Command xen_linux file [arguments]
>>>> -Load a dom0 kernel image for xen hypervisor at the booting process of xen.
>>>> +@deffn Command xen_module [--nounzip] file [arguments]
>>>> +Load a module for xen hypervisor at the booting process of xen.
>>>> The rest of the line is passed verbatim as the module command line.
>>>> +Each module will be identified by the order in which the modules are added.
>>>> +The 1st module: dom0 kernel image
>>>> +The 2nd module: dom0 ramdisk
>>>> +All subsequent modules: UNKNOW
>>>> @end deffn
>>>
>>> Hmm ... from previous discussion I gathered that Xen can detect module
>>> type. What if there is no initrd for dom0? How can subsequent modules be
>>
>> Now , Xen detect module type by the order. (at least on ARM64).
>> I think i386 is using Multiboot(2) protocol, so maybe this order is
>> nothing to do with i386.
>>
>
> Then we have obvious problem with your XSM patch (http://savannah.gnu.org/bugs/?43420) - XSM may land as the first module. That's actually something to solve on Xen side I think. It's just that so far we had just kernel and initrd, so that was non issue.

Oh, did you mean Wei Liu's patch?

I guess XSM may land as the third module (or the module after linux
kernel, if you don't have initrd)

Yes, agree. (That's actually something to solve on Xen side)

I guess xen can get xsm from a special initrd. so for now there is not
big problem on xsm.

Please correct me if I misunderstand something. :-)

Thanks!

Back to this patch, is that OK for you, or any suggestion?  Thanks !

>
>
>> so maybe we can say:
>> -----------------------------
>> On ARM64, each module will be identified by the order in which the
>> modules are added.
>> The 1st module: dom0 kernel image
>> The 2nd module: dom0 ramdisk (optional)
>> All subsequent modules: UNKNOWN
>>
>> On i386,  the modules will be identified by Multiboot(2) protocol.
>> -----------------------------
>>
>> Is that better?  please correct me if I miss something.
>>
>>> loaded then?
>>>
>>>> -@node xen_initrd
>>>> -@subsection xen_initrd
>>>> -
>>>> -@deffn Command xen_initrd file
>>>> -Load a initrd image for dom0 kernel at the booting process of xen.
>>>> -@end deffn
>>>> -
>>>> -@node xen_xsm
>>>> -@subsection xen_xsm
>>>> -
>>>> -@deffn Command xen_xsm file
>>>> -Load a xen security module for xen hypervisor at the booting process of xen.
>>>> -See @uref{http://wiki.xen.org/wiki/XSM} for more detail.
>>>> -@end deffn
>>>> -
>>>> -
>>>> @node Networking commands
>>>> @section The list of networking commands
>>
>>
>>
>> --
>> Best regards,
>>
>> Fu Wei
>> Software Engineer
>> Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch
>> Ph: +86 21 61221326(direct)
>> Ph: +86 186 2020 4684 (mobile)
>> Room 1512, Regus One Corporate Avenue,Level 15,
>> One Corporate Avenue,222 Hubin Road,Huangpu District,
>> Shanghai,China 200021



-- 
Best regards,

Fu Wei
Software Engineer
Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch
Ph: +86 21 61221326(direct)
Ph: +86 186 2020 4684 (mobile)
Room 1512, Regus One Corporate Avenue,Level 15,
One Corporate Avenue,222 Hubin Road,Huangpu District,
Shanghai,China 200021


  reply	other threads:[~2016-02-26  6:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25  6:39 [PATCH v2 1/4] arm64: add "--nounzip" option support in xen_module command fu.wei
2016-02-25  6:39 ` [PATCH v2 2/4] * util/grub.d/20_linux_xen.in: Add xen_boot command support fu.wei
2016-02-25  6:39 ` [PATCH v2 3/4] i386, xen: Add xen_hypervisor and xen_module aliases for i386 fu.wei
2016-02-25  6:39 ` [PATCH v2 4/4] arm64: update the introduction of xen boot commands in docs/grub.texi fu.wei
2016-02-25 17:34   ` Andrei Borzenkov
2016-02-26  4:48     ` Fu Wei
2016-02-26  4:55       ` Fu Wei
2016-02-26  5:24       ` Andrei Borzenkov
2016-02-26  5:59         ` Fu Wei [this message]
2016-02-26 10:50           ` Andrei Borzenkov
2016-02-26 11:15             ` Fu Wei
2016-02-26 14:03               ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-02-27  2:43                 ` Fu Wei
     [not found]               ` <20160227203341.GM31035@char.us.oracle.com>
2016-02-28  5:10                 ` Andrei Borzenkov
     [not found]                   ` <20160229144114.GC16364@char.us.oracle.com>
2016-03-01  4:02                     ` Andrei Borzenkov
2016-02-25 22:26   ` [Xen-devel] " Doug Goldstein
2016-02-26  4:49     ` Fu Wei

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=CADyBb7sETqYE5xztcRHie_dpbQJGJHb95fRNvoM9DiZ214M6Ew@mail.gmail.com \
    --to=fu.wei@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=jcm@redhat.com \
    --cc=julien.grall@linaro.org \
    --cc=leif.lindholm@linaro.org \
    --cc=linaro-uefi@lists.linaro.org \
    --cc=phcoder@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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).