transitional config CONFIG_GENERIC_CLOCKEVENTS
in [Kernel]
|
From: Thomas Gleixner on 26 May 2010 10:00 On Wed, 26 May 2010, Christoph Egger wrote: > Hi all! > > As part of the VAMOS[0] research project at the University of > Erlangen we are looking at multiple integrity errors in linux' > configuration system. > > This was an aid for a transition finished 2007 so not > necessary for some time now, ready for removal. > > Please keep me informed of this patch getting confirmed / > merged so we can keep track of it. It's still necessary/helpful for any arch which is not yet converted. And there are a few unfortunately. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on 26 May 2010 10:00 On Wed, May 26, 2010 at 03:44:15PM +0200, Christoph Egger wrote: > @@ -25,5 +25,5 @@ config HIGH_RES_TIMERS > config GENERIC_CLOCKEVENTS_BUILD > bool > default y > - depends on GENERIC_CLOCKEVENTS || GENERIC_CLOCKEVENTS_MIGR > + depends on GENERIC_CLOCKEVENTS At this point you can also get rid of GENERIC_CLOCKEVENTS_BUILD and replace all instances of it with GENERIC_CLOCKEVENTS. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Egger on 26 May 2010 11:00 On Wed, May 26, 2010 at 03:56:09PM +0200, Thomas Gleixner wrote: > On Wed, 26 May 2010, Christoph Egger wrote: > > > Hi all! > > > > As part of the VAMOS[0] research project at the University of > > Erlangen we are looking at multiple integrity errors in linux' > > configuration system. > > > > This was an aid for a transition finished 2007 so not > > necessary for some time now, ready for removal. > > > > Please keep me informed of this patch getting confirmed / > > merged so we can keep track of it. > > It's still necessary/helpful for any arch which is not yet > converted. And there are a few unfortunately. Are you referring to some out-of-tree architectures? I've verified the string GENERIC_CLOCKEVENTS_MIGR is only appearing at this single spot in kconfig and nowhere else in code/Kconfig in my up-to-date linux tree. If not maybe I was a bit unclear about the actual rational behind the code patch. As GENERIC_CLOCKEVENTS_MIGR is not selectable GENERIC_CLOCKEVENTS_BUILD implies GENERIC_CLOCKEVENTS so inside a GENERIC_CLOCKEVENTS_BUILD block a check for GENERIC_CLOCKEVENTS is non-necessary for everything inside the linus tree and the else branch unavailable. In this case I'll prepare an more complete patch as suggested by CHristoph Hellwig tomorrow or friday. Regards Christoph -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Thomas Gleixner on 26 May 2010 11:20 On Wed, 26 May 2010, Christoph Egger wrote: > On Wed, May 26, 2010 at 03:56:09PM +0200, Thomas Gleixner wrote: > > On Wed, 26 May 2010, Christoph Egger wrote: > > > > > Hi all! > > > > > > As part of the VAMOS[0] research project at the University of > > > Erlangen we are looking at multiple integrity errors in linux' > > > configuration system. > > > > > > This was an aid for a transition finished 2007 so not > > > necessary for some time now, ready for removal. > > > > > > Please keep me informed of this patch getting confirmed / > > > merged so we can keep track of it. > > > > It's still necessary/helpful for any arch which is not yet > > converted. And there are a few unfortunately. > > Are you referring to some out-of-tree architectures? I've > verified the string GENERIC_CLOCKEVENTS_MIGR is only appearing at this > single spot in kconfig and nowhere else in code/Kconfig in my > up-to-date linux tree. No. I'm referring to in tree archs which do not use the clock events at all yet. The MIGR symbol allows them to do a step by step conversion which builds the generic clock events stuff first before switching over to use them. That's why it was created in the first place and it has been proven useful when doing such work. So I'd rather see it stay until all archs actually use the generic framework. But yes, we can apply your patch and just let them select GENERIC_CLOCKEVENTS_BUILD instead. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Thomas Gleixner on 26 May 2010 12:00 On Wed, 26 May 2010, Thomas Gleixner wrote: > > Are you referring to some out-of-tree architectures? I've > > verified the string GENERIC_CLOCKEVENTS_MIGR is only appearing at this > > single spot in kconfig and nowhere else in code/Kconfig in my > > up-to-date linux tree. > > No. I'm referring to in tree archs which do not use the clock events > at all yet. The MIGR symbol allows them to do a step by step > conversion which builds the generic clock events stuff first before > switching over to use them. That's why it was created in the first > place and it has been proven useful when doing such work. So I'd > rather see it stay until all archs actually use the generic framework. > > But yes, we can apply your patch and just let them select > GENERIC_CLOCKEVENTS_BUILD instead. Gah, we can't. tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: [PATCH] transitional config CONFIG_GENERIC_CLOCKEVENTS Next: arch/tile |