From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124])
 by mx.groups.io with SMTP id smtpd.web10.758.1616694495001968069
 for <devel@edk2.groups.io>;
 Thu, 25 Mar 2021 10:48:15 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=d2unOP5h;
 spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1616694494;
	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=30bpi2+Ec35f4YHr+FRw/E3h09+DDTVHWz3EW3LH8Qw=;
	b=d2unOP5hBtak2YHsAxwaxTnJAVIjqqIzrQx1jips6TEEKv43bVDhPZ/ssGGNDlV9DxWHqr
	rd0775kHi86Bzp1YeMj9IlBhsCamtQSXFuD7AaD+289ZbrGIacm0Ir/6Vtc2Msj5VisIn6
	C4sFOX9A9n3g4eRctel4sHerY7cWYg0=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-369-W0jCYeOIMHS2qps8zjUfZg-1; Thu, 25 Mar 2021 13:48:10 -0400
X-MC-Unique: W0jCYeOIMHS2qps8zjUfZg-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 3752F1034B23;
	Thu, 25 Mar 2021 17:48:09 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-200.ams2.redhat.com [10.36.114.200])
	by smtp.corp.redhat.com (Postfix) with ESMTP id 9792C5C260;
	Thu, 25 Mar 2021 17:48:07 +0000 (UTC)
Subject: Re: [edk2-devel] SR-IOV setup in edk2
To: Jon Nettleton <jon@solid-run.com>
Cc: devel@edk2.groups.io
References: <CABdtJHsn8V6ZjZM0_tFkHNzg0gmg0sH81csDA6goHaO0DjM1Wg@mail.gmail.com>
 <986c079a-137f-c3e5-2e85-1aeccf148f8c@redhat.com>
 <CABdtJHsWACL-db4t_i-taFTN05Ttup=NXvaNeX-1e-SRXrPY6Q@mail.gmail.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <948714c2-dde1-1350-6f51-93777cf4656a@redhat.com>
Date: Thu, 25 Mar 2021 18:48:06 +0100
MIME-Version: 1.0
In-Reply-To: <CABdtJHsWACL-db4t_i-taFTN05Ttup=NXvaNeX-1e-SRXrPY6Q@mail.gmail.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

Hi Jon.

On 03/25/21 09:02, Jon Nettleton wrote:

> I have now implemented a driver connected to gEfiPciPlatformProtocolGuid
> and I can get events passed in for the platform setup hooks, is this where
> we should be doing the bus specific setup, rather than catching
> gEfiPciIoProtocolGuid?

Sorry, the topic you are working on is over my head.

Catching gEfiPciIoProtocolGuid (with a protocol notify registration) is
definitely wrong, from a UEFI driver model perspective.

EFI_PCI_PLATFORM_PROTOCOL *could* be what you are afrer. I recommend
reading through Chapter 11, "PCI Platform", in Volume 5 of the Platform
Init spec (latest release is, to my knowledge, v1.7). Chapter 10 could
be relevant too ("PCI Host Bridge").

I think the PCI maintainers in edk2 could be of more help than I; please
see Hao and Ray in Maintainers.txt.

Thanks
Laszlo