virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: James Morris <jmorris@namei.org>
Cc: virtualization@lists.osdl.org
Subject: Re: APIC clock setup dependent on PAE ?
Date: Wed, 10 Jan 2007 13:54:34 -0800	[thread overview]
Message-ID: <45A5609A.4070201@vmware.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701100933220.8582@d.namei>

James Morris wrote:
> Why are these APIC clock init hooks dependent on CONFIG_X86_PAE ?
>
> include/asm/paravirt.h:
>
> static inline void setup_boot_clock(void)
> {
>         paravirt_ops.setup_boot_clock();
> }
>
> static inline void setup_secondary_clock(void)
> {
>         paravirt_ops.setup_secondary_clock();
> }
>
>
> (via the vmi timer patch).
>   

Um, that is nuts.  What tree are you in?

Zach

  parent reply	other threads:[~2007-01-10 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10 14:40 APIC clock setup dependent on PAE ? James Morris
2007-01-10 14:52 ` James Morris
2007-01-10 21:54 ` Zachary Amsden [this message]
2007-01-11  0:14   ` James Morris
2007-01-11  2:01     ` Chris Wright

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=45A5609A.4070201@vmware.com \
    --to=zach@vmware.com \
    --cc=jmorris@namei.org \
    --cc=virtualization@lists.osdl.org \
    /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;
as well as URLs for NNTP newsgroup(s).