linux-kernel - Re: [Xen-devel] [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Sep 2012 11:45:57 +0100
From:	David Vrabel <david.vrabel@...rix.com>
To:	Stefano Stabellini <stefano.stabellini@...citrix.com>
CC:	<linux-kernel@...r.kernel.org>, <xen-devel@...ts.xensource.com>,
	<Ian.Campbell@...rix.com>, Pawel Moll <pawel.moll@....com>,
	<konrad.wilk@...cle.com>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [Xen-devel] [PATCH] arm: introduce a DTS for Xen unprivileged
 virtual machines

On 19/09/12 18:44, Stefano Stabellini wrote:
> --- /dev/null
> +++ b/arch/arm/boot/dts/vexpress-xenvm-4.2.dts

Does this make sense?  There is no fixed configuration for VMs.

Is the intention to pass a DTS to the toolstack for it to create the VM
with the appropriate amount of memory and peripheral mapped to the right
place etc?  Or is the toolstack going to create the VM and generate the
DTB from (e.g.,) an xl VM configuration file.

> +
> +	hypervisor {
> +		compatible = "xen,xen-4.2", "xen,xen";
> +		reg = <0xb0000000 0x20000>;
> +		interrupts = <1 15 0xf08>;
> +	};

This node needs to be generated by the toolstack as only it knows what
ABI the hypervisor has.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/