All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Andrew Jones <drjones@redhat.com>
Cc: marc.zyngier@arm.com, pbonzini@redhat.com,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	shannon.zhao@linaro.org
Subject: Re: [kvm-unit-tests PATCH] arm/arm64: introduce is_aarch32
Date: Thu, 17 Nov 2016 17:47:51 +0000	[thread overview]
Message-ID: <20161117174751.GD21742@leverpostej> (raw)
In-Reply-To: <20161117164541.uwmearukm3zcwahh@hawk.localdomain>

On Thu, Nov 17, 2016 at 05:45:41PM +0100, Andrew Jones wrote:
> Hi Mark,
> 
> On Wed, Nov 16, 2016 at 05:45:44PM +0000, Mark Rutland wrote:
> > So I don't think we should try to distinguish ARMv8-A AArch32 from
> > ARMv7-A. We should test individual features, or if that's not possible,
> > group them in the same bucket.
> 
> Perhaps I was too quick to look for a general way to approach the first
> place I saw the need, which is
> 
>  check_cntr(read_pmccntr());
>  if (is_aarch64())
>      check_cntr(read_pmccntr64());
> 
> Is PMCCNTR the only "weird" difference?

Define "weird". ;)

I believe the extension of PMCCNTR to 64 bits is part of PMUv3. So you
should be able to check ID_DFR0.PerfMon == 0b0011. For overflow you'll
also need to configure PMCR.LC.

Thanks,
Mark.

  reply	other threads:[~2016-11-17 17:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 14:38 [kvm-unit-tests PATCH] arm/arm64: introduce is_aarch32 Andrew Jones
2016-11-16 17:42 ` Andre Przywara
2016-11-17 16:33   ` Andrew Jones
2016-11-16 17:45 ` Mark Rutland
2016-11-17 16:45   ` Andrew Jones
2016-11-17 17:47     ` Mark Rutland [this message]
2016-11-18 10:57       ` Andrew Jones
2016-11-16 17:46 ` Marc Zyngier
2016-11-16 22:02   ` Christopher Covington
2016-11-17  6:45     ` Wei Huang
2016-11-17 16:59     ` Andrew Jones
2016-11-18 15:06       ` Christopher Covington

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=20161117174751.GD21742@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=shannon.zhao@linaro.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.