From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Serge Semin" <fancer.lancer@gmail.com>
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Tiezhu Yang" <yangtiezhu@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Yinglu Yang" <yangyinglu@loongson.cn>,
"Alexey Malahov" <Alexey.Malahov@baikalelectronics.ru>,
"Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"Aleksandar Rikalo" <arikalo@gmail.com>,
"Dragan Mladjenovic" <dragan.mladjenovic@syrmia.com>,
"Chao-ying Fu" <cfu@wavecomp.com>,
"Marc Zyngier" <maz@kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] mips: dmi: Fix early remap on MIPS32
Date: Tue, 28 Nov 2023 15:46:37 +0000 [thread overview]
Message-ID: <2148a67f-bd4f-432e-aa0d-c914a4bd5e0d@app.fastmail.com> (raw)
In-Reply-To: <3pgnihbrp5orh4tmj45fipbfoxdwzjh6uefitdpcea2vgkarcm@d56gv3areswl>
在2023年11月28日十一月 上午11:34，Serge Semin写道：
> On Mon, Nov 27, 2023 at 09:08:11PM +0000, Jiaxun Yang wrote:
[...]
>
> Indeed. Thanks for pointing that out. In the last days several times I
> was looking at that line and for some reason UNCAC_BASE seemed as
> CAC_BASE to me.) Based on what both IO_BASE and UNCAC_BASE are defined
> as of the uncached region anyway, then it should be safe for any
> currently supported MIPS64 (including the Loongson's) to use ioremap()
> in place of dmi_early_remap(). So basically my current patch in the
> subject won't change the method semantics. Let's not to try to fix a
> problem which doesn't exist then, and keep the patch as is especially
> seeing that the alternatives might still cause some troubles. Will you
> be ok with that?
I'd say the safest option is to use CKSEG0 or TO_CAC here, but I'm fine
with ioremap as long as the semantic remains uncached on Loongson.
Thanks.
>
> -Serge(y)
>
>>
[...]
--
- Jiaxun
next prev parent reply other threads:[~2023-11-28 15:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 18:23 [PATCH 0/7] MIPS: mm: Fix some memory-related issues Serge Semin
2023-11-22 18:23 ` [PATCH 1/7] mips: dmi: Fix early remap on MIPS32 Serge Semin
2023-11-22 19:35 ` Arnd Bergmann
2023-11-23 9:32 ` Serge Semin
2023-11-23 12:13 ` Jiaxun Yang
2023-11-23 12:29 ` Thomas Bogendoerfer
2023-11-23 15:07 ` Jiaxun Yang
2023-11-23 16:07 ` Thomas Bogendoerfer
2023-11-23 17:33 ` Jiaxun Yang
2023-11-24 18:52 ` Serge Semin
2023-11-24 22:03 ` Jiaxun Yang
2023-11-27 16:23 ` Serge Semin
2023-11-27 21:08 ` Jiaxun Yang
2023-11-28 11:34 ` Serge Semin
2023-11-28 15:46 ` Jiaxun Yang [this message]
2023-11-30 19:16 ` Serge Semin
2023-12-01 0:13 ` Jiaxun Yang
2023-12-01 14:54 ` Serge Semin
2023-12-01 15:10 ` Jiaxun Yang
2023-12-01 18:26 ` Serge Semin
2023-11-28 12:41 ` Arnd Bergmann
2023-11-28 13:52 ` Serge Semin
2023-11-28 21:59 ` Arnd Bergmann
2023-11-30 19:26 ` Serge Semin
2023-11-24 22:34 ` Jiaxun Yang
2023-11-22 18:24 ` [PATCH 7/7] mips: Set dump-stack arch description Serge Semin
2023-11-22 18:29 ` [PATCH 0/7] MIPS: mm: Fix some memory-related issues Andrew Morton
2023-11-23 10:12 ` Serge Semin
[not found] ` <20231122182419.30633-7-fancer.lancer@gmail.com>
2023-11-23 10:06 ` [PATCH 6/7] mm/mm_init.c: Append '\n' to the unavailable ranges log-message Mike Rapoport
[not found] ` <20231122182419.30633-6-fancer.lancer@gmail.com>
2023-11-23 10:18 ` [PATCH 5/7] mm/mm_init.c: Extend init unavailable range doc info Mike Rapoport
[not found] ` <ehlzzv37o4exdn4smmu653wzjdotzdv3dhr3bduvemxssp37ro@sgegnyprquk4>
2023-11-24 8:19 ` Mike Rapoport
[not found] ` <h3g6ynqem6h6hefmdawzaspvzf4u5fwfh7rken3ogy5ucr5z5t@d5gagi2ql4ee>
2023-11-28 7:13 ` Mike Rapoport
[not found] ` <z6r4jvuo63deg5ezzrxiewuzgdfwvcluzp45r4gmu7vwx6fmlm@d5r6phck2ovh>
2023-11-29 6:14 ` Mike Rapoport
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=2148a67f-bd4f-432e-aa0d-c914a4bd5e0d@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=akpm@linux-foundation.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=arikalo@gmail.com \
--cc=arnd@arndb.de \
--cc=cfu@wavecomp.com \
--cc=chenhuacai@kernel.org \
--cc=dragan.mladjenovic@syrmia.com \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maz@kernel.org \
--cc=rppt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=willy@infradead.org \
--cc=yangtiezhu@loongson.cn \
--cc=yangyinglu@loongson.cn \
/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