public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Pete Batard <pete@akeo.ie>
To: "Yao, Jiewen" <jiewen.yao@intel.com>, Laszlo Ersek <lersek@redhat.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: [PATCH v2 0/3] MdeModulePkg/EbcDxe: add EBC Debugger
Date: Mon, 14 Nov 2016 14:11:08 +0000	[thread overview]
Message-ID: <70ceee92-2fc0-ef63-bbfd-50f4f71cab75@akeo.ie> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C50386D0543@shsmsx102.ccr.corp.intel.com>

On 2016.11.14 13:58, Yao, Jiewen wrote:
> One minor concern I have is that: I found you include below in
> Protocol/Ebc.h
>
> #define GETOPERANDS(pVM)  (UINT8) (*(UINT8 *) (pVM->Ip + 1))
> #define GETOPCODE(pVM)    (UINT8) (*(UINT8 *) pVM->Ip)
> #define OPERAND1_REGDATA(pvm, op) pvm->Gpr[OPERAND1_REGNUM (op)]
> #define OPERAND2_REGDATA(pvm, op) pvm->Gpr[OPERAND2_REGNUM (op)]
>
> However, pvm->Gpr and pVM->Ip are defined in Protocol/EbcVmTest.h.
>
> I recommend that we had better move PVM related definition there.

I agree. Do you want me to re-send a patch for that?

On that subject, I've also been wondering on whether we might just move 
all the operand related definitions into EbcVmTest.h and leave Ebc.h as 
it was.

The more I think about it, the more I wonder if a header that's just 
meant to define the EBC interpreter interface is the best place to have 
EBC internal definitions. Maybe the header that is intended for use for 
the actual implementation of the EBC VM (EbcVmTest.h) is where we should 
move everything into?

Regards,

/Pete




  reply	other threads:[~2016-11-14 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 11:06 [PATCH v2 0/3] MdeModulePkg/EbcDxe: add EBC Debugger Pete Batard
2016-11-14 11:51 ` Laszlo Ersek
2016-11-14 11:53   ` Laszlo Ersek
2016-11-14 13:18     ` Pete Batard
2016-11-14 13:58       ` Yao, Jiewen
2016-11-14 14:11         ` Pete Batard [this message]
2016-11-14 14:39           ` Yao, Jiewen
2016-11-16  2:08             ` Yao, Jiewen

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=70ceee92-2fc0-ef63-bbfd-50f4f71cab75@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