[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2] xen/arm: Move static event channel feature to a separate module
- To: Michal Orzel <michal.orzel@xxxxxxx>
- From: Luca Fancellu <Luca.Fancellu@xxxxxxx>
- Date: Thu, 30 Nov 2023 13:17:46 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
- Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=LhmCmeazCrVjVTIlI8sjbwjNGKrZZLrBpFK10H5oIZc=; b=boTG4wV27cRipYLuqpo9J8cPxllnJYrfoqLLR6jM4JOP2OmPEn3HEYSBr3H9GLmNpQGFvOm5EnzLd3iaL48F9FpNALyWfZAPn/UkjoFxaTK+sujieTULoKfUKhKS5d8ygrT4GYGB+PPy327q+VMH2ZNynpwu6Tc+PHv1MuNlyF4EfXKs2ABocRIVHDveiztob35IHdFlcajKVhqQNVC+U1ljKYo3hJwF412fdqXMCoy5odMB5YPTAAxprDtRxY6T7xcibnlRQVaT36kKNMbrbHyrup0R1kSPDENF8jzhl4XA6WiT3kYrI9Mcu8EYZeZcJulQ9R5QvnkmbV2jvoRZbw==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=LhmCmeazCrVjVTIlI8sjbwjNGKrZZLrBpFK10H5oIZc=; b=T1Dz7eo7c7zU6QKSGQ1x7iFjNUtSAJaXT5oTlDFiZzJnC6MLS23S9kbwAhmzb8wb+2hWaoKYqMgzUyAj0//UScHqhn26daUGVmg/eBZj2fApSw49VAza5tJAdt9Sa/pt6KAsoQr6dEYebXWHe2vpGwl7aLLXCj69m8qFlxAZaIlNl5vMkgEWqjywFK58WS79ZjqsewjdF7wxy1D3C+ZSKEI6RQAdTCeKaa3RRL2RiPPwv+6buQToQPuU6u8ypv5kXQZbYvYn311sIa76/ZJztt54g/5zQLiEjwF2TRge1HZAy6A7XmNqnXZ9/DBG1C7akwDKAth5v59dEqKeSEqNZw==
- Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=keSW1HYwdbmTjxwB2PfaavIMO8M5l+rcx03qJsNxm9UgutD2d0yw53fHOIiykvTUkXqfEqaQlUtM00eVQdmnFKrvy0IxYXAyj+1S9RGI3LM1EdH/ousWxdQDuBqoLKzlgb+7wrsJHE6zUwVbTwFytLxhJOaJxqB2kWQeh7Pk67JnOQa4Uy3DaPtNGuaEv6M7OsC3M3n7LCd/WOULWBVPAJ1nr8cK59p9YTH926yw+eWPY1wrltPm5JQKRxXW5L/36rFUY/JqZ5Uqpr8+Eh11DPz3aTpSIwCV81fyvvBZJ6CuGAMKeUhNuensrH0xziF/eW/KcMk4EYG8Na1n4iZH1Q==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=i/0O+5gzmy2arHa7i/zWH4BKSACzdWtdkWEdaYhrVZ7OU6Cg7J7Sg8seTsRWbp+v0IUH2ZY1PKA8pVn7pQ8u8ptVEQ2x9kgsyfmudNoo+IIVaFM/j4Ktywp/DWFSqQLVVWRWsz9MWtRaNQ+/Kj2AKLSD+G15G1FogRvyF0wZEYbYk3h1Gz2D10GoY/SRLB7PGs1LR99NUTeUPPN1fDM6IDr3sa3AFcsUegvs49RKZR6Vc2jRfl3CahrYnoy52i58+HdyVwWtwNEH7DbrmnPukYy6dGFDsJVlsi9ZXpqVfL4iX2F6YjH/SKJ8X3TiJv0LITblL7K+0QkEKS2PnUzaUg==
- Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
- Delivery-date: Thu, 30 Nov 2023 13:18:13 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Nodisclaimer: true
- Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Thread-index: AQHaI3PLyHz5Q1Ih30+bcD6BASdasLCS2EKA
- Thread-topic: [PATCH v2] xen/arm: Move static event channel feature to a separate module
> On 30 Nov 2023, at 09:57, Michal Orzel <michal.orzel@xxxxxxx> wrote:
>
> Move static event channel feature related code to a separate module
> (static-evtchn.{c,h}) in the spirit of fine granular configuration, so
> that the feature can be disabled if not needed.
>
> Introduce Kconfig option CONFIG_STATIC_EVTCHN, enabled by default (to
> keep the current behavior) dependent on CONFIG_DOM0LESS. While it could
> be possible to create a loopback connection for dom0 only, this use case
> does not really need this feature and all the docs and commit messages
> refer explicitly to the use in dom0less system.
>
> The only function visible externally is alloc_static_evtchn(), so move
> the prototype to static-evtchn.h and provide a stub in case a feature
> is disabled. Guard static_evtchn_created in struct dt_device_node as
> well as its helpers.
>
> Signed-off-by: Michal Orzel <michal.orzel@xxxxxxx>
> ---
Hi Michal,
FWIW because it is already Ack-ed.
Reviewed-by: Luca Fancellu <luca.fancellu@xxxxxxx>
|
