Re: [PATCH] Expose some h/w info from ILOM to userspace via sysfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Eric Saint Etienne <eric.saint.etienne@xxxxxxxxxx>
Date: Tue, 19 Sep 2017 20:09:57 +0100

> Can you please have a look to the ilom patch
> (arch/sparc/kernel/ilom.c) then please? If you can't find it then
> let me know and I'll resend it.

Ok, I guess that is alright.  But it needs a bunch of changes.

Don't use uint_8_t etc. in the kernel, use u8 et al. instead.

Do not use the __packed attribute unless absolutely necessary
which seems entirely not the case for sunoem_cli_msg.

Please remove the ILOM_PROFILING, you can achieve the same effect
with tracepoints and perf.

Looking at the driver from a high level, it just seems to export
a seemingly arbitrary set of ILOM properties.  Why not provide
a real hierarchy of all the /SYS, /HOST, etc. stuff via /sysfs?

The string parsing and matching in there is exactly the kind of
code I'm talking about which doesn't belong in the kernel.

The kernel should export a family of values for whatever (bus,
firmware settings, etc.) transparently to the user and let them
do whatever they want with whichever values they find interesting.

It is not the kernel's business to filter, not interpret, the
objects.  Yet that is what these drivers are doing.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux