[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4EE710A00200007800067274@nat28.tlf.novell.com>
Date: Tue, 13 Dec 2011 07:45:20 +0000
From: "Jan Beulich" <JBeulich@...e.com>
To: "Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>
Cc: <stefan.bader@...onical.com>, <Ian.Campbell@...rix.com>,
<mike.mcclurg@...rix.com>, <jeremy@...p.org>, <ke.yu@...el.com>,
<kevin.tian@...el.com>, <konrad@...nel.org>, <lenb@...nel.org>,
<xen-devel@...ts.xensource.com>, <liang.tang@...cle.com>,
<rjw@...k.pl>, <linux-acpi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH 5/8] ACPI: add processor driver for Xen
virtual CPUs.
>>> On 12.12.11 at 18:29, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
> On Thu, Dec 01, 2011 at 09:24:23AM +0000, Jan Beulich wrote:
>> >>> On 30.11.11 at 18:21, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
>> > --- a/drivers/acpi/Makefile
>> > +++ b/drivers/acpi/Makefile
>> > @@ -66,6 +66,7 @@ obj-$(CONFIG_ACPI_CUSTOM_METHOD)+= custom_method.o
>> > # processor has its own "processor." module_param namespace
>> > processor-y := processor_driver.o processor_throttling.o
>> > processor-y += processor_idle.o processor_thermal.o
>> > +processor-y += processor_xen.o
>>
>> This should minimally be processor-$(CONFIG_XEN), with other things
>> adjusted as necessary.
>
> I was under the impression that this was required to get the
> processor_xen.ko
> to be a module. Otherwise it would only compile as built-in.
processor_xen.ko? Why not have all the code go into processor.ko?
(And the original construct didn't aim in that direction either.)
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists