From: Julien Grall <julien.grall@arm.com>
To: Wei Liu <wei.liu2@citrix.com>, Shannon Zhao <zhaoshenglong@huawei.com>
Cc: hangaohuai@huawei.com, sstabellini@kernel.org,
ian.jackson@eu.citrix.com, peter.huangpeng@huawei.com,
xen-devel@lists.xen.org, shannon.zhao@linaro.org,
boris.ostrovsky@oracle.com
Subject: Re: [PATCH v3 17/17] libxl/arm: Initialize domain param HVM_PARAM_CALLBACK_IRQ
Date: Thu, 7 Jul 2016 17:57:09 +0100 [thread overview]
Message-ID: <577E89E5.3070100@arm.com> (raw)
In-Reply-To: <20160707161517.GF416@citrix.com>
Hi Wei,
On 07/07/16 17:15, Wei Liu wrote:
> On Tue, Jul 05, 2016 at 11:12:47AM +0800, Shannon Zhao wrote:
>> From: Shannon Zhao <shannon.zhao@linaro.org>
>>
>> The guest kernel will get the event channel interrupt information via
>> domain param HVM_PARAM_CALLBACK_IRQ. Initialize it here.
>>
>> Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
>> ---
>> tools/libxl/libxl_arm.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/tools/libxl/libxl_arm.c b/tools/libxl/libxl_arm.c
>> index bc38318..acacba0 100644
>> --- a/tools/libxl/libxl_arm.c
>> +++ b/tools/libxl/libxl_arm.c
>> @@ -900,8 +900,19 @@ int libxl__arch_domain_init_hw_description(libxl__gc *gc,
>> struct xc_dom_image *dom)
>> {
>> int rc;
>> + uint64_t val;
>>
>> assert(info->type == LIBXL_DOMAIN_TYPE_PV);
>> +
>> + /* Set the value of domain param HVM_PARAM_CALLBACK_IRQ. */
>> + val = (uint64_t)HVM_PARAM_CALLBACK_TYPE_PPI << 56;
>> + val |= (2 << 8); /* Active-low level-sensitive */
>
> Please avoid using magic numbers here -- 56, 2 and 8.
The magic numbers are described in public/hvm/params.h however there is
no defines associated to them.
The public header would need to be updated if we don't want the value
hardcoded in libxl.
>
> Another question to Julien and Stefano: is it normal for ARM guest to
> use hvm callback vector?
Yes. The HVM callback vector is used by ACPI guest to find the PPI
(per-cpu interrupt) which will be used to notify event.
This is how DOM0 is using ACPI on ARM (see [1]), I don't think we should
differ here.
BTW, I have noticed that the design doc is only available on the ML.
Shannon, would it be possible to send a patch to add it in docs/misc/arm?
[2] https://lists.xen.org/archives/html/xen-devel/2015-11/msg00488.html
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-07 16:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 3:12 [PATCH v3 00/17] Xen ARM DomU ACPI support Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 01/17] libxl/arm: Factor out codes for generating DTB Shannon Zhao
2016-07-07 15:41 ` Wei Liu
2016-07-07 15:48 ` Boris Ostrovsky
2016-07-07 16:06 ` Julien Grall
2016-07-07 16:09 ` Wei Liu
2016-07-07 16:12 ` Boris Ostrovsky
2016-07-07 16:15 ` Julien Grall
2016-07-07 16:16 ` Wei Liu
2016-07-07 16:08 ` Wei Liu
2016-07-05 3:12 ` [PATCH v3 02/17] libxc: Add placeholders for ACPI tables blob and size Shannon Zhao
2016-07-07 15:42 ` Wei Liu
2016-07-05 3:12 ` [PATCH v3 03/17] libxl/arm: Add a configuration option for ARM DomU ACPI Shannon Zhao
2016-07-07 15:48 ` Wei Liu
2016-07-05 3:12 ` [PATCH v3 04/17] libxl/arm: prepare for constructing ACPI tables Shannon Zhao
2016-07-07 15:50 ` Wei Liu
2016-07-12 7:05 ` Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 05/17] libxl/arm: Generate static ACPI DSDT table Shannon Zhao
2016-07-07 15:52 ` Wei Liu
2016-07-12 3:50 ` Shannon Zhao
2016-07-12 11:38 ` Wei Liu
2016-07-12 14:49 ` Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 06/17] libxl/arm: Estimate the size of ACPI tables Shannon Zhao
2016-07-07 16:07 ` Wei Liu
2016-07-07 16:39 ` Julien Grall
2016-07-08 10:45 ` Wei Liu
2016-07-05 3:12 ` [PATCH v3 07/17] libxl/arm: Construct ACPI RSDP table Shannon Zhao
2016-07-07 22:43 ` Boris Ostrovsky
2016-07-08 3:31 ` Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 08/17] libxl/arm: Construct ACPI XSDT table Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 09/17] libxl/arm: Construct ACPI GTDT table Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 10/17] libxl/arm: Factor MPIDR computing codes out as a helper Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 11/17] libxl/arm: Construct ACPI MADT table Shannon Zhao
2016-07-07 16:11 ` Wei Liu
2016-07-07 16:46 ` Julien Grall
2016-07-05 3:12 ` [PATCH v3 12/17] libxl/arm: Construct ACPI FADT table Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 13/17] libxl/arm: Construct ACPI DSDT table Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 14/17] libxl/arm: Factor finalise_one_memory_node as a gerneric function Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 15/17] libxl/arm: Add ACPI module Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 16/17] libxc/xc_dom_core: Copy ACPI tables to guest space Shannon Zhao
2016-07-05 3:12 ` [PATCH v3 17/17] libxl/arm: Initialize domain param HVM_PARAM_CALLBACK_IRQ Shannon Zhao
2016-07-07 16:15 ` Wei Liu
2016-07-07 16:57 ` Julien Grall [this message]
2016-07-08 3:41 ` Shannon Zhao
2016-07-08 10:47 ` Wei Liu
2016-07-05 10:32 ` [PATCH v3 00/17] Xen ARM DomU ACPI support Julien Grall
2016-07-05 14:09 ` Shannon Zhao
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=577E89E5.3070100@arm.com \
--to=julien.grall@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hangaohuai@huawei.com \
--cc=ian.jackson@eu.citrix.com \
--cc=peter.huangpeng@huawei.com \
--cc=shannon.zhao@linaro.org \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhaoshenglong@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).