From: "Kevin D. Kissell" <kevink@mips.com>
To: "Florian Lohoff" <flo@rfc822.org>, <debian-mips@lists.debian.org>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: first packages for mipsel
Date: Fri, 6 Apr 2001 13:43:24 +0200 [thread overview]
Message-ID: <00a401c0be8e$cfc065a0$0deca8c0@Ulysses> (raw)
In-Reply-To: 20010406132214.D14083@paradigm.rfc822.org
> On Fri, Apr 06, 2001 at 01:09:58PM +0200, Florian Lohoff wrote:
> There are multiple solutions to this problem:
>
> - ll/sc emulation in the kernel
> Implementing an ll/sc emulation into the fast path of the illegal
instruction
> handler and compile the glibc with ll/sc support.
>
> - repair sysmips
> Sysmips is essentially broken - My fix i have sent to the linux-mips
list
> is only a workaround but not a fix. Also there is currentl NO ISA I
support
> in the sysmips implementation. I hope to get around to build a proper
> fix this weekend in assembly.
>
> Probably we will do both - An even better solution would be to let the
glibc
> detect the ISA level or the existance of ll/sc in userspace and replace
_test_and_set
> with one or the other primitiv - Using sysmips on R3000 or ll/sc less
systems.
What advantage would there be to using sysmips() as opposed
to doing the ll/sc emulation? It seems to me that the decode path
in the kernel would be just as fast, and there would be a single
"ABI" for all programs - the ll/sc instructions themselves.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Florian Lohoff <flo@rfc822.org>, debian-mips@lists.debian.org
Cc: linux-mips@oss.sgi.com
Subject: Re: first packages for mipsel
Date: Fri, 6 Apr 2001 13:43:24 +0200 [thread overview]
Message-ID: <00a401c0be8e$cfc065a0$0deca8c0@Ulysses> (raw)
Message-ID: <20010406114324.uD2F1x3Vbe-FC1w9tGvUy4LPH1qmvFJrZsn3kt3phbE@z> (raw)
In-Reply-To: 20010406132214.D14083@paradigm.rfc822.org
> On Fri, Apr 06, 2001 at 01:09:58PM +0200, Florian Lohoff wrote:
> There are multiple solutions to this problem:
>
> - ll/sc emulation in the kernel
> Implementing an ll/sc emulation into the fast path of the illegal
instruction
> handler and compile the glibc with ll/sc support.
>
> - repair sysmips
> Sysmips is essentially broken - My fix i have sent to the linux-mips
list
> is only a workaround but not a fix. Also there is currentl NO ISA I
support
> in the sysmips implementation. I hope to get around to build a proper
> fix this weekend in assembly.
>
> Probably we will do both - An even better solution would be to let the
glibc
> detect the ISA level or the existance of ll/sc in userspace and replace
_test_and_set
> with one or the other primitiv - Using sysmips on R3000 or ll/sc less
systems.
What advantage would there be to using sysmips() as opposed
to doing the ll/sc emulation? It seems to me that the decode path
in the kernel would be just as fast, and there would be a single
"ABI" for all programs - the ll/sc instructions themselves.
Kevin K.
next prev parent reply other threads:[~2001-04-06 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010406130958.A14083@paradigm.rfc822.org>
2001-04-06 11:22 ` first packages for mipsel Florian Lohoff
2001-04-06 11:43 ` Kevin D. Kissell [this message]
2001-04-06 11:43 ` Kevin D. Kissell
2001-04-06 11:58 ` Florian Lohoff
2001-04-06 12:23 ` Kevin D. Kissell
2001-04-06 12:23 ` Kevin D. Kissell
2001-04-06 13:28 ` Florian Lohoff
2001-04-06 15:33 ` Kevin D. Kissell
2001-04-06 15:33 ` Kevin D. Kissell
2001-04-06 16:48 ` Maciej W. Rozycki
2001-04-06 16:40 ` Maciej W. Rozycki
2001-04-07 9:05 ` Kevin D. Kissell
2001-04-07 9:05 ` Kevin D. Kissell
2001-04-07 10:55 ` Maciej W. Rozycki
2001-04-07 15:29 ` Florian Lohoff
2001-04-09 9:48 ` Maciej W. Rozycki
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='00a401c0be8e$cfc065a0$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=debian-mips@lists.debian.org \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.