From: Greg KH <greg@kroah.com>
To: kernelnewbies@kernelnewbies.org
Subject: Re: the cost of EXPORT_SYMBOL_GPL
Date: Wed, 17 Jun 2020 15:31:48 +0200 [thread overview]
Message-ID: <20200617133148.GA2314715@kroah.com> (raw)
In-Reply-To: <20200617123528.vyxryhhfh7n5f33p@viti.kaiser.cx>
On Wed, Jun 17, 2020 at 02:35:28PM +0200, Martin Kaiser wrote:
> Hello Greg and all,
>
> Thus wrote Greg KH (greg@kroah.com):
>
> > Please do not do that. There are valid kernel apis to grant access to
> > registers easily,
>
> the most simple case would be a "reset reason" register within the
> chip's address space. A hand-crafted driver would ioremap the region and
> implement a sysfs show method that reads the register.
No, that's not what sysfs is for. You would export this in the proper
way that "reset reason" expects.
> What do you recommend for providing read access to such a register
> via sysfs? Is this a job for the userspace I/O (UIO) subsystem?
If all you want is direct memory access to userspace for stuff like
this, what's wrong with /dev/mem ?
If you want access to memory and interrupts to do it all in userspace,
then yes, that's what UIO is for, use that please.
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-06-17 13:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 13:18 the cost of EXPORT_SYMBOL_GPL Tomek The Messenger
2020-06-16 13:27 ` Greg KH
2020-06-17 7:58 ` Tomek The Messenger
2020-06-17 8:55 ` Greg KH
2020-06-17 9:17 ` Tomek The Messenger
2020-06-17 9:28 ` Tomek The Messenger
2020-06-17 9:41 ` Greg KH
2020-06-17 10:39 ` Tomek The Messenger
2020-06-17 12:24 ` Valdis Klētnieks
2020-06-17 12:31 ` Greg KH
2020-06-17 12:35 ` Martin Kaiser
2020-06-17 12:48 ` Tomek The Messenger
2020-06-17 13:20 ` Valdis Klētnieks
2020-06-17 13:34 ` Ahmad Fatoum
2020-06-17 14:26 ` Tomek The Messenger
2020-06-17 15:08 ` Greg KH
2020-06-17 18:33 ` Valdis Klētnieks
2020-06-17 13:31 ` Greg KH [this message]
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=20200617133148.GA2314715@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.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 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.