>>> On 30.05.18 at 22:24, wrote:
> On Tue, 29 May 2018, Jan Beulich wrote:
>> Also - do we perhaps want the
>> prompt to additionally have an EXPERT dependency? Without you saying why
>> you want this configurable I can't tell whether this would make sense.
>
> I am doing this mostly to reduce th
On Wed, May 30, 2018 at 2:24 PM, Stefano Stabellini
wrote:
> On Tue, 29 May 2018, Jan Beulich wrote:
>> >>> On 23.05.18 at 02:25, wrote:
>> > --- a/xen/arch/arm/Kconfig
>> > +++ b/xen/arch/arm/Kconfig
>> > @@ -26,6 +26,9 @@ config ARCH_DEFCONFIG
>> > default "arch/arm/configs/arm32_defconfig"
On Tue, 29 May 2018, Jan Beulich wrote:
> >>> On 23.05.18 at 02:25, wrote:
> > --- a/xen/arch/arm/Kconfig
> > +++ b/xen/arch/arm/Kconfig
> > @@ -26,6 +26,9 @@ config ARCH_DEFCONFIG
> > default "arch/arm/configs/arm32_defconfig" if ARM_32
> > default "arch/arm/configs/arm64_defconfig" if AR
>>> On 23.05.18 at 02:25, wrote:
> --- a/xen/arch/arm/Kconfig
> +++ b/xen/arch/arm/Kconfig
> @@ -26,6 +26,9 @@ config ARCH_DEFCONFIG
> default "arch/arm/configs/arm32_defconfig" if ARM_32
> default "arch/arm/configs/arm64_defconfig" if ARM_64
>
> +config HAS_MEM_ACCESS
> + def_bo
Have arm and x86 select HAS_MEM_ACCESS to mark that they can do
MEM_ACCESS.
Select an additional MEM_ACCESS_ALWAYS_ON on x86 to mark that MEM_ACCESS
is not configurable on x86.
Rename HAS_MEM_ACCESS to MEM_ACCESS everywhere else. Add a prompt and a
description to MEM_ACCESS in xen/common/Kconfig.
