From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
shannmu <shanmu1901@gmail.com>,
xenomai@lists.linux.dev, "Schaffner,
Tobias (T CED SES-DE)" <tobias.schaffner@siemens.com>
Subject: Re: [PATCH 1/3] RISC-V: enable IRQ-PIPELINE
Date: Fri, 11 Oct 2024 09:41:01 +0200 [thread overview]
Message-ID: <87zfnb84tu.fsf@xenomai.org> (raw)
In-Reply-To: <a59c3c6d97a76ea423dcdc283694f9c5baaac9be.camel@siemens.com> (Florian Bezdeka's message of "Fri, 11 Oct 2024 09:24:40 +0200")
Florian Bezdeka <florian.bezdeka@siemens.com> writes:
> On Fri, 2024-10-11 at 09:15 +0200, Jan Kiszka wrote:
>> On 11.10.24 08:37, shannmu wrote:
>> > This adds virtual interrupt functions `arch_xxx`,
>> > irq-pipelined top-level interrupt handler `handle_riscv_irq`
>> > and `handle_arch_irq_pipelined`,
>> > real interrupt-flags functions `native_xxx`,
>> > `mark_trap_entry` and `mark_trap_exit` in trap functions,
>> > multiplexed ipi_message_type `IPI_RESCHEDULE` for in-band ipi.
>> >
>> > Signed-off-by: shannmu <shanmu1901@gmail.com>
>> > ---
>> > arch/riscv/Kconfig | 5 +
>> > arch/riscv/include/asm/dovetail.h | 58 +++++++
>> > arch/riscv/include/asm/irq_pipeline.h | 173 +++++++++++++++++++++
>> > arch/riscv/include/asm/irqflags.h | 26 ++--
>> > arch/riscv/include/asm/mmu_context.h | 21 ++-
>> > arch/riscv/include/asm/syscall.h | 6 +
>> > arch/riscv/kernel/Makefile | 1 +
>> > arch/riscv/kernel/irq.c | 72 ++++++---
>> > arch/riscv/kernel/irq_pipeline.c | 46 ++++++
>> > arch/riscv/kernel/smp.c | 135 ++++++++++++----
>> > arch/riscv/kernel/smpboot.c | 2 +-
>> > arch/riscv/kernel/traps.c | 212 +++++++++++++++-----------
>> > arch/riscv/mm/fault.c | 46 +++---
>> > 13 files changed, 633 insertions(+), 170 deletions(-)
>> > create mode 100644 arch/riscv/include/asm/dovetail.h
>> > create mode 100644 arch/riscv/include/asm/irq_pipeline.h
>> > create mode 100644 arch/riscv/kernel/irq_pipeline.c
>> >
>>
>> Thanks for sharing your work! Could you explain how these bits compare
>> to what Tobias sent earlier [1]? Is it possible to combine your work
>> with that to ensure nothing relevant is missed?
>
> Thanks for sharing +1. One major difference is the base branch. Tobias
> was working on 6.11 while this one is based on 6.6.
>
> As we now have two different works streams it makes sense to
> synchronize and ideally align on a roadmap / work sharing plan. That
> would help to minimize review / testing efforts - at least on my side.
>
Agreed. For the record, I'm willing to merge the RISC-V architecture
support into Dovetail and the EVL core. We'd just need to merge both
ongoing efforts to get this done faster.
--
Philippe.
next prev parent reply other threads:[~2024-10-11 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 6:37 [PATCH 0/3] *** Port dovetail into RISCV *** shannmu
2024-10-11 6:37 ` [PATCH 1/3] RISC-V: enable IRQ-PIPELINE shannmu
2024-10-11 7:15 ` Jan Kiszka
2024-10-11 7:24 ` Florian Bezdeka
2024-10-11 7:39 ` Jan Kiszka
2024-10-11 7:41 ` Philippe Gerum [this message]
2024-10-11 17:07 ` shanmu
2024-10-13 20:15 ` Schaffner, Tobias
2024-10-14 5:04 ` shanmu
2024-10-14 6:10 ` Schaffner, Tobias
2024-10-11 6:37 ` [PATCH 2/3] clocksource: Add irq pipelined clock events shannmu
2024-10-11 8:09 ` Philippe Gerum
2024-10-11 6:37 ` [PATCH 3/3] riscv/evl: Port evl patch to riscv (just compile pass) shannmu
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=87zfnb84tu.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=shanmu1901@gmail.com \
--cc=tobias.schaffner@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.