All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xin Hao <xhao@linux.alibaba.com>
To: will@kernel.org
Cc: fweisbec@gmail.com, john.stultz@linaro.org,
	kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, lorenzo@google.com, maz@kernel.org,
	mika.penttila@nextfour.com, sboyd@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH v2 2/5] tick/broadcast: Split __tick_broadcast_oneshot_control() into a helper
Date: Thu, 27 May 2021 15:23:06 +0800	[thread overview]
Message-ID: <c3573cd8-a4c8-43c2-be66-8b74d688a406@linux.alibaba.com> (raw)
In-Reply-To: <20210524221818.15850-3-will@kernel.org>

Hi  will:

      I  had backport you  tick/broadcast: Prefer per-cpu relatives 
patches,

but i did not get the true result,  the Wakeup Devices are all null, why?

my machine is armv8-a arm64

#cat current_clocksource
arch_sys_counter

my local clock event is

Tick Device: mode:     1
Per CPU device: 95
Clock Event Device: arch_sys_timer
  max_delta_ns:   21474836451
  min_delta_ns:   1000
  mult:           429496730
  shift:          32
  mode:           3
  next_event:     14951080000000 nsecs
  set_next_event: arch_timer_set_next_event_phys
  shutdown: arch_timer_shutdown_phys
  oneshot stopped: arch_timer_shutdown_phys
  event_handler:  hrtimer_interrupt
  retries:        70
Wakeup Device: <NULL>

cat /proc/timer_list  | grep "Wakeup Device:"

Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>

Wakeup Device: <NULL>

-- 
Best Regards!
Xin Hao


WARNING: multiple messages have this Message-ID (diff)
From: Xin Hao <xhao@linux.alibaba.com>
To: will@kernel.org
Cc: fweisbec@gmail.com, john.stultz@linaro.org,
	kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, lorenzo@google.com, maz@kernel.org,
	mika.penttila@nextfour.com, sboyd@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH v2 2/5] tick/broadcast: Split __tick_broadcast_oneshot_control() into a helper
Date: Thu, 27 May 2021 15:23:06 +0800	[thread overview]
Message-ID: <c3573cd8-a4c8-43c2-be66-8b74d688a406@linux.alibaba.com> (raw)
In-Reply-To: <20210524221818.15850-3-will@kernel.org>

Hi  will:

      I  had backport you  tick/broadcast: Prefer per-cpu relatives 
patches,

but i did not get the true result,  the Wakeup Devices are all null, why?

my machine is armv8-a arm64

#cat current_clocksource
arch_sys_counter

my local clock event is

Tick Device: mode:     1
Per CPU device: 95
Clock Event Device: arch_sys_timer
  max_delta_ns:   21474836451
  min_delta_ns:   1000
  mult:           429496730
  shift:          32
  mode:           3
  next_event:     14951080000000 nsecs
  set_next_event: arch_timer_set_next_event_phys
  shutdown: arch_timer_shutdown_phys
  oneshot stopped: arch_timer_shutdown_phys
  event_handler:  hrtimer_interrupt
  retries:        70
Wakeup Device: <NULL>

cat /proc/timer_list  | grep "Wakeup Device:"

Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>
Wakeup Device: <NULL>

Wakeup Device: <NULL>

-- 
Best Regards!
Xin Hao


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-27  7:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 22:18 [PATCH v2 0/5] tick/broadcast: Allow per-cpu timers to be used instead of broadcast Will Deacon
2021-05-24 22:18 ` Will Deacon
2021-05-24 22:18 ` [PATCH v2 1/5] tick/broadcast: Drop unneeded CONFIG_GENERIC_CLOCKEVENTS_BROADCAST guard Will Deacon
2021-05-24 22:18   ` Will Deacon
2021-05-31 15:07   ` [tip: timers/core] " tip-bot2 for Will Deacon
2021-05-24 22:18 ` [PATCH v2 2/5] tick/broadcast: Split __tick_broadcast_oneshot_control() into a helper Will Deacon
2021-05-24 22:18   ` Will Deacon
2021-05-27  7:23   ` Xin Hao [this message]
2021-05-27  7:23     ` Xin Hao
2021-05-27  8:22     ` Will Deacon
2021-05-27  8:22       ` Will Deacon
2021-05-27 11:35       ` Xin Hao
2021-05-27 11:35         ` Xin Hao
2021-05-27 11:55         ` Will Deacon
2021-05-27 11:55           ` Will Deacon
2021-05-27 11:56         ` Will Deacon
2021-05-27 11:56           ` Will Deacon
2021-05-31 14:29           ` Thomas Gleixner
2021-05-31 14:29             ` Thomas Gleixner
2021-06-01 12:13             ` Will Deacon
2021-06-01 12:13               ` Will Deacon
2021-06-01 18:14               ` Thomas Gleixner
2021-06-01 18:14                 ` Thomas Gleixner
2021-05-31 15:06   ` [tip: timers/core] " tip-bot2 for Will Deacon
2021-05-24 22:18 ` [PATCH v2 3/5] tick/broadcast: Prefer per-cpu oneshot wakeup timers to broadcast Will Deacon
2021-05-24 22:18   ` Will Deacon
2021-05-31 15:06   ` [tip: timers/core] " tip-bot2 for Will Deacon
2021-05-24 22:18 ` [PATCH v2 4/5] tick/broadcast: Program wakeup timer when entering idle if required Will Deacon
2021-05-24 22:18   ` Will Deacon
2021-05-31 15:06   ` [tip: timers/core] " tip-bot2 for Will Deacon
2021-05-24 22:18 ` [PATCH v2 5/5] timer_list: Print name of per-cpu wakeup device Will Deacon
2021-05-24 22:18   ` Will Deacon
2021-05-31 15:06   ` [tip: timers/core] " tip-bot2 for Will Deacon

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=c3573cd8-a4c8-43c2-be66-8b74d688a406@linux.alibaba.com \
    --to=xhao@linux.alibaba.com \
    --cc=fweisbec@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@google.com \
    --cc=maz@kernel.org \
    --cc=mika.penttila@nextfour.com \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.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.