All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: tglx@linutronix.de, greg.weeks@timesys.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] PowerPC: clockevents and HRT support
Date: Wed, 08 Nov 2006 17:21:51 +0300	[thread overview]
Message-ID: <4551E7FF.8010209@ru.mvista.com> (raw)
In-Reply-To: <17745.14911.693171.717979@cargo.ozlabs.ibm.com>

Hello.

Paul Mackerras wrote:

>>    Arch-specific accounting hooks which this feature makes use of can't be 
>>called from the generic clockevents code.

> Which hooks specifically?

    You aren't saying you don't know your own code?
    Specifically, it's local account_process_time() function being called 
instead of updated_process_times() with CONFIG_VIRT_CPU_ACCOUNTING option on.

> The deterministic accounting is an essential feature; there's no way
> I'll accept a patch which disables it.

    I'm not talking you into accepting it in any way, this is just to keep 
people informed.
    And I left people a choice: they can either have fancy accounting or HRT, 
just not both at once. What's wrong with that?

> Paul.

WBR, Sergei

  reply	other threads:[~2006-11-08 14:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 21:05 [PATCH] PowerPC: clockevents and HRT support Sergei Shtylyov
2006-11-07 22:36 ` Benjamin Herrenschmidt
2006-11-07 22:44   ` Sergei Shtylyov
2006-11-07 23:04     ` Benjamin Herrenschmidt
2006-11-07 23:21       ` Sergei Shtylyov
2006-11-08  0:18         ` Benjamin Herrenschmidt
2006-11-08  1:19           ` Mark A. Greer
2006-11-08  2:06             ` Benjamin Herrenschmidt
2006-11-08 14:14               ` Sergei Shtylyov
2006-11-08  2:00     ` Paul Mackerras
2006-11-08 14:21       ` Sergei Shtylyov [this message]
2006-11-10  8:32         ` Paul Mackerras
2006-11-10 14:08           ` Sergei Shtylyov
2006-11-10 23:52             ` Paul Mackerras
2006-11-12 18:30               ` Sergei Shtylyov

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=4551E7FF.8010209@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=greg.weeks@timesys.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.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 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.