Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Christoffer Dall <christoffer.dall@arm.com>
Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Subject: Re: kvm-unit-tests gicv2 cases fail
Date: Thu, 01 Nov 2018 10:25:54 +0000	[thread overview]
Message-ID: <86a7mt2ix9.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <20181101101048.GJ12057@e113682-lin.lund.arm.com>

[Thanks Christoffer for cc'ing me]

On Thu, 01 Nov 2018 10:10:48 +0000,
Christoffer Dall <christoffer.dall@arm.com> wrote:
> 
> On Thu, Oct 18, 2018 at 05:17:57PM +0800, Li Zhang wrote:
> > Hi,
> > 
> > I run kvm-units-test on ARM server(QDF2400), but gicv2-ipi,
> > gicv2-active cases fail.
> 
> I didn't think QDF2400 has GICv2 on GICv3 support?
> 
> Do the test cases fail or are they reported as skipped?
> 
> > By debuging kvm-unit-tests source code, I found that interrupt is not
> > handled. do_handle_exception is not called.
> > 
> > By looking into KVM source code, it has GICv2 emulation on GICv3 support.
> > I've tried a lot of kernel versions, from v4.12~v4.19 in mainline,
> > these cases always fail.
> > Is it possible that hardware/software disables this?

Most implementations do not have the v2 compatibility interface, and
nobody really needs it. This is a convenient way to run older VMs that
do not know about GICv3 (32bit VMs, for example), but that's in no way
a common setup.

> > 
> > It seems that GICv2 is a little old for ARM server, I am confused when
> > we can use it.
> > Do we need to care about these cases?
> > 
> 
> I don't think you need to care.  I believe Marc has run the
> GICv2-on-GICv3 tests on his supported platforms with recent
> kvm-unit-tests and other have reported succes as well.

Here you go (on my Chromebook running 4.18):

PASS gicv2-ipi (3 tests)
PASS gicv2-mmio (17 tests)
PASS gicv2-mmio-up (17 tests)
PASS gicv2-mmio-3p (17 tests)
PASS gicv3-ipi (3 tests)
PASS gicv2-active (1 tests)
PASS gicv3-active (1 tests)

Thanks,

	M.

-- 
Jazz is not dead, it just smell funny.

  reply	other threads:[~2018-11-01 10:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  9:17 kvm-unit-tests gicv2 cases fail Li Zhang
2018-10-19  3:25 ` Andrew Jones
2018-10-19  3:35   ` Li Zhang
2018-10-19  3:59   ` Ard Biesheuvel
2018-10-19  4:53     ` Li Zhang
2018-11-01 10:10 ` Christoffer Dall
2018-11-01 10:25   ` Marc Zyngier [this message]
2018-11-05  7:19     ` Li Zhang

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=86a7mt2ix9.wl-marc.zyngier@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.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