From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/4] clockevents: Add generic timer broadcast receiver
Date: Mon, 14 Jan 2013 11:29:52 +0000 [thread overview]
Message-ID: <20130114112951.GC7990@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1301141204421.7475@ionos>
On Mon, Jan 14, 2013 at 11:06:31AM +0000, Thomas Gleixner wrote:
> On Wed, 9 Jan 2013, Mark Rutland wrote:
> > +#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
> > +extern int tick_receive_broadcast(void);
> > +#else
> > +static inline int tick_receive_broadcast(void)
> > +{
> > + return 0;
> > +}
>
> What's the inline function for? If an arch does not have broadcasting
> support it should not have a receive broadcast function call either.
That was how this was originally structured [1], but Santosh suggested this
would break the build for !GENERIC_CLOCKEVENTS_BROADCAST [1]. It means that the
arch-specific receive path (i.e. IPI handler) doesn't have to be #ifdef'd,
which makes it less ugly.
I'm happy to have it the other way, with #ifdef'd IPI handlers.
>
> > +#endif
> > +
> > #ifdef CONFIG_GENERIC_CLOCKEVENTS
> > extern void clockevents_notify(unsigned long reason, void *arg);
> > #else
> > diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
> > index f113755..5079bb7 100644
> > --- a/kernel/time/tick-broadcast.c
> > +++ b/kernel/time/tick-broadcast.c
> > @@ -125,6 +125,18 @@ int tick_device_uses_broadcast(struct clock_event_device *dev, int cpu)
> > return ret;
> > }
> >
> > +int tick_receive_broadcast(void)
> > +{
> > + struct tick_device *td = this_cpu_ptr(&tick_cpu_device);
> > + struct clock_event_device *evt = td->evtdev;
> > +
> > + if (!evt)
> > + return -ENODEV;
>
> Is anything going to use the return value?
I'd added this after looking at the x86 lapic timers, where interrupts might
remain pending over a kexec, and lapic interrupts come up before timers are
registered. The return value is useful for shutting down the timer in that case
(see x86's local_apic_timer_interrupt).
If you don't agree I'll remove the return value.
>
> Thanks,
>
> tglx
>
Thanks,
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/138486.html
next prev parent reply other threads:[~2013-01-14 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 14:46 [PATCHv2 0/4] clockevents: decouple broadcast mechanism from drivers Mark Rutland
2013-01-09 14:46 ` [PATCHv2 1/4] clockevents: Add generic timer broadcast receiver Mark Rutland
2013-01-14 11:06 ` Thomas Gleixner
2013-01-14 11:29 ` Mark Rutland [this message]
2013-01-14 11:50 ` Thomas Gleixner
2013-01-14 12:12 ` Mark Rutland
2013-01-14 14:17 ` Thomas Gleixner
2013-01-14 15:36 ` Mark Rutland
2013-01-15 6:40 ` Santosh Shilimkar
2013-01-15 11:24 ` Thomas Gleixner
2013-01-15 12:00 ` Mark Rutland
2013-01-09 14:46 ` [PATCHv2 2/4] arm: Use " Mark Rutland
2013-01-09 14:46 ` [PATCHv2 3/4] clockevents: Add generic timer broadcast function Mark Rutland
2013-01-14 11:10 ` Thomas Gleixner
2013-01-09 14:46 ` [PATCHv2 4/4] arm: Add generic timer broadcast support Mark Rutland
2013-01-09 20:46 ` [PATCHv2 0/4] clockevents: decouple broadcast mechanism from drivers Stephen Boyd
2013-01-10 9:44 ` Mark Rutland
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=20130114112951.GC7990@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).