From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.61]) by mx.groups.io with SMTP id smtpd.web11.15008.1589212550789654736 for ; Mon, 11 May 2020 08:55:50 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=cFqZqkyS; spf=pass (domain: redhat.com, ip: 205.139.110.61, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589212549; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CWUG32lSkkeJQTv+qTeHNUpAIaxACFzeyxerY8CzQ60=; b=cFqZqkySVDtvgU6+dwrvicmt3GE7nPySoLsdDQFRXWwwomr/zk0zxAIxRC0dAJbUX1vM+k nZ62A6b4cJPVNdZs0YndfuJGhobJDhjN30eJA0gk1BXay4GqWOno0a7lx7L0sWaf4hq8rA 8rW2eQ5xc0OyC/BlINAf7aE/ibdu0FY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-380-MQruBWCXODSF-6PwSqj3Dg-1; Mon, 11 May 2020 11:55:46 -0400 X-MC-Unique: MQruBWCXODSF-6PwSqj3Dg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 63A9E80F5E4; Mon, 11 May 2020 15:55:34 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-11.ams2.redhat.com [10.36.113.11]) by smtp.corp.redhat.com (Postfix) with ESMTP id C739475274; Mon, 11 May 2020 15:55:32 +0000 (UTC) Subject: Re: Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg? To: Rebecca Cran , edk2-devel-groups-io Cc: "Kinney, Michael D" , Andrew Fish , Leif Lindholm , "Ard Biesheuvel (ARM address)" , "Jordan Justen (Intel address)" References: From: "Laszlo Ersek" Message-ID: Date: Mon, 11 May 2020 17:55:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit (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