All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Russell King <linux@armlinux.org.uk>
Cc: marc.zyngier@arm.com, Robin Murphy <robin.murphy@arm.com>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] kvm: arm: Enforce some NS-SVC initialisation
Date: Tue, 6 Sep 2016 18:41:45 +0200	[thread overview]
Message-ID: <20160906164145.GD23592@cbox> (raw)
In-Reply-To: <20160817113249.GA5909@cbox>

On Wed, Aug 17, 2016 at 01:32:49PM +0200, Christoffer Dall wrote:
> Hi Russell,
> 
> On Tue, Aug 16, 2016 at 06:49:18PM +0100, Robin Murphy wrote:
> > Since the non-secure copies of banked registers lack architecturally
> > defined reset values, there is no actual guarantee when entering in Hyp
> > from secure-only firmware that the Non-Secure PL1 state will look the
> > way that kernel entry (in particular the decompressor stub) expects.
> > So far, we've been getting away with it thanks to implementation details
> > of ARMv7 cores and/or bootloader behaviour, but for the sake of forwards
> > compatibility let's try to ensure that we have a minimally sane state
> > before dropping down into it.
> > 
> > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> 
> Can we have your acked-by on this patch to merge it via the KVM tree or
> do you prefer merging this one directly yourself?
> 
I have queued this via the KVM/ARM tree.  If you have any objections,
please let me know asap.

Thanks,
-Christoffer

WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] kvm: arm: Enforce some NS-SVC initialisation
Date: Tue, 6 Sep 2016 18:41:45 +0200	[thread overview]
Message-ID: <20160906164145.GD23592@cbox> (raw)
In-Reply-To: <20160817113249.GA5909@cbox>

On Wed, Aug 17, 2016 at 01:32:49PM +0200, Christoffer Dall wrote:
> Hi Russell,
> 
> On Tue, Aug 16, 2016 at 06:49:18PM +0100, Robin Murphy wrote:
> > Since the non-secure copies of banked registers lack architecturally
> > defined reset values, there is no actual guarantee when entering in Hyp
> > from secure-only firmware that the Non-Secure PL1 state will look the
> > way that kernel entry (in particular the decompressor stub) expects.
> > So far, we've been getting away with it thanks to implementation details
> > of ARMv7 cores and/or bootloader behaviour, but for the sake of forwards
> > compatibility let's try to ensure that we have a minimally sane state
> > before dropping down into it.
> > 
> > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> 
> Can we have your acked-by on this patch to merge it via the KVM tree or
> do you prefer merging this one directly yourself?
> 
I have queued this via the KVM/ARM tree.  If you have any objections,
please let me know asap.

Thanks,
-Christoffer

  reply	other threads:[~2016-09-06 16:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 12:01 [PATCH] kvm: arm: Enforce some NS-SVC initialisation Robin Murphy
2016-07-21 12:01 ` Robin Murphy
2016-08-16 13:33 ` Marc Zyngier
2016-08-16 13:33   ` Marc Zyngier
2016-08-16 14:51   ` Robin Murphy
2016-08-16 14:51     ` Robin Murphy
2016-08-16 17:49 ` [PATCH v2] " Robin Murphy
2016-08-16 17:49   ` Robin Murphy
2016-08-17 10:05   ` Marc Zyngier
2016-08-17 10:05     ` Marc Zyngier
2016-08-17 11:16   ` Christoffer Dall
2016-08-17 11:16     ` Christoffer Dall
2016-08-17 11:17   ` Christoffer Dall
2016-08-17 11:17     ` Christoffer Dall
2016-08-17 11:32   ` Christoffer Dall
2016-08-17 11:32     ` Christoffer Dall
2016-09-06 16:41     ` Christoffer Dall [this message]
2016-09-06 16:41       ` Christoffer Dall
2016-09-06 16:44       ` Robin Murphy
2016-09-06 16:44         ` Robin Murphy
2016-09-06 16:59         ` Christoffer Dall
2016-09-06 16:59           ` Christoffer Dall

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=20160906164145.GD23592@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=marc.zyngier@arm.com \
    --cc=robin.murphy@arm.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 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.