All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dylanger Daly <dylanger@thegrail.co>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Dylanger Daly <dylanger@thegrail.co>,
	xen-devel@lists.xenproject.org, Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] Add Undervolt MSRs to wrmsr function.
Date: Thu, 18 Apr 2019 10:19:34 +0100	[thread overview]
Message-ID: <CANJ4vQ1nOuFZw0kk0dWEsx4Q0h8YE2H8gRzg422cRf65FAkncg@mail.gmail.com> (raw)
In-Reply-To: <53b32c69-b0b4-5441-c8e2-299769eabf8f@citrix.com>


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

No worries Andrew, it was my first patch, thank you for the response.

It's based on Xen 4.8

Dom0 should be controlling it, but I wasn't aware of the Security
implications.

The scope isn't well documented:
 https://ressman.org/posts/2018-06-26-voltage-temperature-tdp-thinkpad/

More experimental as it worked with my Laptop.

Thank you for your time


On Thu, Apr 18, 2019, 10:09 AM Andrew Cooper <andrew.cooper3@citrix.com>
wrote:

> On 18/04/2019 09:56, Dylanger Daly wrote:
> > Giving Laptop Users the ability to Undervolt and change Temp Throttle
> Limits.
> >
> > Signed-off-by: Dylanger Daly <dylanger@thegrail.co>
>
> Thankyou for the patch.  Which version of Xen is it against?  It is
> fairly old, given that the function you patch has now moved to
> arch/x86/pv/emul-priv-op.c.  Furthermore, this is the legacy path, so
> the functions this should be added to are guest_{rdmsr,wrmsr}() in
> arch/x86/msr.c
>
> What entity is controlling this?
>
> Sadly, there are a number of issues.  You open these MSRs up to
> unprivileged domUs, and there is a mismatch between the vcpus/pcpus.
>
> What is the scope of these MSRs?  I guess dom0 is going to write them on
> all cores, but as dom0 gets scheduled around, this wont match up with
> the pcpus across the host.
>
> ~Andrew
>

[-- Attachment #1.2: Type: text/html, Size: 2076 bytes --]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Dylanger Daly <dylanger@thegrail.co>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Dylanger Daly <dylanger@thegrail.co>,
	xen-devel@lists.xenproject.org, Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [Xen-devel] [PATCH] Add Undervolt MSRs to wrmsr function.
Date: Thu, 18 Apr 2019 10:19:34 +0100	[thread overview]
Message-ID: <CANJ4vQ1nOuFZw0kk0dWEsx4Q0h8YE2H8gRzg422cRf65FAkncg@mail.gmail.com> (raw)
Message-ID: <20190418091934.bypVaFxXhEJt3MtTevr9l5IBJZ3dOX2Xw0GP9OP3S-A@z> (raw)
In-Reply-To: <53b32c69-b0b4-5441-c8e2-299769eabf8f@citrix.com>


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

No worries Andrew, it was my first patch, thank you for the response.

It's based on Xen 4.8

Dom0 should be controlling it, but I wasn't aware of the Security
implications.

The scope isn't well documented:
 https://ressman.org/posts/2018-06-26-voltage-temperature-tdp-thinkpad/

More experimental as it worked with my Laptop.

Thank you for your time


On Thu, Apr 18, 2019, 10:09 AM Andrew Cooper <andrew.cooper3@citrix.com>
wrote:

> On 18/04/2019 09:56, Dylanger Daly wrote:
> > Giving Laptop Users the ability to Undervolt and change Temp Throttle
> Limits.
> >
> > Signed-off-by: Dylanger Daly <dylanger@thegrail.co>
>
> Thankyou for the patch.  Which version of Xen is it against?  It is
> fairly old, given that the function you patch has now moved to
> arch/x86/pv/emul-priv-op.c.  Furthermore, this is the legacy path, so
> the functions this should be added to are guest_{rdmsr,wrmsr}() in
> arch/x86/msr.c
>
> What entity is controlling this?
>
> Sadly, there are a number of issues.  You open these MSRs up to
> unprivileged domUs, and there is a mismatch between the vcpus/pcpus.
>
> What is the scope of these MSRs?  I guess dom0 is going to write them on
> all cores, but as dom0 gets scheduled around, this wont match up with
> the pcpus across the host.
>
> ~Andrew
>

[-- Attachment #1.2: Type: text/html, Size: 2076 bytes --]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-04-18  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18  8:56 [PATCH] Add Undervolt MSRs to wrmsr function Dylanger Daly
2019-04-18  8:56 ` [Xen-devel] " Dylanger Daly
2019-04-18  9:09 ` Andrew Cooper
2019-04-18  9:09   ` [Xen-devel] " Andrew Cooper
2019-04-18  9:19   ` Dylanger Daly [this message]
2019-04-18  9:19     ` Dylanger Daly
2019-04-18 11:12     ` Andrew Cooper
2019-04-18 11:12       ` [Xen-devel] " Andrew Cooper
2019-04-18 11:54       ` Dylanger Daly
2019-04-18 11:54         ` [Xen-devel] " Dylanger Daly

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=CANJ4vQ1nOuFZw0kk0dWEsx4Q0h8YE2H8gRzg422cRf65FAkncg@mail.gmail.com \
    --to=dylanger@thegrail.co \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-devel@lists.xenproject.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 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.