From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>,
Rebecca Cran <rebecca@bsdio.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
"Ard Biesheuvel (ARM address)" <ard.biesheuvel@arm.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg?
Date: Mon, 11 May 2020 16:25:36 +0000 [thread overview]
Message-ID: <MN2PR11MB446157ADC5104992D0A44BD5D2A10@MN2PR11MB4461.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f98f7e96-50e1-a871-68a2-ae9072c8073e@redhat.com>
Laszlo,
I prefer all virtual firmware content to go into
OvmfPkg. Subdirectories within OvmfPkg for each
type of virtual firmware makes sense to me.
If a developer does not want virtual firmware source in
their local tree, they can use sparse checkout skipping
OvmfPkg.
Thanks,
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On
> Behalf Of Laszlo Ersek
> Sent: Monday, May 11, 2020 8:56 AM
> To: Rebecca Cran <rebecca@bsdio.com>; edk2-devel-
> groups-io <devel@edk2.groups.io>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>;
> Andrew Fish <afish@apple.com>; Leif Lindholm
> <leif@nuviainc.com>; Ard Biesheuvel (ARM address)
> <ard.biesheuvel@arm.com>; Justen, Jordan L
> <jordan.l.justen@intel.com>
> Subject: Re: [edk2-devel] Where to put the bhyve code
> in the edk2 repo: BhyvePkg, or under OvmfPkg?
>
> (CC'ing Ard and Jordan.)
>
> On 05/08/20 17:44, Rebecca Cran wrote:
> > During the Community Meeting last night, I was asked
> to send this email
> > starting a discussion about where to put the bhyve
> code in the edk2
> > tree: whether it should be in a new BhyvePkg, or
> added under OvmfPkg.
>
> I prefer a top-level BhyvePkg.
>
> If most edk2 consumers wouldn't like to see a top-level
> BhyvePkg
> directory, I can certainly live with OvmfPkg/Bhyve.
>
> I can also live with OvmfPkg/Bhyve*,
> OvmfPkg/Library/Bhyve*, etc, modules.
>
> So I guess these would be my choices in decreasing
> order of preference.
> (To be clear, I consider my option#3 still a lot better
> than not having
> bhyve support in upstream edk2 at all.)
>
> In either case, "Maintainers.txt" should get a new
> section listing the
> bhyve-specific modules as being under your and Peter
> Grehan's
> reviewership ("R").
>
> > It
> > appears it's already been decided it should be in
> edk2 along with the
> > other virtual platforms and not edk2-platforms, where
> code for physical
> > platforms will reside.
>
> I haven't been aware that this is a done deal, but if
> it is, it makes me
> glad! I've always wanted bhyve stuff to be in edk2 and
> not in
> edk2-platforms.
>
> Thanks!
> Laszlo
>
>
>
prev parent reply other threads:[~2020-05-11 16:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 15:44 Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg? Rebecca Cran
2020-05-11 15:55 ` Laszlo Ersek
2020-05-11 16:20 ` Ard Biesheuvel
2020-05-11 16:36 ` Michael D Kinney
2020-05-11 16:38 ` Andrew Fish
2020-05-11 16:41 ` [edk2-devel] " Michael D Kinney
2020-05-11 21:12 ` Laszlo Ersek
2020-05-11 21:22 ` Michael D Kinney
2020-05-11 21:58 ` [edk2-devel] " Rebecca Cran
2020-05-12 9:28 ` Laszlo Ersek
2020-05-12 9:52 ` Ard Biesheuvel
2020-05-12 15:09 ` Laszlo Ersek
2020-05-14 2:34 ` Rebecca Cran
2020-05-14 10:24 ` Laszlo Ersek
2020-05-14 16:20 ` Rebecca Cran
2020-05-14 17:48 ` Sean
2020-05-14 18:22 ` Rebecca Cran
2020-05-14 18:46 ` Sean
2020-05-14 18:54 ` Rebecca Cran
2020-05-15 9:39 ` Laszlo Ersek
2020-05-15 9:42 ` Laszlo Ersek
2020-05-15 9:47 ` Ard Biesheuvel
2020-05-15 12:51 ` Laszlo Ersek
2020-05-15 15:03 ` Leif Lindholm
2020-05-11 16:25 ` Michael D Kinney [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=MN2PR11MB446157ADC5104992D0A44BD5D2A10@MN2PR11MB4461.namprd11.prod.outlook.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