>>> On 12.06.18 at 02:41, <sstabell...@kernel.org> wrote:
> On Wed, 6 Jun 2018, Jan Beulich wrote:
>> >>> On 05.06.18 at 19:52, <julien.gr...@arm.com> wrote:
>> 
>> > 
>> > On 04/06/18 18:23, Stefano Stabellini wrote:
>> >> Hi all,
>> >> 
>> >> This patch series is the first step toward building a small certifiable
>> >> Xen hypervisor for ARM boards.
>> >> 
>> >> First, the series makes a few changes to allow disabling more kconfig
>> >> options: most of them already exist but cannot be disabled.
>> >> 
>> >> Then, it introduces a reference kconfig for Renesas RCar (due to popular
>> >> demand, candidate for certifications), Xilinx MPSoC, and for QEMU
>> >> aarch64 (not for certifications, but useful for debugging).
>> >> 
>> >> The last patch in the series adds a convenient cloc target to count the
>> >> total lines of code of the source files built.
>> >> 
>> >> As a consequence of these changes, some options will become user-visible
>> >> and not dependent on CONFIG_EXPERT. It does not mean that Xen Project
>> >> will security support all possible combinations of kconfig options.
>> >> Instead, there will be a small set of pre-canned configurations that
>> >> will be supported.  See: https://marc.info/?l=xen-devel&m=152424389512432 
>> > 
>> > George, Ian, Jan, shall SUPPORT.MD be updated to reflect the Kconfig 
>> > changes?
>> > 
>> > I am mostly thinking about the board support and the fact that more 
>> > options on Arm are selectable by the users.
>> 
>> I think that would be very desirable, yes.
> 
> Do you want me to add a patch for that to this series, or should I do it
> separately?

I think such a doc change should be right in a particular patch making
things user selectable.

Jan



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

Reply via email to