Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753143AbZGXPIA (ORCPT ); Fri, 24 Jul 2009 11:08:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752128AbZGXPH7 (ORCPT ); Fri, 24 Jul 2009 11:07:59 -0400 Received: from mail-qy0-f196.google.com ([209.85.221.196]:51516 "EHLO mail-qy0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751847AbZGXPH6 (ORCPT ); Fri, 24 Jul 2009 11:07:58 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZDTKczHdISQoJ8qmond9NxTnv7uyh3vqlZEpx3PEylBHNOz0RafVbZCHrutfXLjk7t CeVUgUoi8KUY6RIOAHaxzA5zO9kwvGruFnf0NLBk2z81pzICOYyTq7U7D7ckxfxZXl01 HxK2oE3++fRR+td2JLdDTjRxf6bhs5C2JoWi4= MIME-Version: 1.0 In-Reply-To: <1248446909.6987.110.camel@twins> References: <454c71700907240357l61f5c4fajaca73db0fba7db8@mail.gmail.com> <1248437670.6987.26.camel@twins> <454c71700907240604h4673f117j8ed58b9f2ee54798@mail.gmail.com> <1248441290.6987.52.camel@twins> <454c71700907240626w127fd890ufa91ef90cbcaaa@mail.gmail.com> <1248442415.6987.56.camel@twins> <454c71700907240644h7469e2a5sfcb57f202a2e184d@mail.gmail.com> <1248443656.6987.61.camel@twins> <454c71700907240704o32dcdeb3v57845eb9472dd04c@mail.gmail.com> <1248446909.6987.110.camel@twins> Date: Fri, 24 Jul 2009 23:07:58 +0800 Message-ID: <454c71700907240807t5b682e7cv52534f41d3be961a@mail.gmail.com> Subject: Re: report a bug about sched_rt From: sen wang To: Peter Zijlstra Cc: mingo@elte.hu, akpm@linux-foundation.org, kernel@kolivas.org, npiggin@suse.de, arjan@infradead.org, linux-arm-kernel@lists.arm.linux.org.uk, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 782 Lines: 21 2009/7/24 Peter Zijlstra : > On Fri, 2009-07-24 at 22:04 +0800, sen wang wrote: > >> just one question: >> if cpu is free and there is running state task, how you do? >> schedule the task up? or schedule idle task up? > > Well, when an RT group is over the bandwidth limit I don't consider them > runnable. Therefore, failing to find any other tasks, we run the idle > task. > you havn't anwser the question: if cpu is free, should we schedule the running state task or idle task? face the error and fix it! ok? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/