Re: [Xen-devel] [RFC v1 1/8] xen: make dom0 specific changes depend on XEN_DOM0

["Luis R. Rodriguez" <mcgrof@xxxxxxxx>]

On Thu, Feb 12, 2015 at 09:55:18AM +0000, David Vrabel wrote:
> On 12/02/15 06:03, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@xxxxxxxx>
> > 
> > These are Kconfig options which are known to only make
> > sense with Xen dom0 support. This is as per the agreed
> > upon changes to Xen's kconfig changes [0].
> [...]
> > --- a/arch/x86/xen/Kconfig
> > +++ b/arch/x86/xen/Kconfig
> > @@ -35,13 +35,13 @@ config XEN_MAX_DOMAIN_MEMORY
> >  
> >  config XEN_SAVE_RESTORE
> >         bool
> > -       depends on XEN
> > +       depends on XEN_DOM0
> >         select HIBERNATE_CALLBACKS
> >         default y
> 
> This breaks save/restore of domUs.
> 
> >  config XEN_DEBUG_FS
> >     bool "Enable Xen debug and tuning parameters in debugfs"
> > -   depends on XEN && DEBUG_FS
> > +   depends on XEN_DOM0 && DEBUG_FS
> >     default n
> >     help
> >       Enable statistics output and various tuning options in debugfs.
> 
> This is useful for domUs.
> 
> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> > index 08f41ad..34af197 100644
> > --- a/drivers/watchdog/Kconfig
> > +++ b/drivers/watchdog/Kconfig
> > @@ -1409,7 +1409,7 @@ config WATCHDOG_RIO
> >  
> >  config XEN_WDT
> >     tristate "Xen Watchdog support"
> > -   depends on XEN
> > +   depends on XEN_DOM0
> >     help
> >       Say Y here to support the hypervisor watchdog capability provided
> >       by Xen 4.0 and newer.  The watchdog timeout period is normally one
> 
> Again, useful for domUs.

OK that leaves only XEN_ACPI_PROCESSOR for the patch. Fixed.

 Luis

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