All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fino Meng <fino.meng@linux.intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: [PATCH 1/4] cobalt/x86: adapt fpu code with Linux kernel upstream
Date: Mon, 21 Sep 2020 20:25:34 +0800	[thread overview]
Message-ID: <20200921122533.GA19127@linux.intel.com> (raw)
In-Reply-To: <f768e3fb-b9d1-8229-a8d8-767186d8f493@siemens.com>

On Fri, Sep 18, 2020 at 03:04:06PM +0200, Jan Kiszka wrote:
> <no commit message>
> 
> When I'm asking questions on the code, there was a need for a commit
> message.
> 
> On 18.09.20 08:29, Fino Meng wrote:
> > Signed-off-by: Fino Meng <fino.meng@linux.intel.com>
> > Signed-off-by: Mingliang Hu <mingliang.hu@intel.com>
> > ---
> >   kernel/cobalt/arch/x86/thread.c | 6 +++++-
> >   1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/kernel/cobalt/arch/x86/thread.c b/kernel/cobalt/arch/x86/thread.c
> > index ba807ac1e..c33ad832f 100644
> > --- a/kernel/cobalt/arch/x86/thread.c
> > +++ b/kernel/cobalt/arch/x86/thread.c
> > @@ -26,6 +26,10 @@
> >   #include <asm/mmu_context.h>
> >   #include <asm/processor.h>
> > +#ifdef IPIPE_X86_FPU_EAGER
> > +extern void fpu__initialize(struct fpu *fpu);
> 
> This will go along with ipipe for 5.4 patching that function to be
> non-static again, right?

looks like should use "void fpstate_init(union fpregs_state *state)" to
replace "void fpu__initialize(struct fpu *fpu)", the former is still a
API in header file.

> > +#endif
> > +
> >   static struct kmem_cache *xstate_cache;
> >   #ifdef IPIPE_X86_FPU_EAGER
> > @@ -472,7 +476,7 @@ void xnarch_leave_root(struct xnthread *root)
> >   #if LINUX_VERSION_CODE >= KERNEL_VERSION(4,14,0)
> >   	/* restore current's fpregs */
> >   	__cpu_invalidate_fpregs_state();
> > -	switch_fpu_finish(&current->thread.fpu, smp_processor_id());
> > +	switch_fpu_finish(&current->thread.fpu);
> 
> That is not correct for < 5.2 (5f409e20b794).

preparing V2 patches while fixing the smokey tests.

BR fino

> >   #else
> >   	/* mark current thread as not owning the FPU anymore */
> >   	if (fpregs_active())
> > 
> 
> Jan
> 
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux


  reply	other threads:[~2020-09-21 12:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  6:29 [PATCH 1/4] cobalt/x86: adapt fpu code with Linux kernel upstream Fino Meng
2020-09-18 13:04 ` Jan Kiszka
2020-09-21 12:25   ` Fino Meng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-18  6:31 Fino Meng
2020-09-18  5:56 Fino Meng
2020-09-17 16:53 Fino Meng
2020-09-17 17:11 ` Meng, Fino
2020-09-17 17:51   ` Philippe Gerum

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=20200921122533.GA19127@linux.intel.com \
    --to=fino.meng@linux.intel.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.