Interrupt handling for RISCV

Denis Obrezkov denisobrezkov at gmail.com
Sun Jun 11 20:01:30 UTC 2017


2017-06-11 22:43 GMT+03:00 Hesham Almatary <heshamelmatary at gmail.com>:

> Hi Denis,
>
>
>
> On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov
> <denisobrezkov at gmail.com> wrote:
> > Hello Hesham,
> >
> > I found out that your code in interrupt handling routine is outdated -
> Which interrupt handling routine? The port doesn't handle interrupts.
> The only relevant code is enable/disable interrupts, but it doesn't
> matter at this stage that it's outdated (as we don't have interrupts).
>
> > the format of mstatus and sstatus registers was changed.
> > I can produce some patches in a few days, though, I still don't
> understand
> > how to deal with local and global interrupts.
> >
> Could you illustrate what do you mean by "global" and "local"
> interrupts? I still argue for a simple port that runs hello world, you
> don't need interrupts, so this shouldn't be a blocker for you.
>
> > --
> > Regards, Denis Obrezkov
>
>
>
> --
> Hesham
>
RISC-V has local and global interrupt sources: Privileged ISA 1.10, chapter
7.2.



-- 
Regards, Denis Obrezkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170611/a37d5342/attachment-0002.html>


More information about the devel mailing list