linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Paul Burton <paulburton@kernel.org>, Huacai Chen <chenhc@lemote.com>
Cc: Paul Burton <paul.burton@mips.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>,
	linux-mips@linux-mips.org, linux-mips@vger.kernel.org,
	Fuxin Zhang <zhangfx@lemote.com>,
	Zhangjin Wu <wuzhangjin@gmail.com>,
	Huacai Chen <chenhuacai@gmail.com>
Subject: Re: [PATCH] MIPS: Make sure ebase address is in KSEG0
Date: Sat, 23 Nov 2019 14:11:32 +0800	[thread overview]
Message-ID: <3C1D695B-09AA-4C2D-A94F-84DFC05C6F0C@flygoat.com> (raw)
In-Reply-To: <EAC4F77C-88BE-47FA-83A5-5855A869425A@flygoat.com>



于 2019年11月23日 GMT+08:00 下午1:08:38, Jiaxun Yang <jiaxun.yang@flygoat.com> 写到:
>
>
>于 2019年11月23日 GMT+08:00 上午2:47:31, Paul Burton <paulburton@kernel.org>
>写到:
>>Hi Huacai,
>>
>>On Thu, Nov 21, 2019 at 07:30:20PM +0800, Huacai Chen wrote:
>>> Dynamically allocated ebase address above 0x20000000 can be
>triggered
>>> by some special physical memory layout, or just by a "big kernel +
>>big
>>> initrd + big swiotlb" configuration.
>>> 
>>> For MIPS32, ebase address above 0x20000000 is unusable, for MIPS64
>it
>>> is usable but this case is warned. However, this warning is useless
>>> because it is unfixable in a specific system configuration. So we
>>just
>>> use CKSEG0 as a fallback.
>>
>>I'd prefer that we don't assume there's memory at physical address
>zero
>>- that property doesn't hold for all systems.
>>
>>How about the change I suggested previously over here:
>>
>>https://lore.kernel.org/linux-mips/20191108191149.bbq3h4xp4famsh2n@lantea.localdomain/
>>
>>Would that work for you?
>
>Hi Paul
>
>Our problem is, sometimes the ebase from firmware is totally a random
>address, 
>even not inside the memory region. I'd prefer ignore address if it's
>not valid since the warning here can't deal with it.

I'm sorry. I was wrong. Please ignore the noise.

Thanks

>
>Thanks.
>>
>>Thanks,
>>    Paul
>>

-- 
Jiaxun Yang

  reply	other threads:[~2019-11-23  6:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 11:30 Huacai Chen
2019-11-22 18:47 ` Paul Burton
2019-11-23  5:08   ` Jiaxun Yang
2019-11-23  6:11     ` Jiaxun Yang [this message]
2019-11-24  4:00       ` Huacai Chen
2019-11-25 23:42         ` Paul Burton
2019-11-26  1:55           ` Huacai Chen

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=3C1D695B-09AA-4C2D-A94F-84DFC05C6F0C@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=chenhc@lemote.com \
    --cc=chenhuacai@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul.burton@mips.com \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=wuzhangjin@gmail.com \
    --cc=zhangfx@lemote.com \
    --subject='Re: [PATCH] MIPS: Make sure ebase address is in KSEG0' \
    /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

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).