From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Gregory CLEMENT" <gregory.clement@bootlin.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
vladimir.kondratiev@intel.com
Subject: Re: [PATCH 0/5] MIPS: Fix kernel in XKPHYS
Date: Fri, 27 Oct 2023 21:47:33 +0100 [thread overview]
Message-ID: <bf0f31a4-bfcd-4951-8b7b-67d7c1faf344@app.fastmail.com> (raw)
In-Reply-To: <875y2s81lx.fsf@BL-laptop>
在2023年10月27日十月 下午5:35,Gregory CLEMENT写道:
> Hello Jiaxun,
>
>
>> Hi all,
>>
>> This series fixes support for loading kernel to XKPHYS space.
>> It is derived from "MIPS: use virtual addresses from xkphys for MIPS64" [1].
>>
>> Boot tested on boston and QEMU with loading address set to 0xa800000090000000.
>> QEMU patch on the way.
>>
>> Gregory and Vladimir, do let me know if I missed anything.
>
> Thanks for this series, I reviewed it and tested it on my platform, so
> you can add for all the patches:
>
> Reviewed-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> Tested-by: Gregory CLEMENT <gregory.clement@bootlin.com>
>
> However I add to fix the patch " MIPS: Handle mips_cps_core_entry within
> lower 4G", I think you missed a case. I will comment on it.
I found a better solution for CPS handling, will send v2 later together with
fixes to bring TO_CAC to 32bit.
Thanks.
- Jiaxun
>
> Gregory
>
>
>>
>> Thanks
>> - Jiaxun
>>
>> [1]: https://lore.kernel.org/lkml/20231004161038.2818327-3-gregory.clement@bootlin.com/
>>
>> Jiaxun Yang (5):
>> MIPS: Export higher/highest relocation functions in uasm
>> MIPS: genex: Fix except_vec_vi for kernel in XKPHYS
>> MIPS: Fix set_uncached_handler for ebase in XKPHYS
>> MIPS: Handle mips_cps_core_entry within lower 4G
>> MIPS: Allow kernel base to be set from Kconfig for all platforms
>>
>> arch/mips/Kconfig | 18 +++++++++++++----
>> arch/mips/include/asm/mips-cm.h | 1 +
>> arch/mips/include/asm/uasm.h | 2 ++
>> arch/mips/kernel/genex.S | 19 +++++++++++++----
>> arch/mips/kernel/smp-cps.c | 27 +++++++++++++++++++------
>> arch/mips/kernel/traps.c | 36 +++++++++++++++++++++++----------
>> arch/mips/mm/uasm.c | 6 ++++--
>> 7 files changed, 82 insertions(+), 27 deletions(-)
>>
>> --
>> 2.34.1
>>
>
> --
> Gregory Clement, Bootlin
> Embedded Linux and Kernel engineering
> http://bootlin.com
--
- Jiaxun
prev parent reply other threads:[~2023-10-27 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 19:13 Jiaxun Yang
2023-10-23 19:13 ` [PATCH 1/5] MIPS: Export higher/highest relocation functions in uasm Jiaxun Yang
2023-10-23 19:13 ` [PATCH 2/5] MIPS: genex: Fix except_vec_vi for kernel in XKPHYS Jiaxun Yang
2023-10-23 19:13 ` [PATCH 3/5] MIPS: Fix set_uncached_handler for ebase " Jiaxun Yang
2023-10-25 2:48 ` kernel test robot
2023-10-23 19:13 ` [PATCH 4/5] MIPS: Handle mips_cps_core_entry within lower 4G Jiaxun Yang
2023-10-23 19:14 ` [PATCH 5/5] MIPS: Allow kernel base to be set from Kconfig for all platforms Jiaxun Yang
2023-10-25 18:09 ` [PATCH 0/5] MIPS: Fix kernel in XKPHYS Florian Fainelli
[not found] ` <875y2s81lx.fsf@BL-laptop>
2023-10-27 20:47 ` Jiaxun Yang [this message]
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=bf0f31a4-bfcd-4951-8b7b-67d7c1faf344@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=vladimir.kondratiev@intel.com \
/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
all inboxes | Powered by JetHome®