[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87h5sl3hv3.ffs@tglx>
Date: Fri, 16 Jan 2026 12:41:04 +0100
From: Thomas Gleixner <tglx@...nel.org>
To: Yicong Yang <yang.yicong@...oheart.com>, Anup Patel
<apatel@...tanamicro.com>
Cc: yang.yicong@...oheart.com, anup@...infault.org, pjw@...nel.org,
palmer@...belt.com, aou@...s.berkeley.edu, alex@...ti.fr,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
geshijian@...oheart.com, weidong.wd@...oheart.com, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, "Rafael J. Wysocki" <rafael@...nel.org>,
Danilo Krummrich <dakr@...nel.org>
Subject: Re: [PATCH] irqchip/riscv-aplic: Register the driver prior to
device creation
On Fri, Jan 16 2026 at 14:16, Yicong Yang wrote:
> On 1/15/26 9:28 PM, Thomas Gleixner wrote:
>> On Thu, Jan 15 2026 at 16:31, Yicong Yang wrote:
>>> so based on above, if we use async_wq (with async_schedule* APIs) in
>>> acpi_scan_clear_dep_queue() for creating these devices, the issue
>>> could be solved since we're sure to have these devices before entering
>>> userspace, since the barrier of async_synchronize_full(). This should be
>>> a solution with a conceptual support and I did a quick test on our
>>> platform it solves the issue.
>>
>> Sounds about right to me. The drivers core and ACPI folks might have
>> opinions though :)
>>
> sure I'll wait a bit to see if there's further comment before sending out
> next version.
Btw, there is a reason that this is on the default work queue. See
commit dc612486c919 ("ACPI: scan: Fix device object rescan in
acpi_scan_clear_dep()")
for details. So this needs some more thought.
Thanks,
tglx
Powered by blists - more mailing lists