Page MenuHomeFreeBSD

riscvGroup
ActivePublic

Recent Activity

Tue, Nov 18

jsihv_gmx.com requested review of D53804: riscv cpu_fork(), saving fpe state.
Tue, Nov 18, 3:18 PM · riscv

Oct 23 2025

mengzhuo1203_gmail.com updated the diff for D53232: riscv: explicit memory barrier primitives.
Oct 23 2025, 4:49 AM · riscv
mengzhuo1203_gmail.com added a comment to D53232: riscv: explicit memory barrier primitives.

This will not fix that bug. fence is fence iorw, iorw, so all you are doing is relaxing some ordering requirements.

Oct 23 2025, 1:51 AM · riscv
mengzhuo1203_gmail.com updated the diff for D53232: riscv: explicit memory barrier primitives.
Oct 23 2025, 1:50 AM · riscv

Oct 22 2025

jrtc27 added a comment to D53232: riscv: explicit memory barrier primitives.

This will not fix that bug. fence is fence iorw, iorw, so all you are doing is relaxing some ordering requirements.

Oct 22 2025, 9:47 AM · riscv
mengzhuo1203_gmail.com updated the diff for D53232: riscv: explicit memory barrier primitives.

@jrtc27 I've update the revision, PTAL

Oct 22 2025, 4:58 AM · riscv
mengzhuo1203_gmail.com added a comment to D53232: riscv: explicit memory barrier primitives.

Do we actually have a proper definition of what *our* memory barrier APIs are meant to mean? What the ISA manual says is a sensible mapping isn't necessarily what we want; note that the table you're referencing is for "Linux memory primitives", and we are not Linux, nor do we follow its memory model.

Oct 22 2025, 2:12 AM · riscv

Oct 21 2025

jrtc27 added a reviewer for D53232: riscv: explicit memory barrier primitives: jrtc27.
Oct 21 2025, 9:53 AM · riscv
jrtc27 added a comment to D53232: riscv: explicit memory barrier primitives.

Do we actually have a proper definition of what *our* memory barrier APIs are meant to mean? What the ISA manual says is a sensible mapping isn't necessarily what we want; note that the table you're referencing is for "Linux memory primitives", and we are not Linux, nor do we follow its memory model.

Oct 21 2025, 9:53 AM · riscv
mengzhuo1203_gmail.com requested review of D53232: riscv: explicit memory barrier primitives.
Oct 21 2025, 9:45 AM · riscv

Jul 12 2025

yuri closed D51271: net/usockets: Enable riscv64 build.
Jul 12 2025, 8:56 AM · riscv, network
mengzhuo1203_gmail.com requested review of D51271: net/usockets: Enable riscv64 build.
Jul 12 2025, 4:46 AM · riscv, network

Jul 2 2025

mengzhuo1203_gmail.com removed a watcher for riscv: mengzhuo1203_gmail.com.
Jul 2 2025, 10:59 AM
mengzhuo1203_gmail.com added a member for riscv: mengzhuo1203_gmail.com.
Jul 2 2025, 10:59 AM

Jul 1 2025

mengzhuo1203_gmail.com added a watcher for riscv: mengzhuo1203_gmail.com.
Jul 1 2025, 12:27 PM

Jun 12 2025

himanshu_thechauhan.dev added a comment to D43452: riscv: Introduce support for Incoming MSI Controller (IMSIC).

Shall I send a new patch? No comments on this one.

Jun 12 2025, 4:53 PM · riscv

May 27 2025

cem added a comment to D48943: Add StarFive JH7110 true random number generator driver.

FYI, it's best practice to generate diffs with full context (-U999999 or whatever).

May 27 2025, 2:42 AM · riscv

May 26 2025

thj edited reviewers for D48943: Add StarFive JH7110 true random number generator driver, added: csprng; removed: security.
May 26 2025, 3:12 PM · riscv
thj added a reviewer for D48943: Add StarFive JH7110 true random number generator driver: security.
May 26 2025, 3:09 PM · riscv

