From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752465Ab3AVA0g (ORCPT ); Mon, 21 Jan 2013 19:26:36 -0500 Received: from mail-vc0-f169.google.com ([209.85.220.169]:42197 "EHLO mail-vc0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751706Ab3AVA0f (ORCPT ); Mon, 21 Jan 2013 19:26:35 -0500 MIME-Version: 1.0 In-Reply-To: References: <201301212041.17951.arnd@arndb.de> <50FDAC5F.4040605@linaro.org> <20130121211218.GX23505@n2100.arm.linux.org.uk> <20130121224252.GY23505@n2100.arm.linux.org.uk> <20130121234908.GD23505@n2100.arm.linux.org.uk> From: Matt Sealey Date: Mon, 21 Jan 2013 18:26:14 -0600 Message-ID: Subject: Re: One of these things (CONFIG_HZ) is not like the others.. To: Russell King - ARM Linux Cc: John Stultz , Arnd Bergmann , Linux ARM Kernel ML , LKML , Peter Zijlstra , Ingo Molnar , linux-samsung-soc@vger.kernel.org, Ben Dooks , Kukjin Kim Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 21, 2013 at 6:09 PM, Matt Sealey wrote: [LAKML: about lack of SCHED_HRTICK because we don't use kernel/Kconfig.hz on ARM)] > kind of leaves ARM in the doghouse.. who knows what weirdo scheduler > reactions are related to it not being enabled. Maybe when it is, HZ > *would* need to be allowed to be bumped when using this code path? Or conversely maybe this is exactly why the Samsung maintainers decided they need HZ=200, because SCHED_HRTICK isn't being enabled and they're experiencing some multimedia lag because of it? -- Matt Sealey Product Development Analyst, Genesi USA, Inc.