From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BF176350D58 for ; Thu, 15 Jan 2026 13:28:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768483713; cv=none; b=srckk8G9deVg8tZ2lo+FVEyA54cULcnhidMelP4vyM/9YcgdSxKpFFDrk/9DugCRXntAbEB5gGusDYsfEqJoHvaBspEb38i+0Es5FoBNA90MEUZluU8AMmELaLc1Z/CGGCoowddbaUGH05GHXdCsB98Uv1CmMQ1o/lfbo+NuMw0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768483713; c=relaxed/simple; bh=KkguYVdhvZYXRcg/IO6o4pzafy0TJxYwSM1Upcj7g1A=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=iXJrTrTIL0EfnLFGGxFkX7LbDQdx4sawykGpGTsO7gdPhp0SvxCfLSkoH/kVuH1LmCHN/1VPWED4ONUjgmtujA2S3CPU/Q7HZFD/86MY0TqgCr/KtQAUheUI2aEz2KtvlOhbg0zmCtADy9XnbGGhhevL9t4Q0+TNIVAaiycQVPA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=koAXMGkF; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="koAXMGkF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B34A3C16AAE; Thu, 15 Jan 2026 13:28:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768483713; bh=KkguYVdhvZYXRcg/IO6o4pzafy0TJxYwSM1Upcj7g1A=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=koAXMGkFOUqcNCjLP3cQMW7EarvWVDLzAWDpHjePVFKOj9a5RgGs4T00AnPTMzQ00 //ahHQPUMq+evkJe8Y4IJBdFwuPJEPlW+kdw1hvuS48Tz6EJ5E2PfTOE+PpF4fF2Ao mBYoJTzyIZ0+YhtHrocnIB28PCyLe8/+SCY3JGAalOh/eSv/4TE2BeTQBSI5zAjZcI 7U2bjN0WTb4sFvFebyXPU65TXogFcgPH53bvFAC/LvOft8ux9wthiGIpFQnC3x0xeg Y2aZMHZQHexB/UeeDPtxAfyPueDAL5Chz9mHW5YEAFb1whWAeW6qiHTUplLL4SYHbo y+Hkmite6mQow== From: Thomas Gleixner To: Yicong Yang , Anup Patel Cc: yang.yicong@picoheart.com, anup@brainfault.org, pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, geshijian@picoheart.com, weidong.wd@picoheart.com, Greg Kroah-Hartman , "Rafael J. Wysocki" , Danilo Krummrich Subject: Re: [PATCH] irqchip/riscv-aplic: Register the driver prior to device creation In-Reply-To: References: <20260114063730.78009-1-yang.yicong@picoheart.com> <7b859dd5-9262-4d68-9a8e-e0be0c24ac4a@picoheart.com> <877btkht2v.ffs@tglx> Date: Thu, 15 Jan 2026 14:28:29 +0100 Message-ID: <87y0lz2ef6.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain 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 :) > As for the order of console_on_rootfs()/async_synchronize_full(), > though our issue is not directly caused by it, it will cause the > same issue (by the console open time the async probing maybe not > finised) theoretically and needs to be fixed, is it? Yes, that should move past the synchronization point. Thanks, tglx