Re: [Xen-devel] [RFC 03/29] build: hookup initial Kconfig usage

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 06.10.15 at 11:58, <andrew.cooper3@xxxxxxxxxx> wrote:
> On 05/10/15 23:03, Doug Goldstein wrote:
>> new file mode 100644
>> index 0000000..e69de29
>> diff --git a/xen/arch/x86/Kconfig b/xen/arch/x86/Kconfig
>> new file mode 100644
>> index 0000000..5e34f4e
>> --- /dev/null
>> +++ b/xen/arch/x86/Kconfig
>> @@ -0,0 +1,28 @@
>> +# Select 32 or 64 bit
>> +config 64BIT
>> +    bool "64-bit Xen" if ARCH = "x86_64"
>> +    default ARCH != "i386"
>> +    ---help---
>> +      Say yes to build a 64-bit Xen
>> +      Say no to build a 32-bit Xen
>> +
>> +config X86_32
>> +    def_bool y
>> +    depends on !64BIT
>> +
>> +config X86_64
>> +    def_bool y
>> +    depends on 64BIT
>> +
>> +config X86
>> +    def_bool y
>> +    select HAS_GDBSX
>> +
>> +config ARCH_DEFCONFIG
>> +    string
>> +    default "arch/x86/i386_defconfig" if X86_32
>> +    default "arch/x86/x86_64_defconfig" if X86_64
>> +
>> +source "common/Kconfig"
>> +
>> +source "drivers/Kconfig"
> 
> We dropped 32bit hypervisor builds in 4.4, and it definitely doesn't
> build any more.
> 
> You don't need to provide i386_defconfig or X86_32 as far as the
> hypervisor is concerned.

Are defconfig-s that useful at all? (I ask because I extremely rarely
make us of them in Linux.)

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel