* understanding devpts_pty_new/kill
@ 2002-10-18 15:59 Shaya Potter
0 siblings, 0 replies; only message in thread
From: Shaya Potter @ 2002-10-18 15:59 UTC (permalink / raw)
To: linux-kernel
I'm trying to understand how the path those functions take to be called.
>From a basic understanding, is that we register f_ops for tty's and
ptys. So we register tty_open for tty's which includes ptmx.
therefore when we open ptmx, tty_open gets called, we do the code for
PTMX, which calls devpts_pty_new() which creates the appropriate
enteries in /dev/pts. These f_ops are registered in chrdevs struct
(from fs/devices.c)
I'm a little more hazy on devpts_pty_kill. That seems to similiar
(except it's in pty_close, in pty.c) which is part of a much larger "tty
driver" structure and is the "close" member of that structure. This
structure is then registered. Then basically, it's also registered w/
tty_fops, but tty_release calls tty->driver.close.
Is this a correct understanding, or is there more going on behind the
scenes?
thanks,
shaya potter
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-10-18 15:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-18 15:59 understanding devpts_pty_new/kill Shaya Potter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).