From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: 2.6.31.6 pv_ops with K8 cpufreq
Date: Mon, 15 Feb 2010 16:19:23 +0100 [thread overview]
Message-ID: <4B7965FB.2010908@access.denied> (raw)
In-Reply-To: <4B7022F6.5060405@access.denied>
[-- Attachment #1.1: Type: text/plain, Size: 340 bytes --]
Am 08.02.2010 15:43, schrieb Stefan Kuhne:
> Am 08.02.2010 15:32, schrieb Langsdorf, Mark:
>> cpufreq=xen only works with Family 10h and later processors,
>> but that's not the problem you're having.
>>
> Will it changed, or does i need an K10 CPU?
>
I'll wait for 870G Chipset and upgrade my Server.
Regards,
Stefan Kuhne
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-02-15 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 16:09 2.6.31.6 pv_ops with K8 cpufreq Stefan Kuhne
2010-02-08 14:32 ` Langsdorf, Mark
2010-02-08 14:43 ` Stefan Kuhne
2010-02-15 15:19 ` Stefan Kuhne [this message]
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=4B7965FB.2010908@access.denied \
--to=stefan.kuhne@gmx.net \
--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 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).