On 10/03/2018 01:54 PM, Reinette Chatre wrote:
> Hi Babu,
>
> On 10/2/2018 4:41 PM, Moger, Babu wrote:
>> On 10/02/2018 02:21 PM, Reinette Chatre wrote:
>>> On 9/24/2018 12:19 PM, Moger, Babu wrote:
static enum cpuhp_state rdt_online;
@@ -866,8 +872,22 @@ static int __init rdt_late_in
Hi Babu,
On 10/2/2018 4:41 PM, Moger, Babu wrote:
> On 10/02/2018 02:21 PM, Reinette Chatre wrote:
>> On 9/24/2018 12:19 PM, Moger, Babu wrote:
>>> static enum cpuhp_state rdt_online;
>>> @@ -866,8 +872,22 @@ static int __init rdt_late_init(void)
>>> struct rdt_resource *r;
>>> int state,
Hi Reinette,
Thanks for the review. My response below.
On 10/02/2018 02:21 PM, Reinette Chatre wrote:
> Hi Babu,
>
> On 9/24/2018 12:19 PM, Moger, Babu wrote:
>> Re-organize the RDT init code. Separate the call sequence for each
>> feature. That way, it is easy to call quirks or features separate
Hi Babu,
On 9/24/2018 12:19 PM, Moger, Babu wrote:
> Re-organize the RDT init code. Separate the call sequence for each
> feature. That way, it is easy to call quirks or features separately
> for each vendor if there are differences.
>
> Signed-off-by: Babu Moger
> ---
> arch/x86/kernel/cpu/rdt
Re-organize the RDT init code. Separate the call sequence for each
feature. That way, it is easy to call quirks or features separately
for each vendor if there are differences.
Signed-off-by: Babu Moger
---
arch/x86/kernel/cpu/rdt.c | 44 ---
1 file changed, 3
5 matches
Mail list logo