From: Mike Galbraith <bitbucket@online.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tim Sander <tim.sander@hbm.com>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.4.41-rt55-feat1
Date: Thu, 25 Apr 2013 15:23:52 +0200 [thread overview]
Message-ID: <1366896232.6139.21.camel@marge.simpson.net> (raw)
In-Reply-To: <alpine.LFD.2.02.1304251507370.21884@ionos>
On Thu, 2013-04-25 at 15:09 +0200, Thomas Gleixner wrote:
> On Thu, 25 Apr 2013, Steven Rostedt wrote:
>
> > On Thu, 2013-04-25 at 14:46 +0200, Thomas Gleixner wrote:
> > > On Thu, 25 Apr 2013, Steven Rostedt wrote:
> > > > On Thu, 2013-04-25 at 14:36 +0200, Mike Galbraith wrote:
> > > > > hrtimer: fix hrtimer free zone build bug
> > > >
> > > > Perhaps the better solution is to select HIGH_RES_TIMERS when
> > > > PREEMPT_RT_FULL is selected?
> > >
> > > No, why ?
> >
> > Why not? ;-)
> >
> > Except for the lack of support, one would think that if you want real
> > time responses, you would also want a real time clock.
>
> Well, if your application is driven by an external interrupt, then you
> do not need highres timers at all.
(hey, that's cheating, generic config vs specialized;)
next prev parent reply other threads:[~2013-04-25 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 23:44 [ANNOUNCE] 3.4.41-rt55-feat1 Steven Rostedt
2013-04-25 11:14 ` Tim Sander
2013-04-25 12:32 ` Sebastian Andrzej Siewior
2013-04-25 12:36 ` Mike Galbraith
2013-04-25 12:43 ` Steven Rostedt
2013-04-25 12:46 ` Thomas Gleixner
2013-04-25 12:52 ` Steven Rostedt
2013-04-25 13:09 ` Thomas Gleixner
2013-04-25 13:15 ` Steven Rostedt
2013-04-25 13:23 ` Mike Galbraith [this message]
2013-04-25 12:48 ` Mike Galbraith
2013-04-25 12:52 ` Steven Rostedt
2013-04-25 12:55 ` Sebastian Andrzej Siewior
2013-04-25 13:12 ` Mike Galbraith
2013-04-25 14:22 ` Tim Sander
2013-04-25 14:36 ` Steven Rostedt
2013-04-25 22:20 ` Thomas Gleixner
2013-04-25 22:23 ` Steven Rostedt
2013-04-26 6:29 ` Tim Sander
2013-04-25 12:36 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1366896232.6139.21.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.sander@hbm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.