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>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v1] libxl: Make an ACPI support build for ARM64 configurable.
Date: Wed, 23 Nov 2016 17:47:12 +0200 [thread overview]
Message-ID: <CAC1WxdiC=Sn4SXqrJrjyzkGJ=D3to9jcr36AqRe=pa_eVcjaww@mail.gmail.com> (raw)
In-Reply-To: <dd9c71cc-6eef-d326-5431-0a9fab23e90a@arm.com>
Hello Julien,
> The ACPI support is pretty much contained in a single file and I am not sure you will win much space.
> Can you explain why the ACPI guest support should be optional?
This would increase the system configurability and would let one
shrink a system to a minimal footprint with required functionality
only. Such possibility is very useful in embedded applications.
Unfortunately I don't know the exact space impact of this particular
feature 'cause I can't build it. From other hand I do not need it in
my system. So I would like to have a way to drop not needed
functionality easily.
BTW, excessive functionality reduction is also a way to get more
stable and predictable system.
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-23 15:47 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 [this message]
2016-11-23 19:28 ` Julien Grall
2016-11-23 19:32 ` Andrew Cooper
2016-11-28 9:32 ` Andrii Anisov
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='CAC1WxdiC=Sn4SXqrJrjyzkGJ=D3to9jcr36AqRe=pa_eVcjaww@mail.gmail.com' \
--to=andrii.anisov@gmail.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--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.