On Wed, 25 Feb 2015 16:39:42 +0800
, Hanjun Guo
wrote:
> CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
> but phys_id is used as int in acpi processor driver, so it will lead to
> some inconsistence for the drivers.
>
> Furthermore, to cater for ACPI arch ports that
On Wed, 25 Feb 2015 16:39:42 +0800
, Hanjun Guo hanjun@linaro.org
wrote:
CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
but phys_id is used as int in acpi processor driver, so it will lead to
some inconsistence for the drivers.
Furthermore, to cater for ACPI
On 2015/3/5 21:23, Rafael J. Wysocki wrote:
> On Thu, Mar 5, 2015 at 8:44 AM, Hanjun Guo wrote:
>> On 2015/3/5 6:29, Rafael J. Wysocki wrote:
>>> On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
> [cut]
>
@@ -190,7 +190,7 @@ int acpi_map_cpuid(int phys_id, u32 acpi_id)
On Thu, Mar 5, 2015 at 8:44 AM, Hanjun Guo wrote:
> On 2015/3/5 6:29, Rafael J. Wysocki wrote:
>> On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
[cut]
>>> @@ -190,7 +190,7 @@ int acpi_map_cpuid(int phys_id, u32 acpi_id)
>>> if (nr_cpu_ids <= 1 && acpi_id == 0)
>>>
On 2015/3/5 21:23, Rafael J. Wysocki wrote:
On Thu, Mar 5, 2015 at 8:44 AM, Hanjun Guo guohan...@huawei.com wrote:
On 2015/3/5 6:29, Rafael J. Wysocki wrote:
On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
[cut]
@@ -190,7 +190,7 @@ int acpi_map_cpuid(int phys_id, u32 acpi_id)
On Thu, Mar 5, 2015 at 8:44 AM, Hanjun Guo guohan...@huawei.com wrote:
On 2015/3/5 6:29, Rafael J. Wysocki wrote:
On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
[cut]
@@ -190,7 +190,7 @@ int acpi_map_cpuid(int phys_id, u32 acpi_id)
if (nr_cpu_ids = 1 acpi_id ==
On 2015/3/5 6:29, Rafael J. Wysocki wrote:
> On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
>> CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
>> but phys_id is used as int in acpi processor driver, so it will lead to
>> some inconsistence for the drivers.
On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
> CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
> but phys_id is used as int in acpi processor driver, so it will lead to
> some inconsistence for the drivers.
>
> Furthermore, to cater for ACPI arch ports
On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
but phys_id is used as int in acpi processor driver, so it will lead to
some inconsistence for the drivers.
Furthermore, to cater for ACPI arch ports that
On 2015/3/5 6:29, Rafael J. Wysocki wrote:
On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
but phys_id is used as int in acpi processor driver, so it will lead to
some inconsistence for the drivers.
CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
but phys_id is used as int in acpi processor driver, so it will lead to
some inconsistence for the drivers.
Furthermore, to cater for ACPI arch ports that implement 64 bits CPU
ids a generic CPU physical id type is required.
CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
but phys_id is used as int in acpi processor driver, so it will lead to
some inconsistence for the drivers.
Furthermore, to cater for ACPI arch ports that implement 64 bits CPU
ids a generic CPU physical id type is required.
12 matches
Mail list logo
