From: mbenes at suse.cz (Miroslav Benes)
Subject: [PATCH v3] selftests/livepatch: introduce tests
Date: Tue, 17 Apr 2018 10:06:04 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.1804171004410.12184@pobox.suse.cz> (raw)
In-Reply-To: <20180416150230.6ys6ya7alpodxp3d@pathway.suse.cz>
On Mon, 16 Apr 2018, Petr Mladek wrote:
> On Mon 2018-04-16 13:33:55, Miroslav Benes wrote:
> > On Fri, 13 Apr 2018, Joe Lawrence wrote:
> > > Thanks for reviewing. I'll hold off on posting v4 until Petr (and
> > > others) get a chance to comment. Perhaps there are other tests that
> > > would be helpful?
>
> > I think it would be useful to have tests for a stack checking and a
> > consistency. Nicolai has written some lately for our internal testing, but
> > it would take some time to transform them appropriately, I think.
>
> The future of the stack handling is not clear at the moment. We should
> wait how the discussion goes before spending time on test cases for
> the current behavior.
You're talking about something different. We have to check stacks of all
tasks while patching in order to achieve consistency. Tests for that would
be useful.
Miroslav
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: mbenes@suse.cz (Miroslav Benes)
Subject: [PATCH v3] selftests/livepatch: introduce tests
Date: Tue, 17 Apr 2018 10:06:04 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.1804171004410.12184@pobox.suse.cz> (raw)
Message-ID: <20180417080604.sBRirCKz8Mmg8ywnf0yujOneUM97J28VRHWy5kfMvMo@z> (raw)
In-Reply-To: <20180416150230.6ys6ya7alpodxp3d@pathway.suse.cz>
On Mon, 16 Apr 2018, Petr Mladek wrote:
> On Mon 2018-04-16 13:33:55, Miroslav Benes wrote:
> > On Fri, 13 Apr 2018, Joe Lawrence wrote:
> > > Thanks for reviewing. I'll hold off on posting v4 until Petr (and
> > > others) get a chance to comment. Perhaps there are other tests that
> > > would be helpful?
>
> > I think it would be useful to have tests for a stack checking and a
> > consistency. Nicolai has written some lately for our internal testing, but
> > it would take some time to transform them appropriately, I think.
>
> The future of the stack handling is not clear at the moment. We should
> wait how the discussion goes before spending time on test cases for
> the current behavior.
You're talking about something different. We have to check stacks of all
tasks while patching in order to achieve consistency. Tests for that would
be useful.
Miroslav
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-04-17 8:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 14:54 [PATCH v3] Add livepatch kselftests joe.lawrence
2018-04-12 14:54 ` Joe Lawrence
2018-04-12 14:54 ` [PATCH v3] selftests/livepatch: introduce tests joe.lawrence
2018-04-12 14:54 ` Joe Lawrence
2018-04-12 21:36 ` jpoimboe
2018-04-12 21:36 ` Josh Poimboeuf
2018-04-13 11:20 ` mbenes
2018-04-13 11:20 ` Miroslav Benes
2018-04-13 20:52 ` joe.lawrence
2018-04-13 20:52 ` Joe Lawrence
2018-04-16 11:33 ` mbenes
2018-04-16 11:33 ` Miroslav Benes
2018-04-16 15:02 ` pmladek
2018-04-16 15:02 ` Petr Mladek
2018-04-17 8:06 ` mbenes [this message]
2018-04-17 8:06 ` Miroslav Benes
2018-04-17 13:25 ` joe.lawrence
2018-04-17 13:25 ` Joe Lawrence
2018-04-16 12:49 ` pmladek
2018-04-16 12:49 ` Petr Mladek
2018-04-20 12:56 ` lpechacek
2018-04-20 12:56 ` Libor Pechacek
2018-04-23 14:43 ` joe.lawrence
2018-04-23 14:43 ` Joe Lawrence
2018-04-24 15:50 ` joe.lawrence
2018-04-24 15:50 ` Joe Lawrence
2018-04-24 17:19 ` lpechacek
2018-04-24 17:19 ` Libor Pechacek
2018-04-24 17:35 ` lpechacek
2018-04-24 17:35 ` Libor Pechacek
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=alpine.LSU.2.21.1804171004410.12184@pobox.suse.cz \
--to=linux-kselftest@vger.kernel.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).