From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Josh Triplett <josh@joshtriplett.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel-only deployments?
Date: Thu, 23 Aug 2018 11:43:33 -0700 [thread overview]
Message-ID: <20180823184333.GR4225@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAMuHMdW4utnKZrEjAtWCUyfUj7qp1EXTj5B+fCryE23GHMLtnA@mail.gmail.com>
On Thu, Aug 23, 2018 at 08:16:55PM +0200, Geert Uytterhoeven wrote:
> Hi Paul,
>
> On Thu, Aug 23, 2018 at 7:44 PM Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> > Does anyone do kernel-only deployments, for example, setting up an
> > embedded device having a Linux kernel and absolutely no userspace
> > whatsoever?
>
> Isn't that basically the original porting guide from VxWorks to Linux?
I haven't seen that document, but if you say so. The TimeSys appnote
suggests using Linux userspace, but I can easily imagine cases where
porting the VxWorks "application" into the Linux kernel.
But do you really believe that supporting Linux-kernel-only deployments
in mainline would be something worth doing? Who aside from rcutorture
would really use such a thing?
Thanx, Paul
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2018-08-23 18:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 17:43 Kernel-only deployments? Paul E. McKenney
2018-08-23 18:16 ` Geert Uytterhoeven
2018-08-23 18:43 ` Paul E. McKenney [this message]
2018-08-23 18:42 ` Nicolas Pitre
2018-08-23 20:37 ` Paul E. McKenney
2018-08-23 18:54 ` Adam Borowski
2018-08-23 19:06 ` Willy Tarreau
2023-02-15 2:35 ` Zhangjin Wu
2023-02-15 9:47 ` Willy Tarreau
2023-02-16 13:09 ` Zhangjin Wu
2018-08-23 19:16 ` Josh Triplett
2018-08-23 20:39 ` Paul E. McKenney
2018-08-23 20:39 ` Paul E. McKenney
2018-08-23 19:12 ` Josh Triplett
2018-08-23 20:45 ` Paul E. McKenney
2018-08-23 19:22 ` Ray Clinton
2018-08-23 20:49 ` Paul E. McKenney
2018-08-23 19:52 ` Bernd Petrovitsch
2018-08-23 20:54 ` Paul E. McKenney
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=20180823184333.GR4225@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=geert@linux-m68k.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.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 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).