All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Björn Töpel" <bjorn@kernel.org>
To: guoren@kernel.org, arnd@arndb.de, guoren@kernel.org,
	palmer@rivosinc.com, tglx@linutronix.de, peterz@infradead.org,
	luto@kernel.org, conor.dooley@microchip.com, heiko@sntech.de,
	jszhang@kernel.org, lazyparser@gmail.com, falcon@tinylab.org,
	chenhuacai@kernel.org, apatel@ventanamicro.com,
	atishp@atishpatra.org, paul.walmsley@sifive.com,
	mark.rutland@arm.com, greentime.hu@sifive.com,
	andy.chiu@sifive.com, ben@decadent.org.uk
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH -next V11 0/7] riscv: Add GENERIC_ENTRY support
Date: Mon, 12 Dec 2022 08:18:08 +0100	[thread overview]
Message-ID: <87o7s9ay4v.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20221210171141.1120123-1-guoren@kernel.org>

guoren@kernel.org writes:

> From: Guo Ren <guoren@linux.alibaba.com>
>
> The patches convert riscv to use the generic entry infrastructure from
> kernel/entry/*. Some optimization for entry.S with new .macro and merge
> ret_from_kernel_thread into ret_from_fork.
>
> The 1,2 are the preparation of generic entry. 3~7 are the main part
> of generic entry.
>
> All tested with rv64, rv32, rv64 + 32rootfs, all are passed.
>
> You can directly try it with:
> [1] https://github.com/guoren83/linux/tree/generic_entry_v11

FWIW, the v11 branch is not available here.

This series is a really nice cleanup for the RISC-V entry code. I've run
it on some kernel selftests, and haven't seen any issues.

I'm looking forward to having this series pulled in!

Reviewed-by: Björn Töpel <bjorn@rivosinc.com>

WARNING: multiple messages have this Message-ID (diff)
From: "Björn Töpel" <bjorn@kernel.org>
To: guoren@kernel.org, arnd@arndb.de, guoren@kernel.org,
	palmer@rivosinc.com, tglx@linutronix.de, peterz@infradead.org,
	luto@kernel.org, conor.dooley@microchip.com, heiko@sntech.de,
	jszhang@kernel.org, lazyparser@gmail.com, falcon@tinylab.org,
	chenhuacai@kernel.org, apatel@ventanamicro.com,
	atishp@atishpatra.org, paul.walmsley@sifive.com,
	mark.rutland@arm.com, greentime.hu@sifive.com,
	andy.chiu@sifive.com, ben@decadent.org.uk
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH -next V11 0/7] riscv: Add GENERIC_ENTRY support
Date: Mon, 12 Dec 2022 08:18:08 +0100	[thread overview]
Message-ID: <87o7s9ay4v.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20221210171141.1120123-1-guoren@kernel.org>

guoren@kernel.org writes:

> From: Guo Ren <guoren@linux.alibaba.com>
>
> The patches convert riscv to use the generic entry infrastructure from
> kernel/entry/*. Some optimization for entry.S with new .macro and merge
> ret_from_kernel_thread into ret_from_fork.
>
> The 1,2 are the preparation of generic entry. 3~7 are the main part
> of generic entry.
>
> All tested with rv64, rv32, rv64 + 32rootfs, all are passed.
>
> You can directly try it with:
> [1] https://github.com/guoren83/linux/tree/generic_entry_v11

FWIW, the v11 branch is not available here.

This series is a really nice cleanup for the RISC-V entry code. I've run
it on some kernel selftests, and haven't seen any issues.

I'm looking forward to having this series pulled in!

Reviewed-by: Björn Töpel <bjorn@rivosinc.com>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2022-12-12  7:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 17:11 [PATCH -next V11 0/7] riscv: Add GENERIC_ENTRY support guoren
2022-12-10 17:11 ` guoren
2022-12-10 17:11 ` [PATCH -next V11 1/7] compiler_types.h: Add __noinstr_section() for noinstr guoren
2022-12-10 17:11   ` guoren
2022-12-10 17:11 ` [PATCH -next V11 2/7] riscv: ptrace: Remove duplicate operation guoren
2022-12-10 17:11   ` guoren
2022-12-10 17:11 ` [PATCH -next V11 3/7] riscv: entry: Add noinstr to prevent instrumentation inserted guoren
2022-12-10 17:11   ` guoren
2022-12-10 17:11 ` [PATCH -next V11 4/7] riscv: entry: Convert to generic entry guoren
2022-12-10 17:11   ` guoren
2022-12-10 17:11 ` [PATCH -next V11 5/7] riscv: entry: Remove extra level wrappers of trace_hardirqs_{on,off} guoren
2022-12-10 17:11   ` guoren
2022-12-10 17:11 ` [PATCH -next V11 6/7] riscv: entry: Consolidate ret_from_kernel_thread into ret_from_fork guoren
2022-12-10 17:11   ` guoren
2022-12-10 17:11 ` [PATCH -next V11 7/7] riscv: entry: Consolidate general regs saving/restoring guoren
2022-12-10 17:11   ` guoren
2022-12-12  7:18 ` Björn Töpel [this message]
2022-12-12  7:18   ` [PATCH -next V11 0/7] riscv: Add GENERIC_ENTRY support Björn Töpel
2022-12-12  7:47   ` Guo Ren
2022-12-12  7:47     ` Guo Ren

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=87o7s9ay4v.fsf@all.your.base.are.belong.to.us \
    --to=bjorn@kernel.org \
    --cc=andy.chiu@sifive.com \
    --cc=apatel@ventanamicro.com \
    --cc=arnd@arndb.de \
    --cc=atishp@atishpatra.org \
    --cc=ben@decadent.org.uk \
    --cc=chenhuacai@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=falcon@tinylab.org \
    --cc=greentime.hu@sifive.com \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=heiko@sntech.de \
    --cc=jszhang@kernel.org \
    --cc=lazyparser@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=luto@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.