|
Boot code awareness of the Hypervisor extension
how is this intended to work with versions? so we ratify some 1.0 spec and we come along and call it 1.1 that has additive changes, i thought i heard that ecosystem around risc-v including compilers a
how is this intended to work with versions? so we ratify some 1.0 spec and we come along and call it 1.1 that has additive changes, i thought i heard that ecosystem around risc-v including compilers a
|
By
mark
· #184
·
|
|
Boot code awareness of the Hypervisor extension
Thank you. If I understand this correctly I agree with all you have said. If this is a once at boot time requirement regardless of mode and there is a reasonable way to do it, then i concur that well
Thank you. If I understand this correctly I agree with all you have said. If this is a once at boot time requirement regardless of mode and there is a reasonable way to do it, then i concur that well
|
By
mark
· #188
·
|
|
P extension instruction opcode encoding allocation
Krste has said (correct me if I am wrong) that the unpriv SC owns the opcode space. I know there is a lot of overlap in the SC members but I suggest we get that SC officially in the loop. I have CC'ed
Krste has said (correct me if I am wrong) that the unpriv SC owns the opcode space. I know there is a lot of overlap in the SC members but I suggest we get that SC officially in the loop. I have CC'ed
|
By
mark
· #289
·
|
|
Disabling and re-enabling extensions
Is there a checklist of requirements for priv specifications? if not should there be? If there is, would this be a requirement in that list to specify to some level of clarity (maybe indicating what i
Is there a checklist of requirements for priv specifications? if not should there be? If there is, would this be a requirement in that list to specify to some level of clarity (maybe indicating what i
|
By
mark
· #328
·
|
|
Proposal: Accelerating Handling User-level Interrupts
i remember using DEC VAX ancillary control processes and writing knob and trackball device drivers in user land in the early 80s. I tried to find something describing this but I think it is lost to an
i remember using DEC VAX ancillary control processes and writing knob and trackball device drivers in user land in the early 80s. I tried to find something describing this but I think it is lost to an
|
By
mark
· #361
·
|
|
Performance Monitor Interrupts
+platform -------- sent from a mobile device. please forgive any typos.
+platform -------- sent from a mobile device. please forgive any typos.
|
By
mark
· #412
·
|
|
[Announcement] Successful KVM RISC-V bring up on FPGA (Rocket core with H extension)
congrats! can we send something out to tech-announce about it? -------- sent from a mobile device. please forgive any typos.
congrats! can we send something out to tech-announce about it? -------- sent from a mobile device. please forgive any typos.
|
By
mark
· #460
·
|
|
Architecture extension proposal for ConfigPtr CSR to "Unified RISC-V Discovery Method" config structure
so how do we communicate this to the world? csr is an ISA extension config tab is a software only Non-ISA doc rule required only by a platform spec? So could you do discovery in some other way and be
so how do we communicate this to the world? csr is an ISA extension config tab is a software only Non-ISA doc rule required only by a platform spec? So could you do discovery in some other way and be
|
By
mark
· #708
·
|
|
Smepmp discovery
what do other architectures do? -------- sent from a mobile device. please forgive any typos.
what do other architectures do? -------- sent from a mobile device. please forgive any typos.
|
By
mark
· #788
·
|
|
[RFC] Toolchain interface for privilege spec related stuff.
all the specs will have unique extension names. it is also possible to have rollup extension names like we have for crypto like Zk. I suggest we make the options match the extension names and if neede
all the specs will have unique extension names. it is also possible to have rollup extension names like we have for crypto like Zk. I suggest we make the options match the extension names and if neede
|
By
mark
· #828
·
|
|
[RFC] Toolchain interface for privilege spec related stuff.
+Philipp Tomsich
By
mark
· #829
·
|
|
[RISC-V] [tech-unixplatformspec] RISC-V H-extension plus RISC-V AIA proof-of-concept completed
let's create a top sheet and add this please. philipp is working on a review proposal. likely more like tech-announce for 2 weeks and notify TSC and the board. etc Get BlueMail for Android
let's create a top sheet and add this please. philipp is working on a review proposal. likely more like tech-announce for 2 weeks and notify TSC and the board. etc Get BlueMail for Android
|
By
mark
· #834
·
|
|
[RFC] Toolchain interface for privilege spec related stuff.
it sounds like we are aligned Get BlueMail for Android
it sounds like we are aligned Get BlueMail for Android
|
By
mark
· #835
·
|
|
IOMMU proposal on wiki
Agreed and many thanks to rivos. I think Philipp and Greg as chairs of SW and Priv are discussing the best way/place to create this SIG. remember that we are matrixed and at least these two committees
Agreed and many thanks to rivos. I think Philipp and Greg as chairs of SW and Priv are discussing the best way/place to create this SIG. remember that we are matrixed and at least these two committees
|
By
mark
· #878
·
|
|
IOMMU proposal on wiki
I agree. We are a community and the best solutions are jointly developed with community buy-in. A similar thing occurred with graphics and shading. We had them step and back and develop a strategy wit
I agree. We are a community and the best solutions are jointly developed with community buy-in. A similar thing occurred with graphics and shading. We had them step and back and develop a strategy wit
|
By
mark
· #881
·
|
|
IOMMU proposal on wiki
The Committees (who can delegate to SIGs) now constitute the mechanism for continuity as Task groups must have small tasks and end when they complete their tasks. The goal is that some committee or SI
The Committees (who can delegate to SIGs) now constitute the mechanism for continuity as Task groups must have small tasks and end when they complete their tasks. The goal is that some committee or SI
|
By
mark
· #894
·
|
|
Quality of Service (QoS)
Vedvyas, Thank you. We have a RAS committee on the org and approved by the BOD but has not been formed and QOS is one part of what it was intended to look at (as part of availability). I wonder if we
Vedvyas, Thank you. We have a RAS committee on the org and approved by the BOD but has not been formed and QOS is one part of what it was intended to look at (as part of availability). I wonder if we
|
By
mark
· #927
·
|
|
Smstateen for Zcmt
Please talk with Greg and decide. This is why we have cross group involvement. When a spec is ratified and a TG is disbanded, the Committee has ultimate responsibility. I have a question though. Is th
Please talk with Greg and decide. This is why we have cross group involvement. When a spec is ratified and a TG is disbanded, the Committee has ultimate responsibility. I have a question though. Is th
|
By
mark
· #1008
·
|
|
Smstateen for Zcmt
Apologies. Clearly I am losing track of what is happening when! If you depend on it and its not ratified, then you either need to wait or get a waiver.
Apologies. Clearly I am losing track of what is happening when! If you depend on it and its not ratified, then you either need to wait or get a waiver.
|
By
mark
· #1010
·
|
|
Smstateen for Zcmt
Please explain to me why we would not want implementers to implement Zc* and not C. I am not sure I understand the use cases and workloads well. Am I misunderstanding? I understand that implementers w
Please explain to me why we would not want implementers to implement Zc* and not C. I am not sure I understand the use cases and workloads well. Am I misunderstanding? I understand that implementers w
|
By
mark
· #1026
·
|