All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: "Wei Liu" <wei.liu2@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, sstabellini@kernel.org,
	ian.jackson@eu.citrix.com
Subject: Re: [PATCH 2/2] tools/libxl: Switch Arm guest type to PVH
Date: Mon, 3 Sep 2018 12:11:27 +0100	[thread overview]
Message-ID: <98b5385d-7cff-fc10-8527-585959207017@arm.com> (raw)
In-Reply-To: <20180828164520.dlwadxfhaiyikbi2@citrix.com>

Hi Wei,

On 28/08/18 17:45, Wei Liu wrote:
> On Thu, Aug 23, 2018 at 09:58:57AM +0200, Roger Pau Monné wrote:
> [...]
>>
>>> What I wanted to do here is resetting the union to 0 so you don't get data
>>> mangled by the pv fields.
>>
>> Another possible option I think would be to mark those fields as
>> deprecated in the IDL, and libxl__domain_build_info_copy_deprecated
> 
> I think this is a better approach.
> 
>> will take care of copying them to the new place. In fact I think all
>> guest types should be using the top level kernel, ramdisk and cmdline
>> fields.
>>
>> I'm not specially comfortable with changing the guest type in the
>> middle of libxl__domain_build_info_setdefault, but I also don't have a
>> much better suggestion apart from using the deprecation helper.
>>
>>  From what you say above I assume bootloader or bootloader arguments
>> are not used by ARM?
>>
>>>>
>>>>>    }
>>>>>    /*
>>>>> diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c
>>>>> index d4fa06daea..a6431c5d3f 100644
>>>>> --- a/tools/libxl/libxl_create.c
>>>>> +++ b/tools/libxl/libxl_create.c
>>>>> @@ -215,7 +215,7 @@ int libxl__domain_build_info_setdefault(libxl__gc *gc,
>>>>>        if (!b_info->event_channels)
>>>>>            b_info->event_channels = 1023;
>>>>> -    libxl__arch_domain_build_info_setdefault(b_info);
>>>>> +    libxl__arch_domain_build_info_setdefault(gc, b_info);
>>>>>        libxl_defbool_setdefault(&b_info->dm_restrict, false);
>>>>>        switch (b_info->type) {
>>>>> diff --git a/tools/libxl/libxl_x86.c b/tools/libxl/libxl_x86.c
>>>>> index 81523a568f..8b6759c089 100644
>>>>> --- a/tools/libxl/libxl_x86.c
>>>>> +++ b/tools/libxl/libxl_x86.c
>>>>> @@ -613,7 +613,8 @@ int libxl__arch_domain_finalise_hw_description(libxl__gc *gc,
>>>>>        return rc;
>>>>>    }
>>>>> -void libxl__arch_domain_build_info_setdefault(libxl_domain_build_info *b_info)
>>>>> +void libxl__arch_domain_build_info_setdefault(libxl__gc *gc,
>>>>> +                                              libxl_domain_build_info *b_info)
>>>>>    {
>>>>>        libxl_defbool_setdefault(&b_info->acpi, true);
>>>>>    }
>>>>> diff --git a/tools/xl/xl_parse.c b/tools/xl/xl_parse.c
>>>>> index 971ec1bc56..0bda28152b 100644
>>>>> --- a/tools/xl/xl_parse.c
>>>>> +++ b/tools/xl/xl_parse.c
>>>>> @@ -1286,7 +1286,11 @@ void parse_config_data(const char *config_source,
>>>>>        }
>>>>>        if (c_info->type == LIBXL_DOMAIN_TYPE_INVALID)
>>>>> +#if defined(__arm__) || defined(__aarch64__)
>>>>
>>>> I think #ifdef CONFIG_ARM should DTRT and it's cleaner IMO.
>>>
>>> CONFIG_ARM is not defined in the tools C source. So that's the only way to
>>> know if you are on Arm. This follows what is done in libxc.
>>>
>>> I would be happy to introduce CONFIG_ARM/CONFIG_X86 if people thinks this
>>> would be useful in other places.
>>
>> The tools makefile already uses CONFIG_ARM/X86, so I think it would
>> make sense to have this for the code as well. In any case, I don't
>> feel this should be done just for this patch, so I'm fine as-is.
>>
> 
> I think CONFIG_ARM should already work.

I don't think so. The top makefile does not pass -DCONFIG_ARM on 
compiler command line. This is only done in sub-directory such as 
console and libacpi.

> 
> There are several CONFIG_ARM* in toolstack code, though not in libxl. In
> any case, I think the code is fine as-is.

I am happy to introduce CONFIG_ARM/CONFIG_X86 if you don't mind adding 
-DCONFIG_ARM on the command line.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-09-03 11:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 15:00 [PATCH 0/2] tools/libxl: Switch Arm guest type to PVH Julien Grall
2018-08-22 15:00 ` [PATCH 1/2] tools/libxl: Rename libxl__arch_domain_build_info_acpi_setdefault to Julien Grall
2018-08-22 15:08   ` Roger Pau Monné
2018-08-22 15:34     ` Wei Liu
2018-08-22 15:00 ` [PATCH 2/2] tools/libxl: Switch Arm guest type to PVH Julien Grall
2018-08-22 15:18   ` Roger Pau Monné
2018-08-22 17:48     ` Julien Grall
2018-08-23  7:58       ` Roger Pau Monné
2018-08-28 16:45         ` Wei Liu
2018-09-03 11:11           ` Julien Grall [this message]
2018-09-03 15:21             ` Wei Liu
2018-09-03 11:09         ` Julien Grall
2018-09-03 11:15           ` Julien Grall
2018-09-03 14:40             ` Roger Pau Monné
2018-09-25 19:36               ` Julien Grall
2018-10-01 15:27                 ` Roger Pau Monné
2018-10-01 15:33                   ` Julien Grall
2018-10-01 16:37                     ` Roger Pau Monné
2018-10-01 17:14                       ` Julien Grall

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=98b5385d-7cff-fc10-8527-585959207017@arm.com \
    --to=julien.grall@arm.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.