On 2018-06-01 15:02, Joel Fernandes wrote:
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
On 2018-05-25 14:13, Byungchul Park wrote:
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay on
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
>
>
> On 2018-05-25 14:13, Byungchul Park wrote:
> >
> >
> > On 2018-05-09 15:33, Byungchul Park wrote:
> > > On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
> > > >
> > > >
> > > > Sorry for the huge delay on thi
On 2018-05-25 14:13, Byungchul Park wrote:
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Please consider this. Even
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Please consider this. Even though it's not a big bug, anyway leading
mis-b
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
>
>
> Sorry for the huge delay on this, but I'll have to postpone further.
> Still busy with meltdown/spectre stuff.
Please consider this. Even though it's not a big bug, anyway leading
mis-behavior in certain situaions.
On 3/13/2018 2:52 PM, Byungchul Park wrote:
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Could you review the patch?
Hello,
Could you see the patch now?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Could you review the patch?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Do you have time to see the patch, now that it seems to be managed
to solve those security issues?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Do you have time to see these patches and another set, now?
--
Thanks,
Byungchul
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
1
From: Byungchul Park
Date: Wed, 22 Mar 2017 14:25:56 +0900
Subject: [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for
clean-up
Current code uses cpudl_maximum() to get the root node's cpu, while it
directly accesses the root node like 'cp->elements[0].dl' to get the
roo
1
From: Byungchul Park
Date: Wed, 22 Mar 2017 14:25:56 +0900
Subject: [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for
clean-up
Current code uses cpudl_maximum() to get the root node's cpu, while it
directly accesses the root node like 'cp->elements[0].dl' to get the
roo
Hello, shall I stop sending this? Let me know if so.
> -8<-
> >From 7735382d07ae6a61d740ae39ba2ecf169d43b8a2 Mon Sep 17 00:00:00 2001
> From: Byungchul Park
> Date: Wed, 22 Mar 2017 14:25:56 +0900
> Subject: [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_d
1
From: Byungchul Park
Date: Wed, 22 Mar 2017 14:25:56 +0900
Subject: [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for
clean-up
Current code uses cpudl_maximum() to get the root node's cpu, while it
directly accesses the root node like 'cp->elements[0].dl' to get the
roo
14 matches
Mail list logo
