From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Vijay Kilari <vijay.kilari@gmail.com>,
Vijaya Kumar K <vijaya.kumar@caviumnetworks.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
Roy Franz <roy.franz@linaro.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH FOR-4.5] xen: arm: Do not enable EFI in dom0 since it is not yet supported.
Date: Tue, 14 Oct 2014 16:00:01 +0100 [thread overview]
Message-ID: <543D3A71.6080105@linaro.org> (raw)
In-Reply-To: <1413298307.10417.62.camel@citrix.com>
On 10/14/2014 03:51 PM, Ian Campbell wrote:
> On Tue, 2014-10-14 at 15:02 +0100, Julien Grall wrote:
>> As said earlier, if we consume in Xen how do you choose the console for
>> FreeBSD? Those properties can be considered as the part of the FreeBSD
>> "command line".
>
> Like we do for bootargs, so with xen,dom0-stdin etc.
>
> The ePAPR changelog mentions removing stdin, so I'm not sure it has
> always been FreeBSD specific. I know that u-boot can also use it (that
> is in the case where u-boot itself is configured with an fdt).
>
>> Anyway, the stdin/stdout properties may not be the best examples.
>> Grepping the Documentation in Linux I have found those properties which
>> live in /chosen:
>> - linux,pci-probe-only
>> - linux,sysrq-reset-seq (actually it's a node)
>
> Do those make any sense when running under Xen? would we want to blindly
> expose them? I'm not sure.
For the former one, we may want to modify it if we decide to initialize
PCI devices in Xen.
For the latter, I think we need to copy as it is in Linux. This
properties seems to be used to have a set of keys to reset Linux.
Regards,
--
Julien Grall
prev parent reply other threads:[~2014-10-14 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 16:17 [PATCH FOR-4.5] xen: arm: Do not enable EFI in dom0 since it is not yet supported suravee.suthikulpanit
2014-10-13 16:20 ` Julien Grall
2014-10-13 19:37 ` Roy Franz
2014-10-14 7:21 ` Ian Campbell
2014-10-14 9:59 ` Ian Campbell
2014-10-14 12:28 ` Julien Grall
2014-10-14 12:49 ` Ian Campbell
2014-10-14 12:58 ` Julien Grall
2014-10-14 13:07 ` Ian Campbell
2014-10-14 13:18 ` Julien Grall
2014-10-14 13:47 ` Ian Campbell
2014-10-14 14:02 ` Julien Grall
2014-10-14 14:51 ` Ian Campbell
2014-10-14 15:00 ` Julien Grall [this message]
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=543D3A71.6080105@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=roy.franz@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vijay.kilari@gmail.com \
--cc=vijaya.kumar@caviumnetworks.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.