Date: Fri, 25 Aug 2017 23:03:58 +0000 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 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221813 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 loader. There, loader constructs kernel virtual address space and establishes the initial mappings. Most ample demonstration of the approach is with the runtime 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. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221813-24229-5Ks0OFp505>