linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: guoren@kernel.org
Cc: arnd@arndb.de, 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,
	mark.rutland@arm.com, ben@decadent.org.uk, bjorn@kernel.org,
	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 V15 0/7] riscv: Add GENERIC_ENTRY support
Date: Thu, 26 Jan 2023 19:25:14 +0000	[thread overview]
Message-ID: <Y9LTmmYuEWKNmyl2@spud> (raw)
In-Reply-To: <20230126172516.1580058-1-guoren@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 865 bytes --]

Hey Guo Ren,

On Thu, Jan 26, 2023 at 12:25:09PM -0500, guoren@kernel.org wrote:
> 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_v15
> 
> Any reviews and tests are helpful.
> 
> v15:
>  - Fixup compile error for !MMU (Thx Conor)
>  - Rebase on riscv for-next (20230127)

nommu build looks fine now, thanks for fixing it up. Hopefully you're
good to now now after 15 versions!

Thanks,
Conor.


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

  parent reply	other threads:[~2023-01-26 19:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 17:25 [PATCH -next V15 0/7] riscv: Add GENERIC_ENTRY support guoren
2023-01-26 17:25 ` [PATCH -next V15 1/7] compiler_types.h: Add __noinstr_section() for noinstr guoren
2023-01-26 19:14   ` Miguel Ojeda
2023-01-27  1:55     ` Guo Ren
2023-01-26 17:25 ` [PATCH -next V15 2/7] riscv: ptrace: Remove duplicate operation guoren
2023-01-26 17:25 ` [PATCH -next V15 3/7] riscv: entry: Add noinstr to prevent instrumentation inserted guoren
2023-01-26 17:25 ` [PATCH -next V15 4/7] riscv: entry: Convert to generic entry guoren
2023-01-26 17:25 ` [PATCH -next V15 5/7] riscv: entry: Remove extra level wrappers of trace_hardirqs_{on,off} guoren
2023-01-26 17:25 ` [PATCH -next V15 6/7] riscv: entry: Consolidate ret_from_kernel_thread into ret_from_fork guoren
2023-01-26 17:25 ` [PATCH -next V15 7/7] riscv: entry: Consolidate general regs saving/restoring guoren
2023-01-26 19:25 ` Conor Dooley [this message]
2023-01-27  9:15   ` [PATCH -next V15 0/7] riscv: Add GENERIC_ENTRY support Björn Töpel

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=Y9LTmmYuEWKNmyl2@spud \
    --to=conor@kernel.org \
    --cc=apatel@ventanamicro.com \
    --cc=arnd@arndb.de \
    --cc=atishp@atishpatra.org \
    --cc=ben@decadent.org.uk \
    --cc=bjorn@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=falcon@tinylab.org \
    --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=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 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).