From: Andrew Jones <drjones@redhat.com> To: Christoffer Dall <christoffer.dall@linaro.org> Cc: Marc Zyngier <marc.zyngier@arm.com>, Stable <stable@vger.kernel.org>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org Subject: Re: [PATCH] KVM: arm/arm64: Fix arch timers with userspace irqchips Date: Wed, 31 Jan 2018 14:16:31 +0100 [thread overview] Message-ID: <20180131131631.hecvgdsa67bhf2gv@kamzik.brq.redhat.com> (raw) In-Reply-To: <CAMJs5B_H16cxgAmzZ1+xU9FJWpaG3pHgziN=RBb62nMbQrZdhw@mail.gmail.com> On Wed, Jan 31, 2018 at 12:23:09PM +0100, Christoffer Dall wrote: > Did I mention that I hate this feature, which keeps breaking, and > which really isn't covered by a simple kvm-unit-test script? > Doesn't running the kvm-unit-tests' timer tests with '-machine kernel_irqchip=off' exercise at least some of these paths? If so, then the kvm-unit-tests patch below may help Thanks, drew diff --git a/arm/unittests.cfg b/arm/unittests.cfg index 44b98cfc7afde..7c0041e44d5f3 100644 --- a/arm/unittests.cfg +++ b/arm/unittests.cfg @@ -116,3 +116,10 @@ file = timer.flat groups = timer timeout = 2s arch = arm64 + +[timer-userspace-gic] +file = timer.flat +extra_params = -machine kernel_irqchip=off +groups = timer +timeout = 2s +arch = arm64
WARNING: multiple messages have this Message-ID (diff)
From: drjones@redhat.com (Andrew Jones) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] KVM: arm/arm64: Fix arch timers with userspace irqchips Date: Wed, 31 Jan 2018 14:16:31 +0100 [thread overview] Message-ID: <20180131131631.hecvgdsa67bhf2gv@kamzik.brq.redhat.com> (raw) In-Reply-To: <CAMJs5B_H16cxgAmzZ1+xU9FJWpaG3pHgziN=RBb62nMbQrZdhw@mail.gmail.com> On Wed, Jan 31, 2018 at 12:23:09PM +0100, Christoffer Dall wrote: > Did I mention that I hate this feature, which keeps breaking, and > which really isn't covered by a simple kvm-unit-test script? > Doesn't running the kvm-unit-tests' timer tests with '-machine kernel_irqchip=off' exercise at least some of these paths? If so, then the kvm-unit-tests patch below may help Thanks, drew diff --git a/arm/unittests.cfg b/arm/unittests.cfg index 44b98cfc7afde..7c0041e44d5f3 100644 --- a/arm/unittests.cfg +++ b/arm/unittests.cfg @@ -116,3 +116,10 @@ file = timer.flat groups = timer timeout = 2s arch = arm64 + +[timer-userspace-gic] +file = timer.flat +extra_params = -machine kernel_irqchip=off +groups = timer +timeout = 2s +arch = arm64
next prev parent reply other threads:[~2018-01-31 13:16 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-30 12:46 [PATCH] KVM: arm/arm64: Fix arch timers with userspace irqchips Christoffer Dall 2018-01-30 12:46 ` Christoffer Dall 2018-01-31 9:37 ` Marc Zyngier 2018-01-31 9:37 ` Marc Zyngier 2018-01-31 10:05 ` Christoffer Dall 2018-01-31 10:05 ` Christoffer Dall 2018-01-31 11:19 ` Marc Zyngier 2018-01-31 11:19 ` Marc Zyngier 2018-01-31 11:23 ` Christoffer Dall 2018-01-31 11:23 ` Christoffer Dall 2018-01-31 11:31 ` Marc Zyngier 2018-01-31 11:31 ` Marc Zyngier 2018-01-31 13:16 ` Andrew Jones [this message] 2018-01-31 13:16 ` Andrew Jones 2018-01-31 13:37 ` Christoffer Dall 2018-01-31 13:37 ` Christoffer Dall
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=20180131131631.hecvgdsa67bhf2gv@kamzik.brq.redhat.com \ --to=drjones@redhat.com \ --cc=christoffer.dall@linaro.org \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=marc.zyngier@arm.com \ --cc=stable@vger.kernel.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: linkBe 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.