From: Rusty Russell <rusty@rustcorp.com.au>
To: John Stultz <john.stultz@linaro.org>,
Richard Cochran <richardcochran@gmail.com>
Cc: Miroslav Lichvar <mlichvar@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
Prarit Bhargava <prarit@redhat.com>
Subject: Re: [PATCH RFC 0/3] Improve stability of system clock
Date: Sun, 21 May 2017 12:49:56 +0930 [thread overview]
Message-ID: <87fufykiar.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CALAqxLX+-gQzQ2-sbwmNn=A6C1XXKB00-XrehyX4nqV=3_wNAw@mail.gmail.com>
John Stultz <john.stultz@linaro.org> writes:
> On Wed, May 17, 2017 at 9:54 PM, Richard Cochran
> <richardcochran@gmail.com> wrote:
>> On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote:
>>> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar <mlichvar@redhat.com> wrote:
>>> > Is there a better way to run the timekeeping code in an userspace
>>> > application? I suspect it would need something like the Linux Kernel
>>> > Library project.
>>>
>>> I dunno. There's probably a cleaner way to go about it, but I also
>>> feel like the benefit of just having the test in the kernel tree is
>>> that it can be managed as a unified whole, rather then the test being
>>> a separate thing and always playing catchup to kernel changes.
>>
>> I vaguely recall a rant on the list years ago from a Linux bigwhig
>> saying how we don't support that kind of thing. But maybe it is my
>> imagination. In any case, IMHO running user space tests for chunks of
>> kernel code can be quite useful.
>
> So a few years ago I mentioned this at a testing session at I think
> Linux Plubmers' and Rusty (CC'ed) commented that he had some netfilter
> (or iptables?) simulator code that never made it upstream. However,
> now that kselftests are integrated with the kernel this could change.
> At least that's my memory of the discussion.
Yep, we did it with nfsim, but forward porting was a PITA. Good luck!
Rusty.
next prev parent reply other threads:[~2017-05-22 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 16:13 Miroslav Lichvar
2017-05-17 16:13 ` [PATCH RFC 1/3] timekeeping: Remove support for old vsyscalls Miroslav Lichvar
2017-05-17 16:13 ` [PATCH RFC 2/3] timekeeping: Don't align frequency adjustments to ticks Miroslav Lichvar
2017-05-17 16:13 ` [PATCH RFC 3/3] timekeeping: Determine multiplier directly from NTP tick length Miroslav Lichvar
2017-05-17 16:30 ` [PATCH RFC 0/3] Improve stability of system clock John Stultz
2017-05-17 16:57 ` Miroslav Lichvar
2017-05-17 17:02 ` John Stultz
2017-05-17 17:22 ` Miroslav Lichvar
2017-05-17 23:06 ` John Stultz
2017-05-18 4:54 ` Richard Cochran
2017-05-20 0:35 ` John Stultz
2017-05-21 3:19 ` Rusty Russell [this message]
2017-06-08 16:17 ` Miroslav Lichvar
2017-06-08 18:36 ` John Stultz
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=87fufykiar.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome