Re: [RFC PATCH 1/5] RISC-V: Add logical CPU indexing for RISC-V

On Thu, Aug 16, 2018 at 10:47 AM, Atish Patra wrote: > On 8/15/18 9:06 PM, Anup Patel wrote: >> >> On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote: >>> >>> Currently, both linux cpu id and hardware cpu id are same. >>> This is not recommended as it will lead to discontinuous cpu >>> indexing i

Re: [RFC PATCH 1/5] RISC-V: Add logical CPU indexing for RISC-V

On 8/15/18 9:06 PM, Anup Patel wrote: On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote: Currently, both linux cpu id and hardware cpu id are same. This is not recommended as it will lead to discontinuous cpu indexing in Linux. Moreover, kdump kernel will run from CPU0 which would be absent if

Re: [RFC PATCH 1/5] RISC-V: Add logical CPU indexing for RISC-V

On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote: > Currently, both linux cpu id and hardware cpu id are same. > This is not recommended as it will lead to discontinuous cpu > indexing in Linux. Moreover, kdump kernel will run from CPU0 > which would be absent if we follow existing scheme. > > I

[RFC PATCH 1/5] RISC-V: Add logical CPU indexing for RISC-V

Currently, both linux cpu id and hardware cpu id are same. This is not recommended as it will lead to discontinuous cpu indexing in Linux. Moreover, kdump kernel will run from CPU0 which would be absent if we follow existing scheme. Implement a logical mapping between Linux cpu id and hardware cpu