All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Marc Zyngier <maz@kernel.org>
Cc: kernel-team@android.com,
	Catalin Marinas <catalin.marinas@arm.com>,
	James Morse <james.morse@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Will Deacon <will@kernel.org>,
	Julien Thierry <julien.thierry.kdev@gmail.com>
Subject: Re: [PATCH] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
Date: Tue,  9 Mar 2021 18:01:05 +0000	[thread overview]
Message-ID: <161531284779.3772144.1323992258111335863.b4-ty@kernel.org> (raw)
In-Reply-To: <20210303164505.68492-1-maz@kernel.org>

On Wed, 3 Mar 2021 16:45:05 +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).
> 
> [...]

Applied to fixes, thanks!

[1/1] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
      commit: 01dc9262ff5797b675c32c0c6bc682777d23de05

Cheers,

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



WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	kernel-team@android.com
Subject: Re: [PATCH] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
Date: Tue,  9 Mar 2021 18:01:05 +0000	[thread overview]
Message-ID: <161531284779.3772144.1323992258111335863.b4-ty@kernel.org> (raw)
In-Reply-To: <20210303164505.68492-1-maz@kernel.org>

On Wed, 3 Mar 2021 16:45:05 +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).
> 
> [...]

Applied to fixes, thanks!

[1/1] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
      commit: 01dc9262ff5797b675c32c0c6bc682777d23de05

Cheers,

	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: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Marc Zyngier <maz@kernel.org>
Cc: kernel-team@android.com,
	Catalin Marinas <catalin.marinas@arm.com>,
	James Morse <james.morse@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Will Deacon <will@kernel.org>,
	Julien Thierry <julien.thierry.kdev@gmail.com>
Subject: Re: [PATCH] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
Date: Tue,  9 Mar 2021 18:01:05 +0000	[thread overview]
Message-ID: <161531284779.3772144.1323992258111335863.b4-ty@kernel.org> (raw)
In-Reply-To: <20210303164505.68492-1-maz@kernel.org>

On Wed, 3 Mar 2021 16:45:05 +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).
> 
> [...]

Applied to fixes, thanks!

[1/1] KVM: arm64: Ensure I-cache isolation between vcpus of a same VM
      commit: 01dc9262ff5797b675c32c0c6bc682777d23de05

Cheers,

	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

  parent reply	other threads:[~2021-03-09 18:01 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
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 [this message]
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=161531284779.3772144.1323992258111335863.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=julien.thierry.kdev@gmail.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=mark.rutland@arm.com \
    --cc=suzuki.poulose@arm.com \
    --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.