Date: Fri, 11 Sep 2015 12:00:00 +0100 From: Ian Campbell <ian.campbell@citrix.com> To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Mark Rutland <mark.rutland@arm.com> Cc: Shannon Zhao <zhaoshenglong@huawei.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>, "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>, "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, "julien.grall@citrix.com" <julien.grall@citrix.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, "matt.fleming@intel.com" <matt.fleming@intel.com>, "christoffer.dall@linaro.org" <christoffer.dall@linaro.org>, "jbeulich@suse.com" <jbeulich@suse.com>, "peter.huangpeng@huawei.com" <peter.huangpeng@huawei.com>, "shannon.zhao@linaro.org" <shannon.zhao@linaro.org>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, "daniel.kiper@oracle.com" <daniel.kiper@oracle.com> Subject: Re: [PATCH] efi/libstub/fdt: Standardize the names of EFI stub parameters Message-ID: <1441969200.3549.23.camel@citrix.com> In-Reply-To: <alpine.DEB.2.02.1509101655020.2672@kaball.uk.xensource.com> References: <1441874516-11364-1-git-send-email-zhaoshenglong@huawei.com> <20150910095208.GA29293@leverpostej> <alpine.DEB.2.02.1509101116580.2672@kaball.uk.xensource.com> <20150910112418.GC29293@leverpostej> <alpine.DEB.2.02.1509101223580.2672@kaball.uk.xensource.com> <20150910121514.GE29293@leverpostej> <alpine.DEB.2.02.1509101429480.2672@kaball.uk.xensource.com> <20150910144938.GI29293@leverpostej> <alpine.DEB.2.02.1509101655020.2672@kaball.uk.xensource.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2015-09-10 at 17:10 +0100, Stefano Stabellini wrote: > > C) When you could go: > > > > DT -> Discover Xen -> Xen-specific stuff -> Xen-specific EFI/ACPI > > discovery > > I take you mean discovering Xen with the usual Xen hypervisor node on > device tree. There may be other options, such as ARM defining an architectural mechanism to do early detection of hypervisors e.g. by defining some bit in some hypervisor controllable register (MPIDR?) to say "a hypervisor is present" and defining an hvc or smc call which can be used to ask which one it is. Ian.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1441969200.3549.23.camel>