From: Andrew Jones <drjones@redhat.com>
To: Christoffer Dall <cdall@linaro.org>
Cc: kvm@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>,
kvmarm@lists.cs.columbia.edu, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH kvm-unit-tests 0/3] Add physical timer test
Date: Tue, 18 Jul 2017 14:20:14 +0200 [thread overview]
Message-ID: <20170718122014.5gadoynazm4c7t66@kamzik.brq.redhat.com> (raw)
In-Reply-To: <20170718104226.GC14069@cbox>
On Tue, Jul 18, 2017 at 12:42:26PM +0200, Christoffer Dall wrote:
> On Tue, Jul 18, 2017 at 12:17:07PM +0200, Andrew Jones wrote:
> > On Thu, Jul 13, 2017 at 09:20:06PM +0200, Christoffer Dall wrote:
> > > Add a test for the vtimer. I've tested on
> > > accel=tcg
> > > accel=kvm : on seattle, and mustang
> > > accel=kvm,kernel-irqchip=off : on mustang
> > >
> > > I first fix two issues I had running the basic timer test on APM mustang
> > > on using TCG. I wonder why the vtimer tests worked using TCG for Drew,
> > > since they didn't work for me, and I don't see how they would have
> > > without patch 1.
> >
> > That's weird. I just tested again with a latest qemu master pull and it
> > still works for me without patch 1. However, as you and Marc discussed,
> > it's the right thing to do with regards to the spec.
> >
>
> What is the command line you use to test this?
The one generated by the run script
$ cat logs/timer.log
timeout -k 1s --foreground 2s ../build/q/aarch64-softmmu/qemu-system-aarch64 -nodefaults -machine virt,accel=tcg -cpu cortex-a57 -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/timer.flat -smp 1 # -initrd /tmp/tmp.2Z4KzFEbAs
CNTFRQ_EL0 : 0x0000000003b9aca0
CNTVCT_EL0 : 0x00000000000aa949
CNTV_CTL_EL0 : 0x0000000000000000
CNTV_CVAL_EL0: 0x0000000000000000
PASS: vtimer-busy-loop: not pending before
INFO: vtimer-busy-loop: After timer: 0x0000000000167bd1
INFO: vtimer-busy-loop: Expected : 0x0000000000163ae6
INFO: vtimer-busy-loop: Difference : 268 us
PASS: vtimer-busy-loop: latency within 10 ms
PASS: vtimer-busy-loop: interrupt received
SUMMARY: 3 tests
>
> By looking at the code in QEMU, I see this:
>
> target/arm/helper.c:gt_recalc_timer()
>
> if (gt->ctl & 1) {
> ...
> } else {
> gt->ctl &= ~4;
> qemu_set_irq(cpu->gt_timer_outputs[timeridx], 0);
> timer_del(cpu->gt_timer[timeridx]);
> trace_arm_gt_recalc_disabled(timeridx);
> }
>
> So bits 1 and 2 (IMASK and ISTATUS, respectively) are cleared.
>
> I instrumented the code and verified this.
>
> Confusing.
Indeed.
drew
next prev parent reply other threads:[~2017-07-18 12:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 19:20 [PATCH kvm-unit-tests 0/3] Add physical timer test Christoffer Dall
2017-07-13 19:20 ` [PATCH kvm-unit-tests 1/3] arm64: timer: Fix vtimer interrupt test Christoffer Dall
2017-07-14 7:55 ` Marc Zyngier
2017-07-14 15:43 ` Christoffer Dall
2017-07-14 15:54 ` Marc Zyngier
2017-07-13 19:20 ` [PATCH kvm-unit-tests 2/3] arm64: timer: Fix test on APM X-Gene Christoffer Dall
2017-07-14 8:04 ` Marc Zyngier
2017-07-14 15:45 ` Christoffer Dall
2017-07-18 10:05 ` Andrew Jones
2017-07-18 10:35 ` Christoffer Dall
2017-07-18 12:15 ` Andrew Jones
2017-07-24 17:13 ` Paolo Bonzini
2017-07-24 21:25 ` Christoffer Dall
2017-07-26 11:38 ` Christoffer Dall
2017-07-13 19:20 ` [PATCH kvm-unit-tests 3/3] arm64: timer: Add support for phys timer testing Christoffer Dall
2017-07-18 12:09 ` Andrew Jones
2017-07-18 13:01 ` Christoffer Dall
2017-07-18 13:23 ` Andrew Jones
2017-07-18 13:31 ` Christoffer Dall
2017-07-18 13:50 ` Andrew Jones
2017-07-18 14:15 ` Christoffer Dall
2017-07-18 14:29 ` Andrew Jones
2017-07-18 14:37 ` Christoffer Dall
2017-07-18 10:17 ` [PATCH kvm-unit-tests 0/3] Add physical timer test Andrew Jones
2017-07-18 10:42 ` Christoffer Dall
2017-07-18 12:20 ` Andrew Jones [this message]
2017-07-24 17:16 ` Paolo Bonzini
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=20170718122014.5gadoynazm4c7t66@kamzik.brq.redhat.com \
--to=drjones@redhat.com \
--cc=cdall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
/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.