From: Andrii Anisov <andrii.anisov@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v1] libxl: Make an ACPI support build for ARM64 configurable.
Date: Mon, 28 Nov 2016 11:32:48 +0200 [thread overview]
Message-ID: <CAC1WxdjDdA+nadEUsGJ-gK6LAv-CFK2XxZPgPk6m6tkdb5-T5g@mail.gmail.com> (raw)
In-Reply-To: <49c1830d-f158-aa26-7eca-84c315ec41db@arm.com>
Julien,
> There is no automatic test on all the possible configurations, although we have
> travis to test build (and not booting) a random Kconfig.
I guess there is no need to test booting of a "random" Kconfig within
the mainline anyway. The full-featured defconfig would be enough to be
provided by the mainline.
> Even if we try our best to see any problem when reviewing code, we cannot guarantee an error
> when using a different configuration.
From other hand, those who build their solution based on XEN, will
take care about their specific configurations. And get back to the
community with features and fixes if applicable.
> I got bitten quite a few times in my development because I had a binary but
> not the Kconfig.
I think everyone faced similar issues in their experience.
> I might be more inclined to make more feature optional when we will
> have a way to track the configuration of a hypervisor binary.
> +10 to this idea.
Having a .config built into the XEN binary is a cool feature.
But IMO it is useful rather during development time. Knowing a
production system configuration seems to be closer to an integration
area of responsibility.
> This is because the Kconfig is not embedded in the Xen binary.
This thread was started from the configuration of the tools, which are
not configured by Kconfig.
Is it already possible to get back tools configuration during runtime?
Sincerely,
Andrii Anisov.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-28 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 12:25 [PATCH v1] libxl: Make an ACPI support build for ARM64 configurable Andrii Anisov
2016-11-23 12:45 ` Julien Grall
2016-11-23 13:03 ` Andrii Anisov
2016-11-23 13:12 ` Wei Liu
2016-11-23 13:59 ` Andrii Anisov
2016-11-23 14:05 ` Wei Liu
2016-11-23 14:12 ` Andrii Anisov
2016-11-23 14:29 ` Wei Liu
2016-11-23 14:34 ` Julien Grall
2016-11-23 14:37 ` Wei Liu
2016-11-23 15:10 ` Julien Grall
2016-11-23 15:47 ` Andrii Anisov
2016-11-23 19:28 ` Julien Grall
2016-11-23 19:32 ` Andrew Cooper
2016-11-28 9:32 ` Andrii Anisov [this message]
2016-11-23 14:22 ` Jan Beulich
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=CAC1WxdjDdA+nadEUsGJ-gK6LAv-CFK2XxZPgPk6m6tkdb5-T5g@mail.gmail.com \
--to=andrii.anisov@gmail.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--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 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.