From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Shaohua Li" <shaohua.li@intel.com>
Cc: "Zhang, Yanmin" <yanmin.zhang@intel.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_PCIEASPM needed for ASPM?
Date: Thu, 23 Oct 2008 19:58:06 -0700 [thread overview]
Message-ID: <43e72e890810231958n2ef4f709k86e3d3adf81f5f73@mail.gmail.com> (raw)
In-Reply-To: <20081024024747.GA3900@sli10-desk.sh.intel.com>
On Thu, Oct 23, 2008 at 7:47 PM, Shaohua Li <shaohua.li@intel.com> wrote:
> On Fri, Oct 24, 2008 at 09:40:27AM +0800, Luis R. Rodriguez wrote:
>> I know, the question is silly right? I thought so too, but I started
>> reviewing the code and noticed most of it is just setting up values in
>> data structures for the kernel's awareness of capabilities, it also
>> updates the state in case of BIOS foobar, and there is also clock
>> retraining if possible to reduce latency. Is that it? Did I miss
>> something or is it really possible for devices to be able to use
>> L0s|L1 or L1 by just having a BIOS which does things correctly?
>>
>> That is can our devices be using ASPM without any OS interaction,
>> without CONFIG_PCIEASPM enabled?
> you didn't miss anything. If BIOS enables ASPM, even OS doesn't do anything,
> ASPM will be used.
I see, interesting... how about the clock selection and training? The
ASPM code has it, but without it will it have taken place in hardware
behind the scenes?
> ASPM enter/leave is controlled by hardware, OS just
> enables the capability.
What do you mean by the OS enabling the capability? All I see is
setting the capability bits on the pci struct so the OS can reflect
this internally and to userspace, say through lspci. Is that it?
Luis
next prev parent reply other threads:[~2008-10-24 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 1:40 CONFIG_PCIEASPM needed for ASPM? Luis R. Rodriguez
2008-10-24 2:47 ` Shaohua Li
2008-10-24 2:58 ` Luis R. Rodriguez [this message]
2008-10-24 5:42 ` Shaohua Li
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=43e72e890810231958n2ef4f709k86e3d3adf81f5f73@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=yanmin.zhang@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 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).