Martin Schwidefsky wrote:
On Thu, 2005-10-13 at 08:58 -0700, Fargusson.Alan wrote:
But it isn't a device is it? It isn't a filesystem either.
It looks like sysfs is the best fit even if it isn't really the right
place for it. Actually a architecture specific system call might be the
right thing to do, but I suspect it would be hard to get it implemented.
It's not a device, it's not a filesystem, it is a service that lets you
call a hypervisor function (z/VM AND LPAR by the way). Dependent on the
diagnose code it has to do memory copies. That screams for a system call
and they are not harder to implement then e.g. an ioctl. Doing the
diagnose via a system call would have the benefit that you don't have to
open some device first. Even better you don't need any special device
node, /proc or /sys entry at all. So if we decide that we want such a
It's very like controlling the fan on my laptop, or CPU frequencies, or
loading firmware, and those functions are implemented in procfs/sysfs,
and are accessible from the shell.
beast then we can as well implement it as a system call.
--
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
