* Re: A clocksource question @ 2010-03-12 11:42 Tobias Geiger 0 siblings, 0 replies; 42+ messages in thread From: Tobias Geiger @ 2010-03-12 11:42 UTC (permalink / raw) To: xen-devel Hi, i think i have the same Dom0 Problems as Joanna. My setup is: Xen 4.0.0-rc3-pre with some GFX-Passthrough Patches (btw: works great!) with "vtd=1 dom0_max_vcpus=6 iommu=pv" as cmdline for xen Dom0 Kernel is currently 2.6.33 using rebased Opensuse xen-patches (xen- patches-2.6.33-1) I also get - a slightly different - hrtimer message , but only in my Dom0 (as i have only Windows HVM as DomU) "hrtimer: interrupt took 2951458 ns" This message seems to appear when my DomU is booting. "clocksource=jiffies" as Dom0-Parameter doesn't help. "max_cstate=0" as xen Parameter doesn't seem to help either. The Patch from http://lists.xensource.com/archives/html/xen- devel/2010-03/msg00570.html doesn't seem to help. My "Hiccups" occur - felt - "randomly", they take from 1 up to 5 seconds (not messured, more felt) and the only thing moving on the screen during that is the mouse pointer. If it weren't for the moving pointer one could think the Maschine is completly frozen. The "Hiccups" are ONLY in the Dom0, its even so that i can perfectly work in the DomU, even when one of these long-term-hiccups occur. That all just in case another "affected" system my help you in your analsysis of this strange behaviour. Tell me if i can help testing. Greetings Tobias P.S.: Sorry for the non-threaded Follow-up, but i just subscribed to the list... ^ permalink raw reply [flat|nested] 42+ messages in thread
* A clocksource question @ 2010-03-09 10:47 Joanna Rutkowska 2010-03-09 10:50 ` Keir Fraser 2010-03-09 23:36 ` Jeremy Fitzhardinge 0 siblings, 2 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-09 10:47 UTC (permalink / raw) To: xen-devel@lists.xensource.com [-- Attachment #1.1: Type: text/plain, Size: 1061 bytes --] I would appreciate if somebody could shed some light on the currently preferred setting of the clocksource for the pvops0 kernels, used both in Dom0 and DomU (I'm using pvops0 in DomU because it provides backends, e.g. network backend). I have a bad experience with running the Dom0 kernel (xen/stabale-2.6.31.6-based) with the default clocksource=xen, as it results in the system getting temporary "hangs", very short ones, but annoying. E.g. when one types fast on a keyboard, then every 10 seconds or so, the keystroke processing seems to be slowing down significantly for a second o so. Running the kernel with clocksource=jiffies eliminates the above problem but has a disadvantage of the clock drift in Dom0. This is not acceptable on my setup, where I don't have any networking in Dom0, which means I cannot correct it via NTP. Interestingly the above problem didn't seem to affect the Dom0 kernel based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to run this kernel when using Xen 3.4.2. Thanks, joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 10:47 Joanna Rutkowska @ 2010-03-09 10:50 ` Keir Fraser 2010-03-09 10:54 ` Joanna Rutkowska 2010-03-09 23:36 ` Jeremy Fitzhardinge 1 sibling, 1 reply; 42+ messages in thread From: Keir Fraser @ 2010-03-09 10:50 UTC (permalink / raw) To: Joanna Rutkowska, xen-devel@lists.xensource.com On 09/03/2010 10:47, "Joanna Rutkowska" <joanna@invisiblethingslab.com> wrote: > Interestingly the above problem didn't seem to affect the Dom0 kernel > based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to > run this kernel when using Xen 3.4.2. You could run the 3.4.3 release candidates? -- Keir ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 10:50 ` Keir Fraser @ 2010-03-09 10:54 ` Joanna Rutkowska 2010-03-09 11:06 ` Joanna Rutkowska 0 siblings, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-09 10:54 UTC (permalink / raw) To: Keir Fraser; +Cc: xen-devel@lists.xensource.com [-- Attachment #1.1: Type: text/plain, Size: 770 bytes --] On 03/09/2010 11:50 AM, Keir Fraser wrote: > On 09/03/2010 10:47, "Joanna Rutkowska" <joanna@invisiblethingslab.com> > wrote: > >> Interestingly the above problem didn't seem to affect the Dom0 kernel >> based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to >> run this kernel when using Xen 3.4.2. > > You could run the 3.4.3 release candidates? > Let's just say that after my recent experience with a 4.0.0 release candidate, I decided to use a stable version (or at least for the hypervisor) for now :) I really want to use on a production system. Perhaps you would say that in that case I should not be using a pvops0 kernel at all? But what would be a good alternative with all reasonable hardware support then? joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 10:54 ` Joanna Rutkowska @ 2010-03-09 11:06 ` Joanna Rutkowska 2010-03-09 12:07 ` Pasi Kärkkäinen 2010-03-09 15:42 ` Konrad Rzeszutek Wilk 0 siblings, 2 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-09 11:06 UTC (permalink / raw) To: Keir Fraser; +Cc: xen-devel@lists.xensource.com [-- Attachment #1.1: Type: text/plain, Size: 933 bytes --] On 03/09/2010 11:54 AM, Joanna Rutkowska wrote: > On 03/09/2010 11:50 AM, Keir Fraser wrote: >> On 09/03/2010 10:47, "Joanna Rutkowska" <joanna@invisiblethingslab.com> >> wrote: >> >>> Interestingly the above problem didn't seem to affect the Dom0 kernel >>> based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to >>> run this kernel when using Xen 3.4.2. >> >> You could run the 3.4.3 release candidates? >> > Let's just say that after my recent experience with a 4.0.0 release > candidate, I decided to use a stable version (or at least for the > hypervisor) for now :) I really want to use on a production system. > > Perhaps you would say that in that case I should not be using a pvops0 > kernel at all? But what would be a good alternative with all reasonable > hardware support then? > ...plus the xen/stable-2.6/.32 doesn't have the pciback, which I happen to need in Dom0... j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 11:06 ` Joanna Rutkowska @ 2010-03-09 12:07 ` Pasi Kärkkäinen 2010-03-09 12:10 ` Joanna Rutkowska 2010-03-09 15:42 ` Konrad Rzeszutek Wilk 1 sibling, 1 reply; 42+ messages in thread From: Pasi Kärkkäinen @ 2010-03-09 12:07 UTC (permalink / raw) To: Joanna Rutkowska; +Cc: xen-devel@lists.xensource.com, Keir Fraser On Tue, Mar 09, 2010 at 12:06:57PM +0100, Joanna Rutkowska wrote: > On 03/09/2010 11:54 AM, Joanna Rutkowska wrote: > > On 03/09/2010 11:50 AM, Keir Fraser wrote: > >> On 09/03/2010 10:47, "Joanna Rutkowska" <joanna@invisiblethingslab.com> > >> wrote: > >> > >>> Interestingly the above problem didn't seem to affect the Dom0 kernel > >>> based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to > >>> run this kernel when using Xen 3.4.2. > >> > >> You could run the 3.4.3 release candidates? > >> > > Let's just say that after my recent experience with a 4.0.0 release > > candidate, I decided to use a stable version (or at least for the > > hypervisor) for now :) I really want to use on a production system. > > > > Perhaps you would say that in that case I should not be using a pvops0 > > kernel at all? But what would be a good alternative with all reasonable > > hardware support then? > > > ...plus the xen/stable-2.6/.32 doesn't have the pciback, which I happen > to need in Dom0... > Your options are listed here: http://wiki.xensource.com/xenwiki/XenDom0Kernels -- Pasi ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 12:07 ` Pasi Kärkkäinen @ 2010-03-09 12:10 ` Joanna Rutkowska 0 siblings, 0 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-09 12:10 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: xen-devel@lists.xensource.com, Keir Fraser [-- Attachment #1.1: Type: text/plain, Size: 1342 bytes --] On 03/09/2010 01:07 PM, Pasi Kärkkäinen wrote: > On Tue, Mar 09, 2010 at 12:06:57PM +0100, Joanna Rutkowska wrote: >> On 03/09/2010 11:54 AM, Joanna Rutkowska wrote: >>> On 03/09/2010 11:50 AM, Keir Fraser wrote: >>>> On 09/03/2010 10:47, "Joanna Rutkowska" <joanna@invisiblethingslab.com> >>>> wrote: >>>> >>>>> Interestingly the above problem didn't seem to affect the Dom0 kernel >>>>> based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to >>>>> run this kernel when using Xen 3.4.2. >>>> >>>> You could run the 3.4.3 release candidates? >>>> >>> Let's just say that after my recent experience with a 4.0.0 release >>> candidate, I decided to use a stable version (or at least for the >>> hypervisor) for now :) I really want to use on a production system. >>> >>> Perhaps you would say that in that case I should not be using a pvops0 >>> kernel at all? But what would be a good alternative with all reasonable >>> hardware support then? >>> >> ...plus the xen/stable-2.6/.32 doesn't have the pciback, which I happen >> to need in Dom0... >> > > Your options are listed here: > http://wiki.xensource.com/xenwiki/XenDom0Kernels > Ok, but what about the original question about what is the preferred clocksource setting and perhaps some comments on various settings? Thanks, joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 11:06 ` Joanna Rutkowska 2010-03-09 12:07 ` Pasi Kärkkäinen @ 2010-03-09 15:42 ` Konrad Rzeszutek Wilk 1 sibling, 0 replies; 42+ messages in thread From: Konrad Rzeszutek Wilk @ 2010-03-09 15:42 UTC (permalink / raw) To: Joanna Rutkowska; +Cc: xen-devel@lists.xensource.com, Keir Fraser On Tue, Mar 09, 2010 at 12:06:57PM +0100, Joanna Rutkowska wrote: > On 03/09/2010 11:54 AM, Joanna Rutkowska wrote: > > On 03/09/2010 11:50 AM, Keir Fraser wrote: > >> On 09/03/2010 10:47, "Joanna Rutkowska" <joanna@invisiblethingslab.com> > >> wrote: > >> > >>> Interestingly the above problem didn't seem to affect the Dom0 kernel > >>> based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to > >>> run this kernel when using Xen 3.4.2. > >> > >> You could run the 3.4.3 release candidates? > >> > > Let's just say that after my recent experience with a 4.0.0 release > > candidate, I decided to use a stable version (or at least for the > > hypervisor) for now :) I really want to use on a production system. > > > > Perhaps you would say that in that case I should not be using a pvops0 > > kernel at all? But what would be a good alternative with all reasonable > > hardware support then? > > > ...plus the xen/stable-2.6/.32 doesn't have the pciback, which I happen > to need in Dom0... You will be happy to know that I just finished that. git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git pv/pciback-2.6.32 or a copy of jeremy/xen/net with the pciback merged in: pv/merge.xen.next Or refer to the e-mail I have sent to Xen-Devel with details. ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 10:47 Joanna Rutkowska 2010-03-09 10:50 ` Keir Fraser @ 2010-03-09 23:36 ` Jeremy Fitzhardinge 2010-03-10 22:13 ` Joanna Rutkowska 1 sibling, 1 reply; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-09 23:36 UTC (permalink / raw) To: Joanna Rutkowska; +Cc: xen-devel@lists.xensource.com On 03/09/2010 02:47 AM, Joanna Rutkowska wrote: > I would appreciate if somebody could shed some light on the currently > preferred setting of the clocksource for the pvops0 kernels, used both > in Dom0 and DomU (I'm using pvops0 in DomU because it provides backends, > e.g. network backend). > clocksource=xen is supposed to be the ideal clocksource, with no downsides. > I have a bad experience with running the Dom0 kernel > (xen/stabale-2.6.31.6-based) with the default clocksource=xen, as it > results in the system getting temporary "hangs", very short ones, but > annoying. E.g. when one types fast on a keyboard, then every 10 seconds > or so, the keystroke processing seems to be slowing down significantly > for a second o so. > There have been a number of reports about hiccups of varying degrees of severity when using clocksource=xen (and, interestingly, in KVM when using its very similar pv clock interface). I haven't seen anyone mention keyboard interactive performance; the failure mode I've seen is disk IO hiccuping or even getting completely wedged. Unfortunately I haven't made much headway in debugging it (or even reliably reproducing it). What is the hardware platform? How many CPUs are you using? Does pinning the vcpus to pcpus help? > Running the kernel with clocksource=jiffies eliminates the above problem > but has a disadvantage of the clock drift in Dom0. This is not > acceptable on my setup, where I don't have any networking in Dom0, which > means I cannot correct it via NTP. > > Interestingly the above problem didn't seem to affect the Dom0 kernel > based on xen/stable-2.6.32. That's interesting; there's no difference in the Xen-specific timekeeping parts of the kernel, but perhaps something else has changed in the way time is handled. I don't remember if 3.4.2 ended up with tsc emulation, but if it does you might try enabling it. > Unfortunately I assume I'm no longer able to > run this kernel when using Xen 3.4.2. > Yes. 3.4.3 will support the newer kernels, but that isn't released yet. J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-09 23:36 ` Jeremy Fitzhardinge @ 2010-03-10 22:13 ` Joanna Rutkowska 2010-03-11 0:07 ` Dan Magenheimer 2010-03-11 7:47 ` Keir Fraser 0 siblings, 2 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-10 22:13 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: xen-devel@lists.xensource.com [-- Attachment #1.1: Type: text/plain, Size: 3088 bytes --] On 03/10/2010 12:36 AM, Jeremy Fitzhardinge wrote: > On 03/09/2010 02:47 AM, Joanna Rutkowska wrote: >> I would appreciate if somebody could shed some light on the currently >> preferred setting of the clocksource for the pvops0 kernels, used both >> in Dom0 and DomU (I'm using pvops0 in DomU because it provides backends, >> e.g. network backend). >> > > clocksource=xen is supposed to be the ideal clocksource, with no downsides. > >> I have a bad experience with running the Dom0 kernel >> (xen/stabale-2.6.31.6-based) with the default clocksource=xen, as it >> results in the system getting temporary "hangs", very short ones, but >> annoying. E.g. when one types fast on a keyboard, then every 10 seconds >> or so, the keystroke processing seems to be slowing down significantly >> for a second o so. >> > > There have been a number of reports about hiccups of varying degrees of > severity when using clocksource=xen (and, interestingly, in KVM when > using its very similar pv clock interface). I haven't seen anyone > mention keyboard interactive performance; the failure mode I've seen is > disk IO hiccuping or even getting completely wedged. Unfortunately I > haven't made much headway in debugging it (or even reliably reproducing > it). > > What is the hardware platform? Intel Core 2 Duo, Intel PM45 chipset. > How many CPUs are you using? 2 cores, all CPU-specific power management in BIOS disabled. > Does pinning the vcpus to pcpus help? I tried: xm vcpu-pin <dom> all all for all my running domains, and it didn't change anything. But not sure if this is correct? Perhaps I should do: xm vcpu-pin <dom> 0 0 xm vcpu-pin <dom> 1 1 ? Perhaps there is a boot option to do the same system-wide? >> Running the kernel with clocksource=jiffies eliminates the above problem >> but has a disadvantage of the clock drift in Dom0. This is not >> acceptable on my setup, where I don't have any networking in Dom0, which >> means I cannot correct it via NTP. >> >> Interestingly the above problem didn't seem to affect the Dom0 kernel >> based on xen/stable-2.6.32. > > That's interesting; there's no difference in the Xen-specific > timekeeping parts of the kernel, but perhaps something else has changed > in the way time is handled. > > Interestingly, this keyboard hiccup effect does not occur in DomUs, only in Dom0. However, the DomUs clearly experience some scheduling problems -- e.g. sometime programs take a loooong time to start up, just like if their CPU time was miscalculated and they were constantly preempted, but xentop doesn't show any high load anywhere. Occasionally this is visible in both Dom0's and DomU's dmesgs: Clocksource tsc unstable (delta = 62752834 ns) hrtimer: interrupt too slow, forcing clock min delta to 412700358 ns > I don't remember if 3.4.2 ended up with tsc emulation, but if it does > you might try enabling it. > TSC emulation? But I'm running only PV guests. Not sure what do you mean by this, or how to enable it? j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: A clocksource question 2010-03-10 22:13 ` Joanna Rutkowska @ 2010-03-11 0:07 ` Dan Magenheimer 2010-03-11 0:15 ` Joanna Rutkowska 2010-03-11 0:21 ` Ian Pratt 2010-03-11 7:47 ` Keir Fraser 1 sibling, 2 replies; 42+ messages in thread From: Dan Magenheimer @ 2010-03-11 0:07 UTC (permalink / raw) To: Joanna Rutkowska, Jeremy Fitzhardinge; +Cc: xen-devel > Clocksource tsc unstable (delta = 62752834 ns) > hrtimer: interrupt too slow, forcing clock min delta to 412700358 ns > > > I don't remember if 3.4.2 ended up with tsc emulation, but if it does > > you might try enabling it. > > > > TSC emulation? But I'm running only PV guests. Not sure what do you > mean > by this, or how to enable it? I don't think there is any TSC emulation (or more properly "rdtsc emulation") in 3.4.x, certainly not without a special Xen boot option. The TSC delta is troubling... if you hadn't said you had turned off all power management, I would have guessed a problem with C-state management. Maybe Xen is discovering some power management capability not visible in BIOS settings? ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 0:07 ` Dan Magenheimer @ 2010-03-11 0:15 ` Joanna Rutkowska 2010-03-11 0:21 ` Ian Pratt 1 sibling, 0 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-11 0:15 UTC (permalink / raw) To: Dan Magenheimer; +Cc: Jeremy Fitzhardinge, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 1208 bytes --] On 03/11/2010 01:07 AM, Dan Magenheimer wrote: >> Clocksource tsc unstable (delta = 62752834 ns) >> hrtimer: interrupt too slow, forcing clock min delta to 412700358 ns >> >>> I don't remember if 3.4.2 ended up with tsc emulation, but if it does >>> you might try enabling it. >>> >> >> TSC emulation? But I'm running only PV guests. Not sure what do you >> mean >> by this, or how to enable it? > > I don't think there is any TSC emulation (or more properly "rdtsc emulation") > in 3.4.x, certainly not without a special Xen boot option. > > The TSC delta is troubling... Actually I'm getting this also when booting Dom0 (pvops 2.6.31.6-based) with clocksource=jifffies: Clocksource tsc unstable (delta = 62528016 ns) But, there are not visible problems like kbd hiccup or process scheduling in VM (besides wallclock drift in Dom0 which is annoying). > if you hadn't said you had turned > off all power management, I would have guessed a problem with > C-state management. Maybe Xen is discovering some power management > capability not visible in BIOS settings? > I'm not very much of an ACPI expert, so if there are any output I can send, just let me know. j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: A clocksource question 2010-03-11 0:07 ` Dan Magenheimer 2010-03-11 0:15 ` Joanna Rutkowska @ 2010-03-11 0:21 ` Ian Pratt 2010-03-11 0:44 ` Dan Magenheimer 2010-03-11 0:52 ` Joanna Rutkowska 1 sibling, 2 replies; 42+ messages in thread From: Ian Pratt @ 2010-03-11 0:21 UTC (permalink / raw) To: Dan Magenheimer, Joanna Rutkowska, Jeremy Fitzhardinge Cc: Ian Pratt, xen-devel@lists.xensource.com > The TSC delta is troubling... if you hadn't said you had turned > off all power management, I would have guessed a problem with > C-state management. Maybe Xen is discovering some power management > capability not visible in BIOS settings? Xen uses the architectural C state mechanism, bypassing ACPI. Use "max_cstate=0" Ian ^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: A clocksource question 2010-03-11 0:21 ` Ian Pratt @ 2010-03-11 0:44 ` Dan Magenheimer 2010-03-12 0:34 ` Joanna Rutkowska 2010-03-11 0:52 ` Joanna Rutkowska 1 sibling, 1 reply; 42+ messages in thread From: Dan Magenheimer @ 2010-03-11 0:44 UTC (permalink / raw) To: Ian Pratt, Joanna Rutkowska, Jeremy Fitzhardinge; +Cc: xen-devel > From: Ian Pratt [mailto:Ian.Pratt@eu.citrix.com] > Sent: Wednesday, March 10, 2010 5:22 PM > To: Dan Magenheimer; Joanna Rutkowska; Jeremy Fitzhardinge > Cc: Ian Pratt; xen-devel@lists.xensource.com > Subject: RE: [Xen-devel] A clocksource question > > > The TSC delta is troubling... if you hadn't said you had turned > > off all power management, I would have guessed a problem with > > C-state management. Maybe Xen is discovering some power management > > capability not visible in BIOS settings? > > Xen uses the architectural C state mechanism, bypassing ACPI. > Use "max_cstate=0" Yes! The Core 2 Duo fooled me. There are some versions of Core 2 Duo ("Conroe") that don't support C3-state and some ("Merom") that do support C3-state. And the code to "recover" from C3, which I think was added before 3.4 was released, has been observed to be very poor in its attempt to reset TSC after C3 to a reasonable value. I didn't think it was THAT poor though! See: http://lists.xensource.com/archives/html/xen-devel/2009-10/msg01414.html (AFAIK, this is not fixed in 4.0, though the new default rdtsc emulation may mask the problem by ensuring TSC always moves forward, even across different processors.) So that may explain the TSC delta. Since the pv clocksource algorithm is dependent in part on the hardware TSC being synced reasonably well by Xen, that may also explain other clock strangeness. P.S. Joanna -- max_cstate=0 must be specified on the Xen boot line in grub.conf, not in the vm.cfg or grub.conf of the guest. ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 0:44 ` Dan Magenheimer @ 2010-03-12 0:34 ` Joanna Rutkowska 0 siblings, 0 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-12 0:34 UTC (permalink / raw) To: Dan Magenheimer; +Cc: Ian Pratt, xen-devel, Jeremy Fitzhardinge [-- Attachment #1.1: Type: text/plain, Size: 2308 bytes --] On 03/11/2010 01:44 AM, Dan Magenheimer wrote: >> From: Ian Pratt [mailto:Ian.Pratt@eu.citrix.com] >> Sent: Wednesday, March 10, 2010 5:22 PM >> To: Dan Magenheimer; Joanna Rutkowska; Jeremy Fitzhardinge >> Cc: Ian Pratt; xen-devel@lists.xensource.com >> Subject: RE: [Xen-devel] A clocksource question >> >>> The TSC delta is troubling... if you hadn't said you had turned >>> off all power management, I would have guessed a problem with >>> C-state management. Maybe Xen is discovering some power management >>> capability not visible in BIOS settings? >> >> Xen uses the architectural C state mechanism, bypassing ACPI. >> Use "max_cstate=0" > > Yes! The Core 2 Duo fooled me. There are some versions > of Core 2 Duo ("Conroe") that don't support C3-state and > some ("Merom") that do support C3-state. And the code > to "recover" from C3, which I think was added before 3.4 > was released, has been observed to be very poor in its > attempt to reset TSC after C3 to a reasonable value. I > didn't think it was THAT poor though! See: > http://lists.xensource.com/archives/html/xen-devel/2009-10/msg01414.html > > (AFAIK, this is not fixed in 4.0, though the new default > rdtsc emulation may mask the problem by ensuring TSC always > moves forward, even across different processors.) > > So that may explain the TSC delta. Since the pv clocksource > algorithm is dependent in part on the hardware TSC being > synced reasonably well by Xen, that may also explain > other clock strangeness. > > P.S. Joanna -- max_cstate=0 must be specified on the > Xen boot line in grub.conf, not in the vm.cfg or grub.conf > of the guest. Dan, I tried passing this argument to Xen, of course and it didn't help. I still think it's a Dom0-related problem rather than a hypervisor, because when I was using xen/stable-2.6.32-based kernel for a moment, I'm pretty sure it worked fine and I didn't have any problem with the clocksource. On the same hypervisor, when I used xen/stable-2.6.31 kernel, the problem was present. (I had to switch back to 2.6.31 because, back then, the 2.6.32 didn't have pciback, which was important for me; and recently I decided to downgrade to Xen 3.4.2, for its presumed stability, and so 2.6.31 is the only option now). joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 0:21 ` Ian Pratt 2010-03-11 0:44 ` Dan Magenheimer @ 2010-03-11 0:52 ` Joanna Rutkowska 2010-03-11 1:06 ` Jeremy Fitzhardinge 1 sibling, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-11 0:52 UTC (permalink / raw) To: Ian Pratt Cc: Dan Magenheimer, xen-devel@lists.xensource.com, Jeremy Fitzhardinge [-- Attachment #1.1: Type: text/plain, Size: 531 bytes --] On 03/11/2010 01:21 AM, Ian Pratt wrote: >> The TSC delta is troubling... if you hadn't said you had turned >> off all power management, I would have guessed a problem with >> C-state management. Maybe Xen is discovering some power management >> capability not visible in BIOS settings? > > Xen uses the architectural C state mechanism, bypassing ACPI. > Use "max_cstate=0" > Tried it (as an argument to xen) and it didn't seem to help. BTW, how does the clocksource=jiffies work on a pvops kernel in Dom0? j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 0:52 ` Joanna Rutkowska @ 2010-03-11 1:06 ` Jeremy Fitzhardinge 2010-03-11 1:19 ` Joanna Rutkowska 0 siblings, 1 reply; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-11 1:06 UTC (permalink / raw) To: Joanna Rutkowska Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer On 03/10/2010 04:52 PM, Joanna Rutkowska wrote: > BTW, how does the clocksource=jiffies work on a pvops kernel in Dom0? > Not very well. clocksource=jiffies just sets up timer interrupts at approx 100ms intervals and assumes that's 100ms. You get very low res timers and timekeeping. J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 1:06 ` Jeremy Fitzhardinge @ 2010-03-11 1:19 ` Joanna Rutkowska 2010-03-11 4:55 ` Jeremy Fitzhardinge 0 siblings, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-11 1:19 UTC (permalink / raw) To: Jeremy Fitzhardinge Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer [-- Attachment #1.1: Type: text/plain, Size: 808 bytes --] On 11/03/2010 02:06, Jeremy Fitzhardinge wrote: > On 03/10/2010 04:52 PM, Joanna Rutkowska wrote: >> BTW, how does the clocksource=jiffies work on a pvops kernel in Dom0? >> > > Not very well. clocksource=jiffies just sets up timer interrupts at > approx 100ms intervals and assumes that's 100ms. You get very low res > timers and timekeeping. > So, how to explain that there is no wallclock drift *at all*, even in a long run -- uptime of a few days, in Dom0, when it uses the jiffies source? Anyway, I assume that the "xen" clock source is much more fine grained (1ms?) and so, maybe my kbd hiccups are caused by some code executed by the timer interrupt too frequently (maybe too much code executes per each timer interrupt, because of some other bug)? Just a though... j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 163 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 1:19 ` Joanna Rutkowska @ 2010-03-11 4:55 ` Jeremy Fitzhardinge 2010-03-11 10:49 ` Joanna Rutkowska 2010-03-12 0:27 ` Joanna Rutkowska 0 siblings, 2 replies; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-11 4:55 UTC (permalink / raw) To: Joanna Rutkowska Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer On 03/10/2010 05:19 PM, Joanna Rutkowska wrote: > On 11/03/2010 02:06, Jeremy Fitzhardinge wrote: > >> On 03/10/2010 04:52 PM, Joanna Rutkowska wrote: >> >>> BTW, how does the clocksource=jiffies work on a pvops kernel in Dom0? >>> >>> >> Not very well. clocksource=jiffies just sets up timer interrupts at >> approx 100ms intervals and assumes that's 100ms. You get very low res >> timers and timekeeping. >> >> > So, how to explain that there is no wallclock drift *at all*, even in a > long run -- uptime of a few days, in Dom0, when it uses the jiffies source? > You said earlier that you were seeing clock drift with clocksource=jiffies in dom0. > Anyway, I assume that the "xen" clock source is much more fine grained > (1ms?) The xen clocksource has nanosecond resolution. But clocksources are different from event sources, and so the ns resolution of time measurement doesn't have much relationship to the timer precision (which is always going to use the xen event source, which is also ns resolution, but it will tend to fold together timer events which are closer than 50us). > and so, maybe my kbd hiccups are caused by some code executed by > the timer interrupt too frequently (maybe too much code executes per > each timer interrupt, because of some other bug)? Just a though... > Possibly, but doesn't seem too likely. Can you tell if your hiccups are accompanied by bursts of timer interrupts in /proc/interrupts? There is another possibility, which is that the scheduler is getting confused by xen's scheduler clock. Rather than just scheduling based on real time, we try to take into account time stolen from a vcpu so that it isn't credited against the process (which may have had all its time stolen by another domain). But that could just be confusing things. Does this help? diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c index 0d3f07c..9029885 100644 --- a/arch/x86/xen/time.c +++ b/arch/x86/xen/time.c @@ -161,6 +161,9 @@ static void do_stolen_accounting(void) */ unsigned long long xen_sched_clock(void) { +#if 1 + return xen_clocksource_read(); +#else struct vcpu_runstate_info state; cycle_t now; u64 ret; @@ -190,6 +193,7 @@ unsigned long long xen_sched_clock(void) preempt_enable(); return ret; +#endif } J ^ permalink raw reply related [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 4:55 ` Jeremy Fitzhardinge @ 2010-03-11 10:49 ` Joanna Rutkowska 2010-03-12 0:27 ` Joanna Rutkowska 1 sibling, 0 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-11 10:49 UTC (permalink / raw) To: Jeremy Fitzhardinge Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer [-- Attachment #1.1: Type: text/plain, Size: 2203 bytes --] On 03/11/2010 05:55 AM, Jeremy Fitzhardinge wrote: > On 03/10/2010 05:19 PM, Joanna Rutkowska wrote: >> On 11/03/2010 02:06, Jeremy Fitzhardinge wrote: >> >>> On 03/10/2010 04:52 PM, Joanna Rutkowska wrote: >>> >>>> BTW, how does the clocksource=jiffies work on a pvops kernel in Dom0? >>>> >>>> >>> Not very well. clocksource=jiffies just sets up timer interrupts at >>> approx 100ms intervals and assumes that's 100ms. You get very low res >>> timers and timekeeping. >>> >>> >> So, how to explain that there is no wallclock drift *at all*, even in a >> long run -- uptime of a few days, in Dom0, when it uses the jiffies >> source? >> > > You said earlier that you were seeing clock drift with > clocksource=jiffies in dom0. > Correct, sorry. With jiffies I do get a wallclock drift, yes. >> Anyway, I assume that the "xen" clock source is much more fine grained >> (1ms?) > > The xen clocksource has nanosecond resolution. But clocksources are > different from event sources, and so the ns resolution of time > measurement doesn't have much relationship to the timer precision (which > is always going to use the xen event source, which is also ns > resolution, but it will tend to fold together timer events which are > closer than 50us). > >> and so, maybe my kbd hiccups are caused by some code executed by >> the timer interrupt too frequently (maybe too much code executes per >> each timer interrupt, because of some other bug)? Just a though... >> > > Possibly, but doesn't seem too likely. Can you tell if your hiccups are > accompanied by bursts of timer interrupts in /proc/interrupts? > > There is another possibility, which is that the scheduler is getting > confused by xen's scheduler clock. Rather than just scheduling based on > real time, we try to take into account time stolen from a vcpu so that > it isn't credited against the process (which may have had all its time > stolen by another domain). But that could just be confusing things. > > Does this help? > > diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c Will build a new kernel with this and let you know. j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-11 4:55 ` Jeremy Fitzhardinge 2010-03-11 10:49 ` Joanna Rutkowska @ 2010-03-12 0:27 ` Joanna Rutkowska 2010-03-12 0:49 ` Jeremy Fitzhardinge 1 sibling, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-12 0:27 UTC (permalink / raw) To: Jeremy Fitzhardinge Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer [-- Attachment #1.1: Type: text/plain, Size: 2918 bytes --] On 03/11/2010 05:55 AM, Jeremy Fitzhardinge wrote: >> and so, maybe my kbd hiccups are caused by some code executed by >> the timer interrupt too frequently (maybe too much code executes per >> each timer interrupt, because of some other bug)? Just a though... >> > > Possibly, but doesn't seem too likely. Can you tell if your hiccups are > accompanied by bursts of timer interrupts in /proc/interrupts? > > There is another possibility, which is that the scheduler is getting > confused by xen's scheduler clock. Rather than just scheduling based on > real time, we try to take into account time stolen from a vcpu so that > it isn't credited against the process (which may have had all its time > stolen by another domain). But that could just be confusing things. > > Does this help? > > diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c > index 0d3f07c..9029885 100644 > --- a/arch/x86/xen/time.c > +++ b/arch/x86/xen/time.c > @@ -161,6 +161,9 @@ static void do_stolen_accounting(void) > */ > unsigned long long xen_sched_clock(void) > { > +#if 1 > + return xen_clocksource_read(); > +#else > struct vcpu_runstate_info state; > cycle_t now; > u64 ret; > @@ -190,6 +193,7 @@ unsigned long long xen_sched_clock(void) > preempt_enable(); > > return ret; > +#endif > } > Nope, it didn't. I think that the important clue is this message appearing in my dmesg (in Dom0 and also in DomUs): hrtimer: interrupt too slow, forcing clock min delta to 540150561 ns This is almost 0.5s (!) and I think this might explain my kbd hiccup. I wrote that I feel it every 10s or so, but when I was playing on my system without jiffies setting today, I saw this hiccup occurring much more often; in fact it was more of a "slow keyboard/system" feeling than a hiccup". Anyway, this is a comment from the function that displays this warning (kernel/hrtimer.c): /* * After 5 iteration's attempts, we consider that hrtimer_interrupt() * is hanging, which could happen with something that slows the interrupt * such as the tracing. Then we force the clock reprogramming for each future * hrtimer interrupts to avoid infinite loops and use the min_delta_ns * threshold that we will overwrite. * The next tick event will be scheduled to 3 times we currently spend on * hrtimer_interrupt(). This gives a good compromise, the cpus will spend * 1/4 of their time to process the hrtimer interrupts. This is enough to * let it running without serious starvation. */ static inline void hrtimer_interrupt_hanging(struct clock_event_device *dev, ktime_t try_time) { force_clock_reprogram = 1; dev->min_delta_ns = (unsigned long)try_time.tv64 * 3; printk(KERN_WARNING "hrtimer: interrupt too slow, " "forcing clock min delta to %lu ns\n", dev->min_delta_ns); } joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 0:27 ` Joanna Rutkowska @ 2010-03-12 0:49 ` Jeremy Fitzhardinge 2010-03-12 0:38 ` Joanna Rutkowska 0 siblings, 1 reply; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-12 0:49 UTC (permalink / raw) To: Joanna Rutkowska Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer On 03/11/2010 04:27 PM, Joanna Rutkowska wrote: > I think that the important clue is this message appearing in my dmesg > (in Dom0 and also in DomUs): > > hrtimer: interrupt too slow, forcing clock min delta to 540150561 ns > > This is almost 0.5s (!) and I think this might explain my kbd hiccup. I > wrote that I feel it every 10s or so, but when I was playing on my > system without jiffies setting today, I saw this hiccup occurring much > more often; in fact it was more of a "slow keyboard/system" feeling than > a hiccup". > Yes, its definitely a good clue. It could point to a Xen scheduler issue (I assume you don't have any other busy domains when this is going on), but that wouldn't explain why it works OK with jiffies. Perhaps there's a problem with programming the timer so that sometimes it gets missed and the system doesn't get a kick until some subsequent event (whereas with clocksource=jiffies there'll always be a timer in the next 100ms). J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 0:49 ` Jeremy Fitzhardinge @ 2010-03-12 0:38 ` Joanna Rutkowska 2010-03-12 19:02 ` Joanna Rutkowska 0 siblings, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-12 0:38 UTC (permalink / raw) To: Jeremy Fitzhardinge Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer [-- Attachment #1.1: Type: text/plain, Size: 1417 bytes --] On 03/12/2010 01:49 AM, Jeremy Fitzhardinge wrote: > On 03/11/2010 04:27 PM, Joanna Rutkowska wrote: >> I think that the important clue is this message appearing in my dmesg >> (in Dom0 and also in DomUs): >> >> hrtimer: interrupt too slow, forcing clock min delta to 540150561 ns >> >> This is almost 0.5s (!) and I think this might explain my kbd hiccup. I >> wrote that I feel it every 10s or so, but when I was playing on my >> system without jiffies setting today, I saw this hiccup occurring much >> more often; in fact it was more of a "slow keyboard/system" feeling than >> a hiccup". >> > > Yes, its definitely a good clue. It could point to a Xen scheduler > issue (I assume you don't have any other busy domains when this is going > on), but that wouldn't explain why it works OK with jiffies. Perhaps > there's a problem with programming the timer so that sometimes it gets > missed and the system doesn't get a kick until some subsequent event > (whereas with clocksource=jiffies there'll always be a timer in the next > 100ms). > One detail: when I boot the system and there is only Dom0 running, everything seems ok. Only after I start at least one VM the problem becomes noticeable. But the other VM(s) is pretty much idle (as xentop shows). When I kill all the other VMs, so that Dom0 is alone again, the problem does *not* seem to go away, strangely... j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 0:38 ` Joanna Rutkowska @ 2010-03-12 19:02 ` Joanna Rutkowska 2010-03-12 21:24 ` Jeremy Fitzhardinge 0 siblings, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-12 19:02 UTC (permalink / raw) To: Jeremy Fitzhardinge Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer [-- Attachment #1.1: Type: text/plain, Size: 1623 bytes --] On 03/12/2010 01:38 AM, Joanna Rutkowska wrote: > On 03/12/2010 01:49 AM, Jeremy Fitzhardinge wrote: >> On 03/11/2010 04:27 PM, Joanna Rutkowska wrote: >>> I think that the important clue is this message appearing in my dmesg >>> (in Dom0 and also in DomUs): >>> >>> hrtimer: interrupt too slow, forcing clock min delta to 540150561 ns >>> >>> This is almost 0.5s (!) and I think this might explain my kbd hiccup. I >>> wrote that I feel it every 10s or so, but when I was playing on my >>> system without jiffies setting today, I saw this hiccup occurring much >>> more often; in fact it was more of a "slow keyboard/system" feeling than >>> a hiccup". >>> >> >> Yes, its definitely a good clue. It could point to a Xen scheduler >> issue (I assume you don't have any other busy domains when this is going >> on), but that wouldn't explain why it works OK with jiffies. Perhaps >> there's a problem with programming the timer so that sometimes it gets >> missed and the system doesn't get a kick until some subsequent event >> (whereas with clocksource=jiffies there'll always be a timer in the next >> 100ms). >> > One detail: when I boot the system and there is only Dom0 running, > everything seems ok. Only after I start at least one VM the problem > becomes noticeable. But the other VM(s) is pretty much idle (as xentop > shows). > > When I kill all the other VMs, so that Dom0 is alone again, the problem > does *not* seem to go away, strangely... > Today I upgraded to xen 3.4.3-rc3 and tried the 2.6.32 kernel (the Micheal Young's one) -- the same problem :( joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 19:02 ` Joanna Rutkowska @ 2010-03-12 21:24 ` Jeremy Fitzhardinge 2010-03-12 21:56 ` Tobias Geiger 0 siblings, 1 reply; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-12 21:24 UTC (permalink / raw) To: Joanna Rutkowska Cc: Ian Pratt, xen-devel@lists.xensource.com, Dan Magenheimer On 03/12/2010 11:02 AM, Joanna Rutkowska wrote: > Today I upgraded to xen 3.4.3-rc3 and tried the 2.6.32 kernel (the > Micheal Young's one) -- the same problem :( > Good, in a way. I can't think of a reason it would change from .31 -> .32. Experiment of the moment: does changing the clocksource in /sys/devices/system/clocksource/clocksource0/current_clocksource reset the problem after killing the other domains? Ie, switch it from xen->jiffies->xen for a while. Thanks, J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 21:24 ` Jeremy Fitzhardinge @ 2010-03-12 21:56 ` Tobias Geiger 2010-03-12 22:02 ` Jeremy Fitzhardinge 0 siblings, 1 reply; 42+ messages in thread From: Tobias Geiger @ 2010-03-12 21:56 UTC (permalink / raw) To: xen-devel Am Freitag 12 März 2010 22:24:54 schrieb Jeremy Fitzhardinge: > On 03/12/2010 11:02 AM, Joanna Rutkowska wrote: > > Today I upgraded to xen 3.4.3-rc3 and tried the 2.6.32 kernel (the > > Micheal Young's one) -- the same problem :( > > Good, in a way. I can't think of a reason it would change from .31 -> .32. > > Experiment of the moment: does changing the clocksource in > /sys/devices/system/clocksource/clocksource0/current_clocksource reset > the problem after killing the other domains? Ie, switch it from > xen->jiffies->xen for a while. > kbpc2:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource xen kbpc2:~# cat /sys/devices/system/clocksource/clocksource0/available_clocksource xen kbpc2:~# echo "jiffies" >/sys/devices/system/clocksource/clocksource0/current_clocksource kbpc2:~# dmesg | tail -1 [ 7898.642404] Override clocksource jiffies is not HRT compatible. Cannot switch while in HRT/NOHZ mode kbpc2:~# Seems like it's not possible to switch to jiffies - however: kbpc2:~# zcat /proc/config.gz | grep NO_HZ # CONFIG_NO_HZ is not set but CONFIG_SCHED_HRTICK=y Greetings Tobias > Thanks, > J > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 21:56 ` Tobias Geiger @ 2010-03-12 22:02 ` Jeremy Fitzhardinge 2010-03-12 21:01 ` Joanna Rutkowska 2010-03-12 22:56 ` Tobias Geiger 0 siblings, 2 replies; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-12 22:02 UTC (permalink / raw) To: Tobias Geiger; +Cc: xen-devel, Joanna Rutkowska On 03/12/2010 01:56 PM, Tobias Geiger wrote: > kbpc2:~# cat > /sys/devices/system/clocksource/clocksource0/current_clocksource > xen > kbpc2:~# cat > /sys/devices/system/clocksource/clocksource0/available_clocksource > xen > kbpc2:~# echo "jiffies" > >> /sys/devices/system/clocksource/clocksource0/current_clocksource >> > kbpc2:~# dmesg | tail -1 > [ 7898.642404] Override clocksource jiffies is not HRT compatible. Cannot switch > while in HRT/NOHZ mode > kbpc2:~# > > Seems like it's not possible to switch to jiffies - however: > kbpc2:~# zcat /proc/config.gz | grep NO_HZ > # CONFIG_NO_HZ is not set > > but CONFIG_SCHED_HRTICK=y > Interesting. BTW, does NO_HZ change the behaviour of this? In principle NO_HZ should be preferable, and particularly in a virtual machine since it should limit the number of timer interrupts. Joanna, are you using NO_HZ? Thanks, J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 22:02 ` Jeremy Fitzhardinge @ 2010-03-12 21:01 ` Joanna Rutkowska 2010-03-12 21:13 ` Joanna Rutkowska 2010-03-12 22:56 ` Tobias Geiger 1 sibling, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-12 21:01 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: Tobias Geiger, xen-devel [-- Attachment #1.1.1: Type: text/plain, Size: 2489 bytes --] On 03/12/2010 11:02 PM, Jeremy Fitzhardinge wrote: > On 03/12/2010 01:56 PM, Tobias Geiger wrote: >> kbpc2:~# cat >> /sys/devices/system/clocksource/clocksource0/current_clocksource >> xen >> kbpc2:~# cat >> /sys/devices/system/clocksource/clocksource0/available_clocksource >> xen >> kbpc2:~# echo "jiffies" >> >>> /sys/devices/system/clocksource/clocksource0/current_clocksource >>> >> kbpc2:~# dmesg | tail -1 >> [ 7898.642404] Override clocksource jiffies is not HRT compatible. >> Cannot switch >> while in HRT/NOHZ mode >> kbpc2:~# >> >> Seems like it's not possible to switch to jiffies - however: >> kbpc2:~# zcat /proc/config.gz | grep NO_HZ >> # CONFIG_NO_HZ is not set >> >> but CONFIG_SCHED_HRTICK=y >> > > Interesting. BTW, does NO_HZ change the behaviour of this? In > principle NO_HZ should be preferable, and particularly in a virtual > machine since it should limit the number of timer interrupts. > > Joanna, are you using NO_HZ? > Yes, I have: CONFIG_NO_HZ=y BTW, FWIW, I'm attaching my kernel config. It's almost the same as the previously mentioned "Young's Dec23" kernel (the only difference being some more recent pvops git patches applied and pcifront being enabled as a module). While trying to switch from xen source to jiffies source, I got the same message as Tobias: jiffies clocksource is not HRT compatible. Cannot switch while in HRT/NOHZ mode I can definitely say that this previously mentioned warning from hrtimer about interrupt being too slow is the marking of the start of all the troubles. E.g. when I run my Dom0 for some time without starting any other VMs, the system behaves good, and no warning in dmesg. Only after I start a VM, and probably depending on how heavy load it produces, the warning appears in Dom0 dmesg and the problem becomes "feelable". And, depending on what new "delta" is being chosen, the system is either still usable -- e.g. with a delta like in this case: hrtimer: interrupt too slow, forcing clock min delta to 82595226 ns which is around 80ms (still the very subtle hiccups can be observed when you press and hold a key for some time), or totally unusable, if one is unlucky, and the "safe" delta got chosen to be something around 0.5s (which interestingly happens most often in my case). The "clocksource tsc unstable" messages trouble me too BTW. They seem to appear before the hrtimer "interrupt too slow" messages. joanna. [-- Attachment #1.1.2: kernel-2.6.31.9-x86_64.config --] [-- Type: text/plain, Size: 103478 bytes --] # x86_64 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.31.9 # Fri Mar 12 21:40:02 2010 # CONFIG_64BIT=y # CONFIG_X86_32 is not set CONFIG_X86_64=y CONFIG_X86=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_HAVE_DYNAMIC_PER_CPU_AREA=y CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ZONE_DMA32=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_X86_TRAMPOLINE=y CONFIG_X86_VSYSCALL=y # CONFIG_KTIME_SCALAR is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y # # RCU Subsystem # # CONFIG_CLASSIC_RCU is not set CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=64 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_GROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_RT_GROUP_SCHED=y # CONFIG_USER_SCHED is not set CONFIG_CGROUP_SCHED=y CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_NS=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_RESOURCE_COUNTERS=y CONFIG_CGROUP_MEM_RES_CTLR=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y CONFIG_MM_OWNER=y # CONFIG_SYSFS_DEPRECATED_V2 is not set CONFIG_RELAY=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_HAVE_PERF_COUNTERS=y # # Performance Counters # CONFIG_PERF_COUNTERS=y CONFIG_EVENT_PROFILE=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y CONFIG_STRIP_ASM_SYMS=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_MARKERS=y CONFIG_OPROFILE=m CONFIG_OPROFILE_IBS=y CONFIG_HAVE_OPROFILE=y CONFIG_KPROBES=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_KRETPROBES=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_HAVE_DMA_API_DEBUG=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set CONFIG_SLOW_WORK=y # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_STOP_MACHINE=y CONFIG_UTRACE=y CONFIG_BLOCK=y CONFIG_BLK_DEV_BSG=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_PREEMPT_NOTIFIERS=y CONFIG_FREEZER=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y CONFIG_X86_X2APIC=y CONFIG_SPARSE_IRQ=y CONFIG_NUMA_IRQ_DESC=y CONFIG_X86_MPPARSE=y CONFIG_X86_EXTENDED_PLATFORM=y # CONFIG_X86_VSMP is not set # CONFIG_X86_UV is not set CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_PARAVIRT_GUEST=y CONFIG_XEN=y CONFIG_XEN_TIME_VSYSCALL=y CONFIG_XEN_MAX_DOMAIN_MEMORY=32 CONFIG_XEN_SAVE_RESTORE=y CONFIG_XEN_DEBUG_FS=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y CONFIG_MICROCODE_XEN=y CONFIG_KVM_CLOCK=y CONFIG_KVM_GUEST=y CONFIG_PARAVIRT=y # CONFIG_PARAVIRT_SPINLOCKS is not set CONFIG_PARAVIRT_CLOCK=y CONFIG_PARAVIRT_CLOCK_VSYSCALL=y # CONFIG_PARAVIRT_DEBUG is not set # CONFIG_MEMTEST is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set CONFIG_GENERIC_CPU=y CONFIG_X86_CPU=y CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y # CONFIG_X86_DS is not set CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y CONFIG_CALGARY_IOMMU=y CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y CONFIG_AMD_IOMMU=y CONFIG_AMD_IOMMU_STATS=y CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y CONFIG_IOMMU_API=y # CONFIG_MAXSMP is not set CONFIG_NR_CPUS=256 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y CONFIG_X86_MCE=y CONFIG_X86_NEW_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_X86_MCE_AMD=y CONFIG_X86_MCE_THRESHOLD=y # CONFIG_X86_MCE_INJECT is not set CONFIG_X86_THERMAL_VECTOR=y CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_CPU_DEBUG=m CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_DIRECT_GBPAGES=y CONFIG_NUMA=y CONFIG_K8_NUMA=y CONFIG_X86_64_ACPI_NUMA=y CONFIG_NODES_SPAN_OTHER_NODES=y # CONFIG_NUMA_EMU is not set CONFIG_NODES_SHIFT=9 CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y # CONFIG_FLATMEM_MANUAL is not set # CONFIG_DISCONTIGMEM_MANUAL is not set CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_NEED_MULTIPLE_NODES=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y # # Memory hotplug is currently incompatible with Software Suspend # CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_HAVE_MLOCK=y CONFIG_HAVE_MLOCKED_PAGE_BIT=y CONFIG_MMU_NOTIFIER=y CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW_64K=y CONFIG_MTRR=y CONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=y CONFIG_EFI=y CONFIG_SECCOMP=y CONFIG_CC_STACKPROTECTOR=y # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y CONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y # CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y # # Power management and ACPI options # CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_PM=y CONFIG_PM_DEBUG=y # CONFIG_PM_VERBOSE is not set CONFIG_CAN_PM_TRACE=y CONFIG_PM_TRACE=y CONFIG_PM_TRACE_RTC=y CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y CONFIG_SUSPEND=y # CONFIG_PM_TEST_SUSPEND is not set CONFIG_SUSPEND_FREEZER=y CONFIG_HIBERNATION_NVS=y CONFIG_HIBERNATION=y CONFIG_PM_STD_PARTITION="" CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROCFS_POWER=y CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y CONFIG_ACPI_SBS=m # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=m CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=m CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=m CONFIG_X86_POWERNOW_K8=m # CONFIG_X86_SPEEDSTEP_CENTRINO is not set CONFIG_X86_P4_CLOCKMOD=m # # shared options # CONFIG_X86_SPEEDSTEP_LIB=m CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Memory power savings # CONFIG_I7300_IDLE_IOAT_CHANNEL=y CONFIG_I7300_IDLE=m # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_XEN=y CONFIG_PCI_DOMAINS=y CONFIG_DMAR=y CONFIG_DMAR_DEFAULT_ON=y CONFIG_DMAR_BROKEN_GFX_WA=y CONFIG_DMAR_FLOPPY_WA=y CONFIG_INTR_REMAP=y CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=y CONFIG_PCIEAER=y CONFIG_PCIE_ECRC=y CONFIG_PCIEAER_INJECT=m CONFIG_PCIEASPM=y # CONFIG_PCIEASPM_DEBUG is not set CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y CONFIG_PCI_MSI_DEFAULT_ON=y CONFIG_PCI_LEGACY=y # CONFIG_PCI_DEBUG is not set CONFIG_PCI_STUB=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_HT_IRQ=y CONFIG_PCI_IOV=y CONFIG_ISA_DMA_API=y CONFIG_K8_NB=y CONFIG_PCCARD=y # CONFIG_PCMCIA_DEBUG is not set CONFIG_PCMCIA=y CONFIG_PCMCIA_LOAD_CIS=y CONFIG_PCMCIA_IOCTL=y CONFIG_CARDBUS=y # # PC-card bridges # CONFIG_YENTA=m CONFIG_YENTA_O2=y CONFIG_YENTA_RICOH=y CONFIG_YENTA_TI=y CONFIG_YENTA_ENE_TUNE=y CONFIG_YENTA_TOSHIBA=y CONFIG_PD6729=m CONFIG_I82092=m CONFIG_PCCARD_NONSTATIC=m CONFIG_HOTPLUG_PCI=y CONFIG_HOTPLUG_PCI_FAKE=m CONFIG_HOTPLUG_PCI_ACPI=y CONFIG_HOTPLUG_PCI_ACPI_IBM=m # CONFIG_HOTPLUG_PCI_CPCI is not set CONFIG_HOTPLUG_PCI_SHPC=m # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y # CONFIG_HAVE_AOUT is not set CONFIG_BINFMT_MISC=y CONFIG_IA32_EMULATION=y # CONFIG_IA32_AOUT is not set CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=y CONFIG_XFRM_SUB_POLICY=y CONFIG_XFRM_MIGRATE=y CONFIG_XFRM_STATISTICS=y CONFIG_XFRM_IPCOMP=m CONFIG_NET_KEY=m CONFIG_NET_KEY_MIGRATE=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y # CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_VERBOSE=y # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m CONFIG_NET_IPGRE_BROADCAST=y CONFIG_IP_MROUTE=y CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y CONFIG_ARPD=y CONFIG_SYN_COOKIES=y CONFIG_INET_AH=m CONFIG_INET_ESP=m CONFIG_INET_IPCOMP=m CONFIG_INET_XFRM_TUNNEL=m CONFIG_INET_TUNNEL=m CONFIG_INET_XFRM_MODE_TRANSPORT=m CONFIG_INET_XFRM_MODE_TUNNEL=m CONFIG_INET_XFRM_MODE_BEET=m CONFIG_INET_LRO=y CONFIG_INET_DIAG=m CONFIG_INET_TCP_DIAG=m CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=y CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m CONFIG_TCP_CONG_HYBLA=m CONFIG_TCP_CONG_VEGAS=m CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=m CONFIG_TCP_CONG_VENO=m CONFIG_TCP_CONG_YEAH=m CONFIG_TCP_CONG_ILLINOIS=m # CONFIG_DEFAULT_BIC is not set CONFIG_DEFAULT_CUBIC=y # CONFIG_DEFAULT_HTCP is not set # CONFIG_DEFAULT_VEGAS is not set # CONFIG_DEFAULT_WESTWOOD is not set # CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" CONFIG_TCP_MD5SIG=y CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y CONFIG_IPV6_OPTIMISTIC_DAD=y CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m CONFIG_IPV6_MIP6=m CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_IPV6_SUBTREES=y CONFIG_IPV6_MROUTE=y CONFIG_IPV6_PIMSM_V2=y CONFIG_NETLABEL=y CONFIG_NETWORK_SECMARK=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y CONFIG_BRIDGE_NETFILTER=y # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=m CONFIG_NETFILTER_NETLINK_QUEUE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NF_CONNTRACK=y CONFIG_NF_CT_ACCT=y CONFIG_NF_CONNTRACK_MARK=y CONFIG_NF_CONNTRACK_SECMARK=y CONFIG_NF_CONNTRACK_EVENTS=y CONFIG_NF_CT_PROTO_DCCP=m CONFIG_NF_CT_PROTO_GRE=m CONFIG_NF_CT_PROTO_SCTP=m CONFIG_NF_CT_PROTO_UDPLITE=m CONFIG_NF_CONNTRACK_AMANDA=m CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m CONFIG_NF_CONNTRACK_PPTP=m CONFIG_NF_CONNTRACK_SANE=m CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m CONFIG_NF_CT_NETLINK=m CONFIG_NETFILTER_TPROXY=m CONFIG_NETFILTER_XTABLES=y CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m CONFIG_NETFILTER_XT_TARGET_CONNMARK=m CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m CONFIG_NETFILTER_XT_TARGET_DSCP=m CONFIG_NETFILTER_XT_TARGET_HL=m CONFIG_NETFILTER_XT_TARGET_LED=m CONFIG_NETFILTER_XT_TARGET_IMQ=m CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m CONFIG_NETFILTER_XT_TARGET_NOTRACK=m CONFIG_NETFILTER_XT_TARGET_RATEEST=m CONFIG_NETFILTER_XT_TARGET_TPROXY=m CONFIG_NETFILTER_XT_TARGET_TRACE=m CONFIG_NETFILTER_XT_TARGET_SECMARK=m CONFIG_NETFILTER_XT_TARGET_TCPMSS=m CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m CONFIG_NETFILTER_XT_MATCH_CLUSTER=m CONFIG_NETFILTER_XT_MATCH_COMMENT=m CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ESP=m CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_HL=m CONFIG_NETFILTER_XT_MATCH_IPRANGE=m CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m CONFIG_NETFILTER_XT_MATCH_MARK=m CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m CONFIG_NETFILTER_XT_MATCH_OWNER=m CONFIG_NETFILTER_XT_MATCH_POLICY=m CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m CONFIG_NETFILTER_XT_MATCH_QUOTA=m CONFIG_NETFILTER_XT_MATCH_RATEEST=m CONFIG_NETFILTER_XT_MATCH_REALM=m CONFIG_NETFILTER_XT_MATCH_RECENT=m # CONFIG_NETFILTER_XT_MATCH_RECENT_PROC_COMPAT is not set CONFIG_NETFILTER_XT_MATCH_SCTP=m CONFIG_NETFILTER_XT_MATCH_SOCKET=m CONFIG_NETFILTER_XT_MATCH_STATE=y CONFIG_NETFILTER_XT_MATCH_STATISTIC=m CONFIG_NETFILTER_XT_MATCH_STRING=m CONFIG_NETFILTER_XT_MATCH_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_TIME=m CONFIG_NETFILTER_XT_MATCH_U32=m CONFIG_NETFILTER_XT_MATCH_OSF=m CONFIG_IP_VS=m # CONFIG_IP_VS_IPV6 is not set # CONFIG_IP_VS_DEBUG is not set CONFIG_IP_VS_TAB_BITS=12 # # IPVS transport protocol load balancing support # CONFIG_IP_VS_PROTO_TCP=y CONFIG_IP_VS_PROTO_UDP=y CONFIG_IP_VS_PROTO_AH_ESP=y CONFIG_IP_VS_PROTO_ESP=y CONFIG_IP_VS_PROTO_AH=y # # IPVS scheduler # CONFIG_IP_VS_RR=m CONFIG_IP_VS_WRR=m CONFIG_IP_VS_LC=m CONFIG_IP_VS_WLC=m CONFIG_IP_VS_LBLC=m CONFIG_IP_VS_LBLCR=m CONFIG_IP_VS_DH=m CONFIG_IP_VS_SH=m CONFIG_IP_VS_SED=m CONFIG_IP_VS_NQ=m # # IPVS application helper # CONFIG_IP_VS_FTP=m # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=y CONFIG_NF_CONNTRACK_IPV4=y # CONFIG_NF_CONNTRACK_PROC_COMPAT is not set CONFIG_IP_NF_QUEUE=m CONFIG_IP_NF_IPTABLES=y CONFIG_IP_NF_MATCH_ADDRTYPE=m CONFIG_IP_NF_MATCH_AH=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_TARGET_LOG=m CONFIG_IP_NF_TARGET_ULOG=m CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_DCCP=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_PROTO_UDPLITE=m CONFIG_NF_NAT_PROTO_SCTP=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_CLUSTERIP=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_TTL=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_SECURITY=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration # CONFIG_NF_CONNTRACK_IPV6=m CONFIG_IP6_NF_QUEUE=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_RAW=m CONFIG_IP6_NF_SECURITY=m # # DECnet: Netfilter Configuration # # CONFIG_DECNET_NF_GRABULATOR is not set CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_ULOG=m CONFIG_BRIDGE_EBT_NFLOG=m CONFIG_IP_DCCP=m CONFIG_INET_DCCP_DIAG=m # # DCCP CCIDs Configuration (EXPERIMENTAL) # # CONFIG_IP_DCCP_CCID2_DEBUG is not set CONFIG_IP_DCCP_CCID3=y # CONFIG_IP_DCCP_CCID3_DEBUG is not set CONFIG_IP_DCCP_CCID3_RTO=100 CONFIG_IP_DCCP_TFRC_LIB=y # # DCCP Kernel Hacking # # CONFIG_IP_DCCP_DEBUG is not set CONFIG_NET_DCCPPROBE=m CONFIG_IP_SCTP=m # CONFIG_SCTP_DBG_MSG is not set # CONFIG_SCTP_DBG_OBJCNT is not set # CONFIG_SCTP_HMAC_NONE is not set CONFIG_SCTP_HMAC_SHA1=y # CONFIG_SCTP_HMAC_MD5 is not set CONFIG_RDS=m # CONFIG_RDS_DEBUG is not set CONFIG_TIPC=m # CONFIG_TIPC_ADVANCED is not set # CONFIG_TIPC_DEBUG is not set CONFIG_ATM=m CONFIG_ATM_CLIP=m # CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m # CONFIG_ATM_MPOA is not set CONFIG_ATM_BR2684=m # CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_STP=m CONFIG_GARP=m CONFIG_BRIDGE=m CONFIG_NET_DSA=y CONFIG_NET_DSA_TAG_DSA=y CONFIG_NET_DSA_TAG_EDSA=y CONFIG_NET_DSA_TAG_TRAILER=y CONFIG_NET_DSA_MV88E6XXX=y CONFIG_NET_DSA_MV88E6060=y CONFIG_NET_DSA_MV88E6XXX_NEED_PPU=y CONFIG_NET_DSA_MV88E6131=y CONFIG_NET_DSA_MV88E6123_61_65=y CONFIG_VLAN_8021Q=m CONFIG_VLAN_8021Q_GVRP=y CONFIG_DECNET=m CONFIG_DECNET_ROUTER=y CONFIG_LLC=m # CONFIG_LLC2 is not set CONFIG_IPX=m # CONFIG_IPX_INTERN is not set CONFIG_ATALK=m CONFIG_DEV_APPLETALK=m CONFIG_IPDDP=m CONFIG_IPDDP_ENCAP=y CONFIG_IPDDP_DECAP=y # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_ECONET is not set CONFIG_WAN_ROUTER=m CONFIG_PHONET=m CONFIG_IEEE802154=m CONFIG_NET_SCHED=y # # Queueing/Scheduling # CONFIG_NET_SCH_CBQ=m CONFIG_NET_SCH_HTB=m CONFIG_NET_SCH_HFSC=m CONFIG_NET_SCH_ATM=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_MULTIQ=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m CONFIG_NET_SCH_NETEM=m CONFIG_NET_SCH_DRR=m CONFIG_NET_SCH_INGRESS=m # # Classification # CONFIG_NET_CLS=y CONFIG_NET_CLS_BASIC=m CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m CONFIG_CLS_U32_PERF=y CONFIG_CLS_U32_MARK=y CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m CONFIG_NET_CLS_FLOW=m CONFIG_NET_CLS_CGROUP=y CONFIG_NET_EMATCH=y CONFIG_NET_EMATCH_STACK=32 CONFIG_NET_EMATCH_CMP=m CONFIG_NET_EMATCH_NBYTE=m CONFIG_NET_EMATCH_U32=m CONFIG_NET_EMATCH_META=m CONFIG_NET_EMATCH_TEXT=m CONFIG_NET_CLS_ACT=y CONFIG_NET_ACT_POLICE=m CONFIG_NET_ACT_GACT=m CONFIG_GACT_PROB=y CONFIG_NET_ACT_MIRRED=m CONFIG_NET_ACT_IPT=m CONFIG_NET_ACT_NAT=m CONFIG_NET_ACT_PEDIT=m CONFIG_NET_ACT_SIMP=m CONFIG_NET_ACT_SKBEDIT=m CONFIG_NET_CLS_IND=y CONFIG_NET_SCH_FIFO=y CONFIG_DCB=y # # Network testing # CONFIG_NET_PKTGEN=m # CONFIG_NET_TCPPROBE is not set CONFIG_NET_DROP_MONITOR=y CONFIG_HAMRADIO=y # # Packet Radio protocols # CONFIG_AX25=m CONFIG_AX25_DAMA_SLAVE=y CONFIG_NETROM=m CONFIG_ROSE=m # # AX.25 network device drivers # CONFIG_MKISS=m CONFIG_6PACK=m CONFIG_BPQETHER=m CONFIG_BAYCOM_SER_FDX=m CONFIG_BAYCOM_SER_HDX=m CONFIG_BAYCOM_PAR=m CONFIG_YAM=m CONFIG_CAN=m CONFIG_CAN_RAW=m CONFIG_CAN_BCM=m # # CAN Device Drivers # CONFIG_CAN_VCAN=m CONFIG_CAN_DEV=m CONFIG_CAN_CALC_BITTIMING=y CONFIG_CAN_SJA1000=m CONFIG_CAN_SJA1000_PLATFORM=m CONFIG_CAN_EMS_PCI=m CONFIG_CAN_KVASER_PCI=m # CONFIG_CAN_DEBUG_DEVICES is not set CONFIG_IRDA=m # # IrDA protocols # CONFIG_IRLAN=m CONFIG_IRNET=m CONFIG_IRCOMM=m # CONFIG_IRDA_ULTRA is not set # # IrDA options # CONFIG_IRDA_CACHE_LAST_LSAP=y CONFIG_IRDA_FAST_RR=y # CONFIG_IRDA_DEBUG is not set # # Infrared-port device drivers # # # SIR device drivers # CONFIG_IRTTY_SIR=m # # Dongle support # CONFIG_DONGLE=y CONFIG_ESI_DONGLE=m CONFIG_ACTISYS_DONGLE=m CONFIG_TEKRAM_DONGLE=m CONFIG_TOIM3232_DONGLE=m CONFIG_LITELINK_DONGLE=m CONFIG_MA600_DONGLE=m CONFIG_GIRBIL_DONGLE=m CONFIG_MCP2120_DONGLE=m CONFIG_OLD_BELKIN_DONGLE=m CONFIG_ACT200L_DONGLE=m CONFIG_KINGSUN_DONGLE=m CONFIG_KSDAZZLE_DONGLE=m CONFIG_KS959_DONGLE=m # # FIR device drivers # CONFIG_USB_IRDA=m CONFIG_SIGMATEL_FIR=m CONFIG_NSC_FIR=m CONFIG_WINBOND_FIR=m CONFIG_SMC_IRCC_FIR=m CONFIG_ALI_FIR=m CONFIG_VLSI_FIR=m CONFIG_VIA_FIR=m CONFIG_MCS_FIR=m CONFIG_BT=m CONFIG_BT_L2CAP=m CONFIG_BT_SCO=m CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=m CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y CONFIG_BT_CMTP=m CONFIG_BT_HIDP=m # # Bluetooth device drivers # CONFIG_BT_HCIBTUSB=m CONFIG_BT_HCIBTSDIO=m CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y CONFIG_BT_HCIUART_LL=y CONFIG_BT_HCIBCM203X=m CONFIG_BT_HCIBPA10X=m CONFIG_BT_HCIBFUSB=m CONFIG_BT_HCIDTL1=m CONFIG_BT_HCIBT3C=m CONFIG_BT_HCIBLUECARD=m CONFIG_BT_HCIBTUART=m CONFIG_BT_HCIVHCI=m # CONFIG_AF_RXRPC is not set CONFIG_FIB_RULES=y CONFIG_WIRELESS=y CONFIG_CFG80211=m # CONFIG_CFG80211_REG_DEBUG is not set CONFIG_CFG80211_DEBUGFS=y # CONFIG_WIRELESS_OLD_REGULATORY is not set CONFIG_WIRELESS_EXT=y CONFIG_WIRELESS_EXT_SYSFS=y CONFIG_LIB80211=m CONFIG_LIB80211_CRYPT_WEP=m CONFIG_LIB80211_CRYPT_CCMP=m CONFIG_LIB80211_CRYPT_TKIP=m # CONFIG_LIB80211_DEBUG is not set CONFIG_MAC80211=m CONFIG_MAC80211_DEFAULT_PS=y CONFIG_MAC80211_DEFAULT_PS_VALUE=1 # # Rate control algorithm selection # CONFIG_MAC80211_RC_MINSTREL=y # CONFIG_MAC80211_RC_DEFAULT_PID is not set CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT="minstrel" CONFIG_MAC80211_LEDS=y CONFIG_MAC80211_DEBUGFS=y # CONFIG_MAC80211_DEBUG_MENU is not set CONFIG_WIMAX=m CONFIG_WIMAX_DEBUG_LEVEL=8 CONFIG_RFKILL=m CONFIG_RFKILL_LEDS=y CONFIG_RFKILL_INPUT=y CONFIG_NET_9P=m CONFIG_NET_9P_VIRTIO=m CONFIG_NET_9P_RDMA=m # CONFIG_NET_9P_DEBUG is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="" CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y # CONFIG_FIRMWARE_IN_KERNEL is not set CONFIG_EXTRA_FIRMWARE="" # CONFIG_DEBUG_DRIVER is not set CONFIG_DEBUG_DEVRES=y CONFIG_SYS_HYPERVISOR=y CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y CONFIG_MTD=m # CONFIG_MTD_DEBUG is not set CONFIG_MTD_CONCAT=m CONFIG_MTD_PARTITIONS=y # CONFIG_MTD_TESTS is not set CONFIG_MTD_REDBOOT_PARTS=m CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1 # CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set # CONFIG_MTD_REDBOOT_PARTS_READONLY is not set CONFIG_MTD_AR7_PARTS=m # # User Modules And Translation Layers # CONFIG_MTD_CHAR=m CONFIG_MTD_BLKDEVS=m CONFIG_MTD_BLOCK=m CONFIG_MTD_BLOCK_RO=m CONFIG_FTL=m CONFIG_NFTL=m CONFIG_NFTL_RW=y CONFIG_INFTL=m CONFIG_RFD_FTL=m CONFIG_SSFDC=m CONFIG_MTD_OOPS=m # # RAM/ROM/Flash chip drivers # CONFIG_MTD_CFI=m CONFIG_MTD_JEDECPROBE=m CONFIG_MTD_GEN_PROBE=m # CONFIG_MTD_CFI_ADV_OPTIONS is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_CFI_I4 is not set # CONFIG_MTD_CFI_I8 is not set CONFIG_MTD_CFI_INTELEXT=m CONFIG_MTD_CFI_AMDSTD=m CONFIG_MTD_CFI_STAA=m CONFIG_MTD_CFI_UTIL=m CONFIG_MTD_RAM=m CONFIG_MTD_ROM=m CONFIG_MTD_ABSENT=m # # Mapping drivers for chip access # CONFIG_MTD_COMPLEX_MAPPINGS=y # CONFIG_MTD_PHYSMAP is not set CONFIG_MTD_SC520CDP=m CONFIG_MTD_NETSC520=m CONFIG_MTD_TS5500=m # CONFIG_MTD_SBC_GXX is not set # CONFIG_MTD_AMD76XROM is not set # CONFIG_MTD_ICHXROM is not set CONFIG_MTD_ESB2ROM=m CONFIG_MTD_CK804XROM=m CONFIG_MTD_SCB2_FLASH=m # CONFIG_MTD_NETtel is not set # CONFIG_MTD_L440GX is not set CONFIG_MTD_PCI=m # CONFIG_MTD_INTEL_VR_NOR is not set # CONFIG_MTD_PLATRAM is not set # # Self-contained MTD device drivers # CONFIG_MTD_PMC551=m # CONFIG_MTD_PMC551_BUGFIX is not set # CONFIG_MTD_PMC551_DEBUG is not set # CONFIG_MTD_SLRAM is not set # CONFIG_MTD_PHRAM is not set CONFIG_MTD_MTDRAM=m CONFIG_MTDRAM_TOTAL_SIZE=4096 CONFIG_MTDRAM_ERASE_SIZE=128 CONFIG_MTD_BLOCK2MTD=m # # Disk-On-Chip Device Drivers # # CONFIG_MTD_DOC2000 is not set # CONFIG_MTD_DOC2001 is not set # CONFIG_MTD_DOC2001PLUS is not set CONFIG_MTD_NAND=m # CONFIG_MTD_NAND_VERIFY_WRITE is not set CONFIG_MTD_NAND_ECC_SMC=y # CONFIG_MTD_NAND_MUSEUM_IDS is not set CONFIG_MTD_NAND_IDS=m CONFIG_MTD_NAND_DISKONCHIP=m # CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0 # CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set # CONFIG_MTD_NAND_CAFE is not set CONFIG_MTD_NAND_NANDSIM=m # CONFIG_MTD_NAND_PLATFORM is not set CONFIG_MTD_ALAUDA=m # CONFIG_MTD_ONENAND is not set # # LPDDR flash memory drivers # CONFIG_MTD_LPDDR=m CONFIG_MTD_QINFO_PROBE=m # # UBI - Unsorted block images # CONFIG_MTD_UBI=m CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_RESERVE=1 # CONFIG_MTD_UBI_GLUEBI is not set # # UBI debugging options # # CONFIG_MTD_UBI_DEBUG is not set CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_SERIAL=m # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set CONFIG_PARPORT_PC_PCMCIA=m # CONFIG_PARPORT_GSC is not set # CONFIG_PARPORT_AX88796 is not set CONFIG_PARPORT_1284=y CONFIG_PARPORT_NOT_PC=y CONFIG_PNP=y # CONFIG_PNP_DEBUG_MESSAGES is not set # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y CONFIG_BLK_DEV_FD=m CONFIG_PARIDE=m # # Parallel IDE high-level drivers # CONFIG_PARIDE_PD=m CONFIG_PARIDE_PCD=m CONFIG_PARIDE_PF=m CONFIG_PARIDE_PT=m CONFIG_PARIDE_PG=m # # Parallel IDE protocol modules # CONFIG_PARIDE_ATEN=m CONFIG_PARIDE_BPCK=m CONFIG_PARIDE_COMM=m CONFIG_PARIDE_DSTR=m CONFIG_PARIDE_FIT2=m CONFIG_PARIDE_FIT3=m CONFIG_PARIDE_EPAT=m CONFIG_PARIDE_EPATC8=y CONFIG_PARIDE_EPIA=m CONFIG_PARIDE_FRIQ=m CONFIG_PARIDE_FRPW=m CONFIG_PARIDE_KBIC=m CONFIG_PARIDE_KTTI=m CONFIG_PARIDE_ON20=m CONFIG_PARIDE_ON26=m CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m CONFIG_CISS_SCSI_TAPE=y CONFIG_BLK_DEV_DAC960=m CONFIG_BLK_DEV_UMEM=m # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_OSD=m CONFIG_BLK_DEV_SX8=m # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=16384 # CONFIG_BLK_DEV_XIP is not set CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set CONFIG_ATA_OVER_ETH=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_VIRTIO_BLK=m # CONFIG_BLK_DEV_HD is not set CONFIG_MISC_DEVICES=y # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not set CONFIG_SGI_IOC4=m CONFIG_TIFM_CORE=m CONFIG_TIFM_7XX1=m CONFIG_ICS932S401=m CONFIG_ENCLOSURE_SERVICES=m # CONFIG_HP_ILO is not set CONFIG_DELL_LAPTOP=m CONFIG_ISL29003=m # CONFIG_C2PORT is not set # # EEPROM support # CONFIG_EEPROM_AT24=m CONFIG_EEPROM_LEGACY=m CONFIG_EEPROM_MAX6875=m CONFIG_EEPROM_93CX6=m CONFIG_CB710_CORE=m # CONFIG_CB710_DEBUG is not set CONFIG_CB710_DEBUG_ASSUMPTIONS=y CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # CONFIG_RAID_ATTRS=m CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_TGT=m CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=y CONFIG_CHR_DEV_SCH=m CONFIG_SCSI_ENCLOSURE=m CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_SCAN_ASYNC=y CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=m CONFIG_SCSI_FC_ATTRS=m CONFIG_SCSI_FC_TGT_ATTRS=y CONFIG_SCSI_ISCSI_ATTRS=m CONFIG_SCSI_SAS_ATTRS=m CONFIG_SCSI_SAS_LIBSAS=m CONFIG_SCSI_SAS_ATA=y CONFIG_SCSI_SAS_HOST_SMP=y # CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set CONFIG_SCSI_SRP_ATTRS=m CONFIG_SCSI_SRP_TGT_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_ISCSI_TCP=m CONFIG_SCSI_CXGB3_ISCSI=m CONFIG_SCSI_BNX2_ISCSI=m CONFIG_BLK_DEV_3W_XXXX_RAID=m CONFIG_SCSI_3W_9XXX=m CONFIG_SCSI_ACARD=m CONFIG_SCSI_AACRAID=m CONFIG_SCSI_AIC7XXX=m CONFIG_AIC7XXX_CMDS_PER_DEVICE=4 CONFIG_AIC7XXX_RESET_DELAY_MS=15000 # CONFIG_AIC7XXX_DEBUG_ENABLE is not set CONFIG_AIC7XXX_DEBUG_MASK=0 # CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set CONFIG_SCSI_AIC7XXX_OLD=m CONFIG_SCSI_AIC79XX=m CONFIG_AIC79XX_CMDS_PER_DEVICE=4 CONFIG_AIC79XX_RESET_DELAY_MS=15000 # CONFIG_AIC79XX_DEBUG_ENABLE is not set CONFIG_AIC79XX_DEBUG_MASK=0 # CONFIG_AIC79XX_REG_PRETTY_PRINT is not set CONFIG_SCSI_AIC94XX=m # CONFIG_AIC94XX_DEBUG is not set CONFIG_SCSI_MVSAS=m # CONFIG_SCSI_MVSAS_DEBUG is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set CONFIG_SCSI_ARCMSR=m CONFIG_SCSI_ARCMSR_AER=y CONFIG_MEGARAID_NEWGEN=y CONFIG_MEGARAID_MM=m CONFIG_MEGARAID_MAILBOX=m CONFIG_MEGARAID_LEGACY=m CONFIG_MEGARAID_SAS=m CONFIG_SCSI_MPT2SAS=m CONFIG_SCSI_MPT2SAS_MAX_SGE=128 CONFIG_SCSI_MPT2SAS_LOGGING=y CONFIG_SCSI_HPTIOP=m CONFIG_SCSI_BUSLOGIC=m CONFIG_LIBFC=m CONFIG_LIBFCOE=m CONFIG_FCOE=m CONFIG_FCOE_FNIC=m # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set CONFIG_SCSI_GDTH=m CONFIG_SCSI_IPS=m CONFIG_SCSI_INITIO=m CONFIG_SCSI_INIA100=m CONFIG_SCSI_PPA=m CONFIG_SCSI_IMM=m # CONFIG_SCSI_IZIP_EPP16 is not set # CONFIG_SCSI_IZIP_SLOW_CTR is not set CONFIG_SCSI_STEX=m CONFIG_SCSI_SYM53C8XX_2=m CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 CONFIG_SCSI_SYM53C8XX_MMIO=y # CONFIG_SCSI_IPR is not set CONFIG_SCSI_QLOGIC_1280=m CONFIG_SCSI_QLA_FC=m CONFIG_SCSI_QLA_ISCSI=m CONFIG_SCSI_LPFC=m # CONFIG_SCSI_LPFC_DEBUG_FS is not set CONFIG_SCSI_DC395x=m CONFIG_SCSI_DC390T=m CONFIG_SCSI_DEBUG=m CONFIG_SCSI_SRP=m CONFIG_SCSI_LOWLEVEL_PCMCIA=y # CONFIG_PCMCIA_FDOMAIN is not set CONFIG_PCMCIA_QLOGIC=m CONFIG_PCMCIA_SYM53C500=m CONFIG_SCSI_DH=y CONFIG_SCSI_DH_RDAC=m CONFIG_SCSI_DH_HP_SW=m CONFIG_SCSI_DH_EMC=m CONFIG_SCSI_DH_ALUA=m CONFIG_SCSI_OSD_INITIATOR=m CONFIG_SCSI_OSD_ULD=m CONFIG_SCSI_OSD_DPRINT_SENSE=1 # CONFIG_SCSI_OSD_DEBUG is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y CONFIG_SATA_PMP=y CONFIG_SATA_AHCI=y CONFIG_SATA_SIL24=m CONFIG_ATA_SFF=y CONFIG_SATA_SVW=m CONFIG_ATA_PIIX=y CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_PDC_ADMA=m CONFIG_SATA_QSTOR=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SX4=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m CONFIG_SATA_INIC162X=m CONFIG_PATA_ACPI=m CONFIG_PATA_ALI=m CONFIG_PATA_AMD=m CONFIG_PATA_ARTOP=m CONFIG_PATA_ATIIXP=m CONFIG_PATA_CMD640_PCI=m CONFIG_PATA_CMD64X=m CONFIG_PATA_CS5520=m CONFIG_PATA_CS5530=m CONFIG_PATA_CYPRESS=m CONFIG_PATA_EFAR=m CONFIG_ATA_GENERIC=m CONFIG_PATA_HPT366=m CONFIG_PATA_HPT37X=m CONFIG_PATA_HPT3X2N=m CONFIG_PATA_HPT3X3=m # CONFIG_PATA_HPT3X3_DMA is not set CONFIG_PATA_IT821X=m CONFIG_PATA_IT8213=m CONFIG_PATA_JMICRON=m CONFIG_PATA_TRIFLEX=m CONFIG_PATA_MARVELL=m CONFIG_PATA_MPIIX=m CONFIG_PATA_OLDPIIX=m CONFIG_PATA_NETCELL=m CONFIG_PATA_NINJA32=m CONFIG_PATA_NS87410=m CONFIG_PATA_NS87415=m CONFIG_PATA_OPTI=m CONFIG_PATA_OPTIDMA=m CONFIG_PATA_PCMCIA=m CONFIG_PATA_PDC_OLD=m # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set CONFIG_PATA_SERVERWORKS=m CONFIG_PATA_PDC2027X=m CONFIG_PATA_SIL680=m CONFIG_PATA_SIS=m CONFIG_PATA_VIA=m CONFIG_PATA_WINBOND=m CONFIG_PATA_SCH=m CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_AUTODETECT=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m CONFIG_MD_RAID6_PQ=m CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m CONFIG_BLK_DEV_DM=y CONFIG_DM_DEBUG=y CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=y CONFIG_DM_MIRROR=y CONFIG_DM_LOG_USERSPACE=m CONFIG_DM_ZERO=y CONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=m # CONFIG_DM_DELAY is not set CONFIG_DM_UEVENT=y CONFIG_FUSION=y CONFIG_FUSION_SPI=m CONFIG_FUSION_FC=m CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=40 CONFIG_FUSION_CTL=m CONFIG_FUSION_LAN=m CONFIG_FUSION_LOGGING=y # # IEEE 1394 (FireWire) support # # # You can enable one or both FireWire driver stacks. # # # See the help texts for more information. # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_OHCI_DEBUG=y CONFIG_FIREWIRE_SBP2=m CONFIG_FIREWIRE_NET=m # CONFIG_IEEE1394 is not set CONFIG_I2O=m # CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set CONFIG_I2O_EXT_ADAPTEC=y CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_I2O_CONFIG=m CONFIG_I2O_CONFIG_OLD_IOCTL=y CONFIG_I2O_BUS=m CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m CONFIG_MACINTOSH_DRIVERS=y CONFIG_MAC_EMUMOUSEBTN=y CONFIG_NETDEVICES=y CONFIG_IFB=m CONFIG_DUMMY=m CONFIG_BONDING=m CONFIG_MACVLAN=m CONFIG_EQUALIZER=m CONFIG_IMQ=m # CONFIG_IMQ_BEHAVIOR_AA is not set CONFIG_IMQ_BEHAVIOR_AB=y # CONFIG_IMQ_BEHAVIOR_BA is not set # CONFIG_IMQ_BEHAVIOR_BB is not set CONFIG_IMQ_NUM_DEVS=16 CONFIG_TUN=m CONFIG_VETH=m CONFIG_NET_SB1000=m # CONFIG_ARCNET is not set CONFIG_PHYLIB=y # # MII PHY device drivers # CONFIG_MARVELL_PHY=m CONFIG_DAVICOM_PHY=m CONFIG_QSEMI_PHY=m CONFIG_LXT_PHY=m CONFIG_CICADA_PHY=m CONFIG_VITESSE_PHY=m CONFIG_SMSC_PHY=m CONFIG_BROADCOM_PHY=m CONFIG_ICPLUS_PHY=m CONFIG_REALTEK_PHY=m CONFIG_NATIONAL_PHY=m CONFIG_STE10XP=m CONFIG_LSI_ET1011C_PHY=m CONFIG_FIXED_PHY=y CONFIG_MDIO_BITBANG=m CONFIG_NET_ETHERNET=y CONFIG_MII=m CONFIG_HAPPYMEAL=m CONFIG_SUNGEM=m CONFIG_CASSINI=m CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=m CONFIG_TYPHOON=m CONFIG_ETHOC=m CONFIG_DNET=m CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_DE2104X_DSL=0 CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set CONFIG_TULIP_MMIO=y # CONFIG_TULIP_NAPI is not set CONFIG_DE4X5=m CONFIG_WINBOND_840=m CONFIG_DM9102=m CONFIG_ULI526X=m CONFIG_PCMCIA_XIRCOM=m # CONFIG_HP100 is not set # CONFIG_IBM_NEW_EMAC_ZMII is not set # CONFIG_IBM_NEW_EMAC_RGMII is not set # CONFIG_IBM_NEW_EMAC_TAH is not set # CONFIG_IBM_NEW_EMAC_EMAC4 is not set # CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=y CONFIG_PCNET32=m CONFIG_AMD8111_ETH=m CONFIG_ADAPTEC_STARFIRE=m CONFIG_B44=m CONFIG_B44_PCI_AUTOSELECT=y CONFIG_B44_PCICORE_AUTOSELECT=y CONFIG_B44_PCI=y CONFIG_FORCEDETH=m CONFIG_FORCEDETH_NAPI=y CONFIG_E100=m CONFIG_FEALNX=m CONFIG_NATSEMI=m CONFIG_NE2K_PCI=m CONFIG_8139CP=m CONFIG_8139TOO=m # CONFIG_8139TOO_PIO is not set # CONFIG_8139TOO_TUNE_TWISTER is not set CONFIG_8139TOO_8129=y # CONFIG_8139_OLD_RX_RESET is not set CONFIG_R6040=m CONFIG_SIS900=m CONFIG_EPIC100=m CONFIG_SMSC9420=m CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set CONFIG_TLAN=m # CONFIG_KS8842 is not set CONFIG_VIA_RHINE=m CONFIG_VIA_RHINE_MMIO=y CONFIG_SC92031=m CONFIG_NET_POCKET=y CONFIG_ATP=m CONFIG_DE600=m CONFIG_DE620=m CONFIG_ATL2=m CONFIG_NETDEV_1000=y CONFIG_ACENIC=m # CONFIG_ACENIC_OMIT_TIGON_I is not set CONFIG_DL2K=m CONFIG_E1000=m CONFIG_E1000E=m CONFIG_IP1000=m CONFIG_IGB=m CONFIG_IGB_DCA=y CONFIG_IGBVF=m CONFIG_NS83820=m CONFIG_HAMACHI=m CONFIG_YELLOWFIN=m CONFIG_R8169=m CONFIG_R8169_VLAN=y CONFIG_SIS190=m CONFIG_SKGE=m # CONFIG_SKGE_DEBUG is not set CONFIG_SKY2=m # CONFIG_SKY2_DEBUG is not set CONFIG_VIA_VELOCITY=m CONFIG_TIGON3=m CONFIG_BNX2=m CONFIG_CNIC=m CONFIG_QLA3XXX=m CONFIG_ATL1=m CONFIG_ATL1E=m CONFIG_ATL1C=m CONFIG_JME=m CONFIG_NETDEV_10000=y CONFIG_MDIO=m CONFIG_CHELSIO_T1=m CONFIG_CHELSIO_T1_1G=y CONFIG_CHELSIO_T3_DEPENDS=y CONFIG_CHELSIO_T3=m CONFIG_ENIC=m CONFIG_IXGBE=m CONFIG_IXGBE_DCA=y CONFIG_IXGBE_DCB=y CONFIG_IXGB=m CONFIG_S2IO=m CONFIG_VXGE=m # CONFIG_VXGE_DEBUG_TRACE_ALL is not set CONFIG_MYRI10GE=m CONFIG_MYRI10GE_DCA=y CONFIG_NETXEN_NIC=m CONFIG_NIU=m CONFIG_MLX4_EN=m CONFIG_MLX4_CORE=m CONFIG_MLX4_DEBUG=y CONFIG_TEHUTI=m CONFIG_BNX2X=m CONFIG_QLGE=m CONFIG_SFC=m CONFIG_SFC_MTD=y CONFIG_BE2NET=m # CONFIG_TR is not set # # Wireless LAN # # CONFIG_WLAN_PRE80211 is not set CONFIG_WLAN_80211=y # CONFIG_PCMCIA_RAYCS is not set CONFIG_LIBERTAS=m CONFIG_LIBERTAS_USB=m CONFIG_LIBERTAS_CS=m CONFIG_LIBERTAS_SDIO=m CONFIG_LIBERTAS_DEBUG=y CONFIG_LIBERTAS_THINFIRM=m CONFIG_LIBERTAS_THINFIRM_USB=m CONFIG_AIRO=m CONFIG_ATMEL=m CONFIG_PCI_ATMEL=m CONFIG_PCMCIA_ATMEL=m CONFIG_AT76C50X_USB=m CONFIG_AIRO_CS=m CONFIG_PCMCIA_WL3501=m CONFIG_PRISM54=m CONFIG_USB_ZD1201=m CONFIG_USB_NET_RNDIS_WLAN=m CONFIG_RTL8180=m CONFIG_RTL8187=m CONFIG_RTL8187_LEDS=y CONFIG_ADM8211=m CONFIG_MAC80211_HWSIM=m CONFIG_MWL8K=m CONFIG_P54_COMMON=m CONFIG_P54_USB=m CONFIG_P54_PCI=m CONFIG_P54_LEDS=y CONFIG_ATH_COMMON=m CONFIG_ATH5K=m CONFIG_ATH5K_DEBUG=y CONFIG_ATH9K=m # CONFIG_ATH9K_DEBUG is not set CONFIG_AR9170_USB=m CONFIG_AR9170_LEDS=y CONFIG_IPW2100=m CONFIG_IPW2100_MONITOR=y # CONFIG_IPW2100_DEBUG is not set CONFIG_IPW2200=m CONFIG_IPW2200_MONITOR=y CONFIG_IPW2200_RADIOTAP=y CONFIG_IPW2200_PROMISCUOUS=y CONFIG_IPW2200_QOS=y # CONFIG_IPW2200_DEBUG is not set CONFIG_LIBIPW=m # CONFIG_LIBIPW_DEBUG is not set CONFIG_IWLWIFI=m CONFIG_IWLWIFI_LEDS=y CONFIG_IWLWIFI_SPECTRUM_MEASUREMENT=y CONFIG_IWLWIFI_DEBUG=y CONFIG_IWLWIFI_DEBUGFS=y CONFIG_IWLAGN=m CONFIG_IWL4965=y CONFIG_IWL5000=y CONFIG_IWL3945=m CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y CONFIG_HOSTAP=m CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_FIRMWARE_NVRAM=y CONFIG_HOSTAP_PLX=m CONFIG_HOSTAP_PCI=m CONFIG_HOSTAP_CS=m CONFIG_B43=m CONFIG_B43_PCI_AUTOSELECT=y CONFIG_B43_PCICORE_AUTOSELECT=y CONFIG_B43_PCMCIA=y CONFIG_B43_PIO=y CONFIG_B43_LEDS=y CONFIG_B43_HWRNG=y # CONFIG_B43_DEBUG is not set CONFIG_B43LEGACY=m CONFIG_B43LEGACY_PCI_AUTOSELECT=y CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y CONFIG_B43LEGACY_LEDS=y CONFIG_B43LEGACY_HWRNG=y # CONFIG_B43LEGACY_DEBUG is not set CONFIG_B43LEGACY_DMA=y CONFIG_B43LEGACY_PIO=y CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y # CONFIG_B43LEGACY_DMA_MODE is not set # CONFIG_B43LEGACY_PIO_MODE is not set CONFIG_ZD1211RW=m # CONFIG_ZD1211RW_DEBUG is not set CONFIG_RT2X00=m CONFIG_RT2400PCI=m CONFIG_RT2500PCI=m CONFIG_RT61PCI=m CONFIG_RT2500USB=m CONFIG_RT73USB=m CONFIG_RT2800USB=m CONFIG_RT2X00_LIB_PCI=m CONFIG_RT2X00_LIB_USB=m CONFIG_RT2X00_LIB=m CONFIG_RT2X00_LIB_HT=y CONFIG_RT2X00_LIB_FIRMWARE=y CONFIG_RT2X00_LIB_CRYPTO=y CONFIG_RT2X00_LIB_RFKILL=y CONFIG_RT2X00_LIB_LEDS=y CONFIG_RT2X00_LIB_DEBUGFS=y # CONFIG_RT2X00_DEBUG is not set CONFIG_HERMES=m CONFIG_HERMES_CACHE_FW_ON_INIT=y CONFIG_PLX_HERMES=m CONFIG_TMD_HERMES=m CONFIG_NORTEL_HERMES=m CONFIG_PCI_HERMES=m CONFIG_PCMCIA_HERMES=m CONFIG_PCMCIA_SPECTRUM=m CONFIG_IWM=m # CONFIG_IWM_DEBUG is not set # # WiMAX Wireless Broadband devices # CONFIG_WIMAX_I2400M=m CONFIG_WIMAX_I2400M_USB=m CONFIG_WIMAX_I2400M_SDIO=m CONFIG_WIMAX_I2400M_DEBUG_LEVEL=8 # # USB Network Adapters # CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m CONFIG_USB_NET_CDCETHER=m CONFIG_USB_NET_CDC_EEM=m CONFIG_USB_NET_DM9601=m CONFIG_USB_NET_SMSC95XX=m CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_PLUSB=m CONFIG_USB_NET_MCS7830=m CONFIG_USB_NET_RNDIS_HOST=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=m CONFIG_USB_HSO=m CONFIG_USB_NET_INT51X1=m CONFIG_USB_CDC_PHONET=m CONFIG_NET_PCMCIA=y CONFIG_PCMCIA_3C589=m CONFIG_PCMCIA_3C574=m CONFIG_PCMCIA_FMVJ18X=m CONFIG_PCMCIA_PCNET=m CONFIG_PCMCIA_NMCLAN=m CONFIG_PCMCIA_SMC91C92=m CONFIG_PCMCIA_XIRC2PS=m CONFIG_PCMCIA_AXNET=m # CONFIG_WAN is not set CONFIG_ATM_DRIVERS=y # CONFIG_ATM_DUMMY is not set CONFIG_ATM_TCP=m # CONFIG_ATM_LANAI is not set CONFIG_ATM_ENI=m # CONFIG_ATM_ENI_DEBUG is not set # CONFIG_ATM_ENI_TUNE_BURST is not set CONFIG_ATM_FIRESTREAM=m # CONFIG_ATM_ZATM is not set # CONFIG_ATM_IDT77252 is not set # CONFIG_ATM_AMBASSADOR is not set # CONFIG_ATM_HORIZON is not set # CONFIG_ATM_IA is not set # CONFIG_ATM_FORE200E is not set # CONFIG_ATM_HE is not set CONFIG_ATM_SOLOS=m CONFIG_IEEE802154_DRIVERS=m CONFIG_IEEE802154_FAKEHARD=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_NETCHANNEL2=m CONFIG_XEN_NETDEV2_BACKEND=y CONFIG_XEN_NETDEV2_FRONTEND=y CONFIG_XEN_NETDEV2_BYPASSABLE=y CONFIG_XEN_NETDEV2_BYPASS_ENDPOINT=y CONFIG_XEN_NETDEV2_AUTOMATIC_BYPASS=y CONFIG_FDDI=y # CONFIG_DEFXX is not set CONFIG_SKFP=m # CONFIG_HIPPI is not set CONFIG_PLIP=m CONFIG_PPP=m CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m # CONFIG_PPP_BSDCOMP is not set CONFIG_PPP_MPPE=m CONFIG_PPPOE=m CONFIG_PPPOATM=m CONFIG_PPPOL2TP=m CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLHC=m CONFIG_SLIP_SMART=y # CONFIG_SLIP_MODE_SLIP6 is not set CONFIG_NET_FC=y CONFIG_NETCONSOLE=m CONFIG_NETCONSOLE_DYNAMIC=y CONFIG_NETPOLL=y CONFIG_NETPOLL_TRAP=y CONFIG_NET_POLL_CONTROLLER=y CONFIG_VIRTIO_NET=m CONFIG_ISDN=y CONFIG_MISDN=m CONFIG_MISDN_DSP=m CONFIG_MISDN_L1OIP=m # # mISDN hardware drivers # CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCUSB=m CONFIG_ISDN_I4L=m CONFIG_ISDN_PPP=y CONFIG_ISDN_PPP_VJ=y CONFIG_ISDN_MPP=y CONFIG_IPPP_FILTER=y # CONFIG_ISDN_PPP_BSDCOMP is not set CONFIG_ISDN_AUDIO=y CONFIG_ISDN_TTY_FAX=y # # ISDN feature submodules # CONFIG_ISDN_DIVERSION=m # # ISDN4Linux hardware drivers # # # Passive cards # CONFIG_ISDN_DRV_HISAX=m # # D-channel protocol features # CONFIG_HISAX_EURO=y CONFIG_DE_AOC=y CONFIG_HISAX_NO_SENDCOMPLETE=y CONFIG_HISAX_NO_LLC=y CONFIG_HISAX_NO_KEYPAD=y CONFIG_HISAX_1TR6=y CONFIG_HISAX_NI1=y CONFIG_HISAX_MAX_CARDS=8 # # HiSax supported cards # CONFIG_HISAX_16_3=y CONFIG_HISAX_TELESPCI=y CONFIG_HISAX_S0BOX=y CONFIG_HISAX_FRITZPCI=y CONFIG_HISAX_AVM_A1_PCMCIA=y CONFIG_HISAX_ELSA=y CONFIG_HISAX_DIEHLDIVA=y CONFIG_HISAX_SEDLBAUER=y CONFIG_HISAX_NETJET=y CONFIG_HISAX_NETJET_U=y CONFIG_HISAX_NICCY=y CONFIG_HISAX_BKM_A4T=y CONFIG_HISAX_SCT_QUADRO=y CONFIG_HISAX_GAZEL=y CONFIG_HISAX_HFC_PCI=y CONFIG_HISAX_W6692=y CONFIG_HISAX_HFC_SX=y CONFIG_HISAX_ENTERNOW_PCI=y # CONFIG_HISAX_DEBUG is not set # # HiSax PCMCIA card service modules # CONFIG_HISAX_SEDLBAUER_CS=m CONFIG_HISAX_ELSA_CS=m CONFIG_HISAX_AVM_A1_CS=m CONFIG_HISAX_TELES_CS=m # # HiSax sub driver modules # CONFIG_HISAX_ST5481=m # CONFIG_HISAX_HFCUSB is not set CONFIG_HISAX_HFC4S8S=m CONFIG_HISAX_FRITZ_PCIPNP=m CONFIG_HISAX_HDLC=y # # Active cards # CONFIG_HYSDN=m CONFIG_HYSDN_CAPI=y CONFIG_ISDN_CAPI=m CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y # CONFIG_CAPI_TRACE is not set CONFIG_ISDN_CAPI_MIDDLEWARE=y CONFIG_ISDN_CAPI_CAPI20=m CONFIG_ISDN_CAPI_CAPIFS_BOOL=y CONFIG_ISDN_CAPI_CAPIFS=m CONFIG_ISDN_CAPI_CAPIDRV=m # # CAPI hardware drivers # CONFIG_CAPI_AVM=y CONFIG_ISDN_DRV_AVMB1_B1PCI=m CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m CONFIG_ISDN_DRV_AVMB1_AVM_CS=m CONFIG_ISDN_DRV_AVMB1_T1PCI=m CONFIG_ISDN_DRV_AVMB1_C4=m CONFIG_CAPI_EICON=y CONFIG_ISDN_DIVAS=m CONFIG_ISDN_DIVAS_BRIPCI=y CONFIG_ISDN_DIVAS_PRIPCI=y CONFIG_ISDN_DIVAS_DIVACAPI=m CONFIG_ISDN_DIVAS_USERIDI=m CONFIG_ISDN_DIVAS_MAINT=m CONFIG_ISDN_DRV_GIGASET=m CONFIG_GIGASET_BASE=m CONFIG_GIGASET_M105=m CONFIG_GIGASET_M101=m # CONFIG_GIGASET_DEBUG is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y CONFIG_INPUT_FF_MEMLESS=y CONFIG_INPUT_POLLDEV=m # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y # CONFIG_INPUT_MOUSEDEV_PSAUX is not set CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set CONFIG_XEN_KBDDEV_FRONTEND=m # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_LM8323 is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_STOWAWAY is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_XTKBD is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y CONFIG_MOUSE_PS2_ELANTECH=y # CONFIG_MOUSE_PS2_TOUCHKIT is not set CONFIG_MOUSE_SERIAL=m CONFIG_MOUSE_APPLETOUCH=m CONFIG_MOUSE_BCM5974=m CONFIG_MOUSE_VSXXXAA=m CONFIG_MOUSE_SYNAPTICS_I2C=m CONFIG_INPUT_JOYSTICK=y CONFIG_JOYSTICK_ANALOG=m CONFIG_JOYSTICK_A3D=m CONFIG_JOYSTICK_ADI=m CONFIG_JOYSTICK_COBRA=m CONFIG_JOYSTICK_GF2K=m CONFIG_JOYSTICK_GRIP=m CONFIG_JOYSTICK_GRIP_MP=m CONFIG_JOYSTICK_GUILLEMOT=m CONFIG_JOYSTICK_INTERACT=m CONFIG_JOYSTICK_SIDEWINDER=m CONFIG_JOYSTICK_TMDC=m CONFIG_JOYSTICK_IFORCE=m CONFIG_JOYSTICK_IFORCE_USB=y CONFIG_JOYSTICK_IFORCE_232=y CONFIG_JOYSTICK_WARRIOR=m CONFIG_JOYSTICK_MAGELLAN=m CONFIG_JOYSTICK_SPACEORB=m CONFIG_JOYSTICK_SPACEBALL=m CONFIG_JOYSTICK_STINGER=m CONFIG_JOYSTICK_TWIDJOY=m CONFIG_JOYSTICK_ZHENHUA=m CONFIG_JOYSTICK_DB9=m CONFIG_JOYSTICK_GAMECON=m CONFIG_JOYSTICK_TURBOGRAFX=m CONFIG_JOYSTICK_JOYDUMP=m CONFIG_JOYSTICK_XPAD=m CONFIG_JOYSTICK_XPAD_FF=y CONFIG_JOYSTICK_XPAD_LEDS=y CONFIG_JOYSTICK_WALKERA0701=m CONFIG_INPUT_TABLET=y CONFIG_TABLET_USB_ACECAD=m CONFIG_TABLET_USB_AIPTEK=m CONFIG_TABLET_USB_GTCO=m CONFIG_TABLET_USB_KBTAB=m CONFIG_TABLET_USB_WACOM=m CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_AD7879_I2C=m CONFIG_TOUCHSCREEN_AD7879=m CONFIG_TOUCHSCREEN_EETI=m CONFIG_TOUCHSCREEN_FUJITSU=m CONFIG_TOUCHSCREEN_GUNZE=m CONFIG_TOUCHSCREEN_ELO=m CONFIG_TOUCHSCREEN_WACOM_W8001=m CONFIG_TOUCHSCREEN_MTOUCH=m CONFIG_TOUCHSCREEN_INEXIO=m CONFIG_TOUCHSCREEN_MK712=m CONFIG_TOUCHSCREEN_PENMOUNT=m CONFIG_TOUCHSCREEN_TOUCHRIGHT=m CONFIG_TOUCHSCREEN_TOUCHWIN=m # CONFIG_TOUCHSCREEN_WM97XX is not set CONFIG_TOUCHSCREEN_USB_COMPOSITE=m CONFIG_TOUCHSCREEN_USB_EGALAX=y CONFIG_TOUCHSCREEN_USB_PANJIT=y CONFIG_TOUCHSCREEN_USB_3M=y CONFIG_TOUCHSCREEN_USB_ITM=y CONFIG_TOUCHSCREEN_USB_ETURBO=y CONFIG_TOUCHSCREEN_USB_GUNZE=y CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y CONFIG_TOUCHSCREEN_USB_IRTOUCH=y CONFIG_TOUCHSCREEN_USB_IDEALTEK=y CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y CONFIG_TOUCHSCREEN_USB_GOTOP=y CONFIG_TOUCHSCREEN_TOUCHIT213=m CONFIG_TOUCHSCREEN_TSC2007=m CONFIG_TOUCHSCREEN_W90X900=m CONFIG_INPUT_LIRC=m CONFIG_LIRC_BT829=m CONFIG_LIRC_ENE0100=m CONFIG_LIRC_I2C=m CONFIG_LIRC_IGORPLUGUSB=m CONFIG_LIRC_IMON=m CONFIG_LIRC_IT87=m CONFIG_LIRC_ITE8709=m CONFIG_LIRC_MCEUSB=m CONFIG_LIRC_SASEM=m CONFIG_LIRC_SERIAL=m CONFIG_LIRC_SERIAL_TRANSMITTER=y CONFIG_LIRC_SIR=m CONFIG_LIRC_STREAMZAP=m CONFIG_LIRC_TTUSBIR=m CONFIG_LIRC_ZILOG=m CONFIG_INPUT_MISC=y CONFIG_INPUT_PCSPKR=m CONFIG_INPUT_APANEL=m CONFIG_INPUT_ATLAS_BTNS=m CONFIG_INPUT_ATI_REMOTE=m CONFIG_INPUT_ATI_REMOTE2=m CONFIG_INPUT_KEYSPAN_REMOTE=m CONFIG_INPUT_POWERMATE=m CONFIG_INPUT_YEALINK=m CONFIG_INPUT_CM109=m CONFIG_INPUT_UINPUT=m # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PARKBD is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y CONFIG_SERIO_RAW=m CONFIG_GAMEPORT=m CONFIG_GAMEPORT_NS558=m CONFIG_GAMEPORT_L4=m CONFIG_GAMEPORT_EMU10K1=m CONFIG_GAMEPORT_FM801=m # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y # CONFIG_DEVKMEM is not set CONFIG_SERIAL_NONSTANDARD=y # CONFIG_COMPUTONE is not set CONFIG_ROCKETPORT=m CONFIG_CYCLADES=m # CONFIG_CYZ_INTR is not set # CONFIG_DIGIEPCA is not set # CONFIG_MOXA_INTELLIO is not set # CONFIG_MOXA_SMARTIO is not set # CONFIG_ISI is not set CONFIG_SYNCLINK=m CONFIG_SYNCLINKMP=m CONFIG_SYNCLINK_GT=m CONFIG_N_HDLC=m # CONFIG_RISCOM8 is not set # CONFIG_SPECIALIX is not set # CONFIG_STALDRV is not set CONFIG_NOZOMI=m # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_CS=m CONFIG_SERIAL_8250_NR_UARTS=32 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_8250_DETECT_IRQ=y CONFIG_SERIAL_8250_RSA=y # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_CONSOLE_POLL=y CONFIG_SERIAL_JSM=m CONFIG_UNIX98_PTYS=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y # CONFIG_LEGACY_PTYS is not set CONFIG_CRASH=m CONFIG_PRINTER=m CONFIG_LP_CONSOLE=y CONFIG_PPDEV=m CONFIG_HVC_DRIVER=y CONFIG_HVC_IRQ=y CONFIG_HVC_XEN=y CONFIG_VIRTIO_CONSOLE=m CONFIG_IPMI_HANDLER=m # CONFIG_IPMI_PANIC_EVENT is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m CONFIG_IPMI_POWEROFF=m CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_TIMERIOMEM=m CONFIG_HW_RANDOM_INTEL=m CONFIG_HW_RANDOM_AMD=m CONFIG_HW_RANDOM_VIA=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_NVRAM=y CONFIG_R3964=m # CONFIG_APPLICOM is not set # # PCMCIA character devices # # CONFIG_SYNCLINK_CS is not set CONFIG_CARDMAN_4000=m CONFIG_CARDMAN_4040=m CONFIG_IPWIRELESS=m CONFIG_MWAVE=m # CONFIG_PC8736x_GPIO is not set CONFIG_RAW_DRIVER=y CONFIG_MAX_RAW_DEVS=8192 CONFIG_HPET=y # CONFIG_HPET_MMAP is not set CONFIG_HANGCHECK_TIMER=m CONFIG_TCG_TPM=y CONFIG_TCG_TIS=y CONFIG_TCG_NSC=m CONFIG_TCG_ATMEL=m CONFIG_TCG_INFINEON=m CONFIG_TELCLOCK=m CONFIG_DEVPORT=y CONFIG_I2C=m CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=m CONFIG_I2C_HELPER_AUTO=y CONFIG_I2C_ALGOBIT=m CONFIG_I2C_ALGOPCA=m # # I2C Hardware Bus support # # # PC SMBus host controller drivers # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set CONFIG_I2C_AMD756=m CONFIG_I2C_AMD756_S4882=m CONFIG_I2C_AMD8111=m CONFIG_I2C_I801=m CONFIG_I2C_ISCH=m CONFIG_I2C_PIIX4=m CONFIG_I2C_NFORCE2=m CONFIG_I2C_NFORCE2_S4985=m # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set CONFIG_I2C_SIS96X=m CONFIG_I2C_VIA=m CONFIG_I2C_VIAPRO=m # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_OCORES is not set CONFIG_I2C_SIMTEC=m # # External I2C/SMBus adapter drivers # CONFIG_I2C_PARPORT=m CONFIG_I2C_PARPORT_LIGHT=m # CONFIG_I2C_TAOS_EVM is not set CONFIG_I2C_TINY_USB=m # # Graphics adapter I2C/DDC channel drivers # CONFIG_I2C_VOODOO3=m # # Other I2C/SMBus bus drivers # CONFIG_I2C_PCA_PLATFORM=m CONFIG_I2C_STUB=m # # Miscellaneous I2C Chip support # # CONFIG_DS1682 is not set CONFIG_SENSORS_PCF8574=m CONFIG_PCF8575=m CONFIG_SENSORS_PCA9539=m CONFIG_SENSORS_TSL2550=m # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # CONFIG_SPI is not set # # PPS support # CONFIG_PPS=m # CONFIG_PPS_DEBUG is not set CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y # CONFIG_GPIOLIB is not set CONFIG_W1=m CONFIG_W1_CON=y # # 1-wire Bus Masters # # CONFIG_W1_MASTER_MATROX is not set CONFIG_W1_MASTER_DS2490=m CONFIG_W1_MASTER_DS2482=m # # 1-wire Slaves # CONFIG_W1_SLAVE_THERM=m CONFIG_W1_SLAVE_SMEM=m CONFIG_W1_SLAVE_DS2431=m CONFIG_W1_SLAVE_DS2433=m CONFIG_W1_SLAVE_DS2433_CRC=y CONFIG_W1_SLAVE_DS2760=m CONFIG_W1_SLAVE_BQ27000=m CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set CONFIG_WM8350_POWER=m # CONFIG_BATTERY_DS2760 is not set # CONFIG_BATTERY_DS2782 is not set CONFIG_BATTERY_BQ27x00=m CONFIG_BATTERY_MAX17040=m CONFIG_HWMON=y CONFIG_HWMON_VID=m CONFIG_SENSORS_ABITUGURU=m CONFIG_SENSORS_ABITUGURU3=m CONFIG_SENSORS_AD7414=m CONFIG_SENSORS_AD7418=m CONFIG_SENSORS_ADM1021=m CONFIG_SENSORS_ADM1025=m CONFIG_SENSORS_ADM1026=m CONFIG_SENSORS_ADM1029=m CONFIG_SENSORS_ADM1031=m CONFIG_SENSORS_ADM9240=m CONFIG_SENSORS_ADT7462=m CONFIG_SENSORS_ADT7470=m CONFIG_SENSORS_ADT7473=m CONFIG_SENSORS_ADT7475=m CONFIG_SENSORS_K8TEMP=m CONFIG_SENSORS_ASB100=m CONFIG_SENSORS_ATK0110=m CONFIG_SENSORS_ATXP1=m CONFIG_SENSORS_DS1621=m CONFIG_SENSORS_I5K_AMB=m CONFIG_SENSORS_F71805F=m CONFIG_SENSORS_F71882FG=m CONFIG_SENSORS_F75375S=m CONFIG_SENSORS_FSCHER=m CONFIG_SENSORS_FSCPOS=m CONFIG_SENSORS_FSCHMD=m CONFIG_SENSORS_G760A=m CONFIG_SENSORS_GL518SM=m CONFIG_SENSORS_GL520SM=m CONFIG_SENSORS_CORETEMP=m CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IT87=m CONFIG_SENSORS_LM63=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_LM90=m CONFIG_SENSORS_LM92=m CONFIG_SENSORS_LM93=m CONFIG_SENSORS_LTC4215=m CONFIG_SENSORS_LTC4245=m CONFIG_SENSORS_LM95241=m CONFIG_SENSORS_MAX1619=m CONFIG_SENSORS_MAX6650=m CONFIG_SENSORS_PC87360=m CONFIG_SENSORS_PC87427=m CONFIG_SENSORS_PCF8591=m CONFIG_SENSORS_SIS5595=m CONFIG_SENSORS_DME1737=m CONFIG_SENSORS_SMSC47M1=m CONFIG_SENSORS_SMSC47M192=m CONFIG_SENSORS_SMSC47B397=m CONFIG_SENSORS_ADS7828=m CONFIG_SENSORS_THMC50=m CONFIG_SENSORS_TMP401=m CONFIG_SENSORS_VIA_CPUTEMP=m CONFIG_SENSORS_VIA686A=m CONFIG_SENSORS_VT1211=m CONFIG_SENSORS_VT8231=m CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83791D=m CONFIG_SENSORS_W83792D=m CONFIG_SENSORS_W83793=m CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83L786NG=m CONFIG_SENSORS_W83627HF=m CONFIG_SENSORS_W83627EHF=m CONFIG_SENSORS_HDAPS=m CONFIG_SENSORS_LIS3LV02D=m CONFIG_SENSORS_APPLESMC=m # CONFIG_HWMON_DEBUG_CHIP is not set CONFIG_THERMAL=y CONFIG_THERMAL_HWMON=y CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # CONFIG_SOFT_WATCHDOG=m CONFIG_WM8350_WATCHDOG=m # CONFIG_ACQUIRE_WDT is not set # CONFIG_ADVANTECH_WDT is not set CONFIG_ALIM1535_WDT=m CONFIG_ALIM7101_WDT=m # CONFIG_SC520_WDT is not set # CONFIG_EUROTECH_WDT is not set # CONFIG_IB700_WDT is not set CONFIG_IBMASR=m # CONFIG_WAFER_WDT is not set CONFIG_I6300ESB_WDT=m CONFIG_ITCO_WDT=m CONFIG_ITCO_VENDOR_SUPPORT=y CONFIG_IT8712F_WDT=m CONFIG_IT87_WDT=m CONFIG_HP_WATCHDOG=m # CONFIG_SC1200_WDT is not set # CONFIG_PC87413_WDT is not set # CONFIG_60XX_WDT is not set # CONFIG_SBC8360_WDT is not set # CONFIG_CPU5_WDT is not set CONFIG_SMSC_SCH311X_WDT=m # CONFIG_SMSC37B787_WDT is not set CONFIG_W83627HF_WDT=m CONFIG_W83697HF_WDT=m CONFIG_W83697UG_WDT=m CONFIG_W83877F_WDT=m CONFIG_W83977F_WDT=m CONFIG_MACHZ_WDT=m # CONFIG_SBC_EPX_C3_WATCHDOG is not set # # PCI-based Watchdog Cards # CONFIG_PCIPCWATCHDOG=m CONFIG_WDTPCI=m # # USB-based Watchdog Cards # CONFIG_USBPCWATCHDOG=m CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # CONFIG_SSB=m CONFIG_SSB_SPROM=y CONFIG_SSB_BLOCKIO=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y CONFIG_SSB_B43_PCI_BRIDGE=y CONFIG_SSB_PCMCIAHOST_POSSIBLE=y CONFIG_SSB_PCMCIAHOST=y # CONFIG_SSB_DEBUG is not set CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y # # Multifunction device drivers # CONFIG_MFD_CORE=m CONFIG_MFD_SM501=m # CONFIG_HTC_PASIC3 is not set # CONFIG_MFD_TMIO is not set CONFIG_MFD_WM8400=m CONFIG_MFD_WM8350=m CONFIG_MFD_WM8350_I2C=m # CONFIG_MFD_PCF50633 is not set CONFIG_AB3100_CORE=m CONFIG_REGULATOR=y # CONFIG_REGULATOR_DEBUG is not set CONFIG_REGULATOR_FIXED_VOLTAGE=m # CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set CONFIG_REGULATOR_USERSPACE_CONSUMER=m CONFIG_REGULATOR_BQ24022=m CONFIG_REGULATOR_MAX1586=m CONFIG_REGULATOR_WM8350=m CONFIG_REGULATOR_WM8400=m CONFIG_REGULATOR_LP3971=m CONFIG_MEDIA_SUPPORT=m # # Multimedia core support # CONFIG_VIDEO_DEV=m CONFIG_VIDEO_V4L2_COMMON=m CONFIG_VIDEO_ALLOW_V4L1=y CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_DVB_CORE=m CONFIG_VIDEO_MEDIA=m # # Multimedia drivers # CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_MEDIA_ATTACH=y CONFIG_MEDIA_TUNER=m # CONFIG_MEDIA_TUNER_CUSTOMISE is not set CONFIG_MEDIA_TUNER_SIMPLE=m CONFIG_MEDIA_TUNER_TDA8290=m CONFIG_MEDIA_TUNER_TDA827X=m CONFIG_MEDIA_TUNER_TDA18271=m CONFIG_MEDIA_TUNER_TDA9887=m CONFIG_MEDIA_TUNER_TEA5761=m CONFIG_MEDIA_TUNER_TEA5767=m CONFIG_MEDIA_TUNER_MT20XX=m CONFIG_MEDIA_TUNER_MT2060=m CONFIG_MEDIA_TUNER_MT2266=m CONFIG_MEDIA_TUNER_MT2131=m CONFIG_MEDIA_TUNER_QT1010=m CONFIG_MEDIA_TUNER_XC2028=m CONFIG_MEDIA_TUNER_XC5000=m CONFIG_MEDIA_TUNER_MXL5005S=m CONFIG_MEDIA_TUNER_MXL5007T=m CONFIG_MEDIA_TUNER_MC44S803=m CONFIG_VIDEO_V4L2=m CONFIG_VIDEO_V4L1=m CONFIG_VIDEOBUF_GEN=m CONFIG_VIDEOBUF_DMA_SG=m CONFIG_VIDEOBUF_VMALLOC=m CONFIG_VIDEOBUF_DVB=m CONFIG_VIDEO_BTCX=m CONFIG_VIDEO_IR=m CONFIG_VIDEO_TVEEPROM=m CONFIG_VIDEO_TUNER=m CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set # CONFIG_VIDEO_FIXED_MINOR_RANGES is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y CONFIG_VIDEO_IR_I2C=m CONFIG_VIDEO_TVAUDIO=m CONFIG_VIDEO_TDA7432=m CONFIG_VIDEO_TDA9840=m CONFIG_VIDEO_TEA6415C=m CONFIG_VIDEO_TEA6420=m CONFIG_VIDEO_MSP3400=m CONFIG_VIDEO_CS5345=m CONFIG_VIDEO_CS53L32A=m CONFIG_VIDEO_M52790=m CONFIG_VIDEO_WM8775=m CONFIG_VIDEO_WM8739=m CONFIG_VIDEO_VP27SMPX=m CONFIG_VIDEO_SAA6588=m CONFIG_VIDEO_BT819=m CONFIG_VIDEO_BT856=m CONFIG_VIDEO_BT866=m CONFIG_VIDEO_KS0127=m CONFIG_VIDEO_MT9V011=m CONFIG_VIDEO_SAA7110=m CONFIG_VIDEO_SAA711X=m CONFIG_VIDEO_SAA717X=m CONFIG_VIDEO_TVP5150=m CONFIG_VIDEO_VPX3220=m CONFIG_VIDEO_CX25840=m CONFIG_VIDEO_CX2341X=m CONFIG_VIDEO_SAA7127=m CONFIG_VIDEO_SAA7185=m CONFIG_VIDEO_ADV7170=m CONFIG_VIDEO_ADV7175=m CONFIG_VIDEO_UPD64031A=m CONFIG_VIDEO_UPD64083=m # CONFIG_VIDEO_VIVI is not set CONFIG_VIDEO_BT848=m CONFIG_VIDEO_BT848_DVB=y CONFIG_VIDEO_BWQCAM=m CONFIG_VIDEO_CQCAM=m CONFIG_VIDEO_W9966=m CONFIG_VIDEO_CPIA=m CONFIG_VIDEO_CPIA_PP=m CONFIG_VIDEO_CPIA_USB=m CONFIG_VIDEO_CPIA2=m CONFIG_VIDEO_SAA5246A=m CONFIG_VIDEO_SAA5249=m CONFIG_VIDEO_STRADIS=m CONFIG_VIDEO_ZORAN=m CONFIG_VIDEO_ZORAN_DC30=m CONFIG_VIDEO_ZORAN_ZR36060=m CONFIG_VIDEO_ZORAN_BUZ=m CONFIG_VIDEO_ZORAN_DC10=m CONFIG_VIDEO_ZORAN_LML33=m CONFIG_VIDEO_ZORAN_LML33R10=m CONFIG_VIDEO_ZORAN_AVS6EYES=m CONFIG_VIDEO_MEYE=m CONFIG_VIDEO_SAA7134=m CONFIG_VIDEO_SAA7134_ALSA=m CONFIG_VIDEO_SAA7134_DVB=m CONFIG_VIDEO_MXB=m CONFIG_VIDEO_HEXIUM_ORION=m CONFIG_VIDEO_HEXIUM_GEMINI=m CONFIG_VIDEO_CX88=m CONFIG_VIDEO_CX88_ALSA=m CONFIG_VIDEO_CX88_BLACKBIRD=m CONFIG_VIDEO_CX88_DVB=m CONFIG_VIDEO_CX88_MPEG=m CONFIG_VIDEO_CX88_VP3054=m CONFIG_VIDEO_CX23885=m CONFIG_VIDEO_AU0828=m CONFIG_VIDEO_IVTV=m CONFIG_VIDEO_FB_IVTV=m CONFIG_VIDEO_CX18=m # CONFIG_VIDEO_CAFE_CCIC is not set CONFIG_SOC_CAMERA=m CONFIG_SOC_CAMERA_MT9M001=m CONFIG_SOC_CAMERA_MT9M111=m CONFIG_SOC_CAMERA_MT9T031=m CONFIG_SOC_CAMERA_MT9V022=m CONFIG_SOC_CAMERA_TW9910=m CONFIG_SOC_CAMERA_PLATFORM=m CONFIG_SOC_CAMERA_OV772X=m CONFIG_V4L_USB_DRIVERS=y CONFIG_USB_VIDEO_CLASS=m CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_GSPCA=m CONFIG_USB_M5602=m CONFIG_USB_STV06XX=m CONFIG_USB_GSPCA_CONEX=m CONFIG_USB_GSPCA_ETOMS=m CONFIG_USB_GSPCA_FINEPIX=m CONFIG_USB_GSPCA_MARS=m CONFIG_USB_GSPCA_MR97310A=m CONFIG_USB_GSPCA_OV519=m CONFIG_USB_GSPCA_OV534=m CONFIG_USB_GSPCA_PAC207=m CONFIG_USB_GSPCA_PAC7311=m CONFIG_USB_GSPCA_SN9C20X=m CONFIG_USB_GSPCA_SN9C20X_EVDEV=y CONFIG_USB_GSPCA_SONIXB=m CONFIG_USB_GSPCA_SONIXJ=m CONFIG_USB_GSPCA_SPCA500=m CONFIG_USB_GSPCA_SPCA501=m CONFIG_USB_GSPCA_SPCA505=m CONFIG_USB_GSPCA_SPCA506=m CONFIG_USB_GSPCA_SPCA508=m CONFIG_USB_GSPCA_SPCA561=m CONFIG_USB_GSPCA_SQ905=m CONFIG_USB_GSPCA_SQ905C=m CONFIG_USB_GSPCA_STK014=m CONFIG_USB_GSPCA_SUNPLUS=m CONFIG_USB_GSPCA_T613=m CONFIG_USB_GSPCA_TV8532=m CONFIG_USB_GSPCA_VC032X=m CONFIG_USB_GSPCA_ZC3XX=m CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DVB=y # CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set CONFIG_VIDEO_HDPVR=m CONFIG_VIDEO_EM28XX=m CONFIG_VIDEO_EM28XX_ALSA=m CONFIG_VIDEO_EM28XX_DVB=m CONFIG_VIDEO_CX231XX=m CONFIG_VIDEO_CX231XX_ALSA=m CONFIG_VIDEO_CX231XX_DVB=m CONFIG_VIDEO_USBVISION=m CONFIG_VIDEO_USBVIDEO=m CONFIG_USB_VICAM=m CONFIG_USB_IBMCAM=m CONFIG_USB_KONICAWC=m # CONFIG_USB_QUICKCAM_MESSENGER is not set CONFIG_USB_ET61X251=m CONFIG_VIDEO_OVCAMCHIP=m CONFIG_USB_W9968CF=m # CONFIG_USB_OV511 is not set CONFIG_USB_SE401=m CONFIG_USB_SN9C102=m CONFIG_USB_STV680=m # CONFIG_USB_ZC0301 is not set CONFIG_USB_PWC=m # CONFIG_USB_PWC_DEBUG is not set CONFIG_USB_PWC_INPUT_EVDEV=y CONFIG_USB_ZR364XX=m CONFIG_USB_STKWEBCAM=m CONFIG_USB_S2255=m CONFIG_RADIO_ADAPTERS=y CONFIG_RADIO_GEMTEK_PCI=m CONFIG_RADIO_MAXIRADIO=m CONFIG_RADIO_MAESTRO=m CONFIG_USB_DSBR=m CONFIG_USB_SI470X=m CONFIG_USB_MR800=m # CONFIG_RADIO_TEA5764 is not set CONFIG_DVB_DYNAMIC_MINORS=y CONFIG_DVB_CAPTURE_DRIVERS=y # # Supported SAA7146 based PCI Adapters # CONFIG_TTPCI_EEPROM=m CONFIG_DVB_AV7110=m CONFIG_DVB_AV7110_OSD=y CONFIG_DVB_BUDGET_CORE=m CONFIG_DVB_BUDGET=m CONFIG_DVB_BUDGET_CI=m CONFIG_DVB_BUDGET_AV=m CONFIG_DVB_BUDGET_PATCH=m # # Supported USB Adapters # CONFIG_DVB_USB=m # CONFIG_DVB_USB_DEBUG is not set CONFIG_DVB_USB_A800=m CONFIG_DVB_USB_DIBUSB_MB=m # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set CONFIG_DVB_USB_DIBUSB_MC=m CONFIG_DVB_USB_DIB0700=m CONFIG_DVB_USB_UMT_010=m CONFIG_DVB_USB_CXUSB=m CONFIG_DVB_USB_M920X=m CONFIG_DVB_USB_GL861=m CONFIG_DVB_USB_AU6610=m CONFIG_DVB_USB_DIGITV=m CONFIG_DVB_USB_VP7045=m CONFIG_DVB_USB_VP702X=m CONFIG_DVB_USB_GP8PSK=m CONFIG_DVB_USB_NOVA_T_USB2=m CONFIG_DVB_USB_TTUSB2=m CONFIG_DVB_USB_DTT200U=m CONFIG_DVB_USB_OPERA1=m CONFIG_DVB_USB_AF9005=m CONFIG_DVB_USB_AF9005_REMOTE=m CONFIG_DVB_USB_DW2102=m CONFIG_DVB_USB_CINERGY_T2=m CONFIG_DVB_USB_ANYSEE=m CONFIG_DVB_USB_DTV5100=m CONFIG_DVB_USB_AF9015=m CONFIG_DVB_USB_CE6230=m CONFIG_DVB_TTUSB_BUDGET=m CONFIG_DVB_TTUSB_DEC=m CONFIG_SMS_SIANO_MDTV=m # # Siano module components # CONFIG_SMS_USB_DRV=m CONFIG_SMS_SDIO_DRV=m # # Supported FlexCopII (B2C2) Adapters # CONFIG_DVB_B2C2_FLEXCOP=m CONFIG_DVB_B2C2_FLEXCOP_PCI=m CONFIG_DVB_B2C2_FLEXCOP_USB=m # CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set # # Supported BT878 Adapters # CONFIG_DVB_BT8XX=m # # Supported Pluto2 Adapters # CONFIG_DVB_PLUTO2=m # # Supported SDMC DM1105 Adapters # CONFIG_DVB_DM1105=m # # Supported DVB Frontends # # CONFIG_DVB_FE_CUSTOMISE is not set CONFIG_DVB_STB0899=m CONFIG_DVB_STB6100=m CONFIG_DVB_CX24110=m CONFIG_DVB_CX24123=m CONFIG_DVB_MT312=m CONFIG_DVB_ZL10036=m CONFIG_DVB_S5H1420=m CONFIG_DVB_STV0288=m CONFIG_DVB_STB6000=m CONFIG_DVB_STV0299=m CONFIG_DVB_STV6110=m CONFIG_DVB_STV0900=m CONFIG_DVB_TDA8083=m CONFIG_DVB_TDA10086=m CONFIG_DVB_TDA8261=m CONFIG_DVB_VES1X93=m CONFIG_DVB_TUNER_ITD1000=m CONFIG_DVB_TUNER_CX24113=m CONFIG_DVB_TDA826X=m CONFIG_DVB_TUA6100=m CONFIG_DVB_CX24116=m CONFIG_DVB_SI21XX=m CONFIG_DVB_SP8870=m CONFIG_DVB_SP887X=m CONFIG_DVB_CX22700=m CONFIG_DVB_CX22702=m CONFIG_DVB_L64781=m CONFIG_DVB_TDA1004X=m CONFIG_DVB_NXT6000=m CONFIG_DVB_MT352=m CONFIG_DVB_ZL10353=m CONFIG_DVB_DIB3000MB=m CONFIG_DVB_DIB3000MC=m CONFIG_DVB_DIB7000M=m CONFIG_DVB_DIB7000P=m CONFIG_DVB_TDA10048=m CONFIG_DVB_AF9013=m CONFIG_DVB_VES1820=m CONFIG_DVB_TDA10021=m CONFIG_DVB_TDA10023=m CONFIG_DVB_STV0297=m CONFIG_DVB_NXT200X=m CONFIG_DVB_OR51211=m CONFIG_DVB_OR51132=m CONFIG_DVB_BCM3510=m CONFIG_DVB_LGDT330X=m CONFIG_DVB_LGDT3305=m CONFIG_DVB_S5H1409=m CONFIG_DVB_AU8522=m CONFIG_DVB_S5H1411=m CONFIG_DVB_PLL=m CONFIG_DVB_TUNER_DIB0070=m CONFIG_DVB_LNBP21=m CONFIG_DVB_ISL6405=m CONFIG_DVB_ISL6421=m CONFIG_DVB_LGS8GL5=m CONFIG_DAB=y CONFIG_USB_DABUSB=m # # Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=y CONFIG_AGP_SIS=y CONFIG_AGP_VIA=y CONFIG_VGA_ARB=y CONFIG_DRM=m CONFIG_DRM_KMS_HELPER=m CONFIG_DRM_TTM=m CONFIG_DRM_TDFX=m CONFIG_DRM_R128=m CONFIG_DRM_RADEON=m CONFIG_DRM_I810=m CONFIG_DRM_I830=m CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y CONFIG_DRM_MGA=m CONFIG_DRM_SIS=m CONFIG_DRM_VIA=m CONFIG_DRM_SAVAGE=m CONFIG_DRM_NOUVEAU=m CONFIG_DRM_NOUVEAU_KMS=y CONFIG_DRM_NOUVEAU_BACKLIGHT=y CONFIG_DRM_NOUVEAU_DEBUG=y # # I2C encoder or helper chips # CONFIG_DRM_I2C_CH7006=m CONFIG_VGASTATE=m CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set CONFIG_FB_DDC=m CONFIG_FB_BOOT_VESA_SUPPORT=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set CONFIG_FB_SYS_FILLRECT=m CONFIG_FB_SYS_COPYAREA=m CONFIG_FB_SYS_IMAGEBLIT=m # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=m CONFIG_FB_DEFERRED_IO=y CONFIG_FB_SVGALIB=m # CONFIG_FB_MACMODES is not set CONFIG_FB_BACKLIGHT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # CONFIG_FB_CIRRUS=m # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set CONFIG_FB_VGA16=m # CONFIG_FB_UVESA is not set CONFIG_FB_VESA=y CONFIG_FB_EFI=y # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y # CONFIG_FB_NVIDIA_DEBUG is not set CONFIG_FB_NVIDIA_BACKLIGHT=y CONFIG_FB_RIVA=m # CONFIG_FB_RIVA_I2C is not set # CONFIG_FB_RIVA_DEBUG is not set CONFIG_FB_RIVA_BACKLIGHT=y # CONFIG_FB_LE80578 is not set CONFIG_FB_MATROX=m CONFIG_FB_MATROX_MILLENIUM=y CONFIG_FB_MATROX_MYSTIQUE=y CONFIG_FB_MATROX_G=y CONFIG_FB_MATROX_I2C=m CONFIG_FB_MATROX_MAVEN=m CONFIG_FB_MATROX_MULTIHEAD=y CONFIG_FB_RADEON=m CONFIG_FB_RADEON_I2C=y CONFIG_FB_RADEON_BACKLIGHT=y # CONFIG_FB_RADEON_DEBUG is not set CONFIG_FB_ATY128=m CONFIG_FB_ATY128_BACKLIGHT=y CONFIG_FB_ATY=m CONFIG_FB_ATY_CT=y CONFIG_FB_ATY_GENERIC_LCD=y CONFIG_FB_ATY_GX=y CONFIG_FB_ATY_BACKLIGHT=y CONFIG_FB_S3=m CONFIG_FB_SAVAGE=m CONFIG_FB_SAVAGE_I2C=y CONFIG_FB_SAVAGE_ACCEL=y # CONFIG_FB_SIS is not set CONFIG_FB_VIA=m CONFIG_FB_NEOMAGIC=m CONFIG_FB_KYRO=m CONFIG_FB_3DFX=m CONFIG_FB_3DFX_ACCEL=y CONFIG_FB_3DFX_I2C=y CONFIG_FB_VOODOO1=m # CONFIG_FB_VT8623 is not set CONFIG_FB_TRIDENT=m # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_TMIO is not set CONFIG_FB_SM501=m CONFIG_FB_VIRTUAL=m CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_FB_METRONOME=m CONFIG_FB_MB862XX=m CONFIG_FB_MB862XX_PCI_GDC=y # CONFIG_FB_BROADSHEET is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=m # CONFIG_LCD_ILI9320 is not set CONFIG_LCD_PLATFORM=m CONFIG_BACKLIGHT_CLASS_DEVICE=y # CONFIG_BACKLIGHT_GENERIC is not set CONFIG_BACKLIGHT_PROGEAR=m CONFIG_BACKLIGHT_MBP_NVIDIA=m # CONFIG_BACKLIGHT_SAHARA is not set # # Display device support # CONFIG_DISPLAY_SUPPORT=m # # Display hardware drivers # # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64 CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y CONFIG_LOGO=y # CONFIG_LOGO_LINUX_MONO is not set # CONFIG_LOGO_LINUX_VGA16 is not set CONFIG_LOGO_LINUX_CLUT224=y CONFIG_SOUND=m CONFIG_SOUND_OSS_CORE=y CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_JACK=y CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_HRTIMER=m CONFIG_SND_SEQ_HRTIMER_DEFAULT=y CONFIG_SND_DYNAMIC_MINORS=y # CONFIG_SND_SUPPORT_OLD_API is not set CONFIG_SND_VERBOSE_PROCFS=y CONFIG_SND_VERBOSE_PRINTK=y CONFIG_SND_DEBUG=y # CONFIG_SND_DEBUG_VERBOSE is not set CONFIG_SND_PCM_XRUN_DEBUG=y CONFIG_SND_VMASTER=y CONFIG_SND_RAWMIDI_SEQ=m CONFIG_SND_OPL3_LIB_SEQ=m # CONFIG_SND_OPL4_LIB_SEQ is not set # CONFIG_SND_SBAWE_SEQ is not set CONFIG_SND_EMU10K1_SEQ=m CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m CONFIG_SND_VX_LIB=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_DRIVERS=y CONFIG_SND_PCSP=m CONFIG_SND_DUMMY=m CONFIG_SND_VIRMIDI=m CONFIG_SND_MTPAV=m CONFIG_SND_MTS64=m CONFIG_SND_SERIAL_U16550=m CONFIG_SND_MPU401=m CONFIG_SND_PORTMAN2X4=m CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0 CONFIG_SND_SB_COMMON=m CONFIG_SND_SB16_DSP=m CONFIG_SND_PCI=y CONFIG_SND_AD1889=m CONFIG_SND_ALS300=m CONFIG_SND_ALS4000=m CONFIG_SND_ALI5451=m CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m CONFIG_SND_AU8810=m CONFIG_SND_AU8820=m CONFIG_SND_AU8830=m # CONFIG_SND_AW2 is not set CONFIG_SND_AZT3328=m CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set CONFIG_SND_CA0106=m CONFIG_SND_CMIPCI=m CONFIG_SND_OXYGEN_LIB=m CONFIG_SND_OXYGEN=m CONFIG_SND_CS4281=m CONFIG_SND_CS46XX=m CONFIG_SND_CS46XX_NEW_DSP=y CONFIG_SND_CS5530=m CONFIG_SND_CTXFI=m CONFIG_SND_DARLA20=m CONFIG_SND_GINA20=m CONFIG_SND_LAYLA20=m CONFIG_SND_DARLA24=m CONFIG_SND_GINA24=m CONFIG_SND_LAYLA24=m CONFIG_SND_MONA=m CONFIG_SND_MIA=m CONFIG_SND_ECHO3G=m CONFIG_SND_INDIGO=m CONFIG_SND_INDIGOIO=m CONFIG_SND_INDIGODJ=m CONFIG_SND_INDIGOIOX=m CONFIG_SND_INDIGODJX=m CONFIG_SND_EMU10K1=m CONFIG_SND_EMU10K1X=m CONFIG_SND_ENS1370=m CONFIG_SND_ENS1371=m CONFIG_SND_ES1938=m CONFIG_SND_ES1968=m CONFIG_SND_FM801=m CONFIG_SND_FM801_TEA575X_BOOL=y CONFIG_SND_FM801_TEA575X=m CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_RECONFIG=y CONFIG_SND_HDA_INPUT_BEEP=y CONFIG_SND_HDA_INPUT_JACK=y CONFIG_SND_HDA_CODEC_REALTEK=y CONFIG_SND_HDA_CODEC_ANALOG=y CONFIG_SND_HDA_CODEC_SIGMATEL=y CONFIG_SND_HDA_CODEC_VIA=y CONFIG_SND_HDA_CODEC_ATIHDMI=y CONFIG_SND_HDA_CODEC_NVHDMI=y CONFIG_SND_HDA_CODEC_INTELHDMI=y CONFIG_SND_HDA_ELD=y CONFIG_SND_HDA_CODEC_CONEXANT=y CONFIG_SND_HDA_CODEC_CA0110=y CONFIG_SND_HDA_CODEC_CMEDIA=y CONFIG_SND_HDA_CODEC_SI3054=y CONFIG_SND_HDA_GENERIC=y CONFIG_SND_HDA_POWER_SAVE=y CONFIG_SND_HDA_POWER_SAVE_DEFAULT=5 CONFIG_SND_HDSP=m CONFIG_SND_HDSPM=m CONFIG_SND_HIFIER=m CONFIG_SND_ICE1712=m CONFIG_SND_ICE1724=m CONFIG_SND_INTEL8X0=m CONFIG_SND_INTEL8X0M=m CONFIG_SND_KORG1212=m CONFIG_SND_LX6464ES=m CONFIG_SND_MAESTRO3=m CONFIG_SND_MIXART=m CONFIG_SND_NM256=m CONFIG_SND_PCXHR=m CONFIG_SND_RIPTIDE=m CONFIG_SND_RME32=m CONFIG_SND_RME96=m CONFIG_SND_RME9652=m CONFIG_SND_SONICVIBES=m CONFIG_SND_TRIDENT=m CONFIG_SND_VIA82XX=m CONFIG_SND_VIA82XX_MODEM=m CONFIG_SND_VIRTUOSO=m CONFIG_SND_VX222=m CONFIG_SND_YMFPCI=m CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m CONFIG_SND_USB_USX2Y=m CONFIG_SND_USB_CAIAQ=m CONFIG_SND_USB_CAIAQ_INPUT=y CONFIG_SND_USB_US122L=m CONFIG_SND_PCMCIA=y CONFIG_SND_VXPOCKET=m CONFIG_SND_PDAUDIOCF=m # CONFIG_SND_SOC is not set # CONFIG_SOUND_PRIME is not set CONFIG_AC97_BUS=m CONFIG_HID_SUPPORT=y CONFIG_HID=y CONFIG_HID_DEBUG=y CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=y CONFIG_HID_PID=y CONFIG_USB_HIDDEV=y # # Special HID drivers # CONFIG_HID_A4TECH=y CONFIG_HID_APPLE=y CONFIG_HID_BELKIN=y CONFIG_HID_CHERRY=y CONFIG_HID_CHICONY=y CONFIG_HID_CYPRESS=y CONFIG_HID_DRAGONRISE=y CONFIG_DRAGONRISE_FF=y CONFIG_HID_EZKEY=y CONFIG_HID_KYE=y CONFIG_HID_GYRATION=y CONFIG_HID_KENSINGTON=y CONFIG_HID_LOGITECH=y CONFIG_LOGITECH_FF=y CONFIG_LOGIRUMBLEPAD2_FF=y CONFIG_HID_MICROSOFT=y CONFIG_HID_MONTEREY=y CONFIG_HID_NTRIG=y CONFIG_HID_PANTHERLORD=y CONFIG_PANTHERLORD_FF=y CONFIG_HID_PETALYNX=y CONFIG_HID_SAMSUNG=y CONFIG_HID_SONY=y CONFIG_HID_SUNPLUS=y CONFIG_HID_GREENASIA=y CONFIG_GREENASIA_FF=y CONFIG_HID_SMARTJOYPLUS=y CONFIG_SMARTJOYPLUS_FF=y CONFIG_HID_TOPSEED=y CONFIG_HID_THRUSTMASTER=y CONFIG_THRUSTMASTER_FF=y CONFIG_HID_WACOM=m CONFIG_HID_ZEROPLUS=y CONFIG_ZEROPLUS_FF=y CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set CONFIG_USB_ANNOUNCE_NEW_DEVICES=y # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set CONFIG_USB_SUSPEND=y # CONFIG_USB_OTG is not set CONFIG_USB_MON=y CONFIG_USB_WUSB=m CONFIG_USB_WUSB_CBAF=m # CONFIG_USB_WUSB_CBAF_DEBUG is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set CONFIG_USB_XHCI_HCD=m # CONFIG_USB_XHCI_HCD_DEBUGGING is not set CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y # CONFIG_USB_OXU210HP_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_ISP1760_HCD is not set CONFIG_USB_OHCI_HCD=y # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=y CONFIG_USB_U132_HCD=m CONFIG_USB_SL811_HCD=m # CONFIG_USB_SL811_CS is not set # CONFIG_USB_R8A66597_HCD is not set CONFIG_USB_WHCI_HCD=m CONFIG_USB_HWA_HCD=m # # USB Device Class drivers # CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m CONFIG_USB_WDM=m CONFIG_USB_TMC=m # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_DATAFAB=m CONFIG_USB_STORAGE_FREECOM=m CONFIG_USB_STORAGE_ISD200=m CONFIG_USB_STORAGE_USBAT=m CONFIG_USB_STORAGE_SDDR09=m CONFIG_USB_STORAGE_SDDR55=m CONFIG_USB_STORAGE_JUMPSHOT=m CONFIG_USB_STORAGE_ALAUDA=m CONFIG_USB_STORAGE_ONETOUCH=m CONFIG_USB_STORAGE_KARMA=m CONFIG_USB_STORAGE_CYPRESS_ATACB=m # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # CONFIG_USB_MDC800=m CONFIG_USB_MICROTEK=m # # USB port drivers # CONFIG_USB_USS720=m CONFIG_USB_SERIAL=m CONFIG_USB_EZUSB=y CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_AIRCABLE=m CONFIG_USB_SERIAL_ARK3116=m CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_CH341=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_CP210X=m CONFIG_USB_SERIAL_CYPRESS_M8=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_FUNSOFT=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_EDGEPORT_TI=m CONFIG_USB_SERIAL_GARMIN=m CONFIG_USB_SERIAL_IPW=m CONFIG_USB_SERIAL_IUU=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_KOBIL_SCT=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_MOS7720=m CONFIG_USB_SERIAL_MOS7840=m CONFIG_USB_SERIAL_MOTOROLA=m CONFIG_USB_SERIAL_NAVMAN=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_OTI6858=m CONFIG_USB_SERIAL_QUALCOMM=m CONFIG_USB_SERIAL_SPCP8X5=m CONFIG_USB_SERIAL_HP4X=m CONFIG_USB_SERIAL_SAFE=m CONFIG_USB_SERIAL_SAFE_PADDED=y CONFIG_USB_SERIAL_SIEMENS_MPI=m CONFIG_USB_SERIAL_SIERRAWIRELESS=m CONFIG_USB_SERIAL_SYMBOL=m CONFIG_USB_SERIAL_TI=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OPTION=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_SERIAL_OPTICON=m CONFIG_USB_SERIAL_DEBUG=m # # USB Miscellaneous drivers # CONFIG_USB_EMI62=m CONFIG_USB_EMI26=m CONFIG_USB_ADUTUX=m CONFIG_USB_SEVSEG=m # CONFIG_USB_RIO500 is not set CONFIG_USB_LEGOTOWER=m CONFIG_USB_LCD=m CONFIG_USB_BERRY_CHARGE=m CONFIG_USB_LED=m # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set CONFIG_USB_IDMOUSE=m CONFIG_USB_FTDI_ELAN=m CONFIG_USB_APPLEDISPLAY=m CONFIG_USB_SISUSBVGA=m CONFIG_USB_SISUSBVGA_CON=y CONFIG_USB_LD=m CONFIG_USB_TRANCEVIBRATOR=m CONFIG_USB_IOWARRIOR=m # CONFIG_USB_TEST is not set CONFIG_USB_ISIGHTFW=m CONFIG_USB_VST=m CONFIG_USB_ATM=m CONFIG_USB_SPEEDTOUCH=m CONFIG_USB_CXACRU=m CONFIG_USB_UEAGLEATM=m CONFIG_USB_XUSBATM=m # CONFIG_USB_GADGET is not set # # OTG and related infrastructure # CONFIG_USB_OTG_UTILS=y CONFIG_NOP_USB_XCEIV=m CONFIG_UWB=m CONFIG_UWB_HWA=m CONFIG_UWB_WHCI=m CONFIG_UWB_WLP=m CONFIG_UWB_I1480U=m CONFIG_UWB_I1480U_WLP=m CONFIG_MMC=m # CONFIG_MMC_DEBUG is not set # CONFIG_MMC_UNSAFE_RESUME is not set # # MMC/SD/SDIO Card Drivers # CONFIG_MMC_BLOCK=m CONFIG_MMC_BLOCK_BOUNCE=y CONFIG_SDIO_UART=m # CONFIG_MMC_TEST is not set # # MMC/SD/SDIO Host Controller Drivers # CONFIG_MMC_SDHCI=m CONFIG_MMC_SDHCI_PCI=m CONFIG_MMC_RICOH_MMC=m CONFIG_MMC_SDHCI_PLTFM=m CONFIG_MMC_WBSD=m CONFIG_MMC_TIFM_SD=m CONFIG_MMC_SDRICOH_CS=m CONFIG_MMC_CB710=m CONFIG_MMC_VIA_SDMMC=m CONFIG_MEMSTICK=m # CONFIG_MEMSTICK_DEBUG is not set # # MemoryStick drivers # # CONFIG_MEMSTICK_UNSAFE_RESUME is not set CONFIG_MSPRO_BLOCK=m # # MemoryStick Host Controller Drivers # CONFIG_MEMSTICK_TIFM_MS=m CONFIG_MEMSTICK_JMICRON_38X=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y # # LED drivers # CONFIG_LEDS_ALIX2=m # CONFIG_LEDS_PCA9532 is not set CONFIG_LEDS_LP3944=m CONFIG_LEDS_CLEVO_MAIL=m # CONFIG_LEDS_PCA955X is not set CONFIG_LEDS_WM8350=m # CONFIG_LEDS_BD2802 is not set # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_HEARTBEAT=m CONFIG_LEDS_TRIGGER_BACKLIGHT=m CONFIG_LEDS_TRIGGER_DEFAULT_ON=m # # iptables trigger is under Netfilter config (LED target) # CONFIG_ACCESSIBILITY=y CONFIG_A11Y_BRAILLE_CONSOLE=y CONFIG_INFINIBAND=m CONFIG_INFINIBAND_USER_MAD=m CONFIG_INFINIBAND_USER_ACCESS=m CONFIG_INFINIBAND_USER_MEM=y CONFIG_INFINIBAND_ADDR_TRANS=y CONFIG_INFINIBAND_MTHCA=m CONFIG_INFINIBAND_MTHCA_DEBUG=y CONFIG_INFINIBAND_IPATH=m CONFIG_INFINIBAND_AMSO1100=m # CONFIG_INFINIBAND_AMSO1100_DEBUG is not set CONFIG_INFINIBAND_CXGB3=m # CONFIG_INFINIBAND_CXGB3_DEBUG is not set CONFIG_MLX4_INFINIBAND=m CONFIG_INFINIBAND_NES=m # CONFIG_INFINIBAND_NES_DEBUG is not set CONFIG_INFINIBAND_IPOIB=m CONFIG_INFINIBAND_IPOIB_CM=y CONFIG_INFINIBAND_IPOIB_DEBUG=y CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y CONFIG_INFINIBAND_SRP=m CONFIG_INFINIBAND_ISER=m CONFIG_EDAC=y # # Reporting subsystems # # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_MM_EDAC=m CONFIG_EDAC_AMD64=m # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_X38=m CONFIG_EDAC_I5400=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m CONFIG_RTC_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_DEBUG is not set # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set # CONFIG_RTC_DRV_TEST is not set # # I2C RTC drivers # CONFIG_RTC_DRV_DS1307=m CONFIG_RTC_DRV_DS1374=m CONFIG_RTC_DRV_DS1672=m CONFIG_RTC_DRV_MAX6900=m CONFIG_RTC_DRV_RS5C372=m CONFIG_RTC_DRV_ISL1208=m CONFIG_RTC_DRV_X1205=m CONFIG_RTC_DRV_PCF8563=m CONFIG_RTC_DRV_PCF8583=m CONFIG_RTC_DRV_M41T80=m CONFIG_RTC_DRV_M41T80_WDT=y # CONFIG_RTC_DRV_S35390A is not set CONFIG_RTC_DRV_FM3130=m CONFIG_RTC_DRV_RX8581=m CONFIG_RTC_DRV_RX8025=m # # SPI RTC drivers # # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=y CONFIG_RTC_DRV_DS1286=m CONFIG_RTC_DRV_DS1511=m CONFIG_RTC_DRV_DS1553=m CONFIG_RTC_DRV_DS1742=m CONFIG_RTC_DRV_STK17TA8=m # CONFIG_RTC_DRV_M48T86 is not set CONFIG_RTC_DRV_M48T35=m CONFIG_RTC_DRV_M48T59=m CONFIG_RTC_DRV_BQ4802=m CONFIG_RTC_DRV_V3020=m CONFIG_RTC_DRV_WM8350=m # # on-CPU RTC drivers # CONFIG_DMADEVICES=y # # DMA Devices # CONFIG_INTEL_IOATDMA=m CONFIG_DMA_ENGINE=y # # DMA Clients # CONFIG_NET_DMA=y CONFIG_ASYNC_TX_DMA=y # CONFIG_DMATEST is not set CONFIG_DCA=m CONFIG_AUXDISPLAY=y CONFIG_KS0108=m CONFIG_KS0108_PORT=0x378 CONFIG_KS0108_DELAY=2 CONFIG_CFAG12864B=m CONFIG_CFAG12864B_RATE=20 CONFIG_UIO=m CONFIG_UIO_CIF=m CONFIG_UIO_PDRV=m CONFIG_UIO_PDRV_GENIRQ=m CONFIG_UIO_SMX=m CONFIG_UIO_AEC=m CONFIG_UIO_SERCOS3=m # # TI VLYNQ # CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=m CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND=m CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_S3=y CONFIG_XEN_MCE=y CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_STAGING=y # CONFIG_STAGING_EXCLUDE_BUILD is not set # CONFIG_ET131X is not set # CONFIG_SLICOSS is not set # CONFIG_SXG is not set # CONFIG_ME4000 is not set # CONFIG_MEILHAUS is not set # CONFIG_VIDEO_GO7007 is not set # CONFIG_USB_IP_COMMON is not set # CONFIG_W35UND is not set # CONFIG_PRISM2_USB is not set # CONFIG_ECHO is not set CONFIG_USB_ATMEL=m # CONFIG_POCH is not set # CONFIG_AGNX is not set # CONFIG_OTUS is not set # CONFIG_RT2860 is not set # CONFIG_RT2870 is not set # CONFIG_RT3070 is not set # CONFIG_COMEDI is not set # CONFIG_ASUS_OLED is not set # CONFIG_PANEL is not set # CONFIG_ALTERA_PCIE_CHDMA is not set # CONFIG_RTL8187SE is not set # CONFIG_RTL8192SU is not set # CONFIG_INPUT_MIMIO is not set # CONFIG_TRANZPORT is not set # CONFIG_EPL is not set # # Android # # CONFIG_ANDROID is not set # CONFIG_DST is not set # CONFIG_POHMELFS is not set # CONFIG_B3DFG is not set # CONFIG_IDE_PHISON is not set # CONFIG_PLAN9AUTH is not set # CONFIG_HECI is not set # CONFIG_LINE6_USB is not set CONFIG_DRM_RADEON_KMS=y # CONFIG_USB_SERIAL_QUATECH2 is not set # CONFIG_VT6655 is not set # CONFIG_USB_CPC is not set # CONFIG_RDC_17F3101X is not set # CONFIG_FB_UDL is not set CONFIG_X86_PLATFORM_DEVICES=y CONFIG_ACER_WMI=m CONFIG_ACERHDF=m CONFIG_ASUS_LAPTOP=m CONFIG_DELL_WMI=m CONFIG_FUJITSU_LAPTOP=m # CONFIG_FUJITSU_LAPTOP_DEBUG is not set CONFIG_HP_WMI=m CONFIG_MSI_LAPTOP=m CONFIG_PANASONIC_LAPTOP=m CONFIG_COMPAL_LAPTOP=m CONFIG_SONY_LAPTOP=m CONFIG_SONYPI_COMPAT=y CONFIG_THINKPAD_ACPI=m # CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set # CONFIG_THINKPAD_ACPI_DEBUG is not set # CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y # CONFIG_INTEL_MENLOW is not set # CONFIG_EEEPC_LAPTOP is not set CONFIG_ACPI_WMI=m # CONFIG_ACPI_ASUS is not set CONFIG_ACPI_TOSHIBA=m # # Firmware Drivers # CONFIG_EDD=m # CONFIG_EDD_OFF is not set CONFIG_FIRMWARE_MEMMAP=y CONFIG_EFI_VARS=y CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y CONFIG_ISCSI_IBFT_FIND=y CONFIG_ISCSI_IBFT=m # # File systems # CONFIG_EXT2_FS=m CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y CONFIG_EXT2_FS_XIP=y CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4_FS=y CONFIG_EXT4DEV_COMPAT=y CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y CONFIG_FS_XIP=y CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=y CONFIG_JBD2_DEBUG=y CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set CONFIG_REISERFS_PROC_INFO=y CONFIG_REISERFS_FS_XATTR=y CONFIG_REISERFS_FS_POSIX_ACL=y CONFIG_REISERFS_FS_SECURITY=y CONFIG_JFS_FS=m CONFIG_JFS_POSIX_ACL=y CONFIG_JFS_SECURITY=y # CONFIG_JFS_DEBUG is not set # CONFIG_JFS_STATISTICS is not set CONFIG_FS_POSIX_ACL=y CONFIG_XFS_FS=m CONFIG_XFS_QUOTA=y CONFIG_XFS_POSIX_ACL=y # CONFIG_XFS_RT is not set # CONFIG_XFS_DEBUG is not set CONFIG_GFS2_FS=m CONFIG_GFS2_FS_LOCKING_DLM=y CONFIG_OCFS2_FS=m CONFIG_OCFS2_FS_O2CB=m CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m # CONFIG_OCFS2_FS_STATS is not set # CONFIG_OCFS2_DEBUG_MASKLOG is not set # CONFIG_OCFS2_DEBUG_FS is not set CONFIG_OCFS2_FS_POSIX_ACL=y CONFIG_BTRFS_FS=m CONFIG_BTRFS_FS_POSIX_ACL=y CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y # CONFIG_PRINT_QUOTA_WARNING is not set CONFIG_QUOTA_TREE=y # CONFIG_QFMT_V1 is not set CONFIG_QFMT_V2=y CONFIG_QUOTACTL=y # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=m CONFIG_FUSE_FS=m CONFIG_CUSE=m CONFIG_GENERIC_ACL=y # # Caches # CONFIG_FSCACHE=m CONFIG_FSCACHE_STATS=y # CONFIG_FSCACHE_HISTOGRAM is not set # CONFIG_FSCACHE_DEBUG is not set CONFIG_CACHEFILES=m # CONFIG_CACHEFILES_DEBUG is not set # CONFIG_CACHEFILES_HISTOGRAM is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="ascii" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_VMCORE=y CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_CONFIGFS_FS=m CONFIG_MISC_FILESYSTEMS=y # CONFIG_ADFS_FS is not set CONFIG_AFFS_FS=m CONFIG_ECRYPT_FS=m CONFIG_HFS_FS=m CONFIG_HFSPLUS_FS=m CONFIG_BEFS_FS=m # CONFIG_BEFS_DEBUG is not set CONFIG_BFS_FS=m CONFIG_EFS_FS=m CONFIG_JFFS2_FS=m CONFIG_JFFS2_FS_DEBUG=0 CONFIG_JFFS2_FS_WRITEBUFFER=y # CONFIG_JFFS2_FS_WBUF_VERIFY is not set CONFIG_JFFS2_SUMMARY=y CONFIG_JFFS2_FS_XATTR=y CONFIG_JFFS2_FS_POSIX_ACL=y CONFIG_JFFS2_FS_SECURITY=y # CONFIG_JFFS2_COMPRESSION_OPTIONS is not set CONFIG_JFFS2_ZLIB=y # CONFIG_JFFS2_LZO is not set CONFIG_JFFS2_RTIME=y # CONFIG_JFFS2_RUBIN is not set CONFIG_UBIFS_FS=m CONFIG_UBIFS_FS_XATTR=y # CONFIG_UBIFS_FS_ADVANCED_COMPR is not set CONFIG_UBIFS_FS_LZO=y CONFIG_UBIFS_FS_ZLIB=y # CONFIG_UBIFS_FS_DEBUG is not set CONFIG_CRAMFS=m CONFIG_SQUASHFS=m # CONFIG_SQUASHFS_EMBEDDED is not set CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 CONFIG_VXFS_FS=m CONFIG_MINIX_FS=m CONFIG_OMFS_FS=m # CONFIG_HPFS_FS is not set CONFIG_QNX4FS_FS=m CONFIG_ROMFS_FS=m CONFIG_ROMFS_BACKED_BY_BLOCK=y # CONFIG_ROMFS_BACKED_BY_MTD is not set # CONFIG_ROMFS_BACKED_BY_BOTH is not set CONFIG_ROMFS_ON_BLOCK=y CONFIG_SYSV_FS=m CONFIG_UFS_FS=m # CONFIG_UFS_FS_WRITE is not set # CONFIG_UFS_DEBUG is not set CONFIG_EXOFS_FS=m # CONFIG_EXOFS_DEBUG is not set CONFIG_NILFS2_FS=m CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=m CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y # CONFIG_NFS_V4_1 is not set CONFIG_NFS_FSCACHE=y CONFIG_NFSD=m CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y CONFIG_NFSD_V4=y CONFIG_LOCKD=m CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=m CONFIG_NFS_ACL_SUPPORT=m CONFIG_NFS_COMMON=y CONFIG_SUNRPC=m CONFIG_SUNRPC_GSS=m CONFIG_SUNRPC_XPRT_RDMA=m CONFIG_RPCSEC_GSS_KRB5=m CONFIG_RPCSEC_GSS_SPKM3=m # CONFIG_SMB_FS is not set CONFIG_CIFS=m CONFIG_CIFS_STATS=y # CONFIG_CIFS_STATS2 is not set CONFIG_CIFS_WEAK_PW_HASH=y CONFIG_CIFS_UPCALL=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set CONFIG_CIFS_DFS_UPCALL=y CONFIG_CIFS_EXPERIMENTAL=y CONFIG_NCP_FS=m CONFIG_NCPFS_PACKET_SIGNING=y CONFIG_NCPFS_IOCTL_LOCKING=y CONFIG_NCPFS_STRONG=y CONFIG_NCPFS_NFS_NS=y CONFIG_NCPFS_OS2_NS=y CONFIG_NCPFS_SMALLDOS=y CONFIG_NCPFS_NLS=y CONFIG_NCPFS_EXTRAS=y CONFIG_CODA_FS=m # CONFIG_AFS_FS is not set CONFIG_9P_FS=m # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set CONFIG_OSF_PARTITION=y CONFIG_AMIGA_PARTITION=y # CONFIG_ATARI_PARTITION is not set CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y CONFIG_MINIX_SUBPARTITION=y CONFIG_SOLARIS_X86_PARTITION=y CONFIG_UNIXWARE_DISKLABEL=y # CONFIG_LDM_PARTITION is not set CONFIG_SGI_PARTITION=y # CONFIG_ULTRIX_PARTITION is not set CONFIG_SUN_PARTITION=y CONFIG_KARMA_PARTITION=y CONFIG_EFI_PARTITION=y # CONFIG_SYSV68_PARTITION is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="utf8" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=m CONFIG_DLM=m CONFIG_DLM_DEBUG=y # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set # CONFIG_ENABLE_WARN_DEPRECATED is not set CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=2048 CONFIG_MAGIC_SYSRQ=y CONFIG_UNUSED_SYMBOLS=y CONFIG_DEBUG_FS=y CONFIG_HEADERS_CHECK=y CONFIG_DEBUG_KERNEL=y CONFIG_DEBUG_SHIRQ=y CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 CONFIG_DETECT_HUNG_TASK=y # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0 CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y CONFIG_DEBUG_NMI_TIMEOUT=5 CONFIG_TIMER_STATS=y # CONFIG_DEBUG_OBJECTS is not set # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set # CONFIG_DEBUG_KMEMLEAK is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set CONFIG_DEBUG_SPINLOCK_SLEEP=y # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set CONFIG_STACKTRACE=y # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_VIRTUAL is not set # CONFIG_DEBUG_WRITECOUNT is not set CONFIG_DEBUG_MEMORY_INIT=y CONFIG_DEBUG_LIST=y # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y CONFIG_FRAME_POINTER=y CONFIG_BOOT_PRINTK_DELAY=y # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_KPROBES_SANITY_TEST is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_LKDTM is not set # CONFIG_FAULT_INJECTION is not set CONFIG_LATENCYTOP=y # CONFIG_SYSCTL_SYSCALL_CHECK is not set # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FTRACE_NMI_ENTER=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_FTRACE_SYSCALLS=y CONFIG_TRACER_MAX_TRACE=y CONFIG_RING_BUFFER=y CONFIG_FTRACE_NMI_ENTER=y CONFIG_EVENT_TRACING=y CONFIG_CONTEXT_SWITCH_TRACER=y CONFIG_TRACING=y CONFIG_GENERIC_TRACER=y CONFIG_TRACING_SUPPORT=y CONFIG_FTRACE=y CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y # CONFIG_IRQSOFF_TRACER is not set CONFIG_SYSPROF_TRACER=y CONFIG_SCHED_TRACER=y CONFIG_FTRACE_SYSCALLS=y # CONFIG_BOOT_TRACER is not set CONFIG_BRANCH_PROFILE_NONE=y # CONFIG_PROFILE_ANNOTATED_BRANCHES is not set # CONFIG_PROFILE_ALL_BRANCHES is not set CONFIG_POWER_TRACER=y CONFIG_STACK_TRACER=y CONFIG_KMEMTRACE=y CONFIG_WORKQUEUE_TRACER=y CONFIG_BLK_DEV_IO_TRACE=y CONFIG_DYNAMIC_FTRACE=y CONFIG_FUNCTION_PROFILER=y CONFIG_FTRACE_MCOUNT_RECORD=y # CONFIG_FTRACE_STARTUP_TEST is not set # CONFIG_MMIOTRACE is not set CONFIG_RING_BUFFER_BENCHMARK=m CONFIG_PROVIDE_OHCI1394_DMA_INIT=y # CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set CONFIG_BUILD_DOCSRC=y CONFIG_DYNAMIC_DEBUG=y # CONFIG_DMA_API_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y CONFIG_KGDB=y CONFIG_KGDB_SERIAL_CONSOLE=y CONFIG_KGDB_TESTS=y # CONFIG_KGDB_TESTS_ON_BOOT is not set CONFIG_HAVE_ARCH_KMEMCHECK=y CONFIG_STRICT_DEVMEM=y # CONFIG_X86_VERBOSE_BOOTUP is not set CONFIG_EARLY_PRINTK=y CONFIG_EARLY_PRINTK_DBGP=y CONFIG_DEBUG_STACKOVERFLOW=y # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PER_CPU_MAPS is not set # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y CONFIG_DEBUG_RODATA_TEST=y CONFIG_DEBUG_NX_TEST=m # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 CONFIG_DEBUG_BOOT_PARAMS=y # CONFIG_CPA_DEBUG is not set CONFIG_OPTIMIZE_INLINING=y # # Security options # CONFIG_KEYS=y CONFIG_KEYS_DEBUG_PROC_KEYS=y CONFIG_SECURITY=y CONFIG_SECURITYFS=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_NETWORK_XFRM=y # CONFIG_SECURITY_PATH is not set CONFIG_SECURITY_FILE_CAPABILITIES=y # CONFIG_SECURITY_ROOTPLUG is not set CONFIG_LSM_MMAP_MIN_ADDR=65536 CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1 CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set # CONFIG_SECURITY_SMACK is not set # CONFIG_SECURITY_TOMOYO is not set CONFIG_IMA=y CONFIG_IMA_MEASURE_PCR_IDX=10 CONFIG_IMA_AUDIT=y CONFIG_IMA_LSM_RULES=y CONFIG_XOR_BLOCKS=m CONFIG_ASYNC_CORE=m CONFIG_ASYNC_MEMCPY=m CONFIG_ASYNC_XOR=m CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_FIPS=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=m CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m # # Block modes # CONFIG_CRYPTO_CBC=m CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_FPU=m # # Hash modes # CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m # # Digest # CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m # # Ciphers # CONFIG_CRYPTO_AES=m CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m # CONFIG_CRYPTO_SALSA20 is not set CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_TEA=m # CONFIG_CRYPTO_TWOFISH is not set CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m # # Random Number Generation # CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_HW=y CONFIG_CRYPTO_DEV_PADLOCK=m CONFIG_CRYPTO_DEV_PADLOCK_AES=m CONFIG_CRYPTO_DEV_PADLOCK_SHA=m CONFIG_CRYPTO_DEV_HIFN_795X=m CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y CONFIG_VIRTUALIZATION=y CONFIG_KVM=m CONFIG_KVM_INTEL=m CONFIG_KVM_AMD=m CONFIG_KVM_TRACE=y CONFIG_VIRTIO=m CONFIG_VIRTIO_RING=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m CONFIG_BINARY_PRINTF=y # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=m CONFIG_CRC16=y CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=m CONFIG_CRC32=y # CONFIG_CRC7 is not set CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_LZO_COMPRESS=m CONFIG_LZO_DECOMPRESS=m CONFIG_DECOMPRESS_GZIP=y CONFIG_DECOMPRESS_BZIP2=y CONFIG_DECOMPRESS_LZMA=y CONFIG_GENERIC_ALLOCATOR=y CONFIG_REED_SOLOMON=m CONFIG_REED_SOLOMON_DEC16=y CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_CHECK_SIGNATURE=y CONFIG_NLATTR=y [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 21:01 ` Joanna Rutkowska @ 2010-03-12 21:13 ` Joanna Rutkowska 2010-03-12 23:48 ` Jeremy Fitzhardinge 0 siblings, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-12 21:13 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: Tobias Geiger, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 3096 bytes --] On 03/12/2010 10:01 PM, Joanna Rutkowska wrote: > On 03/12/2010 11:02 PM, Jeremy Fitzhardinge wrote: >> On 03/12/2010 01:56 PM, Tobias Geiger wrote: >>> kbpc2:~# cat >>> /sys/devices/system/clocksource/clocksource0/current_clocksource >>> xen >>> kbpc2:~# cat >>> /sys/devices/system/clocksource/clocksource0/available_clocksource >>> xen >>> kbpc2:~# echo "jiffies" >>> >>>> /sys/devices/system/clocksource/clocksource0/current_clocksource >>>> >>> kbpc2:~# dmesg | tail -1 >>> [ 7898.642404] Override clocksource jiffies is not HRT compatible. >>> Cannot switch >>> while in HRT/NOHZ mode >>> kbpc2:~# >>> >>> Seems like it's not possible to switch to jiffies - however: >>> kbpc2:~# zcat /proc/config.gz | grep NO_HZ >>> # CONFIG_NO_HZ is not set >>> >>> but CONFIG_SCHED_HRTICK=y >>> >> >> Interesting. BTW, does NO_HZ change the behaviour of this? In >> principle NO_HZ should be preferable, and particularly in a virtual >> machine since it should limit the number of timer interrupts. >> >> Joanna, are you using NO_HZ? >> > Yes, I have: > CONFIG_NO_HZ=y > > BTW, FWIW, I'm attaching my kernel config. It's almost the same as the > previously mentioned "Young's Dec23" kernel (the only difference being > some more recent pvops git patches applied and pcifront being enabled as > a module). > > While trying to switch from xen source to jiffies source, I got the same > message as Tobias: > > jiffies clocksource is not HRT compatible. Cannot switch while in > HRT/NOHZ mode > > I can definitely say that this previously mentioned warning from hrtimer > about interrupt being too slow is the marking of the start of all the > troubles. E.g. when I run my Dom0 for some time without starting any > other VMs, the system behaves good, and no warning in dmesg. Only after > I start a VM, and probably depending on how heavy load it produces, the > warning appears in Dom0 dmesg and the problem becomes "feelable". And, > depending on what new "delta" is being chosen, the system is either > still usable -- e.g. with a delta like in this case: > > hrtimer: interrupt too slow, forcing clock min delta to 82595226 ns > > which is around 80ms (still the very subtle hiccups can be observed when > you press and hold a key for some time), or totally unusable, if one is > unlucky, and the "safe" delta got chosen to be something around 0.5s > (which interestingly happens most often in my case). > > The "clocksource tsc unstable" messages trouble me too BTW. They seem to > appear before the hrtimer "interrupt too slow" messages. > But this "tsc unstable" message does not seem to be so critical, e.g. I just started my system (xen clocksource) and started a VM, and got the usual hrtimer "slow interrupt" warning, and then all the symptoms started, but there no "tsc unstables" warning in dmesg. However, I previously missed another message, that seem to occur at the very beginning of the system life (before I started any other VMs): Marking TSC unstable due to TSC halts in idle j. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 21:13 ` Joanna Rutkowska @ 2010-03-12 23:48 ` Jeremy Fitzhardinge 2010-03-13 9:58 ` Joanna Rutkowska 0 siblings, 1 reply; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-12 23:48 UTC (permalink / raw) To: Joanna Rutkowska; +Cc: Tobias Geiger, xen-devel On 03/12/2010 01:13 PM, Joanna Rutkowska wrote: > >> The "clocksource tsc unstable" messages trouble me too BTW. They seem to >> appear before the hrtimer "interrupt too slow" messages. >> >> > But this "tsc unstable" message does not seem to be so critical, They're nothing to worry about. > e.g. I > just started my system (xen clocksource) and started a VM, and got the > usual hrtimer "slow interrupt" warning, and then all the symptoms > started, but there no "tsc unstables" warning in dmesg. > > However, I previously missed another message, that seem to occur at the > very beginning of the system life (before I started any other VMs): > > Marking TSC unstable due to TSC halts in idle > That doesn't matter because it doesn't use the tsc clocksource. The Xen clocksource uses the tsc hardware register, but it isn't subject to the same constraints that the tsc clocksource is. The tsc clocksource calibration is probably getting confused by being on a vcpu. J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 23:48 ` Jeremy Fitzhardinge @ 2010-03-13 9:58 ` Joanna Rutkowska 2010-03-13 19:30 ` Jeremy Fitzhardinge 0 siblings, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-13 9:58 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: Tobias Geiger, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 1436 bytes --] On 03/13/2010 12:48 AM, Jeremy Fitzhardinge wrote: > On 03/12/2010 01:13 PM, Joanna Rutkowska wrote: >> >>> The "clocksource tsc unstable" messages trouble me too BTW. They seem to >>> appear before the hrtimer "interrupt too slow" messages. >>> >>> >> But this "tsc unstable" message does not seem to be so critical, > > They're nothing to worry about. > >> e.g. I >> just started my system (xen clocksource) and started a VM, and got the >> usual hrtimer "slow interrupt" warning, and then all the symptoms >> started, but there no "tsc unstables" warning in dmesg. >> >> However, I previously missed another message, that seem to occur at the >> very beginning of the system life (before I started any other VMs): >> >> Marking TSC unstable due to TSC halts in idle >> > > That doesn't matter because it doesn't use the tsc clocksource. The Xen > clocksource uses the tsc hardware register, but it isn't subject to the > same constraints that the tsc clocksource is. The tsc clocksource > calibration is probably getting confused by being on a vcpu. > In the meantime found a similar thread on KVM: http://www.mail-archive.com/kvm@vger.kernel.org/msg22925.html and also a patch suggested there: http://www.mail-archive.com/kvm@vger.kernel.org/msg23491.html Don't have time to try the patch right now, but courious to hear your opinion in the meantime... Thanks, joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-13 9:58 ` Joanna Rutkowska @ 2010-03-13 19:30 ` Jeremy Fitzhardinge 2010-03-15 6:49 ` Tobias Geiger 2010-03-16 6:01 ` Joanna Rutkowska 0 siblings, 2 replies; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-13 19:30 UTC (permalink / raw) To: Joanna Rutkowska; +Cc: Tobias Geiger, xen-devel On 03/13/2010 01:58 AM, Joanna Rutkowska wrote: > In the meantime found a similar thread on KVM: > http://www.mail-archive.com/kvm@vger.kernel.org/msg22925.html > > and also a patch suggested there: > > http://www.mail-archive.com/kvm@vger.kernel.org/msg23491.html > > Don't have time to try the patch right now, but courious to hear your > opinion in the meantime... > I was just looking at that logic yesterday and was approaching a similar conclusion, so I'm glad Marcelo sorted it out. It looks like a variant of that patch got into 2.6.33 (41d2e4949377) , so I'll look at backporting it. Actually it's probably -stable material. J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-13 19:30 ` Jeremy Fitzhardinge @ 2010-03-15 6:49 ` Tobias Geiger 2010-03-16 6:01 ` Joanna Rutkowska 1 sibling, 0 replies; 42+ messages in thread From: Tobias Geiger @ 2010-03-15 6:49 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: xen-devel, Joanna Rutkowska > It looks like a variant > of that patch got into 2.6.33 (41d2e4949377) > according to http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=commit;h=41d2e4949377 there is a /proc/timer_list - here is mine with 2.6.33 and CONFIG_NOHZ active: Timer List Version: v0.5 HRTIMER_MAX_CLOCK_BASES: 2 now at 39700078385698 nsecs cpu: 0 clock 0: .base: ffff880008013f08 .index: 0 .resolution: 1 nsecs .get_time: ktime_get_real .offset: 1268594403242758210 nsecs active timers: clock 1: .base: ffff880008013f48 .index: 1 .resolution: 1 nsecs .get_time: ktime_get .offset: 0 nsecs active timers: #0: <ffff8800ec2f1948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, xend/14751 # expires at 39700088244281-39700088294281 nsecs [in 9858583 to 9908583 nsecs] #1: <ffff88011de87a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, kwin/3976 # expires at 39700088517904-39700088567904 nsecs [in 10132206 to 10182206 nsecs] #2: <ffff880114271a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, gkrellm/4029 # expires at 39700090903507-39700090953507 nsecs [in 12517809 to 12567809 nsecs] #3: <ffff880008013fe0>, tick_sched_timer, S:01, tick_nohz_stop_sched_tick, swapper/0 # expires at 39700319000000-39700319000000 nsecs [in 240614302 to 240614302 nsecs] #4: <ffff8801172f5a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, plasma- desktop/3980 # expires at 39700375492906-39700375841905 nsecs [in 297107208 to 297456207 nsecs] #5: <ffff88010e1cda78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, gkrellm/4030 # expires at 39700513816021-39700514369020 nsecs [in 435430323 to 435983322 nsecs] #6: <ffff88010e1cfa78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, gkrellm/4031 # expires at 39700928500172-39700929452171 nsecs [in 850114474 to 851066473 nsecs] #7: <ffff8801eeeb1948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, xend/2498 # expires at 39701136632456-39701138632455 nsecs [in 1058246758 to 1060246757 nsecs] #8: <ffff8801ecff7a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, avahi- daemon/2643 # expires at 39701630089942-39701658854941 nsecs [in 1551704244 to 1580469243 nsecs] #9: <ffff8801edd05948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, munin- node/2936 # expires at 39701811354852-39701813354851 nsecs [in 1732969154 to 1734969153 nsecs] #10: <ffff8801ead57a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, ntpd/1863 # expires at 39805530083909-39805630083909 nsecs [in 105451698211 to 105551698211 nsecs] #11: <ffff8800da159948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, rsyslogd/16096 # expires at 39911498142700-39911598142700 nsecs [in 211419757002 to 211519757002 nsecs] .expires_next : 39700088294281 nsecs .hres_active : 1 .nr_events : 17061828 .nr_retries : 3170 .nr_hangs : 0 .max_hang_time : 0 nsecs .nohz_mode : 2 .idle_tick : 39700077000000 nsecs .tick_stopped : 1 .idle_jiffies : 4334367373 .idle_calls : 54289068 .idle_sleeps : 34911450 .idle_entrytime : 39700077164622 nsecs .idle_waketime : 39700077116565 nsecs .idle_exittime : 39700074096546 nsecs .idle_sleeptime : 31394496198384 nsecs .last_jiffies : 4334367374 .next_jiffies : 4334367616 .idle_expires : 39700319000000 nsecs jiffies: 4334367375 cpu: 1 clock 0: .base: ffff880008026f08 .index: 0 .resolution: 1 nsecs .get_time: ktime_get_real .offset: 1268594403242758210 nsecs active timers: clock 1: .base: ffff880008026f48 .index: 1 .resolution: 1 nsecs .get_time: ktime_get .offset: 0 nsecs active timers: #0: <ffff880008026fe0>, tick_sched_timer, S:01, tick_nohz_restart_sched_tick, swapper/0 # expires at 39700079083333-39700079083333 nsecs [in 697635 to 697635 nsecs] #1: <ffff8801ebdb6468>, it_real_fn, S:01, do_setitimer, uml_switch/2130 # expires at 39700827086561-39700827086561 nsecs [in 748700863 to 748700863 nsecs] #2: <ffff88000396f948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, dirmngr/16013 # expires at 39700984969090-39700985969086 nsecs [in 906583392 to 907583388 nsecs] #3: <ffffffff816c1838>, sched_rt_period_timer, S:01, enqueue_task_rt, swapper/1 # expires at 39701000000000-39701000000000 nsecs [in 921614302 to 921614302 nsecs] #4: <ffff8801ee5df948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, mysqld/2346 # expires at 39702678123264-39702683123263 nsecs [in 2599737566 to 2604737565 nsecs] #5: <ffff8801eeea5948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, xend/2496 # expires at 100000015827667689-100000015927667689 nsecs [in 99960315749281991 to 99960315849281991 nsecs] .expires_next : 39700079083333 nsecs .hres_active : 1 .nr_events : 15140240 .nr_retries : 964 .nr_hangs : 1 .max_hang_time : 3968056 nsecs .nohz_mode : 2 .idle_tick : 39699985083333 nsecs .tick_stopped : 0 .idle_jiffies : 4334367281 .idle_calls : 20003807 .idle_sleeps : 5904872 .idle_entrytime : 39700078089128 nsecs .idle_waketime : 39700076359045 nsecs .idle_exittime : 39700076361140 nsecs .idle_sleeptime : 37710292484734 nsecs .last_jiffies : 4334367374 .next_jiffies : 4334367375 .idle_expires : 39701700000000 nsecs jiffies: 4334367375 cpu: 2 clock 0: .base: ffff880008039f08 .index: 0 .resolution: 1 nsecs .get_time: ktime_get_real .offset: 1268594403242758210 nsecs active timers: clock 1: .base: ffff880008039f48 .index: 1 .resolution: 1 nsecs .get_time: ktime_get .offset: 0 nsecs active timers: #0: <ffff880008039fe0>, tick_sched_timer, S:01, tick_nohz_restart_sched_tick, swapper/0 # expires at 39700079166666-39700079166666 nsecs [in 780968 to 780968 nsecs] #1: <ffff8801098aba78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, amarok/4040 # expires at 39700121985119-39700122084118 nsecs [in 43599421 to 43698420 nsecs] #2: <ffff880114253a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, klipper/4011 # expires at 39700334245968-39700335244967 nsecs [in 255860270 to 256859269 nsecs] #3: <ffff8801143f9a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, kmix/4018 # expires at 39700351305204-39700353303203 nsecs [in 272919506 to 274917505 nsecs] #4: <ffff8801ee6bfa78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, kontact/4039 # expires at 39700432386829-39700433385828 nsecs [in 354001131 to 355000130 nsecs] #5: <ffff8801ecd63948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, mysqld/2344 # expires at 39701067743916-39701068743915 nsecs [in 989358218 to 990358217 nsecs] #6: <ffff88011dd5ba78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, kded4/3950 # expires at 39701351300666-39701356298665 nsecs [in 1272914968 to 1277912967 nsecs] #7: <ffff8801098e1a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, akonadiserver/4049 # expires at 39701849232912-39701855575911 nsecs [in 1770847214 to 1777190213 nsecs] #8: <ffff88012091b948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, gpg- agent/3856 # expires at 39702757252653-39702760249600 nsecs [in 2678866955 to 2681863902 nsecs] #9: <ffff880109b03a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, akonadi_control/4047 # expires at 39707457215355-39707467205354 nsecs [in 7378829657 to 7388819656 nsecs] #10: <ffff8801edd43eb8>, hrtimer_wakeup, S:01, do_nanosleep, cron/2170 # expires at 39718231470880-39718231520880 nsecs [in 18153085182 to 18153135182 nsecs] #11: <ffff8800ec3f9d28>, hrtimer_wakeup, S:01, futex_wait_queue_me, rsyslogd/12234 # expires at 39733019433875-39733019483875 nsecs [in 32941048177 to 32941098177 nsecs] #12: <ffff8801ee14f948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, mdadm/2194 # expires at 40019833645109-40019933645109 nsecs [in 319755259411 to 319855259411 nsecs] .expires_next : 39700079166666 nsecs .hres_active : 1 .nr_events : 6718421 .nr_retries : 1069 .nr_hangs : 0 .max_hang_time : 0 nsecs .nohz_mode : 2 .idle_tick : 39700068166666 nsecs .tick_stopped : 0 .idle_jiffies : 4334367364 .idle_calls : 8721853 .idle_sleeps : 3768379 .idle_entrytime : 39700067749764 nsecs .idle_waketime : 39700076873579 nsecs .idle_exittime : 39700076874813 nsecs .idle_sleeptime : 37892101915060 nsecs .last_jiffies : 4334367364 .next_jiffies : 4334367500 .idle_expires : 39700203000000 nsecs jiffies: 4334367375 cpu: 3 clock 0: .base: ffff88000804cf08 .index: 0 .resolution: 1 nsecs .get_time: ktime_get_real .offset: 1268594403242758210 nsecs active timers: clock 1: .base: ffff88000804cf48 .index: 1 .resolution: 1 nsecs .get_time: ktime_get .offset: 0 nsecs active timers: #0: <ffff88000804cfe0>, tick_sched_timer, S:01, tick_nohz_restart_sched_tick, swapper/0 # expires at 39700079249999-39700079249999 nsecs [in 864301 to 864301 nsecs] #1: <ffff8801efc9f948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, init/1 # expires at 39702931328063-39702936328062 nsecs [in 2852942365 to 2857942364 nsecs] .expires_next : 39700079249999 nsecs .hres_active : 1 .nr_events : 7019712 .nr_retries : 703 .nr_hangs : 0 .max_hang_time : 0 nsecs .nohz_mode : 2 .idle_tick : 39697932249999 nsecs .tick_stopped : 0 .idle_jiffies : 4334365228 .idle_calls : 15211478 .idle_sleeps : 11625422 .idle_entrytime : 39699938261592 nsecs .idle_waketime : 39698025114890 nsecs .idle_exittime : 39698025116159 nsecs .idle_sleeptime : 37962384222924 nsecs .last_jiffies : 4334367235 .next_jiffies : 4334367236 .idle_expires : 39698029000000 nsecs jiffies: 4334367375 cpu: 4 clock 0: .base: ffff88000805ff08 .index: 0 .resolution: 1 nsecs .get_time: ktime_get_real .offset: 1268594403242758210 nsecs active timers: clock 1: .base: ffff88000805ff48 .index: 1 .resolution: 1 nsecs .get_time: ktime_get .offset: 0 nsecs active timers: #0: <ffff88000805ffe0>, tick_sched_timer, S:01, tick_nohz_restart_sched_tick, swapper/0 # expires at 39700079333332-39700079333332 nsecs [in 947634 to 947634 nsecs] #1: <ffff8801ecd77948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, mysqld/2345 # expires at 39700515448847-39700516448846 nsecs [in 437063149 to 438063148 nsecs] #2: <ffff8801ee069a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, hald- addon-stor/2731 # expires at 39700757370965-39700759288964 nsecs [in 678985267 to 680903266 nsecs] #3: <ffff8801ee5b9a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, hald- addon-stor/2732 # expires at 39700757368857-39700759355856 nsecs [in 678983159 to 680970158 nsecs] #4: <ffff8801eedcfa78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, krunner/4005 # expires at 39700965439836-39700966438835 nsecs [in 887054138 to 888053137 nsecs] #5: <ffff8801ee0ffa78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, hald- addon-stor/2730 # expires at 39701757375385-39701759293384 nsecs [in 1678989687 to 1680907686 nsecs] #6: <ffff8801ecc95948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, winbindd/2445 # expires at 39704287532303-39704317532302 nsecs [in 4209146605 to 4239146604 nsecs] #7: <ffff88011dc59a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, klauncher/3948 # expires at 39704522370930-39704532360929 nsecs [in 4443985232 to 4453975231 nsecs] #8: <ffff8801eed35a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, hald/2691 # expires at 39708757725862-39708787723861 nsecs [in 8679340164 to 8709338163 nsecs] #9: <ffff880120af7a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, console-kit-dae/3640 # expires at 39711757158054-39711787158053 nsecs [in 11678772356 to 11708772355 nsecs] #10: <ffff8801ec733468>, it_real_fn, S:01, do_setitimer, qmgr/2821 # expires at 39950643408313-39950643408313 nsecs [in 250565022615 to 250565022615 nsecs] #11: <ffff8801efd64868>, it_real_fn, S:01, do_setitimer, master/2812 # expires at 40010643498250-40010643498250 nsecs [in 310565112552 to 310565112552 nsecs] #12: <ffff8801ebe03eb8>, hrtimer_wakeup, S:01, do_nanosleep, atd/2149 # expires at 43215598718315-43215598768315 nsecs [in 3515520332617 to 3515520382617 nsecs] #13: <ffff8801ebdc2068>, it_real_fn, S:01, do_setitimer, pickup/15002 # expires at 45677643431329-45677643431329 nsecs [in 5977565045631 to 5977565045631 nsecs] .expires_next : 39700079333332 nsecs .hres_active : 1 .nr_events : 5181117 .nr_retries : 1352 .nr_hangs : 2 .max_hang_time : 31154440 nsecs .nohz_mode : 2 .idle_tick : 39698048333332 nsecs .tick_stopped : 0 .idle_jiffies : 4334365344 .idle_calls : 6885906 .idle_sleeps : 3874150 .idle_entrytime : 39700078338583 nsecs .idle_waketime : 39698051036847 nsecs .idle_exittime : 39698051038239 nsecs .idle_sleeptime : 37271606112519 nsecs .last_jiffies : 4334367375 .next_jiffies : 4334367411 .idle_expires : 39698691000000 nsecs jiffies: 4334367375 cpu: 5 clock 0: .base: ffff880008072f08 .index: 0 .resolution: 1 nsecs .get_time: ktime_get_real .offset: 1268594403242758210 nsecs active timers: clock 1: .base: ffff880008072f48 .index: 1 .resolution: 1 nsecs .get_time: ktime_get .offset: 0 nsecs active timers: #0: <ffff8801ee259a78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, cupsd/2838 # expires at 39700188554200-39700199554199 nsecs [in 110168502 to 121168501 nsecs] #1: <ffff88011437da78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, kwalletd/4132 # expires at 39701350568747-39701355563746 nsecs [in 1272183049 to 1277178048 nsecs] #2: <ffff880008072fe0>, tick_sched_timer, S:01, tick_nohz_stop_sched_tick, swapper/0 # expires at 39701688000000-39701688000000 nsecs [in 1609614302 to 1609614302 nsecs] #3: <ffff8801ec4c5d28>, hrtimer_wakeup, S:01, futex_wait_queue_me, bacula- fd/3492 # expires at 39709742894693-39709742944693 nsecs [in 9664508995 to 9664558995 nsecs] #4: <ffff8801142fda78>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, korgac/4019 # expires at 39748359758573-39748419730572 nsecs [in 48281372875 to 48341344874 nsecs] #5: <ffff8801ee15b948>, hrtimer_wakeup, S:01, schedule_hrtimeout_range, rsyslogd/2096 # expires at 122711318146941-122711418146941 nsecs [in 83011239761243 to 83011339761243 nsecs] .expires_next : 39700199554199 nsecs .hres_active : 1 .nr_events : 3946402 .nr_retries : 883 .nr_hangs : 2 .max_hang_time : 2960096 nsecs .nohz_mode : 2 .idle_tick : 39699958416665 nsecs .tick_stopped : 1 .idle_jiffies : 4334367254 .idle_calls : 5770603 .idle_sleeps : 3654532 .idle_entrytime : 39699957423004 nsecs .idle_waketime : 39699921692874 nsecs .idle_exittime : 39699921694130 nsecs .idle_sleeptime : 37835103396410 nsecs .last_jiffies : 4334367254 .next_jiffies : 4334368985 .idle_expires : 39701688000000 nsecs jiffies: 4334367375 Tick Device: mode: 1 Per CPU device: 0 Clock Event Device: xen max_delta_ns: 4294967295 min_delta_ns: 100000 mult: 1 shift: 0 mode: 3 next_event: 39700088294281 nsecs set_next_event: vcpuop_set_next_event set_mode: vcpuop_set_mode event_handler: hrtimer_interrupt Tick Device: mode: 1 Per CPU device: 1 Clock Event Device: xen max_delta_ns: 4294967295 min_delta_ns: 100000 mult: 1 shift: 0 mode: 3 next_event: 39700079083333 nsecs set_next_event: vcpuop_set_next_event set_mode: vcpuop_set_mode event_handler: hrtimer_interrupt Tick Device: mode: 1 Per CPU device: 2 Clock Event Device: xen max_delta_ns: 4294967295 min_delta_ns: 100000 mult: 1 shift: 0 mode: 3 next_event: 39700079166666 nsecs set_next_event: vcpuop_set_next_event set_mode: vcpuop_set_mode event_handler: hrtimer_interrupt Tick Device: mode: 1 Per CPU device: 3 Clock Event Device: xen max_delta_ns: 4294967295 min_delta_ns: 100000 mult: 1 shift: 0 mode: 3 next_event: 39700079249999 nsecs set_next_event: vcpuop_set_next_event set_mode: vcpuop_set_mode event_handler: hrtimer_interrupt Tick Device: mode: 1 Per CPU device: 4 Clock Event Device: xen max_delta_ns: 4294967295 min_delta_ns: 100000 mult: 1 shift: 0 mode: 3 next_event: 39700079333332 nsecs set_next_event: vcpuop_set_next_event set_mode: vcpuop_set_mode event_handler: hrtimer_interrupt Tick Device: mode: 1 Per CPU device: 5 Clock Event Device: xen max_delta_ns: 4294967295 min_delta_ns: 100000 mult: 1 shift: 0 mode: 3 next_event: 39700199554199 nsecs set_next_event: vcpuop_set_next_event set_mode: vcpuop_set_mode event_handler: hrtimer_interrupt This is after some uptime with HVM guest active. As the ".nr_retries" indicate i still experience small hiccups, not long ones (but definitly longer than 100ms) but still quite annoying. CONFIG_NOHZ definitly helps, but not enough. Greetings Tobias ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-13 19:30 ` Jeremy Fitzhardinge 2010-03-15 6:49 ` Tobias Geiger @ 2010-03-16 6:01 ` Joanna Rutkowska 2010-03-17 13:35 ` Tobias Geiger 1 sibling, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-16 6:01 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: Tobias Geiger, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 907 bytes --] On 03/13/2010 08:30 PM, Jeremy Fitzhardinge wrote: > On 03/13/2010 01:58 AM, Joanna Rutkowska wrote: >> In the meantime found a similar thread on KVM: >> http://www.mail-archive.com/kvm@vger.kernel.org/msg22925.html >> >> and also a patch suggested there: >> >> http://www.mail-archive.com/kvm@vger.kernel.org/msg23491.html >> >> Don't have time to try the patch right now, but courious to hear your >> opinion in the meantime... >> > > I was just looking at that logic yesterday and was approaching a similar > conclusion, so I'm glad Marcelo sorted it out. It looks like a variant > of that patch got into 2.6.33 (41d2e4949377) , so I'll look at > backporting it. Actually it's probably -stable material. > FWIW, I have finally built and now I'm testing the recent xen/stable-2.6.32.x with the hrtimer commit and it seems to be working fine. No hiccups. Thanks, joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-16 6:01 ` Joanna Rutkowska @ 2010-03-17 13:35 ` Tobias Geiger 2010-03-17 15:21 ` Joanna Rutkowska ` (2 more replies) 0 siblings, 3 replies; 42+ messages in thread From: Tobias Geiger @ 2010-03-17 13:35 UTC (permalink / raw) To: Joanna Rutkowska; +Cc: Jeremy Fitzhardinge, xen-devel Hi, i also compiled 2.6.32.9 from xen/stable , but so far i can't see much improvement. Still many small hiccups in Dom0 One time (i think after HVM DomU creation) i get: "hrtimer: interrupt took 4045137 ns" in Dom0 dmesg I also upgraded to newest xen-unstable: xen_changeset : Wed Mar 17 09:18:34 2010 +0000 21041:066c3eead6ec Could it be that the missing HPET is causing all this trouble? I just noticed that in "xm dmesg" : (XEN) CPUIDLE: disabled due to no HPET. Force enable with \047cpuidle\047. I don't bother really about CPUIDLE, but i should perhaps about HPET ? Is there a reason xen doesn't enable HPET? Motherboard is Intel DX58SO Thanks for your input Greetings Tobias Am Dienstag 16 März 2010 07:01:44 schrieb Joanna Rutkowska: > FWIW, I have finally built and now I'm testing the recent > xen/stable-2.6.32.x with the hrtimer commit and it seems to be working > fine. No hiccups. > ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-17 13:35 ` Tobias Geiger @ 2010-03-17 15:21 ` Joanna Rutkowska 2010-03-17 16:20 ` Jeremy Fitzhardinge 2010-03-17 16:26 ` Dan Magenheimer 2 siblings, 0 replies; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-17 15:21 UTC (permalink / raw) To: Tobias Geiger; +Cc: Jeremy Fitzhardinge, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 481 bytes --] On 03/17/2010 02:35 PM, Tobias Geiger wrote: > Hi, > > i also compiled 2.6.32.9 from xen/stable , but so far i can't see much > improvement. > > Still many small hiccups in Dom0 > One time (i think after HVM DomU creation) i get: > "hrtimer: interrupt took 4045137 ns" in Dom0 dmesg > > I also upgraded to newest xen-unstable: > xen_changeset : Wed Mar 17 09:18:34 2010 +0000 21041:066c3eead6ec > > FWIW, I'm running under Xen 3.4.3-rc3. joanna. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-17 13:35 ` Tobias Geiger 2010-03-17 15:21 ` Joanna Rutkowska @ 2010-03-17 16:20 ` Jeremy Fitzhardinge 2010-03-17 17:05 ` Joanna Rutkowska 2010-03-17 16:26 ` Dan Magenheimer 2 siblings, 1 reply; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-17 16:20 UTC (permalink / raw) To: Tobias Geiger; +Cc: xen-devel, Joanna Rutkowska On 03/17/2010 06:35 AM, Tobias Geiger wrote: > i also compiled 2.6.32.9 from xen/stable , but so far i can't see much > improvement. > I'm not certain you got the relevent changeset; the "xen/stable" branch now has it, but I think I only updated it yesterday. xen/stable is now 2.6.32.10. > Still many small hiccups in Dom0 > One time (i think after HVM DomU creation) i get: > "hrtimer: interrupt took 4045137 ns" in Dom0 dmesg > That's only 4ms. Not great, but not too bad. > I also upgraded to newest xen-unstable: > xen_changeset : Wed Mar 17 09:18:34 2010 +0000 21041:066c3eead6ec > > > Could it be that the missing HPET is causing all this trouble? I just noticed > that in "xm dmesg" : > > (XEN) CPUIDLE: disabled due to no HPET. Force enable with \047cpuidle\047. > > I don't bother really about CPUIDLE, but i should perhaps about HPET ? > Is there a reason xen doesn't enable HPET? Motherboard is Intel DX58SO > I don't think that will be relevent. J ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-17 16:20 ` Jeremy Fitzhardinge @ 2010-03-17 17:05 ` Joanna Rutkowska 2010-03-17 17:21 ` Jeremy Fitzhardinge 0 siblings, 1 reply; 42+ messages in thread From: Joanna Rutkowska @ 2010-03-17 17:05 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: Tobias Geiger, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 785 bytes --] On 03/17/2010 05:20 PM, Jeremy Fitzhardinge wrote: > On 03/17/2010 06:35 AM, Tobias Geiger wrote: >> i also compiled 2.6.32.9 from xen/stable , but so far i can't see much >> improvement. >> > > I'm not certain you got the relevent changeset; the "xen/stable" branch > now has it, but I think I only updated it yesterday. xen/stable is now > 2.6.32.10. > > Correct, I used the xen/stable-2.6.32.x and indeed the xen/stable back a few days ago did not have this hrtimer commit. Jeremy, I think there might be some confusion about xen/stable vs. xen/stable-2.6.32.x as from your earlier email [1] it looked like those should be the same things, while in fact they are not. j. [1] http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00162.html [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 226 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-17 17:05 ` Joanna Rutkowska @ 2010-03-17 17:21 ` Jeremy Fitzhardinge 0 siblings, 0 replies; 42+ messages in thread From: Jeremy Fitzhardinge @ 2010-03-17 17:21 UTC (permalink / raw) To: Joanna Rutkowska; +Cc: Tobias Geiger, xen-devel On 03/17/2010 10:05 AM, Joanna Rutkowska wrote: > On 03/17/2010 05:20 PM, Jeremy Fitzhardinge wrote: > >> On 03/17/2010 06:35 AM, Tobias Geiger wrote: >> >>> i also compiled 2.6.32.9 from xen/stable , but so far i can't see much >>> improvement. >>> >>> >> I'm not certain you got the relevent changeset; the "xen/stable" branch >> now has it, but I think I only updated it yesterday. xen/stable is now >> 2.6.32.10. >> >> >> > Correct, I used the xen/stable-2.6.32.x and indeed the xen/stable back a > few days ago did not have this hrtimer commit. > > Jeremy, I think there might be some confusion about xen/stable vs. > xen/stable-2.6.32.x as from your earlier email [1] it looked like those > should be the same things, while in fact they are not. > Keeping them in sync is manual, and I forgot in that case. Well, I could justify it as being conservative in case the change introduced a regression. J ^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: A clocksource question 2010-03-17 13:35 ` Tobias Geiger 2010-03-17 15:21 ` Joanna Rutkowska 2010-03-17 16:20 ` Jeremy Fitzhardinge @ 2010-03-17 16:26 ` Dan Magenheimer 2 siblings, 0 replies; 42+ messages in thread From: Dan Magenheimer @ 2010-03-17 16:26 UTC (permalink / raw) To: Tobias Geiger, Joanna Rutkowska; +Cc: Jeremy Fitzhardinge, xen-devel On many machines, HPET is disabled by default, but can be enabled in the pre-boot BIOS configuration screens. > -----Original Message----- > From: Tobias Geiger [mailto:tobias.geiger@vido.info] > Sent: Wednesday, March 17, 2010 7:36 AM > To: Joanna Rutkowska > Cc: Jeremy Fitzhardinge; xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] A clocksource question > > Hi, > > i also compiled 2.6.32.9 from xen/stable , but so far i can't see much > improvement. > > Still many small hiccups in Dom0 > One time (i think after HVM DomU creation) i get: > "hrtimer: interrupt took 4045137 ns" in Dom0 dmesg > > I also upgraded to newest xen-unstable: > xen_changeset : Wed Mar 17 09:18:34 2010 +0000 > 21041:066c3eead6ec > > > Could it be that the missing HPET is causing all this trouble? I just > noticed > that in "xm dmesg" : > > (XEN) CPUIDLE: disabled due to no HPET. Force enable with > \047cpuidle\047. > > I don't bother really about CPUIDLE, but i should perhaps about HPET ? > Is there a reason xen doesn't enable HPET? Motherboard is Intel DX58SO > > Thanks for your input > > Greetings > Tobias > > > > > > Am Dienstag 16 März 2010 07:01:44 schrieb Joanna Rutkowska: > > FWIW, I have finally built and now I'm testing the recent > > xen/stable-2.6.32.x with the hrtimer commit and it seems to be > working > > fine. No hiccups. > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-12 22:02 ` Jeremy Fitzhardinge 2010-03-12 21:01 ` Joanna Rutkowska @ 2010-03-12 22:56 ` Tobias Geiger 1 sibling, 0 replies; 42+ messages in thread From: Tobias Geiger @ 2010-03-12 22:56 UTC (permalink / raw) To: xen-devel Am Freitag 12 März 2010 23:02:38 schrieb Jeremy Fitzhardinge: > BTW, does NO_HZ change the behaviour of this? > Oh yes! It does :) Seems like thats the key, at least for the very long and really annoying "hiccups" Whats remaining are very short hiccups (some tenths of a second or so) - seems to be related to heavy disk load or... well i can't tell exactly from the short time NO_HZ is active here. Thanks so far - this is a HUGE improvment, at least here! Greetings and have a nice Weekend! Tobias ^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: A clocksource question 2010-03-10 22:13 ` Joanna Rutkowska 2010-03-11 0:07 ` Dan Magenheimer @ 2010-03-11 7:47 ` Keir Fraser 1 sibling, 0 replies; 42+ messages in thread From: Keir Fraser @ 2010-03-11 7:47 UTC (permalink / raw) To: Joanna Rutkowska, Jeremy Fitzhardinge; +Cc: xen-devel@lists.xensource.com On 10/03/2010 22:13, "Joanna Rutkowska" <joanna@invisiblethingslab.com> wrote: >> I don't remember if 3.4.2 ended up with tsc emulation, but if it does >> you might try enabling it. > > TSC emulation? But I'm running only PV guests. Not sure what do you mean > by this, or how to enable it? There is no TSC emulation for PV guests in 3.4.x. -- Keir ^ permalink raw reply [flat|nested] 42+ messages in thread
end of thread, other threads:[~2010-03-17 17:21 UTC | newest] Thread overview: 42+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-03-12 11:42 A clocksource question Tobias Geiger -- strict thread matches above, loose matches on Subject: below -- 2010-03-09 10:47 Joanna Rutkowska 2010-03-09 10:50 ` Keir Fraser 2010-03-09 10:54 ` Joanna Rutkowska 2010-03-09 11:06 ` Joanna Rutkowska 2010-03-09 12:07 ` Pasi Kärkkäinen 2010-03-09 12:10 ` Joanna Rutkowska 2010-03-09 15:42 ` Konrad Rzeszutek Wilk 2010-03-09 23:36 ` Jeremy Fitzhardinge 2010-03-10 22:13 ` Joanna Rutkowska 2010-03-11 0:07 ` Dan Magenheimer 2010-03-11 0:15 ` Joanna Rutkowska 2010-03-11 0:21 ` Ian Pratt 2010-03-11 0:44 ` Dan Magenheimer 2010-03-12 0:34 ` Joanna Rutkowska 2010-03-11 0:52 ` Joanna Rutkowska 2010-03-11 1:06 ` Jeremy Fitzhardinge 2010-03-11 1:19 ` Joanna Rutkowska 2010-03-11 4:55 ` Jeremy Fitzhardinge 2010-03-11 10:49 ` Joanna Rutkowska 2010-03-12 0:27 ` Joanna Rutkowska 2010-03-12 0:49 ` Jeremy Fitzhardinge 2010-03-12 0:38 ` Joanna Rutkowska 2010-03-12 19:02 ` Joanna Rutkowska 2010-03-12 21:24 ` Jeremy Fitzhardinge 2010-03-12 21:56 ` Tobias Geiger 2010-03-12 22:02 ` Jeremy Fitzhardinge 2010-03-12 21:01 ` Joanna Rutkowska 2010-03-12 21:13 ` Joanna Rutkowska 2010-03-12 23:48 ` Jeremy Fitzhardinge 2010-03-13 9:58 ` Joanna Rutkowska 2010-03-13 19:30 ` Jeremy Fitzhardinge 2010-03-15 6:49 ` Tobias Geiger 2010-03-16 6:01 ` Joanna Rutkowska 2010-03-17 13:35 ` Tobias Geiger 2010-03-17 15:21 ` Joanna Rutkowska 2010-03-17 16:20 ` Jeremy Fitzhardinge 2010-03-17 17:05 ` Joanna Rutkowska 2010-03-17 17:21 ` Jeremy Fitzhardinge 2010-03-17 16:26 ` Dan Magenheimer 2010-03-12 22:56 ` Tobias Geiger 2010-03-11 7:47 ` Keir Fraser
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).