search

riscv-admin / dev-partners

This repo is for tracking of RISC-V Development Partners Activities
3 stars 0 forks source link

PLIC on SAIL model #34

Open ptprasanna opened 1 year ago

ptprasanna commented 1 year ago

Technical Group

PLIC

ratification-pkg

PLIC

Technical Liaison

Prasanna

Task Category

SAIL

Task Sub Category

Ratification Target

2022

Statement of Work (SOW)

Component names:

Requirements: Developing PLIC extension of Riscv Specification, on Sail model using sail programming language. By implementing memory mapped registers on sail for handling the externally generated interrupts (platform generated interrupts).

Deliverables:

Acceptance Criteria:

Projected timeframe: (best guess date)

SOW Signoffs:

Waiver

Pull Request Details

No response

jjscheel commented 1 year ago

Hi, @ptprasanna, I've added the SOW template to your first comment and moved your text into the requirements section. Let's edit it there as-needed.

Thanks!

jrtc27 commented 1 year ago

What's the point of having a PLIC without any devices attached to it that can generate interrupts?

jjscheel commented 1 year ago

Today's DevPartners meeting suggested that this work is on-going to create a PLIC infrastructure in SAIL and it will include a basic framework for testing interrupts.

The open question for the DevPartner's meeting is to determine how much to track here so as not to duplicate work. At this time, I view this item as FYI for us.

ptprasanna commented 1 year ago

PLIC : Algorithm has been completed and coding in progress. Hoping to get this done by this week and will send the code to Bill for review.

Testing : Sail(PLIC) will be listening on a certain port. And an external software will send the interrupt messages to PLIC on that port. We'll use system call for this.

jjscheel commented 1 year ago

@ptprasanna, do we have a target date by which all work is anticipated to be done, including PR acceptance?

jrtc27 commented 1 year ago

NB: Bill doesn't review the code, the community does

jjscheel commented 1 year ago

@jrtc27, indeed. I suspect that because the person is new, they're actually "pre-reviewing" the code with Bill. Everyone understands that the community will review the code, comment, and ultimately accept the PR.

jrtc27 commented 1 year ago

@jrtc27, indeed. I suspect that because the person is new, they're actually "pre-reviewing" the code with Bill. Everyone understands that the community will review the code, comment, and ultimately accept the PR.

Ack

ptprasanna commented 1 year ago

@ptprasanna, do we have a target date by which all work is anticipated to be done, including PR acceptance?

Planning to submit the ongoing work for peer review by this week.

jjscheel commented 1 year ago

@billmcspadden-riscv, if you could provide and outlook on when a review of the code might be expected, that would help @ptprasanna. Thanks!!!

jjscheel commented 1 year ago

@billmcspadden-riscv promises feedback this week. Thanks, Bill!!!

jjscheel commented 12 months ago

@ptprasanna, please see the email to your gmail account on Bill's needs.

jjscheel commented 9 months ago

@ptprasanna, I would like an update in the issue, by the next meeting on December 12, 2023, please.

jjscheel commented 7 months ago

@anuani21, can you see if there's any status here. @billmcspadden-riscv, is this the issue stalled behind the test framework work?

anuani21 commented 7 months ago

Hi Jeff,

I will check with my team and update the status on this item.

Regards, Anusha

On Tue, 30 Jan, 2024, 4:55 pm Jeff Scheel, @.***> wrote:

@anuani21 https://github.com/anuani21, can you see if there's any status here. @billmcspadden-riscv https://github.com/billmcspadden-riscv, is this the issue stalled behind the test framework work?

— Reply to this email directly, view it on GitHub https://github.com/riscv-admin/dev-partners/issues/34#issuecomment-1916636948, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6FFYMHZH6B64CCUTLFQLYRDKDVAVCNFSM6AAAAAAXLF4LHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJWGYZTMOJUHA . You are receiving this because you were mentioned.Message ID: @.***>

jjscheel commented 7 months ago

Thanks, @anuani21. Please post when you have information.

jjscheel commented 7 months ago

Per @anuani21, the developer working on this has been pulled away with other activities. Anusha can we please get an outlook for when they might be back?

Additionally, it would be helpful to add the developer as an assignee to the issue. Are they in Groups.IO as a RISC-V member? If not, we should get them there too so as to receive the mailing list information for the group.

anuani21 commented 7 months ago

++saravanan

On Thu, Feb 22, 2024 at 7:29 PM Jeff Scheel @.***> wrote:

Per @anuani21 https://github.com/anuani21, the developer working on this has been pulled away with other activities. Anusha can we please get an outlook for when they might be back?

Additionally, it would be helpful to add the developer as an assignee to the issue. Are they in Groups.IO as a RISC-V member? If not, we should get them there too so as to receive the mailing list information for the group.

— Reply to this email directly, view it on GitHub https://github.com/riscv-admin/dev-partners/issues/34#issuecomment-1959507613, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6FF5FYHUJBGPA7RPSWXLYU5FNDAVCNFSM6AAAAAAXLF4LHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZGUYDONRRGM . You are receiving this because you were mentioned.Message ID: @.***>

jjscheel commented 1 month ago

@ptprasanna, @anuani21, would you kindly provide status for the August 20 meeting on this item. Thanks!