Hello Dario,
On Thu, 28 Mar 2019 at 16:54, Dario Faggioli wrote:
>
> On Thu, 2019-03-28 at 15:56 +0200, Volodymyr Babchuk wrote:
> > On Thu, 28 Mar 2019 at 15:33, Julien Grall
> > wrote:
> > >
> > Are the logs below actually a mistaken paste?
> > No, this is what I'm seeing in my serial console.
On Thu, 2019-03-28 at 15:56 +0200, Volodymyr Babchuk wrote:
> On Thu, 28 Mar 2019 at 15:33, Julien Grall
> wrote:
> >
> Are the logs below actually a mistaken paste?
> No, this is what I'm seeing in my serial console.
>
Err, sorry, I'm a bit confused now...
So, if you use the ARM suspend/resume
Hi,
On 3/28/19 1:56 PM, Volodymyr Babchuk wrote:
On Thu, 28 Mar 2019 at 15:33, Julien Grall wrote:
On 3/28/19 1:01 PM, Volodymyr Babchuk wrote:
On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
(XEN)
(XEN) Panic on CPU 0:
(XEN) PSCI cpu off failed
Hello Julien,
On Thu, 28 Mar 2019 at 15:33, Julien Grall wrote:
>
> Hi,
>
> On 3/28/19 1:01 PM, Volodymyr Babchuk wrote:
> > Hello Juergen,
> >
> > On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
> >>
> >> Especially in the scheduler area (schedule.c, cpupool.c) there is a
> >> rather complex
On 28/03/2019 13:37, Juergen Gross wrote:
> On 28/03/2019 14:33, Julien Grall wrote:
>> Hi,
>>
>> On 3/28/19 1:01 PM, Volodymyr Babchuk wrote:
>>> Hello Juergen,
>>>
>>> On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
Especially in the scheduler area (schedule.c, cpupool.c) there is
On 28/03/2019 14:33, Julien Grall wrote:
> Hi,
>
> On 3/28/19 1:01 PM, Volodymyr Babchuk wrote:
>> Hello Juergen,
>>
>> On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
>>>
>>> Especially in the scheduler area (schedule.c, cpupool.c) there is a
>>> rather complex handling involved when doing su
Hi,
On Thu, 28 Mar 2019 at 15:21, Juergen Gross wrote:
>
> On 28/03/2019 14:01, Volodymyr Babchuk wrote:
> > Hello Juergen,
> >
> > On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
> >>
> >> Especially in the scheduler area (schedule.c, cpupool.c) there is a
> >> rather complex handling involv
Hi,
On 3/28/19 1:01 PM, Volodymyr Babchuk wrote:
Hello Juergen,
On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
Especially in the scheduler area (schedule.c, cpupool.c) there is a
rather complex handling involved when doing suspend and resume.
This can be simplified a lot by not performi
On 3/28/19 1:21 PM, Juergen Gross wrote:
On 28/03/2019 14:01, Volodymyr Babchuk wrote:
Hello Juergen,
On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
Especially in the scheduler area (schedule.c, cpupool.c) there is a
rather complex handling involved when doing suspend and resume.
This
On 28/03/2019 14:01, Volodymyr Babchuk wrote:
> Hello Juergen,
>
> On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
>>
>> Especially in the scheduler area (schedule.c, cpupool.c) there is a
>> rather complex handling involved when doing suspend and resume.
>>
>> This can be simplified a lot by
Hello Juergen,
On Thu, 28 Mar 2019 at 14:09, Juergen Gross wrote:
>
> Especially in the scheduler area (schedule.c, cpupool.c) there is a
> rather complex handling involved when doing suspend and resume.
>
> This can be simplified a lot by not performing a complete cpu down and
> up cycle for the
Especially in the scheduler area (schedule.c, cpupool.c) there is a
rather complex handling involved when doing suspend and resume.
This can be simplified a lot by not performing a complete cpu down and
up cycle for the non-boot cpus, but keeping the pure software related
state and freeing it only
12 matches
Mail list logo
