From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757276Ab0KKV6a (ORCPT ); Thu, 11 Nov 2010 16:58:30 -0500 Received: from casper.infradead.org ([85.118.1.10]:35243 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757258Ab0KKV62 convert rfc822-to-8bit (ORCPT ); Thu, 11 Nov 2010 16:58:28 -0500 Subject: Re: [RFC][PATCH 17/22] sched: add signaling overrunning -deadline tasks. From: Peter Zijlstra To: Raistlin Cc: Ingo Molnar , Thomas Gleixner , Steven Rostedt , Chris Friesen , oleg@redhat.com, Frederic Weisbecker , Darren Hart , Johan Eker , "p.faure" , linux-kernel , Claudio Scordino , michael trimarchi , Fabio Checconi , Tommaso Cucinotta , Juri Lelli , Nicola Manica , Luca Abeni , Dhaval Giani , Harald Gustafsson , paulmck In-Reply-To: <1288334428.8661.158.camel@Palantir> References: <1288333128.8661.137.camel@Palantir> <1288334428.8661.158.camel@Palantir> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Thu, 11 Nov 2010 22:58:21 +0100 Message-ID: <1289512701.2084.197.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2010-10-29 at 08:40 +0200, Raistlin wrote: > +static inline void __dl_signal(struct task_struct *tsk, int which) > +{ > + struct siginfo info; > + long long amount = which == SF_SIG_DMISS ? tsk->dl.stats.last_dmiss : > + tsk->dl.stats.last_rorun; > + > + info.si_signo = SIGXCPU; > + info.si_errno = which; > + info.si_code = SI_KERNEL; > + info.si_pid = 0; > + info.si_uid = 0; > + info.si_value.sival_int = (int)amount; > + > + /* Correctly take the locks on task's sighand */ > + __group_send_sig_info(SIGXCPU, &info, tsk); > + /* Log what happened to dmesg */ > + printk(KERN_INFO "SCHED_DEADLINE: 0x%4x by %Ld [ns] in %d (%s)\n", > + which, amount, task_pid_nr(tsk), tsk->comm); > +} This being a G-EDF like scheduler with a u<=1 schedulability test, we're firmly in soft-rt territory which means the above will be very easy to trigger.. Maybe not spam dmesg?