[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 2/6] xen/iommu: Move dom0 setup code out of __init

>>> On 04.03.14 at 23:51, Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> wrote:
> This is required to allow the hardware domain to be built by dom0 after
> the __init sections have been discarded.

Can you quantify the amount of code/data getting moved?

Overall I wonder what the purpose is of allowing the hardware
domain to be created later, rather than keeping Dom0 for this
purpose. After all booting the system is very much hardware
control. Once a control domain was spawned, Dom0 could then
be revoked the right to create further domains.

> --- a/xen/drivers/passthrough/vtd/x86/vtd.c
> +++ b/xen/drivers/passthrough/vtd/x86/vtd.c
> @@ -36,7 +36,7 @@
>   * iommu_inclusive_mapping: when set, all memory below 4GB is included in 
> dom0
>   * 1:1 iommu mappings except xen and unusable regions.
>   */
> -static bool_t __initdata iommu_inclusive_mapping = 1;
> +static bool_t iommu_inclusive_mapping = 1;



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.