All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, John Clemens <jclemens@revivesystems.com>
Subject: Re: Dual opteron PIT timing problem?
Date: Sat, 7 Oct 2006 01:49:37 +0100	[thread overview]
Message-ID: <20061007004937.GA13921@redhat.com> (raw)
In-Reply-To: <C14C9BA0.22B7%Keir.Fraser@cl.cam.ac.uk>

On Fri, Oct 06, 2006 at 11:47:44PM +0100, Keir Fraser wrote:
> On 6/10/06 10:00 pm, "John Clemens" <jclemens@revivesystems.com> wrote:
> 
> > Are the any other things I could try? I've tried all sorts of
> > combinations of [no]apic, [no]smp, [no]tsc, [no]lapic, [no]apm, etc.. Is
> > anyone running an SMP xen system without an HPET timer?
> 
> Most people, I should think. Many BIOSes do not advertise the presence of an
> HPET, even if the chipset has one.

Actually there's some pretty common machines which don't include a HPET. IIRC
HP's Opteron based systems such as the DL-{3,5}85 don't typically have a HPET. The
RHEL kernels would typically fallback to using the TSC or the ACPI PMTimer for
these systems (PMTimer is reliable but high overhead, while TSC is low overhead
but pretty tricky to get the code correct to maintain SMP synchronisation).

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2006-10-07  0:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 21:00 Dual opteron PIT timing problem? John Clemens
2006-10-06 22:47 ` Keir Fraser
2006-10-07  0:49   ` Daniel P. Berrange [this message]
2006-10-09 15:33   ` John Clemens

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=20061007004937.GA13921@redhat.com \
    --to=berrange@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=jclemens@revivesystems.com \
    --cc=xen-devel@lists.xensource.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 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.