From mboxrd@z Thu Jan 1 00:00:00 1970 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.web08.4015.1649151454033634353 for ; Tue, 05 Apr 2022 02:37:34 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Rg0XDhrV; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1649151453; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dOZiQVgI55+mG11fwUZ9yrOKITA6MFR1BvKV/9iROng=; b=Rg0XDhrVVeVkKP/MNShG2LALyKiSOsvbIW8M3enJqlsXxsrmODDFIMnVQnmud22BtNfAFd cYwS1PwnUPE0TckWe4XfwA2PP+eSHX3SzVlS0DmTPWC5NyONyu5DerCMWz5w4LlCDktOz+ hWanYGY0bp+gih6STyIcaG7wW2b9muI= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-278-Yh6M-mneMfyAwofUjqD7ZA-1; Tue, 05 Apr 2022 05:37:27 -0400 X-MC-Unique: Yh6M-mneMfyAwofUjqD7ZA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 7CC97804189; Tue, 5 Apr 2022 09:37:07 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.9]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7AFAE4118FDE; Tue, 5 Apr 2022 09:37:02 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id BC60F1800916; Tue, 5 Apr 2022 11:37:00 +0200 (CEST) Date: Tue, 5 Apr 2022 11:37:00 +0200 From: "Gerd Hoffmann" To: Corvin =?utf-8?B?S8O2aG5l?= Cc: "virtualization@freebsd.org" , Ard Biesheuvel , Jiewen Yao , Jordan Justen , Rebecca Cran , Peter Grehan , "devel@edk2.groups.io" Subject: Re: [PATCH] OvmfPkg: reserve igd memory by E820 Message-ID: <20220405093700.ahsezswbumjlg3au@sirius.home.kraxel.org> References: <20220404063448.280-1-c.koehne@beckhoff.com> <20220404113830.6novz55zpid3l6fl@sirius.home.kraxel.org> <20220405070639.uq5uiydxhirwu4gb@sirius.home.kraxel.org> <7de01ae500554923941dc5ff9e537637@beckhoff.com> MIME-Version: 1.0 In-Reply-To: <7de01ae500554923941dc5ff9e537637@beckhoff.com> X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Tue, Apr 05, 2022 at 07:47:38AM +0000, Corvin Köhne wrote: > Hi, > > > Where does the intel gop driver come from? Extracted from host > > firmware? > > https://projectacrn.github.io/latest/tutorials/gpu-passthru.html#enable-the-gvt-d-gop-driver > > I don't know if it's possible to extract it from host firmware within > OS context easily. Extracting from firmware updates is probably easier. > According to Intel you should ask your board manufacturer. I'm wondering why if the opregion initialization (which actually is board-specific) is not done by the gop driver. > https://01.org/sites/default/files/downloads/igvt-g/gvtflyer.pdf > > I'm not familiar with GVT-s. I just know that it exists. Seems to be higher level, sending a directx/opengl command stream, apparently no hardware access for the guest. > > Once we have the code for vgabios and PlatformGopPolicy we can roll them > > with the intelgop driver into a rom image with EfiRom. Ideally also add > > opregion content to the rom somehow. > > Sounds good. Does these EFI drivers have to be maintained outside of > EDKII? Hosting this in https://github.com/tianocore/edk2-staging is probably one option (not fully sure about the policy there). Creating a separate project for that might also make sense given that the roms will not be generic but host-specific, so end-users will have to install the tools needed to collect host-specific bits and to build the final rom image. take care, Gerd