From owner-freebsd-arch@freebsd.org  Fri Aug 25 23:03:58 2017
Return-Path: <owner-freebsd-arch@freebsd.org>
Delivered-To: freebsd-arch@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96AD4DE3623
 for <freebsd-arch@mailman.ysv.freebsd.org>;
 Fri, 25 Aug 2017 23:03:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 844717436F
 for <freebsd-arch@FreeBSD.org>; Fri, 25 Aug 2017 23:03:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7PN3wv0052472
 for <freebsd-arch@FreeBSD.org>; Fri, 25 Aug 2017 23:03:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-arch@FreeBSD.org
Subject: [Bug 221813] Mechanism is needed to utilize discontinuous memory
 segments supplied by the EFI and other boot envs
Date: Fri, 25 Aug 2017 23:03:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: uefi
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-221813-24229-5Ks0OFp505@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221813-24229@https.bugs.freebsd.org/bugzilla/>
References: <bug-221813-24229@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Aug 2017 23:03:58 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221813

Konstantin Belousov <kib@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kib@FreeBSD.org

--- Comment #2 from Konstantin Belousov <kib@FreeBSD.org> ---
EFI model of handing control from loader to OS is dictated by Windows loade=
r.=20
There, loader constructs kernel virtual address space and establishes the
initial mappings.  Most ample demonstration of the approach is with the run=
time
services abomination requirement that loader provides the future mapping of
runtime segments to firmware, while kernel did not even started.

Change of amd64 loader/kernel interaction to adopt this model is possible, =
but
I am not sure that it is worth the efforts.  At least, I do not consider the
use cases of large preloaded md as enough justification for all the work
required, and for causing flag day where new kernel will absolutely require=
 new
loader.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=