lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 3 Apr 2017 10:50:07 -0700
From:   Hoan Tran <>
To:     "Prakash, Prashanth" <>
Cc:     George Cherian <>,
        linux acpi <>,
        lkml <>,,
        Ashwin Chaugule <>,
        "Rafael J. Wysocki" <>,
        Len Brown <>,
        Jassi Brar <>,
        Robert Moore <>,
        Lv Zheng <>
Subject: Re: [PATCH 0/2] Make cppc acpi driver aware of pcc subspace ids

Hi George,

On Mon, Apr 3, 2017 at 9:44 AM, Prakash, Prashanth
<> wrote:
> Hi George,
> On 3/31/2017 12:24 AM, George Cherian wrote:
>> The current cppc acpi driver works with only one pcc subspace id.
>> It maintains and registers only one pcc channel even if the acpi table has
>> different pcc subspace ids. The series tries to address the same by making
>> cppc acpi driver aware of multiple possible pcc subspace ids.
> The current ACPI 6.1 spec restricts the CPPC to a single PCC subspace. See section:
> Using PCC Registers, which states "If the PCC register space is used, all PCC
> registers must be defined to be in the same subspace."

Agreed with Prashanth, beside of that, spec also says "To amortize the
cost of PCC transactions, OSPM should read or
write all PCC registers via a single read or write command when possible."


> --
> Thanks,
> Prashanth
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to
> More majordomo info at

Powered by blists - more mailing lists