Carsten Otte wrote:
McKown, John wrote:
This is likely a foolish question, but could the /sys/devices/diagnose
be set up like the /dev/fd ? E.g. for pid 12345, there exists an entire
tree /sys/devices/diagnose/12345. Then have "self" as a symlink to the
current pid so that for any particular pid, it could reference
/sys/devices/diagnose/self/... It might even be possible to "interlock"
on /sys/devices/diagnose/self/8/command so that you could not cat to it
a second time until you had read /sys/devices/diagnose/self/8/status or
maybe even 'echo "1">/sys/devices/diagnose/self/8/active' where that
pseudo-file gets changed to "0" when ../command is written to you cannot
again write a line to ../command until you write a "1" to ../active (or
something to that effect). Hope this makes sense. I'm not a kernel type
person.
Sounds terrible & complicated to me. What's wrong with the existing
soloution with vmcp? It's safe against races _because_ it splits the whole
thing into a userspace program that keeps an open file handle and a kernel
component that can identify subsequent calls by that handle.
I don't really get where the problem with that one is, could you elaborate
where you see the issue?
_I_ think devices are ultimately for processing user data and preparing
to process user data. So, partitioning & formatting disk, tape handling,
communicating with users and other processes are in order (I've always
wondered about network devices!).
Where you are manipulating the environment, by turning fans on or off,
by starting or stopping CPUs, by sending commands to the host OS, or by
loading firmware into wireless and other cards and peripherals then
something else should be done. In the past, the right thing has been to
manipulate files in procfs.
Whatever is done, it should be consistent with other virtual
environments such as XEN and VMWARE.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
