[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCHv5] 00/28] Kconfig conversion

  • To: xen-devel@xxxxxxxxxxxxx
  • From: Doug Goldstein <cardoe@xxxxxxxxxx>
  • Date: Sat, 21 Nov 2015 09:51:02 -0600
  • Delivery-date: Sat, 21 Nov 2015 15:51:34 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 11/20/15 1:09 PM, Doug Goldstein wrote:
> The following series is a follow on to the Kconfig conversion patch series.
> There are still more components to convert however this is the bare minimal
> to get everything working and get the options out of the existing makefiles.
> The CONFIG_HAS_ variables are there to match the behavior of the Linux
> CONFIG_HAVE_ variables. The purpose is to say that this hardware/profile/env
> supports this option while the CONFIG_ variable states that this option was
> requested on/off by user intervention.
> The UARTs are now uniformly prefixed as CONFIG_UART_ and dropping most of the
> CONFIG_HAS_ labeling for them. This means they are now user selectable as
> requested by Julien Grall in the prior review. The question I've got is
> the old config was just for selecting defaults. Users could enable the OMAP
> UART for arm64 for example but I'm not sure if that's valid. Currently this
> patchset makes those UARTs not user selectable if they were not previously
> defaulted on. But I would like some feedback on this if possible.
> Ultimately my goal is to allow for more parts of the hypervisor to be turned
> off at compile time and potentially make it easier to include more
> experimental features by others which can be turned off by default. Also to
> provide the one true location for all possible knobs in the source code.
> The patch series can be grabbed at:
> https://github.com/cardoe/xen/tree/kconfig_v5

I forgot to note that I did not drop previous ACKs because those patches
remained untouched.

Doug Goldstein

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.