mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Kurt Garloff <garloff@suse.de>,
	Linux kernel list <linux-kernel@vger.kernel.org>,
	"S. Chandra Sekharan" <sekharan@us.ibm.com>
Subject: Re: [PATCH] Support for assymmetric SMP
Date: Mon, 11 Mar 2002 05:29:54 +0100	[thread overview]
Message-ID: <20020311052954.R8949@dualathlon.random> (raw)
In-Reply-To: <20020311043421.D2346@nbkurt.etpnet.phys.tue.nl>
In-Reply-To: <20020311043421.D2346@nbkurt.etpnet.phys.tue.nl>

On Mon, Mar 11, 2002 at 04:34:21AM +0100, Kurt Garloff wrote:
> @@ -53,6 +54,10 @@
>  	unsigned long *pmd_quick;
>  	unsigned long *pte_quick;
>  	unsigned long pgtable_cache_sz;
> +	unsigned long cpu_khz;
> +	unsigned long fast_gettimeoffset_quotient;
> +	unsigned long last_tsc_low;
> +	struct timeval xtime;
>  } __attribute__((__aligned__(SMP_CACHE_BYTES)));
>  
>  #define X86_VENDOR_INTEL 0

the only problem is if you happen to get the timer irq always in the
same cpu for a few seconds, then the last_tsc_low will wrap around and
gettimeofday will be wrong. And even if you snapshot the full 64bit of the
tsc you'll run into some trouble if the timer irq will be delivered only
to the same cpu for a long time (for example if you use irq bindings).
you'd lose precision and you'll run into the measuration errors of
fast_gettimeoffset_quotient. The right support for asynchronous TSC
handling is a bit more complicated unfortunately.

Andrea

  reply	other threads:[~2002-03-11  4:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11  3:34 Kurt Garloff
2002-03-11  4:29 ` Andrea Arcangeli [this message]
2002-03-11 11:25   ` Kurt Garloff
2002-03-11 12:20     ` Andrea Arcangeli
2002-03-12 15:05       ` Eric W. Biederman
2002-03-13 16:17         ` Alan Cox
2002-03-13 16:40           ` Martin J. Bligh
2002-03-12 22:01 ` Frank van de Pol

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=20020311052954.R8949@dualathlon.random \
    --to=andrea@suse.de \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sekharan@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®