public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Pete Batard <pete@akeo.ie>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/2] MdeModulePkg/EbcDxe: add EBC Debugger
Date: Fri, 11 Nov 2016 18:13:54 +0000	[thread overview]
Message-ID: <9bcd84c1-8fe6-f034-43dc-2c59929a371e@akeo.ie> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5648436A3@ORSMSX113.amr.corp.intel.com>

Hi Mike,

On 2016.11.11 17:41, Kinney, Michael D wrote:
> I see the new INF files uses '..' in the [Sources]
> section, which is not allowed.  Can we move that INF
> file up one directory, so it can remove use of ..?

Sure. I'll work on this and submit a V2.

> I also see that this code defined its own
> EFI_EBC_DEBUGGER_CODE macro.  Could these be changed
> to the standard DEBUG_CODE() macro that can be enabled
> and disabled with a PCD?  Or do you think we should add
> a new Feature Flag PCD to enable/disable the EBC
> debugger?

I've been wondering about keeping the macro as well, which I mostly 
carried over from Tiano. If PCD is the more appropriate EDK2 practice, 
then I agree that we probably want to go with that.

I do feel however that we would need a new feature flag, as some people 
may want to compile an EBC module with the current debug PCD 
functionality enabled, but without the EBC debugger, especially as, in 
essence, the EBC debugger is designed to be intrusive and will break the 
flow of regular EBC execution (such as on program entry or thunk calls).

I'll explore this a little bit further, and try have a PCD proposal for V2.

Regards,

/Pete


  reply	other threads:[~2016-11-11 18:13 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 [this message]
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

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=9bcd84c1-8fe6-f034-43dc-2c59929a371e@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