public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: Laszlo Ersek <lersek@redhat.com>, devel@edk2.groups.io
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH v2 (add signed-off-by)] OvmfPkg: Add bhyve support into AcpiTimerLib
Date: Wed, 8 Apr 2020 23:26:52 -0600	[thread overview]
Message-ID: <040c7e56-cb2f-b0ae-736c-0e1a804946f1@bsdio.com> (raw)
In-Reply-To: <fe0601f1-45a1-f1ce-6c14-0a3a29d92e55@redhat.com>

On 3/27/2020 1:01 PM, Laszlo Ersek wrote:
>
> I'm quite happy about this patch, but perhaps for an unexpected reason:
> namely, because it showcases how non-intuitive and unpredictable it can
> be to customize existent code for a new platform.

Thanks! I was wondering if I should try and add new code into OvmfPkg, 
or keep it separate. Also, good point about the commit message: I get 
frustrated when people don't write proper/full messages, so I'm happy 
you called me out on it.


The existing bhyve port removes everything related to QemuFwCfgLib, such 
as calls to QemuFwCfgFindFile in PciHostBridgeLib.c. I'm not sure how I 
should proceed given that there's so much commonality between the ovmf 
and bhyve versions of the file: currently calls to QemuFwCfgFindFile 
don't resolve since references are absent from the .dsc file, so I'm 
wondering if I should re-add it, add a "#ifndef BHYVE" or similar to 
avoid attempting to compile that code, or duplicate the file with that 
code removed?


-- 
Rebecca Cran



  reply	other threads:[~2020-04-09  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 20:16 [PATCH v2 (add signed-off-by)] OvmfPkg: Add bhyve support into AcpiTimerLib Rebecca Cran
2020-03-27 19:01 ` Laszlo Ersek
2020-04-09  5:26   ` Rebecca Cran [this message]
2020-04-09  6:40     ` Laszlo Ersek

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=040c7e56-cb2f-b0ae-736c-0e1a804946f1@bsdio.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