public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "M. Koehrer" <mathias_koehrer@arcor.de>
Cc: lclaudio@uudg.org, linux-rt-users@vger.kernel.org
Subject: Re: Re: Disabling lapic timer for a certain core
Date: Sat, 6 Mar 2010 10:18:48 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1003061011280.2014@localhost.localdomain> (raw)
In-Reply-To: <8898.1267797291298.JavaMail.ngmail@webmail11.arcor-online.net>

On Fri, 5 Mar 2010, M. Koehrer wrote:
> > In theory it's possible to remove the timer interrupt from such an
> > isolated core completely, but there needs to be some work done vs. the
> > scheduler, accounting, RCU etc. There are people looking into this,
> > but we have no patches yet.
> I have checked the LAPIC addresses via the MSRs.
> All LAPIC addresses for all CPU cores are the same. 
> I assume they share the very same configuration, thus a minimum step 
> would be to make a copy of this configuration data and to let CPU core 3
> point to this copy. This would allow to disable the timer.

Really ? If it would be enough to disable the timer interrupt and not
let it fire, it would have been done years ago.

Did you even try to read what I said above ?

> >                 ...., but there needs to be some work done vs. the
> > scheduler, accounting, RCU etc.

Linux was not designed that way and it requires a non trivial amount
of work to get this sorted out:

> > There are people looking into this, but we have no patches yet.

Thanks,

	tglx

      reply	other threads:[~2010-03-06  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 21:03 Re: Disabling lapic timer for a certain core M. Koehrer
2010-03-05  7:05 ` Thomas Gleixner
2010-03-05 13:54   ` M. Koehrer
2010-03-06  9:18     ` Thomas Gleixner [this message]

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=alpine.LFD.2.00.1003061011280.2014@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=lclaudio@uudg.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mathias_koehrer@arcor.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox