From: Cyril Bur <cyrilbur@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: gromero@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/tm: Remove struct thread_info param from tm_reclaim_thread()
Date: Fri, 02 Feb 2018 10:34:08 +1100 [thread overview]
Message-ID: <1517528048.5450.0.camel@gmail.com> (raw)
In-Reply-To: <87inbhe2q8.fsf@concordia.ellerman.id.au>
On Thu, 2018-02-01 at 15:46 +1100, Michael Ellerman wrote:
> Cyril Bur <cyrilbur@gmail.com> writes:
>
> > tm_reclaim_thread() doesn't use the parameter anymore, both callers have
> > to bother getting it as they have no need for a struct thread_info
> > either.
>
> In future please tell me why the parameter is unused and when it became
> unused.
>
Thanks, will do!
> In this case it was previously used but the last usage was removed in:
>
> dc3106690b20 ("powerpc: tm: Always use fp_state and vr_state to store live registers")
>
> cheers
>
> > diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
> > index bfdd783e3916..a47498da6562 100644
> > --- a/arch/powerpc/kernel/process.c
> > +++ b/arch/powerpc/kernel/process.c
> > @@ -853,8 +853,7 @@ static inline bool tm_enabled(struct task_struct *tsk)
> > return tsk && tsk->thread.regs && (tsk->thread.regs->msr & MSR_TM);
> > }
> >
> > -static void tm_reclaim_thread(struct thread_struct *thr,
> > - struct thread_info *ti, uint8_t cause)
> > +static void tm_reclaim_thread(struct thread_struct *thr, uint8_t cause)
> > {
> > /*
> > * Use the current MSR TM suspended bit to track if we have
> > @@ -901,7 +900,7 @@ static void tm_reclaim_thread(struct thread_struct *thr,
> > void tm_reclaim_current(uint8_t cause)
> > {
> > tm_enable();
> > - tm_reclaim_thread(¤t->thread, current_thread_info(), cause);
> > + tm_reclaim_thread(¤t->thread, cause);
> > }
> >
> > static inline void tm_reclaim_task(struct task_struct *tsk)
> > @@ -932,7 +931,7 @@ static inline void tm_reclaim_task(struct task_struct *tsk)
> > thr->regs->ccr, thr->regs->msr,
> > thr->regs->trap);
> >
> > - tm_reclaim_thread(thr, task_thread_info(tsk), TM_CAUSE_RESCHED);
> > + tm_reclaim_thread(thr, TM_CAUSE_RESCHED);
> >
> > TM_DEBUG("--- tm_reclaim on pid %d complete\n",
> > tsk->pid);
> > --
> > 2.16.1
next prev parent reply other threads:[~2018-02-01 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 1:07 [PATCH] powerpc/tm: Remove struct thread_info param from tm_reclaim_thread() Cyril Bur
2018-02-01 4:46 ` Michael Ellerman
2018-02-01 23:34 ` Cyril Bur [this message]
2018-07-24 13:59 ` Michael Ellerman
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=1517528048.5450.0.camel@gmail.com \
--to=cyrilbur@gmail.com \
--cc=gromero@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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.