<div dir="ltr"><div><div><div><div><div>I downloaded the wip-port branch and tried to compile for IMX6 processors. The following compilation error has occurred. <br><br> CHK include/config/kernel.release<br> CHK include/generated/uapi/linux/version.h<br> CHK include/generated/utsrelease.h<br> CHK include/generated/bounds.h<br> CHK include/generated/timeconst.h<br> CHK include/generated/asm-offsets.h<br> CALL scripts/checksyscalls.sh<br> CHK include/generated/compile.h<br> CHK kernel/config_data.h<br> CC litmus/sched_pfp.o<br>In file included from ./arch/arm/include/asm/uaccess.h:18:0,<br> from ./include/linux/uaccess.h:5,<br> from litmus/sched_pfp.c:26:<br>./arch/arm/include/asm/domain.h:88:28: error: expected identifier or ‘(’ before ‘&’ token<br>./arch/arm/include/asm/domain.h:88:28: error: expected ‘)’ before ‘->’ token<br>In file included from ./include/linux/uaccess.h:5:0,<br> from litmus/sched_pfp.c:26:<br>./arch/arm/include/asm/uaccess.h: In function ‘uaccess_save_and_enable’:<br>./arch/arm/include/asm/uaccess.h:61:28: error: expected expression before ‘)’ token<br>make[1]: *** [litmus/sched_pfp.o] Error 1<br>make: *** [litmus] Error 2<br><br>The compilation environment is:<br></div>cross-compiler : arm-linux-gnueabihf-gcc version 4.7.3<br></div>kernel configuration : default imx_v6_v7 configuration (make imx_v6_v7_defconfig)<br><br></div>Does anyone compile the wip-port branch for ARM architectures?<br><br></div>Thanks,<br><br></div>Namhoon<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 27, 2017 at 6:37 PM, Namhoon Kim <span dir="ltr"><<a href="mailto:namhoonk@cs.unc.edu" target="_blank">namhoonk@cs.unc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi,<br><br></div>We will compile and test the wip-port branch on our Freescale IMX6 platform (ARM arch). I will report the results in a few days.<br><br></div>Thanks,<br><br></div>Namhoon<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 27, 2017 at 6:05 PM, Björn Brandenburg <span dir="ltr"><<a href="mailto:bbb@mpi-sws.org" target="_blank">bbb@mpi-sws.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear LITMUS^RT community,<br>
<br>
I’ve prepared an initial port of LITMUS^RT to Linux 4.9.13. It compiles and runs on my x86 box, and even survives light testing. Let’s make this the next release. Obviously, more testing and cleanup is required. Thus:<br>
<br>
******** Please help out with testing! ********<br>
<br>
The port is in the wip-port branch on Github:<br>
<br>
<a href="https://github.com/LITMUS-RT/litmus-rt/commits/wip-port" rel="noreferrer" target="_blank">https://github.com/LITMUS-RT/l<wbr>itmus-rt/commits/wip-port</a><br>
<br>
Please give it a try.<br>
<br>
Some details on what I’ve done:<br>
<br>
First, I squashed the history of the current master branch, the result of which you can find in the sip-squashed branch:<br>
<br>
<a href="https://github.com/LITMUS-RT/litmus-rt/commits/wip-squashed" rel="noreferrer" target="_blank">https://github.com/LITMUS-RT/l<wbr>itmus-rt/commits/wip-squashed</a><br>
<br>
This branch is identical to the current master branch, modulo the simplified history.<br>
<br>
Next, I’ve rebased wip-squashed on top of Linux 4.9.13. Some notes:<br>
<br>
- the hrtimer API has changed; this required some adjustments.<br>
<br>
- I’ve dropped the SRP ceiling blocking hook. This legacy implementation was no longer working right and causing too many problem. SRP support will have to be re-implemented (if anyone still cares).<br>
<br>
- There were many merge conflicts due to regular kernel churn. Most of them I could resolve in ways that seem like they ought to work, but only heavy workloads will show if the kernel holds up.<br>
<br>
******** What to do ********<br>
<br>
- Download, compile, and run the version in the wip-port branch.<br>
<br>
- Run on the machines that you usually use for your research and tests.<br>
<br>
- Run with both debug and benchmarking configs.<br>
<br>
- If you use non-x86 hardware, see if the kernel still compiles for your favorite platform.<br>
<br>
- Run your usual benchmarks / workloads.<br>
<br>
- Report any crashes / warnings / performance regressions / anything else surprising.<br>
<br>
- Ideally, submit patches to fix both minor and major breakage.<br>
<br>
Note: you’ll need the latest liblitmus to work with this kernel.<br>
<br>
I know testing is not the most fun activity on the planet, but if you want to have a stable base system for your next project, now is the time to chip in and help out the project. The plan is to make 4.9 the base version for at least the next two years, so any effort invested now is going to pay off for some time to come.<br>
<br>
Thanks,<br>
Björn<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
litmus-dev mailing list<br>
<a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a><br>
<a href="https://lists.litmus-rt.org/listinfo/litmus-dev" rel="noreferrer" target="_blank">https://lists.litmus-rt.org/li<wbr>stinfo/litmus-dev</a><br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>