mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@kernel.org>, Jinyang He <hejinyang@loongson.cn>
Cc: Youling Tang <tangyouling@loongson.cn>,
	Xuerui Wang <kernel@xen0n.name>,
	loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] LoongArch: Use trampoline for exception handlers and kill la.abs
Date: Mon, 16 Jan 2023 13:41:17 +0800	[thread overview]
Message-ID: <972e4d0c69dea4e9659eb9459072b2b7b2fd963b.camel@xry111.site> (raw)
In-Reply-To: <CAAhV-H55Kj4gMnORHfQUYJ3KBueLv7j+ktkNP9cE-=32nEShzg@mail.gmail.com>

On Mon, 2023-01-16 at 09:30 +0800, Huacai Chen wrote:
> On Sat, Jan 14, 2023 at 2:38 PM Jinyang He <hejinyang@loongson.cn>
> wrote:
> > 
> > Hi, Ruoyao and Youling,
> > 
> > I care about the performance when NUMA enabled. We set CSR.EENTRY
> > for each possible cpus where is NUMA-relative. So, I guess the more
> > codes in NUMA-relative memory makes more performance. If we just set
> > handler_trampoline as exception handler, the performance may be
> > influenced.
> So copying both the handlers and handler_trampoline can solve the
> problem? If that is possible, please do that on top of the latest code
> in
> https://github.com/loongson/linux/commits/loongarch-next

Hi folks,

I just wrote the trampoline code as a PoC to show "relocatable kernel
can work" and there must be some better way.  But I'm too sad to write
any serious code in this month, and I don't have access to a LoongArch
NUMA system.  So I think it's better to leave the job for you guys now
:).

Best regards

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-01-16  5:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  9:07 [PATCH 0/4] LoongArch: Add kernel relocation and KASLR support Youling Tang
2023-01-09  9:07 ` [PATCH 1/4] LoongArch: Use trampoline for exception handlers and kill la.abs Youling Tang
2023-01-14  6:38   ` Jinyang He
2023-01-16  1:30     ` Huacai Chen
2023-01-16  5:41       ` Xi Ruoyao [this message]
2023-01-17  1:38         ` Huacai Chen
2023-01-09  9:07 ` [PATCH 2/4] LoongArch: Add JUMP_LINK_ADDR macro implementation to avoid using la.abs Youling Tang
2023-01-14  6:40   ` Jinyang He
2023-01-14  7:25     ` Youling Tang
2023-01-14  7:30       ` Huacai Chen
2023-01-09  9:07 ` [PATCH 3/4] LoongArch: Add support for kernel relocation Youling Tang
2023-01-09 21:52   ` kernel test robot
2023-01-11  3:18   ` Youling Tang
2023-01-14  6:54   ` Jinyang He
2023-01-14  7:50     ` Youling Tang
2023-01-14  8:30       ` Jinyang He
2023-01-14  8:56         ` Youling Tang
2023-01-09  9:07 ` [PATCH 4/4] LoongArch: Add support for kernel address space layout randomization (KASLR) Youling Tang
2023-01-11  5:02   ` kernel test robot
2023-01-13  6:44 ` [PATCH 0/4] LoongArch: Add kernel relocation and KASLR support 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=972e4d0c69dea4e9659eb9459072b2b7b2fd963b.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=chenhuacai@kernel.org \
    --cc=hejinyang@loongson.cn \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=tangyouling@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

all inboxes | Powered by JetHome®