2020-04-07 01:47:39 -07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0-or-later */
|
|
|
|
#ifndef _ASM_POWERPC_IDLE_H
|
|
|
|
#define _ASM_POWERPC_IDLE_H
|
|
|
|
#include <asm/runlatch.h>
|
|
|
|
#include <asm/paca.h>
|
|
|
|
|
|
|
|
#ifdef CONFIG_PPC_PSERIES
|
2020-04-07 01:47:41 -07:00
|
|
|
DECLARE_PER_CPU(u64, idle_spurr_cycles);
|
powerpc/idle: Store PURR snapshot in a per-cpu global variable
Currently when CPU goes idle, we take a snapshot of PURR via
pseries_idle_prolog() which is used at the CPU idle exit to compute
the idle PURR cycles via the function pseries_idle_epilog(). Thus,
the value of idle PURR cycle thus read before pseries_idle_prolog() and
after pseries_idle_epilog() is always correct.
However, if we were to read the idle PURR cycles from an interrupt
context between pseries_idle_prolog() and pseries_idle_epilog() (this
will be done in a future patch), then, the value of the idle PURR thus
read will not include the cycles spent in the most recent idle period.
Thus, in that interrupt context, we will need access to the snapshot
of the PURR before going idle, in order to compute the idle PURR
cycles for the latest idle duration.
In this patch, we save the snapshot of PURR in pseries_idle_prolog()
in a per-cpu variable, instead of on the stack, so that it can be
accessed from an interrupt context.
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/1586249263-14048-3-git-send-email-ego@linux.vnet.ibm.com
2020-04-07 01:47:40 -07:00
|
|
|
DECLARE_PER_CPU(u64, idle_entry_purr_snap);
|
2020-04-07 01:47:41 -07:00
|
|
|
DECLARE_PER_CPU(u64, idle_entry_spurr_snap);
|
powerpc/idle: Store PURR snapshot in a per-cpu global variable
Currently when CPU goes idle, we take a snapshot of PURR via
pseries_idle_prolog() which is used at the CPU idle exit to compute
the idle PURR cycles via the function pseries_idle_epilog(). Thus,
the value of idle PURR cycle thus read before pseries_idle_prolog() and
after pseries_idle_epilog() is always correct.
However, if we were to read the idle PURR cycles from an interrupt
context between pseries_idle_prolog() and pseries_idle_epilog() (this
will be done in a future patch), then, the value of the idle PURR thus
read will not include the cycles spent in the most recent idle period.
Thus, in that interrupt context, we will need access to the snapshot
of the PURR before going idle, in order to compute the idle PURR
cycles for the latest idle duration.
In this patch, we save the snapshot of PURR in pseries_idle_prolog()
in a per-cpu variable, instead of on the stack, so that it can be
accessed from an interrupt context.
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/1586249263-14048-3-git-send-email-ego@linux.vnet.ibm.com
2020-04-07 01:47:40 -07:00
|
|
|
|
2023-04-06 07:45:35 -07:00
|
|
|
static __always_inline void snapshot_purr_idle_entry(void)
|
powerpc/idle: Store PURR snapshot in a per-cpu global variable
Currently when CPU goes idle, we take a snapshot of PURR via
pseries_idle_prolog() which is used at the CPU idle exit to compute
the idle PURR cycles via the function pseries_idle_epilog(). Thus,
the value of idle PURR cycle thus read before pseries_idle_prolog() and
after pseries_idle_epilog() is always correct.
However, if we were to read the idle PURR cycles from an interrupt
context between pseries_idle_prolog() and pseries_idle_epilog() (this
will be done in a future patch), then, the value of the idle PURR thus
read will not include the cycles spent in the most recent idle period.
Thus, in that interrupt context, we will need access to the snapshot
of the PURR before going idle, in order to compute the idle PURR
cycles for the latest idle duration.
In this patch, we save the snapshot of PURR in pseries_idle_prolog()
in a per-cpu variable, instead of on the stack, so that it can be
accessed from an interrupt context.
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/1586249263-14048-3-git-send-email-ego@linux.vnet.ibm.com
2020-04-07 01:47:40 -07:00
|
|
|
{
|
|
|
|
*this_cpu_ptr(&idle_entry_purr_snap) = mfspr(SPRN_PURR);
|
|
|
|
}
|
|
|
|
|
2023-04-06 07:45:35 -07:00
|
|
|
static __always_inline void snapshot_spurr_idle_entry(void)
|
2020-04-07 01:47:41 -07:00
|
|
|
{
|
|
|
|
*this_cpu_ptr(&idle_entry_spurr_snap) = mfspr(SPRN_SPURR);
|
|
|
|
}
|
|
|
|
|
2023-04-06 07:45:35 -07:00
|
|
|
static __always_inline void update_idle_purr_accounting(void)
|
powerpc/idle: Store PURR snapshot in a per-cpu global variable
Currently when CPU goes idle, we take a snapshot of PURR via
pseries_idle_prolog() which is used at the CPU idle exit to compute
the idle PURR cycles via the function pseries_idle_epilog(). Thus,
the value of idle PURR cycle thus read before pseries_idle_prolog() and
after pseries_idle_epilog() is always correct.
However, if we were to read the idle PURR cycles from an interrupt
context between pseries_idle_prolog() and pseries_idle_epilog() (this
will be done in a future patch), then, the value of the idle PURR thus
read will not include the cycles spent in the most recent idle period.
Thus, in that interrupt context, we will need access to the snapshot
of the PURR before going idle, in order to compute the idle PURR
cycles for the latest idle duration.
In this patch, we save the snapshot of PURR in pseries_idle_prolog()
in a per-cpu variable, instead of on the stack, so that it can be
accessed from an interrupt context.
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/1586249263-14048-3-git-send-email-ego@linux.vnet.ibm.com
2020-04-07 01:47:40 -07:00
|
|
|
{
|
|
|
|
u64 wait_cycles;
|
|
|
|
u64 in_purr = *this_cpu_ptr(&idle_entry_purr_snap);
|
|
|
|
|
|
|
|
wait_cycles = be64_to_cpu(get_lppaca()->wait_state_cycles);
|
|
|
|
wait_cycles += mfspr(SPRN_PURR) - in_purr;
|
|
|
|
get_lppaca()->wait_state_cycles = cpu_to_be64(wait_cycles);
|
|
|
|
}
|
|
|
|
|
2023-04-06 07:45:35 -07:00
|
|
|
static __always_inline void update_idle_spurr_accounting(void)
|
2020-04-07 01:47:41 -07:00
|
|
|
{
|
|
|
|
u64 *idle_spurr_cycles_ptr = this_cpu_ptr(&idle_spurr_cycles);
|
|
|
|
u64 in_spurr = *this_cpu_ptr(&idle_entry_spurr_snap);
|
|
|
|
|
|
|
|
*idle_spurr_cycles_ptr += mfspr(SPRN_SPURR) - in_spurr;
|
|
|
|
}
|
|
|
|
|
2023-04-06 07:45:35 -07:00
|
|
|
static __always_inline void pseries_idle_prolog(void)
|
2020-04-07 01:47:39 -07:00
|
|
|
{
|
|
|
|
ppc64_runlatch_off();
|
powerpc/idle: Store PURR snapshot in a per-cpu global variable
Currently when CPU goes idle, we take a snapshot of PURR via
pseries_idle_prolog() which is used at the CPU idle exit to compute
the idle PURR cycles via the function pseries_idle_epilog(). Thus,
the value of idle PURR cycle thus read before pseries_idle_prolog() and
after pseries_idle_epilog() is always correct.
However, if we were to read the idle PURR cycles from an interrupt
context between pseries_idle_prolog() and pseries_idle_epilog() (this
will be done in a future patch), then, the value of the idle PURR thus
read will not include the cycles spent in the most recent idle period.
Thus, in that interrupt context, we will need access to the snapshot
of the PURR before going idle, in order to compute the idle PURR
cycles for the latest idle duration.
In this patch, we save the snapshot of PURR in pseries_idle_prolog()
in a per-cpu variable, instead of on the stack, so that it can be
accessed from an interrupt context.
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/1586249263-14048-3-git-send-email-ego@linux.vnet.ibm.com
2020-04-07 01:47:40 -07:00
|
|
|
snapshot_purr_idle_entry();
|
2020-04-07 01:47:41 -07:00
|
|
|
snapshot_spurr_idle_entry();
|
2020-04-07 01:47:39 -07:00
|
|
|
/*
|
|
|
|
* Indicate to the HV that we are idle. Now would be
|
|
|
|
* a good time to find other work to dispatch.
|
|
|
|
*/
|
|
|
|
get_lppaca()->idle = 1;
|
|
|
|
}
|
|
|
|
|
2023-04-06 07:45:35 -07:00
|
|
|
static __always_inline void pseries_idle_epilog(void)
|
2020-04-07 01:47:39 -07:00
|
|
|
{
|
powerpc/idle: Store PURR snapshot in a per-cpu global variable
Currently when CPU goes idle, we take a snapshot of PURR via
pseries_idle_prolog() which is used at the CPU idle exit to compute
the idle PURR cycles via the function pseries_idle_epilog(). Thus,
the value of idle PURR cycle thus read before pseries_idle_prolog() and
after pseries_idle_epilog() is always correct.
However, if we were to read the idle PURR cycles from an interrupt
context between pseries_idle_prolog() and pseries_idle_epilog() (this
will be done in a future patch), then, the value of the idle PURR thus
read will not include the cycles spent in the most recent idle period.
Thus, in that interrupt context, we will need access to the snapshot
of the PURR before going idle, in order to compute the idle PURR
cycles for the latest idle duration.
In this patch, we save the snapshot of PURR in pseries_idle_prolog()
in a per-cpu variable, instead of on the stack, so that it can be
accessed from an interrupt context.
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/1586249263-14048-3-git-send-email-ego@linux.vnet.ibm.com
2020-04-07 01:47:40 -07:00
|
|
|
update_idle_purr_accounting();
|
2020-04-07 01:47:41 -07:00
|
|
|
update_idle_spurr_accounting();
|
2020-04-07 01:47:39 -07:00
|
|
|
get_lppaca()->idle = 0;
|
|
|
|
ppc64_runlatch_on();
|
|
|
|
}
|
powerpc/idle: Store PURR snapshot in a per-cpu global variable
Currently when CPU goes idle, we take a snapshot of PURR via
pseries_idle_prolog() which is used at the CPU idle exit to compute
the idle PURR cycles via the function pseries_idle_epilog(). Thus,
the value of idle PURR cycle thus read before pseries_idle_prolog() and
after pseries_idle_epilog() is always correct.
However, if we were to read the idle PURR cycles from an interrupt
context between pseries_idle_prolog() and pseries_idle_epilog() (this
will be done in a future patch), then, the value of the idle PURR thus
read will not include the cycles spent in the most recent idle period.
Thus, in that interrupt context, we will need access to the snapshot
of the PURR before going idle, in order to compute the idle PURR
cycles for the latest idle duration.
In this patch, we save the snapshot of PURR in pseries_idle_prolog()
in a per-cpu variable, instead of on the stack, so that it can be
accessed from an interrupt context.
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/1586249263-14048-3-git-send-email-ego@linux.vnet.ibm.com
2020-04-07 01:47:40 -07:00
|
|
|
|
2020-04-07 01:47:42 -07:00
|
|
|
static inline u64 read_this_idle_purr(void)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* If we are reading from an idle context, update the
|
|
|
|
* idle-purr cycles corresponding to the last idle period.
|
|
|
|
* Since the idle context is not yet over, take a fresh
|
|
|
|
* snapshot of the idle-purr.
|
|
|
|
*/
|
|
|
|
if (unlikely(get_lppaca()->idle == 1)) {
|
|
|
|
update_idle_purr_accounting();
|
|
|
|
snapshot_purr_idle_entry();
|
|
|
|
}
|
|
|
|
|
|
|
|
return be64_to_cpu(get_lppaca()->wait_state_cycles);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline u64 read_this_idle_spurr(void)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* If we are reading from an idle context, update the
|
|
|
|
* idle-spurr cycles corresponding to the last idle period.
|
|
|
|
* Since the idle context is not yet over, take a fresh
|
|
|
|
* snapshot of the idle-spurr.
|
|
|
|
*/
|
|
|
|
if (get_lppaca()->idle == 1) {
|
|
|
|
update_idle_spurr_accounting();
|
|
|
|
snapshot_spurr_idle_entry();
|
|
|
|
}
|
|
|
|
|
|
|
|
return *this_cpu_ptr(&idle_spurr_cycles);
|
|
|
|
}
|
|
|
|
|
2020-04-07 01:47:39 -07:00
|
|
|
#endif /* CONFIG_PPC_PSERIES */
|
|
|
|
#endif
|