From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail05.groups.io (mail05.groups.io [45.79.224.7]) by spool.mail.gandi.net (Postfix) with ESMTPS id D050A780091 for ; Mon, 13 May 2024 09:23:12 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=H7AWaHAwH5f7tlKc7xK4zN4M5wfi+mj2m7FBAbg6DGY=; c=relaxed/simple; d=groups.io; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:In-Reply-To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Resent-Date:Resent-From:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type:Content-Disposition; s=20240206; t=1715592191; v=1; b=xKKw/TIE2wLzTJHaqonCppfGadu84TRVpwyK2Pjv8ZpZBmYrC1HujpSy/9lHdcppZQOZek0x B1zraa3Bt2BPBixD/YPDi376mFrthKlLE+qhh73KMV8kbzFwnKxaC8+99lvm0A/u6RA8Uh5mOZW /4C0mMb97HnJYKBn8gI9C69IP6HEvTo1RKH+M5vsXDW49lB1+m5pxXHAYaNqExH78s/yRcfsMsH yQ7dRcHEytWLmGs+cEvQQdswkKaTCWFQqTLgv8tu73PXKqlDH+6HI246xTR4B19sF6aXytDhWZf QRyY3+fd/nOzzM+nCTvnrAXouYQTjBgrP+K1QEh67FePw== X-Received: by 127.0.0.2 with SMTP id 1rL3YY7687511xoXTXkIKovT; Mon, 13 May 2024 02:23:11 -0700 X-Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web11.55989.1715592190324096915 for ; Mon, 13 May 2024 02:23:10 -0700 X-Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-286-IR2QJ_xhMY6kDAvdYR7nAA-1; Mon, 13 May 2024 05:22:55 -0400 X-MC-Unique: IR2QJ_xhMY6kDAvdYR7nAA-1 X-Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id 8BB801C0515B; Mon, 13 May 2024 09:22:55 +0000 (UTC) X-Received: from sirius.home.kraxel.org (unknown [10.39.194.73]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5BA50492BC6; Mon, 13 May 2024 09:22:54 +0000 (UTC) X-Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 6BD1D18009BA; Mon, 13 May 2024 11:22:53 +0200 (CEST) Date: Mon, 13 May 2024 11:22:53 +0200 From: "Gerd Hoffmann" To: devel@edk2.groups.io, ardb@kernel.org Cc: dougflick@microsoft.com, gaoliming Subject: =?UTF-8?B?UmU6IFtlZGsyLWRldmVsXSDlm57lpI06IFtlZGsyLWRldmVsXSBbUEFUQ0ggdjIgMDMvMTNdIE92bWZQa2c6UGxhdGZvcm1DSTogU3VwcG9ydCB2aXJ0aW8tcm5nLXBjaQ==?= Message-ID: References: <004001daa274$8de608e0$a9b21aa0$@byosoft.com.cn> <32021.1715361185999490629@groups.io> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Resent-Date: Mon, 13 May 2024 02:23:10 -0700 Resent-From: kraxel@redhat.com Reply-To: devel@edk2.groups.io,kraxel@redhat.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: s9d3y3uZrsZjmA7rP4LCEwKjx7686176AA= Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240206 header.b="xKKw/TIE"; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=redhat.com (policy=none); spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io On Sat, May 11, 2024 at 10:40:23AM GMT, Ard Biesheuvel wrote: > As I pointed out before, on the ARM side there are a few intersecting > issues with these changes. (On x86, this is mostly avoided due to the > fact that RDRAND is universally supported) Well, it's not that easy on x86 either. Current state of affairs is that the time based LibRng is used, all OvmfPkg / ArmVirtPkg have this: RngLib|MdeModulePkg/Library/BaseRngLibTimerLib/BaseRngLibTimerLib.inf So, this is what will be used if something uses LibRng. On x64 RngDxe will just use call LibRng too. So adding RngDxe will effectively make BaseRngLibTimerLib available via EFI_RNG_PROTOCOL. In case '-device virtio-rng-pci' is present we now have *two* drivers providing EFI_RNG_PROTOCOL. What will happen in this case? What we surely not want is RngDxe being used in case we have a virtio-rng device ... take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#118861): https://edk2.groups.io/g/devel/message/118861 Mute This Topic: https://groups.io/mt/106013302/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=-=-=-=-=-=-=-=-=-=-=-