Feb 11 2025

jsihv_gmx.com requested review of D48943: Add StarFive JH7110 true random number generator driver.
Feb 11 2025, 4:21 PM · riscv

Dec 23 2024

himanshu_thechauhan.dev updated the diff for D43452: riscv: Introduce support for Incoming MSI Controller (IMSIC).
  • Refactor aplic code into common init and aplic/imsic specific code.
  • Add support for IMSIC.
Dec 23 2024, 5:52 PM · riscv
himanshu_thechauhan.dev retitled D43452: riscv: Introduce support for Incoming MSI Controller (IMSIC) from [RFC] riscv: Introduce support for Incoming MSI Controller (IMSIC) to riscv: Introduce support for Incoming MSI Controller (IMSIC).
Dec 23 2024, 5:50 PM · riscv

Sep 23 2024

thj added a member for riscv: thj.
Sep 23 2024, 2:32 PM

Sep 4 2024

bz added a member for riscv: bz.
Sep 4 2024, 7:14 PM

Aug 14 2024

himanshu_thechauhan.dev added a comment to D43452: riscv: Introduce support for Incoming MSI Controller (IMSIC).
In D43452#1055467, @br wrote:

Hi Himanshu what is status of this? could you regenerate for the latest HEAD ?

Aug 14 2024, 6:39 AM · riscv

Aug 13 2024

br added a comment to D43452: riscv: Introduce support for Incoming MSI Controller (IMSIC).

Hi Himanshu what is status of this? could you regenerate for the latest HEAD ?

Aug 13 2024, 1:29 PM · riscv

Jun 17 2024

jsihv_gmx.com added a watcher for riscv: jsihv_gmx.com.
Jun 17 2024, 5:41 PM

Feb 14 2024

mhorne closed D43293: RISCV: Introduce support for APLIC interrupt controller.
Feb 14 2024, 3:44 PM · riscv
mhorne accepted D43293: RISCV: Introduce support for APLIC interrupt controller.
Feb 14 2024, 3:27 PM · riscv

Feb 12 2024

himanshu_thechauhan.dev updated the diff for D43293: RISCV: Introduce support for APLIC interrupt controller.

Reworked APLIC_IDC_REG as asked

Feb 12 2024, 10:43 AM · riscv

Feb 3 2024

jrtc27 added inline comments to D43293: RISCV: Introduce support for APLIC interrupt controller.
Feb 3 2024, 10:04 AM · riscv
himanshu_thechauhan.dev added inline comments to D43293: RISCV: Introduce support for APLIC interrupt controller.
Feb 3 2024, 9:54 AM · riscv

Feb 2 2024

jrtc27 added inline comments to D43293: RISCV: Introduce support for APLIC interrupt controller.
Feb 2 2024, 10:26 PM · riscv

Feb 1 2024

himanshu_thechauhan.dev updated the diff for D43293: RISCV: Introduce support for APLIC interrupt controller.

Sorry for the mess up in versions in comments. Last patch was v9, as per my local branches. This one is v10.

Feb 1 2024, 3:42 PM · riscv
jrtc27 added inline comments to D43293: RISCV: Introduce support for APLIC interrupt controller.
Feb 1 2024, 11:28 AM · riscv
himanshu_thechauhan.dev updated the diff for D43293: RISCV: Introduce support for APLIC interrupt controller.
Feb 1 2024, 11:12 AM · riscv
himanshu_thechauhan.dev updated the diff for D43293: RISCV: Introduce support for APLIC interrupt controller.

Changes in v10:

  • Save hart indices from FDT and use them to create target value
Feb 1 2024, 11:07 AM · riscv

Jan 31 2024

jrtc27 added inline comments to D43293: RISCV: Introduce support for APLIC interrupt controller.
Jan 31 2024, 7:13 PM · riscv
jrtc27 requested changes to D43293: RISCV: Introduce support for APLIC interrupt controller.
Jan 31 2024, 7:13 PM · riscv
mhorne accepted D43293: RISCV: Introduce support for APLIC interrupt controller.

