From: Pete Batard <pete@akeo.ie>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH 0/2] MdeModulePkg/EbcDxe: add EBC Debugger
Date: Sat, 12 Nov 2016 22:17:32 +0000 [thread overview]
Message-ID: <48e539f6-6173-a77a-1570-5d0ec4b237e1@akeo.ie> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C50386CFB5B@shsmsx102.ccr.corp.intel.com>
Hi Jiewen,
On 2016.11.12 21:44, Yao, Jiewen wrote:
> I realize that the side-effect of library solution is that: we need
> update DSC file to add Library instance.
Yes. I started looking at the library option, and I'm kind of wondering
if we really want to put code in a library when it's unlikely that any
of the hooks will be used anywhere but once, and in the very specific
locations we have now.
I still don't mind going that route if that's what we decide, but
creating a non-generic library, that is only going to be used to build a
single application seems a bit like an overkill.
> Now I am thinking the third options:
> 3.1.3) 2 INF without MACRO.
> 3.1.3.A) Remove EFI_EBC_DEBUGGER_CODE
> 3.1.3.B) EBC driver always calls EbcDebuggerHookXXX.
> 3.1.3.C) Create a EbcDebuggerHookNull.c and add it to EbcDxe.inf.
> So that no change is needed for a platform, and no PCD is introduced.
This sound like a more elegant solution.
I like this option better than the others so far, so that's what I'll go
with for v2.
> 3.1.3.F) I still suggest we remove EbcInit.h and EbcExecute.h from
> Edb.h. The common definition should be in a better place.
Agreed.
I'll try to move the common parts to MdePkg\Include\Protocol\Ebc.h in
the new proposal, if that's still okay with you.
Regards,
/Pete
prev parent reply other threads:[~2016-11-12 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 15:50 [PATCH 0/2] MdeModulePkg/EbcDxe: add EBC Debugger Pete Batard
2016-11-11 17:41 ` Kinney, Michael D
2016-11-11 18:13 ` Pete Batard
2016-11-11 23:48 ` Yao, Jiewen
2016-11-12 0:43 ` Pete Batard
2016-11-12 7:48 ` Yao, Jiewen
2016-11-12 12:46 ` Pete Batard
2016-11-12 13:43 ` Yao, Jiewen
2016-11-12 19:49 ` Yao, Jiewen
2016-11-12 21:44 ` Yao, Jiewen
2016-11-12 22:17 ` Pete Batard [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=48e539f6-6173-a77a-1570-5d0ec4b237e1@akeo.ie \
--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