From: "Dong, Eric" <eric.dong@intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch 0/2] Add missed Depex Protocol/Ppi.
Date: Wed, 8 Nov 2017 01:54:30 +0000 [thread overview]
Message-ID: <ED077930C258884BBCB450DB737E66224AA42361@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <639c28f8-99fc-600c-cc2c-b6573677aa1b@redhat.com>
Hi Laszlo,
Agree with you, I'm not aware the consume protocol/Ppi code is in the library till now. I will discard the changes.
Thanks,
Eric
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Wednesday, November 8, 2017 2:18 AM
> To: Dong, Eric <eric.dong@intel.com>
> Cc: edk2-devel@lists.01.org
> Subject: Re: [edk2] [Patch 0/2] Add missed Depex Protocol/Ppi.
>
> Hi Eric,
>
> On 11/06/17 13:26, Eric Dong wrote:
> > The Protocol/Ppi used in the drivers but the it not add them in the
> > dependence section, it may cause driver assert.
> > This patch series add the missed Protocol/Ppi.
> >
> > Eric Dong (2):
> > UefiCpuPkg/CpuFeaturesDxe.inf: Add missed Depex protocol.
> > UefiCpuPkg/CpuFeaturesPei.inf: Add missed Depex Ppi.
> >
> > UefiCpuPkg/CpuFeatures/CpuFeaturesDxe.inf | 2 +-
> > UefiCpuPkg/CpuFeatures/CpuFeaturesPei.inf | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
>
> (hopefully I'm commenting soon enough,)
>
> where exactly are the MP protocol and PPI used in
> UefiCpuPkg/CpuFeatures/?
>
> I grepped the directory for both protocol and PPI, and I found no matches.
>
> If the dependencies are incurred via library instances, then those library
> instances should spell out the depex.
>
> The only library class used by CpuFeaturesDxe.inf and CpuFeaturesPei.inf,
> for which multi-processing looks remotely relevant,
> is: RegisterCpuFeaturesLib.
>
> For this class, two instances appear to exist:
>
> UefiCpuPkg/Library/RegisterCpuFeaturesLib/DxeRegisterCpuFeaturesLib.inf
> UefiCpuPkg/Library/RegisterCpuFeaturesLib/PeiRegisterCpuFeaturesLib.inf
>
> The DXE instance consumes gEfiMpServiceProtocolGuid alright, but it also
> spells out the protocol in the depex:
>
> [Depex]
> gEfiMpServiceProtocolGuid AND gEdkiiCpuFeaturesSetDoneGuid
>
> The PEI instance is similar, wrt. the PPI:
>
> [Depex]
> gEfiPeiMpServicesPpiGuid AND gEdkiiCpuFeaturesSetDoneGuid
>
> So, this series appears unnecessary. What am I missing?
>
> Thanks
> Laszlo
prev parent reply other threads:[~2017-11-08 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 12:26 [Patch 0/2] Add missed Depex Protocol/Ppi Eric Dong
2017-11-06 12:26 ` [Patch 1/2] UefiCpuPkg/CpuFeaturesDxe.inf: Add missed Depex protocol Eric Dong
2017-11-06 12:26 ` [Patch 2/2] UefiCpuPkg/CpuFeaturesPei.inf: Add missed Depex Ppi Eric Dong
2017-11-07 18:17 ` [Patch 0/2] Add missed Depex Protocol/Ppi Laszlo Ersek
2017-11-08 1:54 ` Dong, Eric [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ED077930C258884BBCB450DB737E66224AA42361@shsmsx102.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox