From: Marc Zyngier <maz@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, kernel-team@android.com,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
Date: Sat, 06 Mar 2021 10:54:47 +0000 [thread overview]
Message-ID: <877dmksgaw.wl-maz@kernel.org> (raw)
In-Reply-To: <20210305190708.GL23855@arm.com>
On Fri, 05 Mar 2021 19:07:09 +0000,
Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Wed, Mar 03, 2021 at 04:45:05PM +0000, Marc Zyngier wrote:
> > It recently became apparent that the ARMv8 architecture has interesting
> > rules regarding attributes being used when fetching instructions
> > if the MMU is off at Stage-1.
> >
> > In this situation, the CPU is allowed to fetch from the PoC and
> > allocate into the I-cache (unless the memory is mapped with
> > the XN attribute at Stage-2).
>
> Digging through the ARM ARM is hard. Do we have this behaviour with FWB
> as well?
The ARM ARM doesn't seem to mention FWB at all when it comes to
instruction fetch, which is sort of expected as it only covers the
D-side. I *think* we could sidestep this when CTR_EL0.DIC is set
though, as the I-side would then snoop the D-side.
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
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel-team@android.com, James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
Date: Sat, 06 Mar 2021 10:54:47 +0000 [thread overview]
Message-ID: <877dmksgaw.wl-maz@kernel.org> (raw)
In-Reply-To: <20210305190708.GL23855@arm.com>
On Fri, 05 Mar 2021 19:07:09 +0000,
Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Wed, Mar 03, 2021 at 04:45:05PM +0000, Marc Zyngier wrote:
> > It recently became apparent that the ARMv8 architecture has interesting
> > rules regarding attributes being used when fetching instructions
> > if the MMU is off at Stage-1.
> >
> > In this situation, the CPU is allowed to fetch from the PoC and
> > allocate into the I-cache (unless the memory is mapped with
> > the XN attribute at Stage-2).
>
> Digging through the ARM ARM is hard. Do we have this behaviour with FWB
> as well?
The ARM ARM doesn't seem to mention FWB at all when it comes to
instruction fetch, which is sort of expected as it only covers the
D-side. I *think* we could sidestep this when CTR_EL0.DIC is set
though, as the I-side would then snoop the D-side.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel-team@android.com, James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
Date: Sat, 06 Mar 2021 10:54:47 +0000 [thread overview]
Message-ID: <877dmksgaw.wl-maz@kernel.org> (raw)
In-Reply-To: <20210305190708.GL23855@arm.com>
On Fri, 05 Mar 2021 19:07:09 +0000,
Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Wed, Mar 03, 2021 at 04:45:05PM +0000, Marc Zyngier wrote:
> > It recently became apparent that the ARMv8 architecture has interesting
> > rules regarding attributes being used when fetching instructions
> > if the MMU is off at Stage-1.
> >
> > In this situation, the CPU is allowed to fetch from the PoC and
> > allocate into the I-cache (unless the memory is mapped with
> > the XN attribute at Stage-2).
>
> Digging through the ARM ARM is hard. Do we have this behaviour with FWB
> as well?
The ARM ARM doesn't seem to mention FWB at all when it comes to
instruction fetch, which is sort of expected as it only covers the
D-side. I *think* we could sidestep this when CTR_EL0.DIC is set
though, as the I-side would then snoop the D-side.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-03-06 10:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 16:45 [PATCH] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM Marc Zyngier
2021-03-03 16:45 ` Marc Zyngier
2021-03-03 16:45 ` Marc Zyngier
2021-03-05 19:07 ` Catalin Marinas
2021-03-05 19:07 ` Catalin Marinas
2021-03-05 19:07 ` Catalin Marinas
2021-03-06 10:54 ` Marc Zyngier [this message]
2021-03-06 10:54 ` Marc Zyngier
2021-03-06 10:54 ` Marc Zyngier
2021-03-06 14:15 ` Catalin Marinas
2021-03-06 14:15 ` Catalin Marinas
2021-03-06 14:15 ` Catalin Marinas
2021-03-08 16:53 ` Alexandru Elisei
2021-03-08 16:53 ` Alexandru Elisei
2021-03-08 16:53 ` Alexandru Elisei
2021-03-08 20:03 ` Marc Zyngier
2021-03-08 20:03 ` Marc Zyngier
2021-03-08 20:03 ` Marc Zyngier
2021-03-09 17:07 ` Alexandru Elisei
2021-03-09 17:07 ` Alexandru Elisei
2021-03-09 17:07 ` Alexandru Elisei
2021-03-09 13:26 ` Will Deacon
2021-03-09 13:26 ` Will Deacon
2021-03-09 13:26 ` Will Deacon
2021-03-09 14:38 ` Catalin Marinas
2021-03-09 14:38 ` Catalin Marinas
2021-03-09 14:38 ` Catalin Marinas
2021-03-09 18:01 ` Marc Zyngier
2021-03-09 18:01 ` Marc Zyngier
2021-03-09 18:01 ` 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=877dmksgaw.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--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.