Hi Daniel,
On Mon, Feb 25, 2019 at 4:01 PM Daniel Lezcano
wrote:
>
>
> Hi Rafael,
>
> On 22/02/2019 11:35, Rafael J. Wysocki wrote:
> > On Thu, Feb 21, 2019 at 6:40 PM Daniel Lezcano
> > wrote:
> >>
> >> On 21/02/2019 17:18, Rafael J. Wysocki wrote:
> >>> On Thu, Feb 21, 2019 at 3:56 PM Daniel L
Hi Rafael,
On 22/02/2019 11:35, Rafael J. Wysocki wrote:
> On Thu, Feb 21, 2019 at 6:40 PM Daniel Lezcano
> wrote:
>>
>> On 21/02/2019 17:18, Rafael J. Wysocki wrote:
>>> On Thu, Feb 21, 2019 at 3:56 PM Daniel Lezcano
>>> wrote:
Predicting the next event on the current CPU is impleme
On Thu, Feb 21, 2019 at 6:40 PM Daniel Lezcano
wrote:
>
> On 21/02/2019 17:18, Rafael J. Wysocki wrote:
> > On Thu, Feb 21, 2019 at 3:56 PM Daniel Lezcano
> > wrote:
> >>
> >> Predicting the next event on the current CPU is implemented in the
> >> idle state selection function, thus the selection
On 21/02/2019 17:18, Rafael J. Wysocki wrote:
> On Thu, Feb 21, 2019 at 3:56 PM Daniel Lezcano
> wrote:
>>
>> Predicting the next event on the current CPU is implemented in the
>> idle state selection function, thus the selection logic and the
>> prediction are tied together and it is hard to deco
On Thu, Feb 21, 2019 at 3:56 PM Daniel Lezcano
wrote:
>
> Predicting the next event on the current CPU is implemented in the
> idle state selection function, thus the selection logic and the
> prediction are tied together and it is hard to decorrelate both.
>
> The following change introduces the
5 matches
Mail list logo