From: Thierry Reding <thierry.reding@gmail•com>
To: Marc Zyngier <maz@kernel•org>
Cc: devicetree@vger•kernel.org, linux-kernel@vger•kernel.org,
Jonathan Hunter <jonathanh@nvidia•com>,
Nagarjuna Kristam <nkristam@nvidia•com>,
linux-tegra@vger•kernel.org,
Sowjanya Komatineni <skomatineni@nvidia•com>,
kernel-team@android•com, linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] arm64: tegra: Fix GIC400 missing GICH/GICV register regions
Date: Tue, 10 Nov 2020 18:39:11 +0100 [thread overview]
Message-ID: <20201110173911.GC2297135@ulmo> (raw)
In-Reply-To: <20201005133256.1390543-1-maz@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 666 bytes --]
On Mon, Oct 05, 2020 at 02:32:56PM +0100, Marc Zyngier wrote:
> GIC400 has full support for virtualization, and yet the tegra186
> DT doesn't expose the GICH/GICV regions (despite exposing the
> maintenance interrupt that only makes sense for virtualization).
>
> Add the missing regions, based on the hunch that the HW doesn't
> use the CPU build-in interfaces, but instead the external ones
> provided by the GIC. KVM's virtual GIC now works with this change.
>
> Signed-off-by: Marc Zyngier <maz@kernel•org>
> ---
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied, thanks.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-10 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 13:32 [PATCH] arm64: tegra: Fix GIC400 missing GICH/GICV register regions Marc Zyngier
2020-11-10 17:39 ` Thierry Reding [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=20201110173911.GC2297135@ulmo \
--to=thierry.reding@gmail$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=jonathanh@nvidia$(echo .)com \
--cc=kernel-team@android$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-tegra@vger$(echo .)kernel.org \
--cc=maz@kernel$(echo .)org \
--cc=nkristam@nvidia$(echo .)com \
--cc=skomatineni@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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