On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote: > On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote: > > > > On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote: > > > > > > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote: > > > > > > > > > > > > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore <ian_at_freebsd.org> wrote: > > > > > > > > > > > > > > > [...] > > > > > What do we do on 32-bit arm that has no dmap but may have efi > > > > > runtime > > > > > support? > > > > > > > > > This should probably just be compiled out for !arm64 && !x86 - its > > > > sole purpose was to compensate for outdated loader.efi that hasn't > > > > done the SetVirtualAddressMap. EFI on 32-bit ARM is "new" enough > > > > that > > > > it shouldn't have this problem. > > > Does EFI on 32bit arm have RT support ? > > I suspect the uboot implementation doesn't, but I can't think of any > > reason why other implementations are not possible/available. In > > particular, even 32bit arm supports virtualization and such an > > environment could provide rt support. > No, I mean, does our kernel has RT support on armv7 ? I only implemented > necessary VM tricks for amd64, then it was ported to arm64, and in both > cases it relies on 64bit address space and specific location of the KVA. I didn't realize the kernel implementation was arch-specific. So I guess this comes under the category of "we'll solve that problem when something comes along that provides efi rt for arm32." -- IanReceived on Sat Aug 04 2018 - 13:47:19 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:17 UTC