[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xen-unstable-smoke test] 169781: regressions - FAIL

To: Stefano Stabellini <sstabellini@xxxxxxxxxx>
From: Julien Grall <julien.grall.oss@xxxxxxxxx>
Date: Thu, 28 Apr 2022 00:13:15 +0100
Cc: osstest service owner <osstest-admin@xxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, David Vrabel <dvrabel@xxxxxxxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>
Delivery-date: Wed, 27 Apr 2022 23:13:34 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Hi Stefano,

On Thu, 28 Apr 2022, 00:02 Stefano Stabellini, <sstabellini@xxxxxxxxxx> wrote

It seems to me that it is acceptable to allocate memory with interrupt
disabled during __init. I cannot see any drawbacks with it. I think we
should change the ASSERT to only trigger after __init: system_state ==
SYS_STATE_active.

What do you think?

This would solve the immediate problem but not the long term one (i.e cpu hotplug).

So I think it would be better to properly fix it right away.

Cheers,

Follow-Ups:
- Re: [xen-unstable-smoke test] 169781: regressions - FAIL
  - From: Stefano Stabellini

References:
- [xen-unstable-smoke test] 169781: regressions - FAIL
  - From: osstest service owner
- Re: [xen-unstable-smoke test] 169781: regressions - FAIL
  - From: Julien Grall
- Re: [xen-unstable-smoke test] 169781: regressions - FAIL
  - From: Stefano Stabellini

Prev by Date: [PATCH 30/30] um: Avoid duplicate call to kmsg_dump()
Next by Date: Re: [PATCH 20/30] panic: Add the panic informational notifier list
Previous by thread: Re: [xen-unstable-smoke test] 169781: regressions - FAIL
Next by thread: Re: [xen-unstable-smoke test] 169781: regressions - FAIL
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.