Hi Bjorn,
Thanks for the review. Other feedback below.
On 1/27/2017 12:07 PM, Bjorn Helgaas wrote:
> Hi Sinan,
>
> On Thu, Jan 26, 2017 at 05:51:32PM -0500, Sinan Kaya wrote:
>> When the operating system is booted with the default ASPM policy,
>> the current code is determining the ASPM policy
Hi Bjorn,
Thanks for the review. Other feedback below.
On 1/27/2017 12:07 PM, Bjorn Helgaas wrote:
> Hi Sinan,
>
> On Thu, Jan 26, 2017 at 05:51:32PM -0500, Sinan Kaya wrote:
>> When the operating system is booted with the default ASPM policy,
>> the current code is determining the ASPM policy
Hi Sinan,
On Thu, Jan 26, 2017 at 05:51:32PM -0500, Sinan Kaya wrote:
> When the operating system is booted with the default ASPM policy,
> the current code is determining the ASPM policy by querying the
> enable/disable states from ASPM registers.
>
> In the case of hotplug removal, the ASPM
Hi Sinan,
On Thu, Jan 26, 2017 at 05:51:32PM -0500, Sinan Kaya wrote:
> When the operating system is booted with the default ASPM policy,
> the current code is determining the ASPM policy by querying the
> enable/disable states from ASPM registers.
>
> In the case of hotplug removal, the ASPM
When the operating system is booted with the default ASPM policy,
the current code is determining the ASPM policy by querying the
enable/disable states from ASPM registers.
In the case of hotplug removal, the ASPM registers get cleared by
calling the exit function.
An insertion following remove
When the operating system is booted with the default ASPM policy,
the current code is determining the ASPM policy by querying the
enable/disable states from ASPM registers.
In the case of hotplug removal, the ASPM registers get cleared by
calling the exit function.
An insertion following remove
6 matches
Mail list logo