From: Philippe Gerum <rpm@xenomai.org>
To: Don Mahurin <don@mperpetuo.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] xenomai/ipipe arm64 port
Date: Tue, 25 Aug 2015 20:43:24 +0200 [thread overview]
Message-ID: <55DCB74C.50400@xenomai.org> (raw)
In-Reply-To: <CAJqUr7xc4C97XpP31tK7HLj03k=_FUQQFmX_38Bm8ejNUYBo2A@mail.gmail.com>
On 08/25/2015 08:05 PM, Don Mahurin wrote:
> On Tue, Aug 25, 2015 at 7:08 AM, Philippe Gerum <rpm@xenomai.org
> <mailto:rpm@xenomai.org>> wrote:
>
> This is likely because -rc7 has added checks to sched-* tests which have
> time-dependent results, so they may not match the expected value in a
> qemu-based execution.
>
>
> Would it be worthwhile to optionally disable the time-dependent nature
> of the tests, just for use in quick/automated emulator testing?
>
I believe so. We should probably have smokey accept a --vm option or
something along, to tell it about a virtual execution environment, which
may be freely interpreted by any test code concerned, e.g. to figure out
whether timings might be inaccurate due to a significant slowdown. We
could likely figure this out automatically, but I'd rather leave this
decision to the user. I'll have a look at this asap.
>
> In general, how should we proceed with arm64 changes? We can continue
> to make updates in the separate repos. But is there anything we need to
> do to get a thorough review of the changes by the community and get this
> incorporated into upstream xenomai/ipipe?
>
I will open dedicated arm64 branches tomorrow into the project
repositories for both the ipipe and xenomai, that could be merged to the
corresponding mainline branches when ready for prime time. The target
would be Xenomai 3.1, it's too late for bringing this in 3.0-rc.
So the process should be fairly common and straightforward: a pull
request from your end for code present in your repo would trigger the
review, bits getting merged gradually from your repo to the dedicated
arm64 branches, along with other contributions, until we can all declare
these branches ready for mainline.
--
Philippe.
next prev parent reply other threads:[~2015-08-25 18:43 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 0:13 [Xenomai] xenomai/ipipe arm64 port Don Mahurin
2015-08-25 14:08 ` Philippe Gerum
2015-08-25 15:20 ` Jorge Ramirez Ortiz
2015-08-25 16:13 ` Jan Kiszka
2015-08-25 17:07 ` Jorge Ramirez Ortiz
2015-08-25 17:34 ` Jorge Ramirez Ortiz
2015-08-25 17:36 ` Jan Kiszka
2015-08-25 17:54 ` Jorge Ramirez Ortiz
2015-08-25 18:03 ` Jan Kiszka
2015-08-25 17:34 ` Jan Kiszka
2015-08-25 18:02 ` Jorge Ramirez Ortiz
2015-08-25 18:05 ` Don Mahurin
2015-08-25 18:34 ` Jorge Ramirez Ortiz
2015-08-25 18:36 ` Jan Kiszka
2015-08-25 18:43 ` Philippe Gerum [this message]
2015-08-25 18:52 ` Gilles Chanteperdrix
2015-08-26 14:40 ` Jorge Ramirez Ortiz
2015-08-26 16:30 ` Don Mahurin
2015-08-27 17:07 ` Jorge Ramirez Ortiz
2015-08-27 21:56 ` Don Mahurin
2015-09-01 17:45 ` Jorge Ramirez Ortiz
[not found] ` <CAPuu0=jX6ig5L7SJrmPVOhCmOm=gwxEmTafTpOqzE85hOji8CA@mail.gmail.com>
2015-09-01 19:11 ` Jorge Ramirez Ortiz
2015-09-01 19:24 ` Philippe Gerum
2015-09-01 20:14 ` Jorge Ramirez Ortiz
2015-09-01 21:02 ` Hongfei Cheng
2015-09-02 0:43 ` Don Mahurin
2015-09-07 16:03 ` Philippe Gerum
2015-09-24 19:39 ` Dmitriy Cherkasov
2015-09-25 15:02 ` Gilles Chanteperdrix
2015-09-25 17:14 ` Dmitriy Cherkasov
2015-09-25 18:01 ` Gilles Chanteperdrix
2015-09-26 11:24 ` Gilles Chanteperdrix
2015-09-28 23:57 ` Dmitriy Cherkasov
2015-09-29 0:12 ` Gilles Chanteperdrix
2015-09-29 12:54 ` Jorge Ramirez Ortiz
2015-09-29 17:31 ` Dmitriy Cherkasov
2015-09-29 17:47 ` Gilles Chanteperdrix
2015-09-29 20:17 ` Jorge Ramirez Ortiz
2015-09-29 17:05 ` Don Mahurin
2015-09-29 14:14 ` Lennart Sorensen
2015-09-29 20:49 ` Gilles Chanteperdrix
2015-10-01 23:51 ` Dmitriy Cherkasov
2015-10-02 10:01 ` Gilles Chanteperdrix
2015-10-02 11:55 ` Gilles Chanteperdrix
2015-10-02 20:18 ` Dmitriy Cherkasov
2015-10-03 9:53 ` Philippe Gerum
2015-10-03 10:01 ` Philippe Gerum
2015-10-03 10:05 ` Philippe Gerum
2015-09-01 19:30 ` Philippe Gerum
2015-09-01 20:47 ` Jorge Ramirez Ortiz
2015-09-01 19:44 ` Gilles Chanteperdrix
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=55DCB74C.50400@xenomai.org \
--to=rpm@xenomai.org \
--cc=don@mperpetuo.com \
--cc=xenomai@xenomai.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 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.