All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Wei Wang <wei.w.wang@intel.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	wei.liu2@citrix.com, jbeulich@suse.com
Subject: Re: intel_pstate driver patches by Wei Wang from 2015
Date: Mon, 17 Dec 2018 12:09:27 +0100	[thread overview]
Message-ID: <20181217110927.GA23474@mail-itl> (raw)
In-Reply-To: <5C176180.3090200@intel.com>


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

On Mon, Dec 17, 2018 at 04:42:40PM +0800, Wei Wang wrote:
> On 12/14/2018 10:16 PM, Marek Marczykowski-Górecki wrote:
> > Hi,
> > 
> > I wonder what happened to intel_pstate patch series[1] back in 2015?
> > I've seen there was some review feedback[2][3][4][5][6][7] on v6,
> > patches 4/6 and 6/6 were acked. Were the review comments ever addressed
> > (can't find it)?  Or maybe there is some other mechanism in place for proper
> > power management on recent Intel CPUs? Apparently acpi-cpufreq driver
> > not always does its job well[8].
> > 
> > [1] https://lists.xenproject.org/archives/html/xen-devel/2015-10/msg03048.html
> > [2] https://lists.xenproject.org/archives/html/xen-devel/2015-11/msg02043.html
> > [3] https://lists.xenproject.org/archives/html/xen-devel/2015-11/msg02410.html
> > [4] https://lists.xenproject.org/archives/html/xen-devel/2015-11/msg02430.html
> > [5] https://lists.xenproject.org/archives/html/xen-devel/2015-11/msg02443.html
> > [6] https://lists.xenproject.org/archives/html/xen-devel/2015-11/msg02456.html
> > [7] https://lists.xenproject.org/archives/html/xen-devel/2015-10/msg03086.html
> > [8] https://github.com/QubesOS/qubes-issues/issues/4604#issuecomment-446816536
> > 
> 
> Hi Marek,
> 
> It was paused because there was no users in the clouds - people usually have
> P-state disabled.

I see. FWIW Xen have also non-cloud use cases, like Qubes OS.

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 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:[~2018-12-17 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 14:16 intel_pstate driver patches by Wei Wang from 2015 Marek Marczykowski-Górecki
2018-12-17  8:42 ` Wei Wang
2018-12-17 11:09   ` Marek Marczykowski-Górecki [this message]
2018-12-17 13:19     ` Andrew Cooper
2018-12-17 14:59       ` Wang, Wei W

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=20181217110927.GA23474@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=jbeulich@suse.com \
    --cc=wei.liu2@citrix.com \
    --cc=wei.w.wang@intel.com \
    --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.