All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [RFC][PATCH 2/2] x86: Add support for ipipe_get_irq_regs
Date: Sat, 05 Jun 2010 23:09:51 +0200	[thread overview]
Message-ID: <1275772191.18250.260.camel@domain.hid> (raw)
In-Reply-To: <4C0AB817.2070000@domain.hid>

On Sat, 2010-06-05 at 22:48 +0200, Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
> > Jan Kiszka wrote:
> >> Philippe Gerum wrote:
> >>> On Thu, 2010-06-03 at 16:22 +0200, Jan Kiszka wrote:
> >>>> From: Jan Kiszka <jan.kiszka@domain.hid>
> >>>>
> >>>> Implement the x86 arch bits for ipipe_get_irq_regs support. This allows
> >>>> to drop __ipipe_tick_regs and use the new service instead.
> >>> I'm unsure whether this patch would actually replace __ipipe_tick_regs
> >>> properly, particularly regarding how the profiling code works.
> >> tick_regs are a "workaround", this approach appears to me way closer to
> >> how native works.
> > 
> > We do not want ipipe_tick_regs to work the way the native kernel works.
> > We want to fool the kernel by passing it the value of the registers at
> > the moment of the real timer tick so that its accounting works more or
> > less reliably. When the kernel used the real registers it got the
> > accounting wrong.
> 
> Right, though current tick_regs approach is not accurate either: the
> preempted task gets the full time slice accounted, neglecting the actual
> schedule inside the preempting domain.
> 

Indeed. This trade-off was made back in 2002.

> 
> Jan
> 
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main


-- 
Philippe.




      reply	other threads:[~2010-06-05 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 14:22 [Adeos-main] [RFC][PATCH 2/2] x86: Add support for ipipe_get_irq_regs Jan Kiszka
2010-06-05 17:40 ` Philippe Gerum
2010-06-05 18:37   ` Jan Kiszka
2010-06-05 19:23     ` Gilles Chanteperdrix
2010-06-05 20:48       ` Jan Kiszka
2010-06-05 21:09         ` Philippe Gerum [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=1275772191.18250.260.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=adeos-main@gna.org \
    --cc=jan.kiszka@domain.hid \
    /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.