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.gnu.org (lists.gnu.org [209.51.188.17]) (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 21224C47DD9 for ; Fri, 22 Mar 2024 08:51:37 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rnabg-00025Q-Bc; Fri, 22 Mar 2024 04:50:32 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rnabf-00025F-25 for qemu-devel@nongnu.org; Fri, 22 Mar 2024 04:50:31 -0400 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rnabR-0000Po-0G for qemu-devel@nongnu.org; Fri, 22 Mar 2024 04:50:29 -0400 Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id CFED83FB77 for ; Fri, 22 Mar 2024 08:50:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1711097408; bh=1NPyyWq4majbmi+xcXjpt8YWDG2Op46iJhonn7+pXvc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=S6j0j8T3iLp78mBd2ydeKqFq48q41zDPvicqmzqLaI24DUDt2MxnYrxsO7l0nhwof 9RrroDXD9K4bsYCNMUu+BDR6r1itMxuByFjSdCfT3LNKFgptqy1Qjw7AWwxiDlR0hm ot+yCRlJkgGaoa1AtX3Wn7w5ZQKh+x9Su6LhpnOWQqC32lYWc6i5GTHLdjGo/+Dwyg YfYqZyJrwlvnao3ts8BDSIGL0tN0QCU/sfmMk/CRw+zpBZXJmjrH/tDOzGlUuqhWSg 8dK8cRbaZfs5hMsxbuDpsmahl/akpfBaT4DrJA5Ilq0jnT0sXv1Nw1nB0nZUDbsxXH gLn9y43+LzKiQ== Received: by mail-wr1-f71.google.com with SMTP id ffacd0b85a97d-33ed8677d16so924861f8f.1 for ; Fri, 22 Mar 2024 01:50:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711097408; x=1711702208; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1NPyyWq4majbmi+xcXjpt8YWDG2Op46iJhonn7+pXvc=; b=sheIZwAlpo03w3VqxGtstROEOxkHlOd3Cqtaag7JDK1JyuNVnctbYQEDksI9qiLK1H isIJf6qGA/zG3PH5USew5lGRmReW6m4c2vdtc7AzeUgvSrLsDgveLFjFnchvjia9CZod zYvRsJSnva1JXA0ZLJWjFl7Z9p2UilqC4RoQhnrWIZYdgMIUqW5FSQTc1cGjFYGY+pw7 ohLxb4YKcHgzOfC3wa5sEVVpCqUHYNpV8eUTbNlfcVtfoRyNL4FZcyxvjtwkBvSojMux l056fUYxAOXNk7KUk6x47Xl+UrjT9xfe1ux8eGT4YpofYZU0/ez7ABdO3U7T9Lrd9dIm JG2g== X-Forwarded-Encrypted: i=1; AJvYcCX4HUUTyTfbdS+jC+KH+9BYpDONdNE/DvQ6OztpUYHVUaccC3moYZcVyy6uYDKp5iRnZKI6pNRreAe5m0ztjZ+vbjAqFpk= X-Gm-Message-State: AOJu0Yz+45hIuQ76LDugdRKhxhO3EunsXPRxF7xuTeMdPEOwJDS58YhI 2tkkc0h2wS0kADFbekNOLuzuIB6tDo7OhKFOQOa/hFNF6OSaydh53H8MOw/mSTQwV4HA85xL28h 1SKjmdFjxP2fQIf0xCuNQq7wm0BeW6igqyelA7O7ioqk6s9HayFyhasoO0xNk4EGiNFFM X-Received: by 2002:a5d:5506:0:b0:33e:6ac:691b with SMTP id b6-20020a5d5506000000b0033e06ac691bmr1064549wrv.9.1711097408280; Fri, 22 Mar 2024 01:50:08 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGf1SKFbtIZlVsgcDgnCK3o0R6C9ULWWIbfzhDWzRDzmP94uEOEmxqdwaBYKvL89leuB6rfEQ== X-Received: by 2002:a5d:5506:0:b0:33e:6ac:691b with SMTP id b6-20020a5d5506000000b0033e06ac691bmr1064516wrv.9.1711097407859; Fri, 22 Mar 2024 01:50:07 -0700 (PDT) Received: from [192.168.123.161] (ip-062-143-245-032.um16.pools.vodafone-ip.de. [62.143.245.32]) by smtp.gmail.com with ESMTPSA id bs20-20020a056000071400b0033e18421618sm1571856wrb.17.2024.03.22.01.50.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 22 Mar 2024 01:50:07 -0700 (PDT) Message-ID: Date: Fri, 22 Mar 2024 09:50:12 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC v2 2/2] hw/riscv: Add server platform reference machine To: Marcin Juszkiewicz Cc: pbonzini@redhat.com, palmer@dabbelt.com, alistair.francis@wdc.com, bin.meng@windriver.com, liwei1518@gmail.com, dbarboza@ventanamicro.com, zhiwei_liu@linux.alibaba.com, qemu-devel@nongnu.org, qemu-riscv@nongnu.org, andrei.warkentin@intel.com, shaolin.xie@alibaba-inc.com, ved@rivosinc.com, sunilvl@ventanamicro.com, haibo1.xu@intel.com, evan.chai@intel.com, yin.wang@intel.com, tech-server-platform@lists.riscv.org, tech-server-soc@lists.riscv.org, atishp@rivosinc.com, ajones@ventanamicro.com, conor@kernel.org, Fei Wu , Alistair Francis References: <20240312135222.3187945-1-fei2.wu@intel.com> <20240312135222.3187945-3-fei2.wu@intel.com> Content-Language: en-US From: Heinrich Schuchardt In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=185.125.188.123; envelope-from=heinrich.schuchardt@canonical.com; helo=smtp-relay-internal-1.canonical.com X-Spam_score_int: -47 X-Spam_score: -4.8 X-Spam_bar: ---- X-Spam_report: (-4.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.372, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On 3/22/24 08:14, Marcin Juszkiewicz wrote: > W dniu 22.03.2024 o 05:55, Alistair Francis pisze: >> I see no mention of device trees in the spec, but I do see ACPI. Do we >> really expect a server platform to use DTs? > > This platform "kind of" follows sbsa-ref where we have very minimalistic > device tree sharing information qemu->firmware. > > libfdt is small, format is known and describes hardware. Firmware is > free to make use of it in any way it wants. > > On sbsa-ref we parse DT in TF-A (base firmware) and provide hardware > information to higher level (edk2) via SMC mechanism. Then EDK2 creates > ACPI tables and provide them to the Operating System. We should ensure that only either an ACPI table or a device-tree description is passed to the OS and not both, e.g. when using qemu-system-riscv64 -kernel vmlinux -M sbsa-ref But that requirement is not machine specific. Best regards Heinrich > > In physical system some parts of information provided in DT would be > read by firmware from onboard Embedded Controller chip. > >> These functions should be shared with the virt machine if we really do >> want DTs, but I'm not convinced we do >