All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: "Lukas Jünger" <lukas.juenger@ice.rwth-aachen.de>
Cc: catalin.marinas@arm.com, will@kernel.org, kvmarm@lists.cs.columbia.edu
Subject: Re: KVM userspace GICv2 IRQ controller on platform with GICv3
Date: Mon, 04 Oct 2021 16:48:53 +0100	[thread overview]
Message-ID: <87zgrordsq.wl-maz@kernel.org> (raw)
In-Reply-To: <098ec673-c28f-d793-eae9-d6aa2147d61f@ice.rwth-aachen.de>

On Mon, 04 Oct 2021 15:15:25 +0100,
Lukas Jünger <lukas.juenger@ice.rwth-aachen.de> wrote:

Please consider subscribing to kvmarm instead of posting as a
non-subscriber. It forces me to manually allow each and every email
you reply to, which gets tiring in the long run.

> > So either you run something that is pretty old and buggy (and I'd like
> > to know what), or you have uncovered a bug and I would need you to
> > trace when vgic_sre gets set.
> Okay. I'm running on N1-SDP with the latest release 2021.05.26.
> uname -a gives:
> 
> Linux n1sdp 5.10.12+ #1 SMP Fri Oct 1 11:50:05 UTC 2021 aarch64
> aarch64 aarch64 GNU/Linux
> 
> 
> Is there a way to debug this without a hardware debugger/JTAG?

Sure, you can always hack the kernel (I assume you know how to boot a
fresh kernel). Put some traces in vgic_v3_enable(), and find out why
vgic_sre is non-zero.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2021-10-04 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 10:07 KVM userspace GICv2 IRQ controller on platform with GICv3 Lukas Jünger
2021-10-04 10:24 ` Marc Zyngier
2021-10-04 10:30   ` Lukas Jünger
2021-10-04 11:02     ` Marc Zyngier
2021-10-04 11:27       ` Lukas Jünger
2021-10-04 13:11         ` Marc Zyngier
2021-10-04 14:15           ` Lukas Jünger
2021-10-04 15:48             ` Marc Zyngier [this message]
2021-10-05 12:06               ` Lukas Jünger

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=87zgrordsq.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=lukas.juenger@ice.rwth-aachen.de \
    --cc=will@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: 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.