On Wed, Dec 14, 2022 at 10:45:07AM +, Alexandru Elisei wrote:
> Hi,
>
> On Tue, Dec 13, 2022 at 10:04:04AM -0800, Ricardo Koller wrote:
> > On Tue, Dec 13, 2022 at 05:03:40PM +, Alexandru Elisei wrote:
> > > Hi,
> > >
> > > Checked that all places where ALL_SET/PRE_OVERFLOW were used are
Hi,
On Tue, Dec 13, 2022 at 10:04:04AM -0800, Ricardo Koller wrote:
> On Tue, Dec 13, 2022 at 05:03:40PM +, Alexandru Elisei wrote:
> > Hi,
> >
> > Checked that all places where ALL_SET/PRE_OVERFLOW were used are now taking
> > into account the fact that counters are programmed to be 64bit.
On Tue, Dec 13, 2022 at 05:03:40PM +, Alexandru Elisei wrote:
> Hi,
>
> Checked that all places where ALL_SET/PRE_OVERFLOW were used are now taking
> into account the fact that counters are programmed to be 64bit.
>
> In the case of 64bit counters, the printf format specifier is %ld, which
>
Hi,
Checked that all places where ALL_SET/PRE_OVERFLOW were used are now taking
into account the fact that counters are programmed to be 64bit.
In the case of 64bit counters, the printf format specifier is %ld, which
means that ALL_SET_64 and PRE_OVERFLOW_64 are now displayed as negative
Modify all tests checking overflows to support both 32 (PMCR_EL0.LP == 0)
and 64-bit overflows (PMCR_EL0.LP == 1). 64-bit overflows are only
supported on PMUv3p5.
Note that chained tests do not implement "overflow_at_64bits == true".
That's because there are no CHAIN events when "PMCR_EL0.LP ==
