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

Re: [Xen-devel] [PATCH] xen: allow CONFIG_ACPI_PROCESSOR_XEN=m



On Thu, 2009-12-03 at 22:41 +0000, Jeremy Fitzhardinge wrote: 
> On 12/03/09 14:03, Ian Campbell wrote:
> > diff --git a/include/xen/acpi.h b/include/xen/acpi.h
> > index 3d7ea40..8506688 100644
> > --- a/include/xen/acpi.h
> > +++ b/include/xen/acpi.h
> > @@ -41,7 +41,7 @@ int acpi_notify_hypervisor_state(u8 sleep_state,
> >   #define HOTPLUG_TYPE_ADD  0
> >   #define HOTPLUG_TYPE_REMOVE       1
> >
> > -#ifdef CONFIG_ACPI_PROCESSOR_XEN
> > +#if defined(CONFIG_ACPI_PROCESSOR_XEN) || 
> > defined(CONFIG_ACPI_PROCESSOR_XEN_MODULE)
> >    
> 
> Is this necessary?  I thought =m defined CONFIG_ACPI_PROCESSOR_XE.

I thought so too but I got a build error without this change:

  CC [M]  drivers/xen/acpi_processor.o
drivers/xen/acpi_processor.c:41: error: variable âxen_opsâ has initializer but 
incomplete type
drivers/xen/acpi_processor.c:42: error: unknown field âhotplugâ specified in 
initializer
drivers/xen/acpi_processor.c:42: warning: excess elements in struct initializer
drivers/xen/acpi_processor.c:42: warning: (near initialization for âxen_opsâ)
drivers/xen/acpi_processor.c:47: error: redefinition of 
âprocessor_cntl_xen_power_cacheâ
include/xen/acpi.h:74: error: previous definition of 
âprocessor_cntl_xen_power_cacheâ was here
drivers/xen/acpi_processor.c:72: error: redefinition of âprocessor_cntl_xenâ
include/xen/acpi.h:63: error: previous definition of âprocessor_cntl_xenâ was 
here
drivers/xen/acpi_processor.c:78: error: redefinition of âprocessor_cntl_xen_pmâ
include/xen/acpi.h:64: error: previous definition of âprocessor_cntl_xen_pmâ 
was here
drivers/xen/acpi_processor.c: In function âprocessor_cntl_xen_pmâ:
drivers/xen/acpi_processor.c:80: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c: At top level:
drivers/xen/acpi_processor.c:84: error: redefinition of 
âprocessor_cntl_xen_pmperfâ
include/xen/acpi.h:65: error: previous definition of 
âprocessor_cntl_xen_pmperfâ was here
drivers/xen/acpi_processor.c: In function âprocessor_cntl_xen_pmperfâ:
drivers/xen/acpi_processor.c:86: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c: At top level:
drivers/xen/acpi_processor.c:90: error: redefinition of 
âprocessor_cntl_xen_pmthrâ
include/xen/acpi.h:66: error: previous definition of âprocessor_cntl_xen_pmthrâ 
was here
drivers/xen/acpi_processor.c: In function âprocessor_cntl_xen_pmthrâ:
drivers/xen/acpi_processor.c:92: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c: At top level:
drivers/xen/acpi_processor.c:96: error: redefinition of 
âprocessor_cntl_xen_notifyâ
include/xen/acpi.h:69: error: previous definition of 
âprocessor_cntl_xen_notifyâ was here
drivers/xen/acpi_processor.c: In function âprocessor_cntl_xen_notifyâ:
drivers/xen/acpi_processor.c:104: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c:107: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c:110: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c:111: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c: In function âxen_acpi_processor_extcntl_initâ:
drivers/xen/acpi_processor.c:327: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c:329: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
drivers/xen/acpi_processor.c:331: error: invalid use of undefined type âstruct 
processor_cntl_xen_opsâ
make[2]: *** [drivers/xen/acpi_processor.o] Error 1
make[1]: *** [drivers/xen/] Error 2
make: *** [sub-make] Error 2


Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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