public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Organov <osv@Javad.RU>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Re: Ecos Port to PPC509/PPC555
Date: Fri, 24 Sep 1999 10:34:00 -0000	[thread overview]
Message-ID: <87emfousa6.fsf@osv.javad.ru> (raw)
In-Reply-To: <37EB9DEA.5AD6EC35@cygnus.co.uk>

I agree with every word in your reply. And I understand that eCos is
open source. I just wanted to make sure that if I begin work on FP
support, I will not do it in parallel with somebody else either inside
or outside Cygnus. Now when I've got exact answer, I'm going to
write down my thoughts how it could be implemented and post them here
for discussion. Hope I'll have time to do it next week.

Regards,
Sergei.

Jonathan Larmour <jlarmour@cygnus.co.uk> writes:
> Sergei Organov wrote:
> > 
> > I don't want
> > to have FP overhead for every task in my system. Actually only few
> > tasks should have floating point context, and the rest of tasks never
> > use floating point. Therefore it is required to somehow specify if
> > given task has FP context or not. This requires change(s) to the
> > kernel API. Optimizing further, if only some tasks have FP context,
> > then FP context switch is actually required only when control is given
> > to FP task. Such lazy FP context switch requires some support from
> > kernel and apparently some changes in HAL interface.
> 
> Yep. This is a sensible optimization, but yes it would require HAL changes.
> The clever thing is implementing an interface that won't affect other HALs -
> some MCUs will never have hard floating-point so we shouldn't be
> complicating their implementations unnecessarily.
> 
> It also has to be configurable because some interrupt/exception handlers may
> want to use FP of course.
> 
> > Overall, I'd prefer to have full FP support in eCos to be able to use
> > all possible tricks to get maximum performance from hardware. That's
> > why I asked about FP support in eCos - I meant general support, and
> > not FP context save/restore implementation for some particular
> > architecture. Sure, I can do all this myself, but then another
> > implementation will come from Cygnus. So the question remains.
> 
> Not if you contribute it back! If you want to propose something more
> concrete on this list, everyone can discuss it. Cygnus aren't working on it,
> but we will do what we can to help you do it. If you submit acceptable
> patches to the list, we will certainly incorporate it in future releases.
> eCos really is open source :-).
> 
> Jifl
> -- 
> Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
> "I used to have an open mind but || Get yer free open source RTOS's here...
>  my brains kept falling out."    || http://sourceware.cygnus.com/ecos
> Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

  reply	other threads:[~1999-09-24 10:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-21 12:32 [ECOS] " Ramana
1999-09-22  2:01 ` Sergei Organov
1999-09-23  8:16 ` [ECOS] " Bart Veer
1999-09-24  4:39   ` Sergei Organov
1999-09-24  8:52     ` Jonathan Larmour
1999-09-24 10:34       ` Sergei Organov [this message]
1999-09-27 11:54     ` Bart Veer
1999-09-27 17:36       ` Jonathan Larmour
1999-09-28  4:23         ` Sergei Organov
1999-09-28  7:42           ` Jonathan Larmour
1999-09-28  8:00         ` Bart Veer
1999-09-28  8:02           ` Jonathan Larmour
1999-09-28  4:19       ` Sergei Organov
1999-09-28  8:08         ` Jonathan Larmour
1999-09-28 11:03         ` Bart Veer

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=87emfousa6.fsf@osv.javad.ru \
    --to=osv@javad.ru \
    --cc=ecos-discuss@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).