On Tue, Aug 25, 2015 at 06:15:10PM +0800, Haojian Zhuang wrote:
> > > 1. We need support both UEFI and uboot. So the reserved buffer have to
> > > be declared in DTB since they are used by kernel driver, not UEFI.
> >
> > The buffer may need to be declared in DTB also, but it most certanily
> > needs to be declared in UEFI.
> >
> > And for the U-Boot case, since it is not memory available to Linux, it
> > should not be declared as "memory".
>
> Something are messed at here. We have these buffer are used in mailbox.
> They should be allocated as non-cacheable.
That is a completely different issue, and if that is not currently
possible, then we need to fix that. But it needs to be fixed in the
right place.
> If these buffers are contained in memory memblock in kernel, it means
> that they exist in kernel page table with cachable property. When it's
> used in mailbox driver with non-cachable property, it'll only cause
> cache maintenance issue. So Leo declared these buffers as reserved
> in DT with "no-map" property. It's the key. It could avoid the cache
> maintenance issue.
Yes, when not booting with UEFI.
> > > 2. UEFI just loads grub. It's no time to run any other custom EFI
> > > application.
> >
> > Apart from being completely irrelevant, how are you intending to
> > validate that GRUB never touches these memory regions?
>
> GRUB is just a part of bootloader. When linux kernel is running,
> who cares GRUB? GRUB's lifetime is already finished.
We don't care once Linux is running - we care between UEFI boot
services starting and Linux memblock being initialised.
> By the way, UEFI code region is at [0x3Dxx_xxxx, 0x3DFF_FFFF]. Those
> mailbox buffer is in [0x05e0_xxxx, 0x06f0_xxxx]. Then I can make sure
> UEFI won't touch the reserved buffer.
And if a UEFI application explicitly requests to map an area
elsewhere, will your UEFI reject that request? How will it do that
without having information in its memory map about areas it must not
access?
> Even if UEFI touched the reserved
> buffer, is it an issue? Definitely it's not. UEFI's lifetime is end
> when linux kernel is running at hikey. Even if UEFI runtime service
> is enabled, the runtime data area is at [0x38xx_xxxx, 0x38xx_xxxx].
The runtime data area is currently, in your current image, at
[0x38xx_xxxx, 0x38xx_xxxx].
What happens if a UEFI application registers a configuration table?
Or registers a protocol for use at runtime?
Areas of memory that are not available for UEFI _must_ be marked as
such in the UEFI memory map. Once they are, we can deal with them in
the kernel. If this is not currently being done, that is a bug that
needs fixing.
> > Build a version once, test it, and hope the results remain valid
> > forever? And then when you move the regions and the previously working
> > GRUB now tramples all over them? Or when something changes in upstream
> > GRUB and its memory allocations drifts into the secretly untouchable
> > regions?
>
> As I said above, UEFI won't touch it. And even UEFI touch it, kernel
> doesn't care since UEFI's lifetime is end.
UEFI's lifetime doesn't end until reset.
> > Are you then going to hack GRUB, release a special HiKey version of
> > GRUB, not support any other versions, and still can your firmware
> > UEFI?
>
> I don't need to hack GRUB at all.
You will if you're running it under a "UEFI" which has areas you can't
touch and aren't telling it about that.
/
Leif
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
