 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] CONFIG_CPU_FREQ
| To: | "Jeremy Katz" <katzj@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] CONFIG_CPU_FREQ |
| From: | "Christian Limpach" <christian.limpach@xxxxxxxxx> |
| Date: | Mon, 20 Feb 2006 11:38:49 +0000 |
| Cc: | "Petersson, Mats" <Mats.Petersson@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Mon, 20 Feb 2006 11:51:53 +0000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O3TbBe/I2Ie7cXwJQ37GrjNYJWJpqO0HaG4YH6rlhp8ZYSHboBmP16N2PYQal31OJ1BMRKHL5d0xPXcnQ4hilaFpa0vrUqE3lFqsTiQgApUwoP7ECYW8KB1BhQBW9imIoQNpoljEBVDcAoX0YawdGNFs2ArBj9yNC9W7Bi0Dy0g= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <1140030889.12083.22.camel@xxxxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <907625E08839C4409CE5768403633E0B0EABF7@xxxxxxxxxxxxxxxxx> <1140030889.12083.22.camel@xxxxxxxxxxxxxx> |
| Reply-to: | Christian.Limpach@xxxxxxxxxxxx |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 2/15/06, Jeremy Katz <katzj@xxxxxxxxxx> wrote:
> I could be insane, but I'm pretty sure it works at least in dom0 right
> now. So disabling it across the board means a loss of functionality for
> anyone wanting to run dom0 on their laptop which isn't really needed.
>
> Having it dependent on either XEN_PHYSDEV_ACCESS or
> XEN_PRIVILEGED_GUEST, on the other hand, doesn't seem unreasonable
It is already dependent on !XEN_UNPRIVILEGED_GUEST on i386, I've
changed x86_64 to match.
christian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH] Fix loading binary kernel images, Kandy Rogers |
|---|---|
| Next by Date: | [Xen-devel] int causing GPF, Ivan Kelly |
| Previous by Thread: | RE: [Xen-devel] CONFIG_CPU_FREQ, Jeremy Katz |
| Next by Thread: | [Xen-devel] [PATCH] i386 linux: eliminate hard coded items from __xen_guest section, Jan Beulich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
