public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Michael Zimmermann <sigmaepsilon92@gmail.com>
To: Blibbet <blibbet@gmail.com>
Cc: "Jayaprakash, N" <n.jayaprakash@intel.com>,
	 "Richardson, Brian" <brian.richardson@intel.com>,
	Thiebaud Weksteen <tweek@google.com>,
	 "python-dev@python.org" <python-dev@python.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Official port of Python on EDK2
Date: Fri, 3 Nov 2017 08:01:51 +0100	[thread overview]
Message-ID: <CAN9vWDJRY9KXA8A8F--ONuB2TkuSTKgFXqY74fAxbxqWpn5q1Q@mail.gmail.com> (raw)
In-Reply-To: <b3891d56-8909-94b9-d33b-42a2b43b1485@gmail.com>

> FYI, this library adds thread support to UEFI:
>
> https://github.com/Openwide-Ingenierie/GreenThreads-UEFI

IMO this library has some crucial problems like changing the TPL
during context switching.
For my project "EFIDroid" I've invested many months analyzing, testing
and implementing my own threading implementation based on
LK(LittleKernel, a MIT licensed project) threads and get/set -context.

The result is a pretty stable implementation which can even be used in
UEFI drivers:
https://github.com/efidroid/uefi_edk2packages_EFIDroidLKLPkg/tree/master/UEFIThreads
I'm currently using this lib for my LKL(LinuxKernelLibrary) port to be
able to use linux touchscreen drivers in UEFI - so you could say it
has been well tested.

The only "problem" is that it only supports ARM right now and that the
get/set context implementation was copied (and simplified) from glibc
which means that this part is GPL code.

Thanks
Michael Zimmermann

On Thu, Nov 2, 2017 at 8:37 PM, Blibbet <blibbet@gmail.com> wrote:
> On 11/02/2017 09:41 AM, Jayaprakash, N wrote:
>> Would you consider adding thread support in this port of Python for
> EDK2 shell?
>
> FYI, this library adds thread support to UEFI:
>
> https://github.com/Openwide-Ingenierie/GreenThreads-UEFI
>
> Note that the library is GPLv2, ...but the author (a 1-person project)
> could be asked to relicense to BSD to fit into Tianocore.
>
> Note that library is currently Intel x64-centric, and contains a bit of
> assembly. Will need some ARM/RISC-V/x86 contributions.
>
> HTH,
> Lee Fisher
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2017-11-03  6:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  9:07 Official port of Python on EDK2 Thiebaud Weksteen
     [not found] ` <ed4b2738-1685-0df0-0889-c11db2f5fb08@python.org>
2017-11-01 12:54   ` Antoine Pitrou
2017-11-02  1:36 ` Richardson, Brian
2017-11-02 10:52   ` Thiebaud Weksteen
2017-11-02 16:41   ` Jayaprakash, N
2017-11-02 19:37     ` Blibbet
2017-11-03  7:01       ` Michael Zimmermann [this message]

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-list 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=CAN9vWDJRY9KXA8A8F--ONuB2TkuSTKgFXqY74fAxbxqWpn5q1Q@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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