|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
The mtime synchronization code sample is only for reference. A platform can have it’s own way (hardware/software) of synchronizing MTIME registers. The code sample shows a simple approach to synchronize MTIME registers assuming MTIMER devices are running at same frequency and clock drift is taken care in hardware.
I think we need some text to explicitly state expectations around clock drift handling.
Regards, Anup
From: Jonathan Behrens <behrensj@...>
Sent: 29 May 2021 04:37 To: jscheid@... Cc: Anup Patel <Anup.Patel@...>; tech-aia@...; tech-unixplatformspec@...; Atish Patra <Atish.Patra@...>; Greg Favor <gfavor@...>; Alistair Francis <Alistair.Francis@...>; Andrew Waterman <andrew@...>; John Hauser <jh.riscv@...> Subject: Re: [RISC-V] [tech-unixplatformspec] [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
If you're interested in reading about pure software approaches to clock synchronization, I recommend looking at https://www.usenix.org/conference/nsdi18/presentation/geng. They focus on synchronizing clocks between different servers in the same datacenter which if anything is a harder problem.
The main issue I see with the mtime synchronization code sample in the linked spec is that it doesn't do anything to address clock drift. The linked paper claims that CPU clocks can drift by 10 microseconds/second or more, so unless you have dedicated hardware to prevent drift (in which case why are you bothering with software at all?) you are very rapidly going to observe time readings that differ by more than one tick even if they start out consistent.
Jonathan
On Fri, May 28, 2021 at 5:44 PM Josh Scheid via lists.riscv.org <jscheid=ventanamicro.com@...> wrote:
|
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Hi Neel,
You first question is already answered by Greg.
Regarding second question/suggestion, I agree we should explicitly state how to disable a pending interrupt.
Regards, Anup
From: tech-unixplatformspec@... <tech-unixplatformspec@...>
On Behalf Of Neel Gala
Sent: 27 May 2021 23:05 To: Anup Patel <Anup.Patel@...> Cc: Josh Scheid <jscheid@...>; tech-aia@...; tech-unixplatformspec@...; Atish Patra <Atish.Patra@...>; Greg Favor <gfavor@...>; Alistair Francis <Alistair.Francis@...>; Andrew Waterman <andrew@...>; John Hauser <jh.riscv@...> Subject: Re: [RISC-V] [tech-unixplatformspec] [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Hi,
Minor comments:
Should there be a mention that the user level "time" csr (0xC01) which is used by the rdtime pseudo-instruction will enable a read-only peek into the mtime register? Would this require change in Table-1 privilege mode accesses? as well?
Should there also be a suggestion/recommendation on how to disable a pending interrupt (typically by writing to mtimecmp)?
On Thu, May 27, 2021 at 10:45 AM Anup Patel <anup.patel@...> wrote:
-- Neel Gala
|
|
|
|
[RESEND PATCH v6 2/2] contributors: Add Abner as contributor
From: Abner Chang <abner.chang@...>
Signed-off-by: Abner Chang <renba.chang@...> --- contributors.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/contributors.adoc b/contributors.adoc index 91cc46e..7bc731e 100644 --- a/contributors.adoc +++ b/contributors.adoc @@ -29,6 +29,7 @@ Alistair Francis, Sunil V L, Rahul Pathak, Mayuresh Chitale +Abner Chang If you have contributed and are not listed, do let us know. We haven't forgotten you, but we may have forgotten to edit this list. -- 2.19.0.windows.1 |
|
|
|
[RESEND PATCH v6 1/2] riscv-platform-spec: PLIC and CLINT for Linux-2022 platform
From: Abner Chang <abner.chang@...>
Initial description of PLIC CLINT section of Linux-2022 platform. On v6 commit, Remove the changes in Embedded-2022 section. On v5 commit, - Remove CLINT from platform spec - Require ACLINT on Linux2020 platform and have a link to https://github.com/riscv/riscv-aclint/blob/master/riscv-aclint.adoc. - Remove Machine mode timer from previous patch because that is in the scope of ACLINT - For Embedded-2022 platform, mention Machine mode timer and refer to ACLINT for the definition of registers On v4 commit, - PLIC section with [DEPRECATED] in Linux- 2022 chapter - CLINT section in Linux- 2022 chapter for M-mode timer. We don't mention IPI because AIA already supported it. - In Embedded-2022 Machine mode timer section, CLINT is not mandatory. - Separate section in appendix for the Machine mode timer registers On v3 commit, - Address review comments. On v2 commit, - CLINT is not deprecated. - Add a standalone section for Machine Mode Timer in System Peripherals. Do you think this is a good place for Machine Mode Timer? @Mayuresh, please check if you are ok with this change, not sure if this overlaps with your text or not (The timer setion). I can remove this if you prefer to put this with your patch. - In Embedded-2022, refer to Machine Mode Timer in System Peripherals section and CLINT in Linux-2022 Platform. @Alistair, is this ok? On v1 commit, - Not sure where to put the [DEPRECATED]. - Change the reference of PLIC in section 2.2.2. Interrupt Controller to 1.1.3.2 PLIC + CLINT section. Signed-off-by: Abner Chang <renba.chang@...> Cc: Alistair Francis <alistair.francis@...> Cc: Sunil V L <sunilvl@...> Cc: Mayuresh Chitale <mchitale@...> --- riscv-platform-spec.adoc | 25 ++++++++++++++++++++----- 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/riscv-platform-spec.adoc b/riscv-platform-spec.adoc index 4418788..d2925ac 100644 --- a/riscv-platform-spec.adoc +++ b/riscv-platform-spec.adoc @@ -79,9 +79,24 @@ include::profiles.adoc[] * Start Address ==== Interrupt Controller -* AIA -* PLIC + CLINT -* Interrupt Assignments +===== AIA[[AIA]] +===== PLIC[DEPRECATED][[PLIC]] +The Platform Level Interrupt Controller (PLIC) provides facilities to route +the non-local interrupts to the external interrupt of a hart context +with a given privilege mode in a given hart. The number of non-local interrupt +sources supported by PLIC and how does each of them connect to the hart +context is PLIC core implementation-specific. + +(Refer to https://github.com/riscv/riscv-plic-spec/blob/master/riscv-plic.adoc[RISC-V PLIC Specification] +for the implementation reference of PLIC operation parameters) + +===== ACLINT +Linux-2020 platform requires the Advanced Core Local Interruptor (ACLINT, +refer to +https://github.com/riscv/riscv-aclint/blob/master/riscv-aclint.adoc[RISC-V ACLINT Specification]) +to provide facilities to route inter-processor interrupt and Machine mode timer +interrupt to each RISC-V processor hart. + +===== Interrupt Assignments ==== System Peripherals * UART/Serial Console @@ -406,8 +421,8 @@ Any RISC-V system that uses at least RV32/64G can meet the Embedded-2022 specification. ==== Interrupt Controller -Embedded systems are recommended to use a spec compliant -https://github.com/riscv/riscv-plic-spec[PLIC], a spec compliant +Embedded systems are recommended to use a spec compliant <<PLIC,PLIC>>, +a spec compliant https://github.com/riscv/riscv-fast-interrupt/blob/master/clic.adoc[CLIC] or both a CLIC and and PLIC. -- 2.19.0.windows.1 |
|
|
|
[PATCH v6 2/2] contributors: Add Abner as contributor
From: Abner Chang <renba.chang@...>
Signed-off-by: Abner Chang <renba.chang@...> --- contributors.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/contributors.adoc b/contributors.adoc index 3d19411..73b99c4 100644 --- a/contributors.adoc +++ b/contributors.adoc @@ -27,6 +27,7 @@ Andrew Waterman, Kumar Sankaran, Alistair Francis, Sunil V L. +Abner Chang If you have contributed and are not listed, do let us know. We haven't forgotten you, but we may have forgotten to edit this list. -- 2.19.0.windows.1 |
|
|
|
[PATCH v6 1/2] riscv-platform-spec: PLIC and CLINT for Linux-2022 platform
From: Abner Chang <renba.chang@...>
Initial description of PLIC CLINT section of Linux-2022 platform. On v6 commit, Remove the changes in Embedded-2022 section. On v5 commit, - Remove CLINT from platform spec - Require ACLINT on Linux2020 platform and have a link to https://github.com/riscv/riscv-aclint/blob/master/riscv-aclint.adoc. - Remove Machine mode timer from previous patch because that is in the scope of ACLINT - For Embedded-2022 platform, mention Machine mode timer and refer to ACLINT for the definition of registers On v4 commit, - PLIC section with [DEPRECATED] in Linux- 2022 chapter - CLINT section in Linux- 2022 chapter for M-mode timer. We don't mention IPI because AIA already supported it. - In Embedded-2022 Machine mode timer section, CLINT is not mandatory. - Separate section in appendix for the Machine mode timer registers On v3 commit, - Address review comments. On v2 commit, - CLINT is not deprecated. - Add a standalone section for Machine Mode Timer in System Peripherals. Do you think this is a good place for Machine Mode Timer? @Mayuresh, please check if you are ok with this change, not sure if this overlaps with your text or not (The timer setion). I can remove this if you prefer to put this with your patch. - In Embedded-2022, refer to Machine Mode Timer in System Peripherals section and CLINT in Linux-2022 Platform. @Alistair, is this ok? On v1 commit, - Not sure where to put the [DEPRECATED]. - Change the reference of PLIC in section 2.2.2. Interrupt Controller to 1.1.3.2 PLIC + CLINT section. Signed-off-by: Abner Chang <renba.chang@...> Cc: Alistair Francis <alistair.francis@...> Cc: Sunil V L <sunilvl@...> Cc: Mayuresh Chitale <mchitale@...> --- riscv-platform-spec.adoc | 25 ++++++++++++++++++++----- 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/riscv-platform-spec.adoc b/riscv-platform-spec.adoc index 160c74a..c0ee75d 100644 --- a/riscv-platform-spec.adoc +++ b/riscv-platform-spec.adoc @@ -49,9 +49,24 @@ include::profiles.adoc[] * Start Address ==== Interrupt Controller -* AIA -* PLIC + CLINT -* Interrupt Assignments +===== AIA[[AIA]] +===== PLIC[DEPRECATED][[PLIC]] +The Platform Level Interrupt Controller (PLIC) provides facilities to route +the non-local interrupts to the external interrupt of a hart context +with a given privilege mode in a given hart. The number of non-local interrupt +sources supported by PLIC and how does each of them connect to the hart +context is PLIC core implementation-specific. + +(Refer to https://github.com/riscv/riscv-plic-spec/blob/master/riscv-plic.adoc[RISC-V PLIC Specification] +for the implementation reference of PLIC operation parameters) + +===== ACLINT +Linux-2020 platform requires the Advanced Core Local Interruptor (ACLINT, +refer to +https://github.com/riscv/riscv-aclint/blob/master/riscv-aclint.adoc[RISC-V ACLINT Specification]) +to provide facilities to route inter-processor interrupt and Machine mode timer +interrupt to each RISC-V processor hart. + +===== Interrupt Assignments ==== System Peripherals * UART/Serial Console @@ -289,8 +304,8 @@ Any RISC-V system that uses at least RV32/64G can meet the Embedded-2022 specification. ==== Interrupt Controller -Embedded systems are recommended to use a spec compliant -https://github.com/riscv/riscv-plic-spec[PLIC], a spec compliant +Embedded systems are recommended to use a spec compliant <<PLIC,PLIC>>, +a spec compliant https://github.com/riscv/riscv-fast-interrupt/blob/master/clic.adoc[CLIC] or both a CLIC and and PLIC. -- 2.19.0.windows.1 |
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Josh Scheid
On Fri, May 28, 2021 at 4:01 PM Greg Favor <gfavor@...> wrote:
Right, I'm attempting to refer to the effective timer resolution as opposed to the apparent timer unit period. I'm just making explicit what this relaxation implies about capabilities in real systems. Platforms should separately consider whether or not to allow this relaxation based on a threshold for effective timer resolution which must be available on compliant implementations of that platform. -Josh |
|
|
|
[PATCH v1 2/2] Platform debug requirements
Paul Donahue
Signed-off-by: Paul Donahue pdonahue@...
--- riscv-platform-spec.adoc | 101 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+) diff --git a/riscv-platform-spec.adoc b/riscv-platform-spec.adoc index 98783c8..e5a1236 100644 --- a/riscv-platform-spec.adoc +++ b/riscv-platform-spec.adoc @@ -73,6 +73,93 @@ include::profiles.adoc[] ** ASID * Debug +==== Debug +The Linux base platform requirements are - + +- Implement resethaltreq + * Rationale: Debugging immediately out of reset is a useful debug tool and + is required by item 5 in chapter 3. The resethaltreq mechanism provides a + standard way to do this. +- Implement the program buffer + * Rationale: The program buffer is easier for most implementations than + abstract access. + * Rationale: Debuggers need to be able to insert ebreak instructions into + memory and make sure that the ebreak is visible to subsequent instruction + fetches. Abstract access has no support for fence.i (or similar + mechanisms). +- abstractcs.relaxedpriv must be 0 + * Rationale: Doing otherwise is a potential security problem. +- abstractauto must be implemented + * Rationale: autoexecprogbuf allows faster instruction-stuffing + * Rationale: autoexecdata allows fast read/write of a region of memory +- dcsr.mprven must be tied to 1 + * Rationale: Emulating two-stage table walks and PMP checks and endianness + swapping is a heavy burden on the debugger. +- In textra, sselect must support the value 0 and either value 1 or 2 (or +both). + * Rationale: There must be some way to limit triggers to only match in a + particular user context and a way to ignore user context. +- If textra.sselect=1 is supported, the number of implemented bits of svalue +must be at least the number of implemented bits of scontext. + * Rationale: This allows matching on every possible scontext. +- If textra.sselect=2 is supported, the number of implemented bits of svalue +must be at least ASIDLEN. + * Rationale: This allows matching on every possible ASID. +- In textra, mhselect must support the value 0. If the H extension is +supported then mhselect must also support either values 1 and 5 or values 2 +and 6 (or all four). + * Rationale: There must be some way to limit triggers to only match in a + particular guest context and a way to ignore guest context. +- If textra.mhselect=1,5 are supported and if H is the number of implemented +bits of hcontext then, unless all bits of mhvalue are implemented, at least +H-1 bits of mhvalue must be implemented. + * Rationale: This allows matching on every possible hcontext (up to the limit + of the field width). It is H-1 bits instead of H because mhselect[2] + provides one bit. +- If textra.mhselect=2,6 are supported, the number of implemented bits of +mhvalue must be at least VMIDLEN-1. + * Rationale: This allows matching on every possible VMID. It is VMIDLEN-1 + instead of VMIDLEN because mhselect[2] provides one bit. +- Implement at least four mcontrol6 triggers that can support matching on PC +(select=0, execute=1, match=0) with timing=0 and full support for mode +filtering (vs, vu, m, s, u) for all supported modes and support for textra as +above. + * Rationale: The debugger needs breakpoints and 4 is a sufficient baseline. +- Implement at least four mcontrol6 triggers that can support matching on load + and store addresses (select=0, match=0, and all combinations of load/store) + with timing=0 and full support for mode filtering (vs, vu, m, s, u) for all + supported modes and support for textra as above. + * Rationale: The debugger needs watchpoints and 4 is a sufficient baseline. +- Implement at least one trigger capable of icount and support for textra as +above. + * Rationale: Self-hosted single step needs this +- Implement at least one trigger capable of etrigger and support for textra as +above. + * Rationale: Debuggers need to be able to catch exceptions. +- Implement at least one trigger capable of itrigger and support for textra as +above. + * Rationale: Debuggers need to be able to catch interrupts. +- The minimum trigger requirements must be met for action=0 and for action=1 +(possibly by the same triggers) + * Rationale: The intent is to have full support for external debug and full + support for self-hosted debug (though not necessarily at the same time). + This can be provided via the same set of triggers or separate sets of + triggers. External debug support for icount is unnecessary due to dcsr.step + and is therefore called out separately. +- For implementations with multiple cores, support for at least one halt group +and one resume group (in addition to group 0) + * Rationale: Allows stopping all harts (approximately) simultaneously which + is useful for debugging MP software +- dcsr.stepie must support the 0 setting. It is optional to support the 1 +setting. + * Rationale: It is not generally useful to step into interrupt handlers. +- dcsr.stopcount and dcsr.stoptime must be supported and the reset value of +each must be 1 + * Rationale: The architecture has strict requirements on minstret which may + be perturbed by an external debugger in a way that's visible to software. + The default should allow code that's sensitive to these requirements to be + debugged. + ==== Memory Map * Virtual Memory * sv39/sv48/sv57 @@ -166,6 +253,20 @@ Spec should be ratified*] file for each HART ?? (*TBD*) - IOMMU with support for memory resident interrupt files ?? (*TBD*) +==== Debug +The Linux server platform requirements are all of the above plus: + +- Implement at least six mcontrol6 triggers that can support matching on PC +(select=0, execute=1, match=0) with timing=0 and full support for mode +filtering (vs, vu, m, s, u) for all supported modes and support for textra as +above. + * Rationale: Other architectures have found that 4 breakpoints are + insufficient in more capable systems and recommend 6. +- If system bus access is implemented then accesses must be coherent with +respect to all harts connected to the DM + * Rationale: Debuggers must be able to view memory coherently + + ==== Boot and Runtime Requirements ===== Firmware The boot and system firmware for the RV64I server platforms required to be -- 2.25.1 |
|
|
|
[PATCH v1 1/2] Updating changelog
Paul Donahue
Updating changelog
Signed-off-by: Paul Donahue pdonahue@... --- changelog.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/changelog.adoc b/changelog.adoc index 7ec1b1f..cc69971 100644 --- a/changelog.adoc +++ b/changelog.adoc @@ -8,6 +8,8 @@ ## Change Log ### version 0.2-rc0 +* 2021-05-20: +** Platform requirements for Debug * 2021-05-19: ** Base boot and runtime requirements - Initial commit * 2021-04-08: --=20 2.25.1 |
|
|
|
[PATCH v1 0/2] Updating contributors
Paul Donahue
Adding myself to list of contributors.
Signed-off-by: Paul Donahue pdonahue@... --- contributors.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contributors.adoc b/contributors.adoc index 08b16f0..13dcf59 100644 --- a/contributors.adoc +++ b/contributors.adoc @@ -27,7 +27,8 @@ Andrew Waterman, Kumar Sankaran, Alistair Francis, Sunil V L, -Rahul Pathak +Rahul Pathak, +Paul Donahue If you have contributed and are not listed, do let us know. We haven't forgotten you, but we may have forgotten to edit this list. -- 2.25.1 |
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Josh Scheid
On Fri, May 28, 2021 at 4:07 PM Jonathan Behrens <behrensj@...> wrote:
At least at the platform level, the requirement of a single reference clock for all timers in a "system" (thus preventing first-order drift) may be a desirable requirement. -Josh |
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Jonathan Behrens <behrensj@...>
If you're interested in reading about pure software approaches to clock synchronization, I recommend looking at https://www.usenix.org/conference/nsdi18/presentation/geng. They focus on synchronizing clocks between different servers in the same datacenter which if anything is a harder problem. The main issue I see with the mtime synchronization code sample in the linked spec is that it doesn't do anything to address clock drift. The linked paper claims that CPU clocks can drift by 10 microseconds/second or more, so unless you have dedicated hardware to prevent drift (in which case why are you bothering with software at all?) you are very rapidly going to observe time readings that differ by more than one tick even if they start out consistent. Jonathan On Fri, May 28, 2021 at 5:44 PM Josh Scheid via lists.riscv.org <jscheid=ventanamicro.com@...> wrote:
|
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Greg Favor
On Fri, May 28, 2021 at 2:44 PM Josh Scheid <jscheid@...> wrote:
More recent ARM SBSA requires a 1 GHz counter resolution, but does not place any requirement on the actual measurable 'time" resolution (i.e. a minimum update frequency). So one can have 1 ns resolution in the 'time' counter value, but the actual measurable granularity could be just 1 us. Upping the standard counter resolution seems of little or secondary value. It's the actual maximum granularity or resolution of measurable time that matters. Which no one in RISC-V (or ARM SBSA) seems willing or wanting to require actual 1 ns resolution to time measurements. Greg |
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Josh Scheid
One other issue with the "mtime" synchronization by SW approach is that this effectively places an upper limit on the achievable timer unit resolution. It'd be some equation based on the ordered access latency of the reference and target resources, perhaps. Has this been explicitly considered? What is the expected upper limit and where should the platform be moving towards in the future? Would further work be needed to enable >=1GHz timer resolution? -Josh |
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Josh Scheid
On Thu, May 27, 2021 at 8:05 PM Greg Favor <gfavor@...> wrote:
Note that the "update latency" between a write to "mtime" and a read of the hart-local "time" is unspecified. -Josh |
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Greg Favor
On Thu, May 27, 2021 at 10:34 AM Neel Gala <neelgala@...> wrote:
Architecturally the 'time' CSR reads the same concept of "time" as the 'mtime' register. Simplistically the RDTIME pseudoinstruction reads what is in the 'mtime' register. One implementation is that each hart has a local copy of 'mtime' that is available to be read by RDTIME (in other words, copies of 'mtime' are distributed in hardware to each hart - to appear as the 'time' CSR inside each hart). Another implementation is to trap and emulate RDTIME using a read of the memory-mapped 'mtime' register. Other implementation approaches are possible. Greg
|
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Hi, Minor comments: Should there be a mention that the user level "time" csr (0xC01) which is used by the rdtime pseudo-instruction will enable a read-only peek into the mtime register? Would this require change in Table-1 privilege mode accesses? as well? Should there also be a suggestion/recommendation on how to disable a pending interrupt (typically by writing to mtimecmp)? On Thu, May 27, 2021 at 10:45 AM Anup Patel <anup.patel@...> wrote:
--
Neel Gala |
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Hi Josh,
I have created a GitHub PR addressing your comments. Please check if you are okay with this. https://github.com/riscv/riscv-aclint/pull/2
Regards, Anup
From: tech-aia@... <tech-aia@...>
On Behalf Of Josh Scheid
Sent: 27 May 2021 01:58 To: Anup Patel <Anup.Patel@...> Cc: tech-aia@...; tech-unixplatformspec@...; Atish Patra <Atish.Patra@...>; Greg Favor <gfavor@...>; Alistair Francis <Alistair.Francis@...>; Andrew Waterman <andrew@...>; John Hauser <jh.riscv@...> Subject: Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Thanks for writing this up, Anup.
In https://github.com/riscv/riscv-aclint/blob/master/riscv-aclint.adoc#24-synchronizing-multiple-mtimer-devices, the SW algorithm should include verifying the reference-target delta, retrying if the delta is out of bounds, and / or reporting failure to verify the synchronization is in bounds.
-Josh
On Tue, May 25, 2021 at 10:18 PM Anup Patel <anup.patel@...> wrote:
|
|
|
|
Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Hi Josh,
Indeed, I missed adding text regarding verifying delta and ensuring that it is within bounds. Thanks for pointing.
I was thinking that aclint_mtime_sync() function should return the adjustment value (delta) so that high-level caller can try acling_mtime_sync() few times until the returned adjustment (delta) becomes zero (or close to it).
Regards, Anup
From: tech-aia@... <tech-aia@...>
On Behalf Of Josh Scheid
Sent: 27 May 2021 01:58 To: Anup Patel <Anup.Patel@...> Cc: tech-aia@...; tech-unixplatformspec@...; Atish Patra <Atish.Patra@...>; Greg Favor <gfavor@...>; Alistair Francis <Alistair.Francis@...>; Andrew Waterman <andrew@...>; John Hauser <jh.riscv@...> Subject: Re: [tech-aia] RISC-V ACLINT specification is now hosted on RISC-V GitHub
Thanks for writing this up, Anup.
In https://github.com/riscv/riscv-aclint/blob/master/riscv-aclint.adoc#24-synchronizing-multiple-mtimer-devices, the SW algorithm should include verifying the reference-target delta, retrying if the delta is out of bounds, and / or reporting failure to verify the synchronization is in bounds.
-Josh
On Tue, May 25, 2021 at 10:18 PM Anup Patel <anup.patel@...> wrote:
|
|
|
|
Re: [RESEND PATCH v5 1/2] riscv-platform-spec: PLIC and CLINT for Linux-2022 platform
Alistair Francis <Alistair.Francis@...> 於 2021年5月26日 週三 下午6:57寫道： On Wed, 2021-05-26 at 10:40 +0000, Anup Patel wrote: Alistair, I can understand your concern just like I have to the server extension. The inflexible spec may lead vendor/OEM hard to follow. Because the Machine mode timer I added in Linux2022 platform and System Peripherals section is removed from the patch, I will just leave the one in Embedded 2022 section untouched for further discussion. Seems ACLINT is not designed to give the flexible offsets to mtime and mtimecmp to afford the adjacent register layout unless we introduce a new capability to MTIME device in ACLINT. We probably can work on making MTIME device register layout more flexible in ACLINT spec, I don't have the preference here...and I remember we would like to separate MTIME from CLINT spec, but now it goes into another spec :) Regards, Abner
|
|
|