public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Sumit Gupta <sumitg@nvidia.com>,
	treding@nvidia.com, krzysztof.kozlowski@linaro.org,
	mark.rutland@arm.com, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org, amhetre@nvidia.com,
	bbasu@nvidia.com
Subject: Re: [Patch] memory: tegra: Skip SID override from Guest VM
Date: Tue, 06 Feb 2024 12:54:48 +0000	[thread overview]
Message-ID: <86ttml69d3.wl-maz@kernel.org> (raw)
In-Reply-To: <c7e71e7e-ef01-4539-b481-9f4a95e6a444@nvidia.com>

On Tue, 06 Feb 2024 12:51:35 +0000,
Jon Hunter <jonathanh@nvidia.com> wrote:
> 
> 
> On 06/02/2024 12:28, Jon Hunter wrote:
> 
> ...
> 
> >> - My own tegra186 HW doesn't have VHE, since it is ARMv8.0, and this
> >>    helper will always return 'false'. How could this result in
> >>    something that still works? Can I get a free CPU upgrade?
> > 
> > I thought this API just checks to see if we are in EL2?
> 
> 
> Sorry to add a bit more info, I see EL2 is used for hypervisor [0],
> but on my Tegra186 with no hypervisor I see ...
> 
>  CPU: All CPU(s) started at EL2

Yes. and yet the kernel runs at EL1 (on ARMv8.0, we can't run the
kernel at EL2 at all).

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2024-02-06 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 11:48 [Patch] memory: tegra: Skip SID override from Guest VM Sumit Gupta
2024-02-06 12:00 ` Krzysztof Kozlowski
2024-02-06 12:08 ` Mark Rutland
2024-02-06 12:17 ` Marc Zyngier
2024-02-06 12:28   ` Jon Hunter
2024-02-06 12:51     ` Jon Hunter
2024-02-06 12:54       ` Marc Zyngier [this message]
2024-02-06 12:53     ` Marc Zyngier
2024-02-06 14:07       ` Thierry Reding
2024-02-06 14:54         ` Marc Zyngier
2024-02-06 17:08           ` Thierry Reding
2024-02-07 12:03             ` Marc Zyngier

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=86ttml69d3.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=amhetre@nvidia.com \
    --cc=bbasu@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=sumitg@nvidia.com \
    --cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox