[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4717719C.703@ru.mvista.com>
Date: Thu, 18 Oct 2007 18:45:48 +0400
From: Sergei Shtylyov <sshtylyov@...mvista.com>
To: Sergei Shtylyov <sshtylyov@...mvista.com>
Cc: tglx@...utronix.de, mingo@...e.hu, linuxppc-dev@...abs.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.21-rt2] PowerPC: decrementer clockevent driver
Sergei Shtylyov wrote:
> Add PowerPC decrementer clock event driver.
> Every effort has been made to support the different implementations of the
> decrementer: the classic one (with 970 series variation), 40x and Book E
> specific ones.
> I had to make CONFIG_GENERIC_CLOCKEVENTS option selectable for the
> compatibility reasons -- this option is not compatible with the PPC64
> deterministic time accounting.
> Thanks to Daniel Walker and Thomas Gleixner for the suggestions they made...
> Signed-off-by: Sergei Shtylyov <sshtylyov@...mvista.com>
> Index: linux-2.6/arch/powerpc/Kconfig
> ===================================================================
> --- linux-2.6.orig/arch/powerpc/Kconfig
> +++ linux-2.6/arch/powerpc/Kconfig
> @@ -317,7 +317,7 @@ config PPC_STD_MMU_32
>
> config VIRT_CPU_ACCOUNTING
> bool "Deterministic task and CPU time accounting"
> - depends on PPC64
> + depends on PPC64 && !GENERIC_CLOCKEVENTS
> default y
> help
> Select this option to enable more accurate task and CPU time
Thomas, that part of the ppc-clockevents.patch (part of the -rt patch) is
now broken, it makes CONFIG_MAX_ZONEORDER dependent on
!CONFIG_GENERIC_CLOCKEVENTS -- this is probably due to patch's fuzzy logic.
Do I need to send a patch to fix this?
WBR, Sergei
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists