From: Sergei Organov <osv@javad.ru>
To: Nick Garnett <nickg@cygnus.co.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] On demand FP context switch major problem.
Date: Fri, 02 Jun 2000 06:47:00 -0000 [thread overview]
Message-ID: <87hfbckxef.fsf@osv.javad.ru> (raw)
In-Reply-To: <posnuw2rpf.fsf@balti.cygnus.co.uk>
Nick Garnett <nickg@cygnus.co.uk> writes:
> Sergei Organov <osv@javad.ru> writes:
[...]
> >
> > Possibility to configure eCos to use simple variant of FP context switch still
> > remains. If application requires FPU even in ISRs/DSRs/alarm handlers, then
> > it's likely that most of tasks require FPU as well, so there is no reason to
> > use on-demand context switch implementation that has some overhead anyway.
>
> I suspect that this is the best approach to this problem. At least for
> the present, or until someone works out how to do it properly. I would
> much rather not provide a facility than supply a badly thought-out or
> poorly implemented version.
Exactly. So I'll focus on implementing on-demand without capability to use FP
in ISRs/DSRs, and leave capability to use FP in ISRs/DSRs only when simple FP
context switch policy is configured.
>
> --
> Nick Garnett
> Cygnus Solutions, a Red Hat Company
> Cambridge, UK
BR,
Sergei.
next prev parent reply other threads:[~2000-06-02 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-18 5:27 Sergei Organov
2000-05-18 6:30 ` Nick Garnett
2000-05-19 1:16 ` Sergei Organov
2000-05-19 3:37 ` [ECOS] eCos synthetic target on Sun/Sparc ? Arvind
2000-05-19 4:12 ` Bart Veer
2000-05-31 6:44 ` [ECOS] On demand FP context switch major problem Sergei Organov
2000-05-31 7:24 ` Nick Garnett
2000-06-01 2:36 ` Sergei Organov
2000-06-01 4:23 ` Nick Garnett
2000-06-02 4:51 ` Sergei Organov
2000-06-02 5:27 ` Nick Garnett
2000-06-02 6:47 ` Sergei Organov [this message]
2001-09-05 0:10 ` Nick Garnett
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=87hfbckxef.fsf@osv.javad.ru \
--to=osv@javad.ru \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=nickg@cygnus.co.uk \
/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).