LGTM!

Jan 31 2024, 7:09 PM · riscv

Jan 28 2024

himanshu_thechauhan.dev added a comment to D43293: RISCV: Introduce support for APLIC interrupt controller.

ping.

Jan 28 2024, 3:50 AM · riscv

Jan 25 2024

himanshu_thechauhan.dev updated the diff for D43293: RISCV: Introduce support for APLIC interrupt controller.

After Convert local interrupt controller to a newbus PIC, commit rebase is required.

Jan 25 2024, 10:09 AM · riscv

Jan 23 2024

himanshu_thechauhan.dev updated the diff for D43293: RISCV: Introduce support for APLIC interrupt controller.

Changes in v7:

  • Keep per-cpu IDC offsets after reading interrupts-extended property
  • Accessing IDC is via the stored per-CPU IDC offsets
  • Remove cleanup after failure in *_attach function (like other drivers)
  • Added aplic.c in files.riscv alphabetically
Jan 23 2024, 2:42 PM · riscv
jrtc27 added inline comments to D43293: RISCV: Introduce support for APLIC interrupt controller.
Jan 23 2024, 9:12 AM · riscv
jrtc27 added a comment to D43293: RISCV: Introduce support for APLIC interrupt controller.

@jrtc27 Thanks for your review! I have taken care of your comments. Patch will follow shortly.

Unless I'm mistaken you still use the hartid to index the APLIC, not the APLIC's hart indexes. You need to actually record, and later use, the index <-> cpu mapping when iterating over interrupts-extended.

Whatever hartid is read from the FDT, its logical CPU is kept in target_cpu cpuset. We already, in a way, keep that mapping. When the interrupts are bound, the logical CPU from target_cpu points to the required hart. There is no need to keep separate mapping.

Jan 23 2024, 9:12 AM · riscv
himanshu_thechauhan.dev added a comment to D43293: RISCV: Introduce support for APLIC interrupt controller.

@jrtc27 Thanks for your review! I have taken care of your comments. Patch will follow shortly.

Unless I'm mistaken you still use the hartid to index the APLIC, not the APLIC's hart indexes. You need to actually record, and later use, the index <-> cpu mapping when iterating over interrupts-extended.

Jan 23 2024, 9:04 AM · riscv
jrtc27 added a comment to D43293: RISCV: Introduce support for APLIC interrupt controller.

@jrtc27 Thanks for your review! I have taken care of your comments. Patch will follow shortly.

Jan 23 2024, 1:46 AM · riscv

Jan 19 2024

himanshu_thechauhan.dev updated the diff for D43293: RISCV: Introduce support for APLIC interrupt controller.

Changes in v6:

  • Added verification of harts that can take interrupt using "interrupts-extended" property of FDT.
  • Added target_cpu cpuset which contains the bit map of logical cpus that can take interrupts.
  • During binding of the irqs, the cpus from target_cpu cpuset is used.
  • Handled failure case and deregister ircs.
  • Took care of comments regarding the brackets.
  • Added a macro APLIC_IDC to give offset of a given hart.
  • Removed return of FILTER_STRAY when IRQ is 0, added a KASSERT instead.
  • Use of DEFINE_CLASS_0
Jan 19 2024, 12:02 PM · riscv
himanshu_thechauhan.dev added a comment to D43293: RISCV: Introduce support for APLIC interrupt controller.

@jrtc27 Thanks for your review! I have taken care of your comments. Patch will follow shortly.

Jan 19 2024, 11:17 AM · riscv

Jan 18 2024

mhorne added a comment to D43293: RISCV: Introduce support for APLIC interrupt controller.

Also this doesn't properly deal with the interrupts-extended property. I believe that, like the PLIC, you need to iterate over its cells to figure out the mapping between architectural hart ID and APLIC hart index, since they are two independent schemes.

Jan 18 2024, 8:10 PM · riscv