From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EEF35C83030 for ; Mon, 30 Jun 2025 12:13:27 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.1029107.1402843 (Exim 4.92) (envelope-from ) id 1uWDNs-000765-6S; Mon, 30 Jun 2025 12:13:16 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1029107.1402843; Mon, 30 Jun 2025 12:13:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1uWDNs-00075y-3X; Mon, 30 Jun 2025 12:13:16 +0000 Received: by outflank-mailman (input) for mailman id 1029107; Mon, 30 Jun 2025 12:13:14 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1uWDNq-00075s-Ji for xen-devel@lists.xenproject.org; Mon, 30 Jun 2025 12:13:14 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.96) (envelope-from ) id 1uWDNp-00AGvf-2U; Mon, 30 Jun 2025 12:13:13 +0000 Received: from [2a02:8012:3a1:0:a1f7:3d35:dea1:a2b4] by xenbits.xenproject.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uWDNp-00F6om-1N; Mon, 30 Jun 2025 12:13:13 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID; bh=QQ1WRMOpNU2NBRAXTEDFPiuLs+JzVHf1HANAaT0glPU=; b=HiSDNAvELHA7+LK1XJPAgeNKCk LDCK8Ym4RK91lxAJDqiaqqE1ZwehsY0CDkbJK5Xoh5aWVqMK4ZtnmlrMbhU2mIlVw1lz7EkySGZCR y542k4Qi2McXKHiWD4FKW7d6kMgR3/kSZ7AVq95ZNAIQLgsIc0T4XlnziET9ceagSNqA=; Message-ID: <5992e6bf-e9ea-480f-bcd3-a6cf1c335190@xen.org> Date: Mon, 30 Jun 2025 13:13:10 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC PATCH v4 8/8] docs: armproposa: l to add separate SCMI node for Xen agent To: Oleksii Moisieiev , Stefano Stabellini Cc: "xen-devel@lists.xenproject.org" , Andrew Cooper , Anthony PERARD , Bertrand Marquis , Jan Beulich , Juergen Gross , Michal Orzel , =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , Volodymyr Babchuk , Grygorii Strashko References: <3f7e1e99f5d1018064f3c4825aff16bd487cf558.1747669845.git.oleksii_moisieiev@epam.com> <3468bb57-3178-460b-8fb2-3ce106475319@xen.org> <41566d23-464b-4676-8e01-e2f27d377a94@xen.org> <6689b22a-f85e-40ba-a89b-7935df1bdd28@epam.com> Content-Language: en-US From: Julien Grall In-Reply-To: <6689b22a-f85e-40ba-a89b-7935df1bdd28@epam.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, On 30/06/2025 12:57, Oleksii Moisieiev wrote: > KVM [1] is not applicable here as it starts under/inside Linux, so it > doesn't have direct access to SCMI, the Linux does. > And Linux will see only one SCMI transport (Agent). > Seems, the only option possible is virtio-scmi (qemu) - the virtio-scmi > potentially can simulate multi-channel, > but this is out if scope of this work. > QNX [0] relies on configuration files rather than the Device Tree. To clarify, I didn't ask to implement anything in KVM or QNX. I asked to write the bindings in a way that they are not Xen specific to give a chance to for other to re-use them. Yes today KVM and QNX would not use them... But I also still don't see why we should actively prevent them to use the bindings you come up with... Cheers, -- Julien Grall