From: Greg KH <greg@kroah.com>
To: Ruben Safir <ruben@mrbrklyn.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Unexpected scheduling with mutexes
Date: Sat, 30 Mar 2019 19:35:59 +0100 [thread overview]
Message-ID: <20190330183559.GA21828@kroah.com> (raw)
In-Reply-To: <0f14b4fd-af65-2903-c692-1ba485c6a852@mrbrklyn.com>
On Sat, Mar 30, 2019 at 08:25:57AM -0400, Ruben Safir wrote:
> On 3/29/19 4:01 PM, Greg KH wrote:
> > As an example of this, serial ports are not "exclusively owned", right?
>
>
> they are not? What handles the interupt?
Context is everything, and you cut out all of it here :(
The kernel handles the interrupt of course, the sentence was referring
to userspace interacting with the kernel, not anything else.
greg k-
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-03-30 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 10:56 Unexpected scheduling with mutexes Martin Christian
2019-03-29 20:01 ` Greg KH
2019-03-29 21:45 ` Valdis Klētnieks
2019-03-30 12:25 ` Ruben Safir
2019-03-30 18:35 ` Greg KH [this message]
2019-04-03 9:33 ` Martin Christian
2019-04-03 9:48 ` Greg KH
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=20190330183559.GA21828@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=ruben@mrbrklyn.com \
/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.