From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andre Bonin <kernel@bonin.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCI coprocessors
Date: Wed, 15 Sep 2004 13:30:04 +0100 [thread overview]
Message-ID: <1095251402.19893.31.camel@localhost.localdomain> (raw)
In-Reply-To: <41483BD3.4030405@bonin.ca>
On Mer, 2004-09-15 at 13:55, Andre Bonin wrote:
> 1) Is their support for having two different 'machine types' within one
> kernel? that is for example, certain executables for intel would get run
> on an intel processor, and others would get run on processor with type XXXX.
The kernel provides everything you need to run userspace apps on the
co-processor - which is very little indeed. It provides binfmt_misc
which allows other binary types to be revectored to user applications.
That is how the example you remember worked.
Your application gets the program to run, you run it, you throw it at
the coprocessor and you need to take any traps back for syscalls (which
might need a little driver kernel side if it involves interrupts).
There are then the hard bits (mmap, ptrace, scheduling...) 8)
> 2) Is their kernel support for PCI coprocessors for thread allocation
> etc. I couldn't find any but i can try looking through the code again.
We don't deal at all with the question of scheduling stuff on different
processor types.
Alan
next prev parent reply other threads:[~2004-09-15 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 12:55 Andre Bonin
2004-09-15 12:30 ` Alan Cox [this message]
2004-09-15 13:44 ` Matti Aarnio
2004-09-15 13:45 ` Richard B. Johnson
2004-09-15 14:55 ` Tomasz Rola
2004-09-15 15:15 ` Andre Bonin
2004-09-15 16:49 ` Tonnerre
2004-09-16 0:12 ` Tomasz Rola
2004-09-15 16:01 ` Jeff Garzik
2004-09-15 22:39 ` Tonnerre
2004-09-17 10:16 ` Andre Tomt
2004-09-17 16:19 ` Tony Lee
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=1095251402.19893.31.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=kernel@bonin.ca \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome