From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] PCI Express ASPM support should default to 'No'
Date: Thu, 24 Apr 2008 08:33:19 -0700 [thread overview]
Message-ID: <200804240833.19614.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1209024126.7479.0.camel@sli10-desk.sh.intel.com>
On Thursday, April 24, 2008 1:02 am Shaohua Li wrote:
> On Thu, 2008-04-24 at 09:49 +0200, Andi Kleen wrote:
> > Shaohua Li <shaohua.li@intel.com> writes:
> > > Ok, I'm fine with the patch. Though by default, the policy is to use
> > > BIOS setting, that is if BIOS disables ASPM, we don't enable it too.
> >
> > Once the feature is considered stable it would be nice to make it
> > default y
> > again. I think any power saving should be on by default (unless
> > serious
> > issues are known), not off.
>
> yes, we could do it in next release.
When we move to 'default y' we should also update the Kconfig text, removing
the experimental tag and changing the advice.
And yeah, I'd like to save power by default too, but do you think this has
seen enough test coverage to enable it by default? Do we know of any
platforms where ASPM causes problems because the BIOS enabled it and we tried
to use it?
Thanks,
Jesse
next prev parent reply other threads:[~2008-04-24 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 22:28 [PATCH] PCI Express ASPM support should default to 'No' Jesper Juhl
2008-04-23 0:12 ` Jesse Barnes
2008-04-23 1:05 ` Shaohua Li
2008-04-23 22:46 ` Jesse Barnes
2008-04-24 7:49 ` Andi Kleen
2008-04-24 8:02 ` Shaohua Li
2008-04-24 15:33 ` Jesse Barnes [this message]
2008-04-25 1:16 ` Shaohua Li
2008-04-27 20:01 ` Jesper Juhl
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=200804240833.19614.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=andi@firstfloor.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shaohua.li@intel.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.