From: haojian.zhuang@linaro.org (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
Date: Tue, 25 Aug 2015 16:13:47 +0800 [thread overview]
Message-ID: <1440490427.10987.29.camel@linaro.org> (raw)
In-Reply-To: <20150824114903.GT10728@bivouac.eciton.net>
On Mon, 2015-08-24 at 12:49 +0100, Leif Lindholm wrote:
> On Mon, Aug 24, 2015 at 06:19:56PM +0800, Haojian Zhuang wrote:
> > > If your EFI memory map describes the memory as mappable, it is wrong.
> >
> > When kernel is working, kernel will create its own page table based on
> > UEFI memory map. Since it's reserved in DTS file as Leo's patch, it'll
> > be moved to reserved memblock. Why is it wrong?
> >
> > In the second, UEFI is firmware. When it's stable, nobody should change
> > it without any reason.
>
> Much like the memory map.
>
> > These reserved memory are used in mailbox driver.
> > Look. It's driver, so it could be changed at any time.
>
> No, it is a set of regions of memory set aside for use by a different
> master in the system as well as communications with that master.
>
> The fact that there is a driver somewhere that is aware of this is
> entirely beside the point. All agents in the system must adher to this
> protocol.
>
> > Why do you want
> > to UEFI knowing this memory range? Do you hope UEFI to change when
> > mailbox driver is changed?
>
> Yes.
>
> UEFI is a runtime environment. Having random magic areas not to be
> touched will cause random pieces of software running under it to break
> horribly or break other things horribly.
> Unless you mark them as reserved in the UEFI memory map.
> At which point the Linux kernel will automatically ignore them, and
> the proposed patch is redundant.
>
> So, yes, if you want a system that can boot reliably, run testsuites
> (like SCT or FWTS), run applications (like fastboot ... or the EFI
> stub kernel itself), then any memory regions that is reserved for
> mailbox communication (or other masters in the system) _must_ be
> marked in the EFI memory map.
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.
2. UEFI just loads grub. It's no time to run any other custom EFI
application.
Regards
Haojian
next prev parent reply other threads:[~2015-08-25 8:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 9:37 [PATCH v1 0/3] mailbox: hisilicon: add Hi6220 mailbox driver Leo Yan
2015-08-19 9:37 ` [PATCH v1 1/3] dt-bindings: mailbox: Document " Leo Yan
2015-08-25 11:17 ` Sudeep Holla
2015-08-25 13:01 ` Leo Yan
2015-08-19 9:37 ` [PATCH v1 2/3] mailbox: Hi6220: add " Leo Yan
2015-08-19 9:37 ` [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node Leo Yan
2015-08-21 18:40 ` Mark Rutland
2015-08-22 13:30 ` Leo Yan
2015-08-24 3:27 ` Leo Yan
2015-08-24 9:18 ` Leo Yan
2015-08-24 9:51 ` Mark Rutland
2015-08-24 10:19 ` Haojian Zhuang
2015-08-24 11:49 ` Leif Lindholm
2015-08-25 8:13 ` Haojian Zhuang [this message]
2015-08-25 9:46 ` Leif Lindholm
2015-08-25 10:15 ` Haojian Zhuang
2015-08-25 10:40 ` Leif Lindholm
2015-08-25 10:42 ` Mark Rutland
2015-08-25 13:43 ` Haojian Zhuang
2015-08-25 14:24 ` Leif Lindholm
2015-08-25 14:51 ` Ard Biesheuvel
2015-08-25 15:37 ` Leif Lindholm
2015-08-25 15:45 ` Ard Biesheuvel
2015-08-26 2:41 ` Haojian Zhuang
2015-08-25 16:00 ` Leo Yan
2015-08-26 1:25 ` Haojian Zhuang
2015-08-26 6:59 ` Leo Yan
2015-08-27 16:31 ` Mark Rutland
2015-08-28 6:37 ` Leo Yan
2015-08-27 15:54 ` Daniel Thompson
2015-08-27 16:46 ` Mark Rutland
2015-08-24 12:48 ` Mark Rutland
2015-08-25 8:04 ` Haojian Zhuang
2015-08-25 11:09 ` Mark Rutland
2015-08-25 11:36 ` Sudeep Holla
2015-08-25 14:04 ` Leo Yan
2015-08-25 14:13 ` Sudeep Holla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1440490427.10987.29.camel@linaro.org \
--to=haojian.zhuang@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).