All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Henning Schild <henning.schild@siemens.com>, jan.kiszka@siemens.com
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] ipipe for 4.14 x86?
Date: Wed, 19 Sep 2018 12:19:48 +0200	[thread overview]
Message-ID: <1920928.FOH158oBg9@blindfold> (raw)
In-Reply-To: <20180918164932.79d3c86d@md1pvb1c.ad001.siemens.net>

Am Dienstag, 18. September 2018, 16:49:32 CEST schrieb Henning Schild:
> > Is this repo/branch the right one when I want to give ipipe x86 a try?
> > Maybe I can help fixing issues too!
> > https://gitlab.denx.de/Xenomai/ipipe-x86/tree/wip/4.14-split
> > 
> 
> This one contains a few more fixes.
> 
> https://gitlab.denx.de/Xenomai/ipipe-x86/tree/henning/wip/4.14-split
> 
> Both are mainly tested under KVM. The 16 core Xeon i am currently
> testing on runs into some timer init issues and gets stuck at boot.
> 
> Feedback welcome!

Hmm, that failed a way earlier than expected.

  AS      arch/x86/entry/vdso/vdso32/system_call.o
arch/x86/kernel/process_32.c: In function ‘__switch_to’:
arch/x86/kernel/process_32.c:238:14: error: implicit declaration of function ‘ipipe_get_domain_slope_hook’; did you mean ‘ipipe_test_and_stall_root’? [-Werror=implicit-function-declaration]
  int slope = ipipe_get_domain_slope_hook(prev_p, next_p);
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~
              ipipe_test_and_stall_root
arch/x86/kernel/process_32.c:242:36: error: ‘slot’ undeclared (first use in this function); did you mean ‘slope’?
  switch_fpu_prepare(prev_fpu, cpu, slot);
                                    ^~~~
                                    slope
arch/x86/kernel/process_32.c:242:36: note: each undeclared identifier is reported only once for each function it appears in
arch/x86/kernel/process_32.c:242:2: error: too many arguments to function ‘switch_fpu_prepare’
  switch_fpu_prepare(prev_fpu, cpu, slot);
  ^~~~~~~~~~~~~~~~~~
In file included from arch/x86/kernel/process_32.c:45:0:
./arch/x86/include/asm/fpu/internal.h:529:1: note: declared here
 switch_fpu_prepare(struct fpu *old_fpu, int cpu)
 ^~~~~~~~~~~~~~~~~~
arch/x86/kernel/process_32.c:303:2: error: too many arguments to function ‘switch_fpu_finish’
  switch_fpu_finish(next_fpu, cpu, slope);
  ^~~~~~~~~~~~~~~~~
In file included from arch/x86/kernel/process_32.c:45:0:
./arch/x86/include/asm/fpu/internal.h:551:20: note: declared here
 static inline void switch_fpu_finish(struct fpu *new_fpu, int cpu)
                    ^~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors

Looks like some ia32 bits are missing.

Thanks,
//richard





  reply	other threads:[~2018-09-19 10:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 13:39 [Xenomai] ipipe for 4.14 x86? Richard Weinberger
2018-09-17 18:10 ` Jan Kiszka
2018-09-18  8:52   ` Richard Weinberger
2018-09-18  8:55     ` Jan Kiszka
2018-09-18 14:49     ` Henning Schild
2018-09-19 10:19       ` Richard Weinberger [this message]
2018-09-19 11:08         ` Jan Kiszka
2018-09-19 12:17           ` Richard Weinberger
2018-09-19 12:30             ` Jan Kiszka
2018-09-27 18:52 ` Henning Schild
     [not found] <1736385944.1779097.1538339902687.ref@mail.yahoo.com>
2018-09-30 20:38 ` Alec Ari
2018-10-01  9:12   ` Henning Schild

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=1920928.FOH158oBg9@blindfold \
    --to=richard@nod.at \
    --cc=henning.schild@siemens.com \
    --cc=jan.kiszka@siemens.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.