From: Peter Maydell <peter.maydell@linaro.org>
To: Alistair Francis <alistair.francis@xilinx.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH target-arm v8 1/1] target-arm: Implements the ARM PMCCNTR register
Date: Tue, 25 Feb 2014 15:43:57 +0000 [thread overview]
Message-ID: <CAFEAcA-y6FsdmuRgjSEH1ics7D8==SQoXc2ybZ7RubY+7H7TEg@mail.gmail.com> (raw)
In-Reply-To: <51ce60d736867c51c81df4789b3da2c3781d6d4c.1392944513.git.alistair.francis@xilinx.com>
On 21 February 2014 01:07, Alistair Francis <alistair.francis@xilinx.com> wrote:
> This patch implements the ARM PMCCNTR register including
> the disable and reset components of the PMCR register.
>
> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
> ---
> @@ -478,9 +485,42 @@ static CPAccessResult pmreg_access(CPUARMState *env, const ARMCPRegInfo *ri)
> static void pmcr_write(CPUARMState *env, const ARMCPRegInfo *ri,
> uint64_t value)
> {
> + /* Don't computer the number of ticks in user mode */
> + #ifndef CONFIG_LINUX_USER
> + uint32_t temp_ticks;
> +
> + temp_ticks = qemu_clock_get_us(QEMU_CLOCK_VIRTUAL) *
> + get_ticks_per_sec() / 1000000;
This isn't what I asked for.
1. you want CONFIG_USER_ONLY, not CONFIG_LINUX_USER
2. just put one set of #ifdefs to encompass the entire set
of functions
3. don't define a reginfo entry for the register at all if
we're CONFIG_USER_ONLY
None of this stuff can be accessed from user mode in
Linux so that will work fine.
thanks
-- PMM
prev parent reply other threads:[~2014-02-25 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 1:07 [Qemu-devel] [PATCH target-arm v8 1/1] target-arm: Implements the ARM PMCCNTR register Alistair Francis
2014-02-25 15:43 ` Peter Maydell [this message]
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='CAFEAcA-y6FsdmuRgjSEH1ics7D8==SQoXc2ybZ7RubY+7H7TEg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alistair.francis@xilinx.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.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).