All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: CONFIG_CPU_FREQ change
Date: Mon, 20 Feb 2006 16:43:46 +0100	[thread overview]
Message-ID: <43F9F1C2.76F0.0078.0@novell.com> (raw)

To my surprise, c/s 8888 enables CPU_FREQ for x86-64 rather than disabling it for i386. Did anyone at your end actually
test that if enabled this at least builds properly now? Not to mention that of course this also should work... If I
remember right, the main reason for posting a patch to disable it on 32-bits (similar to how it was on 64-bits before)
was that there were some missing symbols, and I don't think I saw any changesets addressing this. Also, from previous
discussion I seem to recall that it was generally agreed that there is little point in allowing a single domain (even
dom0) to decide whether/what power management actions should be taken without knowing about the requirements of the rest
of the system...

Thanks, Jan

             reply	other threads:[~2006-02-20 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 15:43 Jan Beulich [this message]
2006-02-20 18:12 ` CONFIG_CPU_FREQ change Christian Limpach
2006-02-20 18:21   ` Jeremy Katz
2006-02-21  7:31   ` Jan Beulich

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=43F9F1C2.76F0.0078.0@novell.com \
    --to=jbeulich@novell.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.