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 F07FA94125D for ; Tue, 9 Jul 2024 14:48:36 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=siXJd9weKj/WTkoUId8YE2vxuO+FlknqVoykGiR+yGQ=; c=relaxed/simple; d=groups.io; h=Date:From:To: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=1720536516; v=1; b=FK1xiXQ2oicxjlQapdasKlt64qeXvPbi2bUPLmeBEgbsRdQZCJWKpUJenHrH12lcZep1zlgN nUYkeVQQW/5c0XdKtGBCRKIm0W4RYPz7z41jAw1kubHC1fY+f5t9BsednYxCP6kM+iKT+9d+ytZ 8DHILVajFojXJiCNClsVshawWRrcEp/wrXd5NRZK1QO57nmUQ7k0WMLvlC5Fv71cyLrxVMT8+Yg LhcfFeBTyj91hH2tG5cKKAetTWl+t+Woc/TPN9TBJeSoN5Z56YrT5E4T9XA/QkPxTEGrrqjcNZh xDFdfwTRlciTP4+Ooy+gB/w5yctWvlCF21dCVwrDF7YwA== X-Received: by 127.0.0.2 with SMTP id naoCYY7687511xFInrZGyjnw; Tue, 09 Jul 2024 07:48:35 -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.89.1720536514723687634 for ; Tue, 09 Jul 2024 07:48:34 -0700 X-Received: from mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-330-d17tkGoTOh-yD9SnbGdClw-1; Tue, 09 Jul 2024 10:48:32 -0400 X-MC-Unique: d17tkGoTOh-yD9SnbGdClw-1 X-Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (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 mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id E64C31955F3B; Tue, 9 Jul 2024 14:48:29 +0000 (UTC) X-Received: from sirius.home.kraxel.org (unknown [10.39.192.232]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 91F411955F21; Tue, 9 Jul 2024 14:48:29 +0000 (UTC) X-Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 347B11800DE0; Tue, 9 Jul 2024 16:48:27 +0200 (CEST) Date: Tue, 9 Jul 2024 16:48:27 +0200 From: "Gerd Hoffmann" To: devel@edk2.groups.io, preisner@cs.fau.de Subject: Re: [edk2-devel] Questions regarding NVDIMM and OVMF Message-ID: References: <108b8e09-7d9f-411a-8384-1a8c0e0fcd07@cs.fau.de> MIME-Version: 1.0 In-Reply-To: <108b8e09-7d9f-411a-8384-1a8c0e0fcd07@cs.fau.de> X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 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: Tue, 09 Jul 2024 07:48:34 -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: ltQRPcH8oDJPzDHOCn2hmpznx7686176AA= 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=FK1xiXQ2; 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 Hi, > Do you have any pointers for implementing the support of nvdimm in > edk2/OVMF? Or is it not feasible and I need to also look at adding it > directly into QEMU qemu. Add e820_add_entry() calls. Possibly edk2 too. Not sure how linux is supposed to figure the memory in question is nvdimm not ram. Is there a e820 type for nvdimm? If so then PlatformAddHobCB() in OvmfPkg/Library/PlatformInitLib/MemDetect.c needs some code to handle it. In any case you I don't think you want qemu announce the nvdimm device twice. So it should be registered either via acpi/nfit, or via e820 table (which gets passed from qemu to firmware via 'etc/e820' fw_cfg file), but probably not both. HTH & take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#119850): https://edk2.groups.io/g/devel/message/119850 Mute This Topic: https://groups.io/mt/107122508/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=-=-=-=-=-=-=-=-=-=-=-