mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Stafford Horne <shorne@gmail.com>, Barebox <barebox@lists.infradead.org>
Cc: Openrisc <openrisc@lists.librecores.org>
Subject: Re: [PATCH 0/4] OpenRISC fixes and setjmp/longjmp work
Date: Wed, 3 Mar 2021 15:03:11 +0100	[thread overview]
Message-ID: <57222afc-9d92-e52d-34d4-0737eff1ec82@pengutronix.de> (raw)
In-Reply-To: <20210303135026.3450789-1-shorne@gmail.com>

Hello Stafford,

On 03.03.21 14:50, Stafford Horne wrote:
> Hello,
> 
> These are the patches I came up with to get the setjmp/longjmp routines to work
> on OpenRISC.  It seems to be working well.
> 
> The patches are on github here:
>   https://github.com/stffrdhrn/barebox/tree/openrisc-bthread
> 
> I had to revert a commit to remove openrisc to do this work, I hope that can be
> reverted.

Great. Thanks for taking the time!
Could this be tested on qemu-system-or1k? If so, it would be great to have this
documented in-tree, so future changes could be tested.

Cheers,
Ahmad

> 
> Test output:
> 
>     barebox@or1ksim:/ bthread -v
>     bthread_printer yield #1
>     bthread_printer yield #2
>     bthread_printer yield #3
>     bthread_printer yield #4
>     36441 bthread yield calls in 1s
>     barebox@or1ksim:/ bthread -v
>     bthread_printer yield #1
>     bthread_printer yield #2
>     bthread_printer yield #3
>     bthread_printer yield #4
>     36504 bthread yield calls in 1s
>     barebox@or1ksim:/ bthread
> 
>     bthread - print info about registered bthreads
> 
>     print info about registered barebox threads
> 
>     Options:
> 	    -i      Print information about registered bthreads
> 	    -t      measure how many bthreads we currently run in 1s
> 	    -c      count maximum context switches in 1s
> 	    -v      verify correct bthread operation
> 
>     barebox@or1ksim:/ bthread -c
>     bthread -c
>     269536 bthread context switches possible in 1s
> 
> Stafford Horne (4):
>   openrisc: Use movhi to zero registers
>   openrisc: Add gitignore for dtb files
>   openrisc: Add linkage.h
>   openrisc: Implement setjmp/longjmp/initjmp
> 
>  arch/openrisc/Kconfig               |  1 +
>  arch/openrisc/cpu/start.S           |  6 ++--
>  arch/openrisc/dts/.gitignore        |  1 +
>  arch/openrisc/include/asm/linkage.h |  7 ++++
>  arch/openrisc/include/asm/setjmp.h  | 17 +++++++++
>  arch/openrisc/lib/Makefile          |  1 +
>  arch/openrisc/lib/setjmp.S          | 56 +++++++++++++++++++++++++++++
>  7 files changed, 86 insertions(+), 3 deletions(-)
>  create mode 100644 arch/openrisc/dts/.gitignore
>  create mode 100644 arch/openrisc/include/asm/linkage.h
>  create mode 100644 arch/openrisc/include/asm/setjmp.h
>  create mode 100644 arch/openrisc/lib/setjmp.S
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  parent reply	other threads:[~2021-03-03 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 13:50 Stafford Horne
2021-03-03 13:50 ` [PATCH 1/4] openrisc: Use movhi to zero registers Stafford Horne
2021-03-03 13:50 ` [PATCH 2/4] openrisc: Add gitignore for dtb files Stafford Horne
2021-03-03 13:50 ` [PATCH 3/4] openrisc: Add linkage.h Stafford Horne
2021-03-03 13:50 ` [PATCH 4/4] openrisc: Implement setjmp/longjmp/initjmp Stafford Horne
2021-03-03 14:03 ` Ahmad Fatoum [this message]
2021-03-03 14:12   ` [PATCH 0/4] OpenRISC fixes and setjmp/longjmp work Stafford Horne
2021-03-03 20:25     ` Stafford Horne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57222afc-9d92-e52d-34d4-0737eff1ec82@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=openrisc@lists.librecores.org \
    --cc=shorne@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox