public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: Paul Mackerras <paulus@samba•org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [POWERPC] Fix duplicate time accounting
Date: Mon, 29 Oct 2007 16:56:50 +0300	[thread overview]
Message-ID: <4725E6A2.10301@ru.mvista.com> (raw)
In-Reply-To: <18213.19066.134475.220466@cargo.ozlabs.ibm.com>

Hello.

Paul Mackerras wrote:

> Currently, process user and system times are advancing twice as fast
> as they should because they are being accounted in two places - in the
> generic code and in timer_interrupt.  This fixes it by removing the
> call to account_process_time in timer_interrupt.

    But will the deterministic accounting option continue to work with such fix?

> Signed-off-by: Paul Mackerras <paulus@samba•org>
> ---
> diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c
> index 9eb3284..5e253d6 100644
> --- a/arch/powerpc/kernel/time.c
> +++ b/arch/powerpc/kernel/time.c
> @@ -599,16 +599,6 @@ void timer_interrupt(struct pt_regs * regs)
>  		get_lppaca()->int_dword.fields.decr_int = 0;
>  #endif
>  
> -	/*
> -	 * We cannot disable the decrementer, so in the period
> -	 * between this cpu's being marked offline in cpu_online_map
> -	 * and calling stop-self, it is taking timer interrupts.
> -	 * Avoid calling into the scheduler rebalancing code if this
> -	 * is the case.
> -	 */
> -	if (!cpu_is_offline(cpu))
> -		account_process_time(regs);
> -
>  	if (evt->event_handler)
>  		evt->event_handler(evt);
>  	else

WBR, Sergei

      parent reply	other threads:[~2007-10-29 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29  2:50 [POWERPC] Fix duplicate time accounting Paul Mackerras
2007-10-29  3:16 ` Olof Johansson
2007-10-29 13:56 ` Sergei Shtylyov [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=4725E6A2.10301@ru.mvista.com \
    --to=sshtylyov@ru$(echo .)mvista.com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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