All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Roessner <christian@roessner-net.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, "Langsdorf,
	Mark" <mark.langsdorf@amd.com>
Subject: Re: Powernow-k8 support
Date: Thu, 15 Jun 2006 11:58:55 +0200	[thread overview]
Message-ID: <44912F5F.2030906@roessner-net.com> (raw)
In-Reply-To: <e254873477c80f1657af0d77457535c8@cl.cam.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1316 bytes --]

Keir Fraser schrieb:
> 
> On 14 Jun 2006, at 22:43, Langsdorf, Mark wrote:
> 
>> Should I (as the powernow-k8 maintainer) be modifying this
>> code as we add new features?  Most of it looks pretty safe,
>> but the new 2.00.00 driver uses different MSRs, and there
>> are other things coming up that will confuse things.
> 
> One thing I'm a bit undecided on is whether MSR emulation is the right
> way to go, or whether we should just pull the low-level cpufreq drivers
> verbatim into Xen and then provide access to them via hypercalls. We
> could then have a paravirtual cpufreq driver added to Linux. This has
> the advantage that we have less new per-cpu-type code to maintain in Xen
> (we can more easily sync with cpufreq changes in Linux) but it does mean
> we change more Linux code and we'd want to be a bit careful not to make
> the hypercall interface too Linux specific (or too x86 specific).

Has this something to do with the private mail I sent to Keir Fraser?

I told him that the powernow-k8 support in dom0 seems to work, while in
domUs not. Second was that the shown Bogomips under /proc/cpuinfo never
changes from ~4000, even when the CPU was @ 800.

Regards
Christian
-- 
Tel.: 0641-2097252, Mobil: 0171-3611230
PGP: http://www.roessner-net.com/0x6B929997.asc




[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2006-06-15  9:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 21:43 Powernow-k8 support Langsdorf, Mark
2006-06-15  6:14 ` Keir Fraser
2006-06-15  9:58   ` Christian Roessner [this message]
2006-06-15 10:21     ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2006-06-12 16:25 Langsdorf, Mark
2006-06-12 16:00 Langsdorf, Mark
2006-06-12 16:06 ` Keir Fraser
2006-06-12 16:58   ` Christian Roessner
2006-06-12 17:29     ` Keir Fraser
2006-06-13  8:49       ` Christian Roessner
2006-06-13  9:11         ` Keir Fraser
2006-06-13  9:24           ` Christian Roessner
2006-06-13  9:30             ` Keir Fraser
2006-06-13 12:20               ` Christian Roessner
2006-06-13 12:51                 ` Keir Fraser
2006-06-13 14:12                   ` Christian Roessner
2006-06-13 14:47                     ` Keir Fraser
2006-06-13 14:57                       ` Christian Roessner
2006-06-13 15:00                         ` Keir Fraser
2006-06-13 15:04                     ` Keir Fraser
2006-06-13 14:35                   ` Christian Roessner
2006-06-11 15:49 Christian Roessner
2006-06-11 16:11 ` Keir Fraser
2006-06-11 19:48   ` Christian Roessner
2006-06-11 21:04     ` Keir Fraser
2006-06-12  0:26       ` Christian Roessner
2006-06-12  7:49         ` Keir Fraser

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=44912F5F.2030906@roessner-net.com \
    --to=christian@roessner-net.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=mark.langsdorf@amd.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.