On Sat, Oct 01, 2016 at 08:57:05AM +0200, Jan Kiszka wrote:
> I was actually looking for and reading something else when I stumbled
> over "hypercall" in that comment: If AArch64 has a strict need for
> *HVC* based PSCI.
Yes, in some cases. On platforms without the security extensions, HVC
must
On Wed, Nov 23, 2016 at 01:52:22PM +0100, Ralf Ramsauer wrote:
> Hi,
>
> I first noticed that on the LeMaker Hikey: After jailhouse is
> (successfully) enabled, the CPU board gets incredibly hot (after a few
> seconds), though the root Linux still idles and no cells are created so
> far. When
On Wed, Apr 05, 2017 at 08:38:52PM +0200, Ralf Ramsauer wrote:
> On 04/05/2017 07:10 PM, Ralf Ramsauer wrote:
> > On 04/05/2017 06:57 PM, Mark Rutland wrote:
> >> It *might* be the case that on Orange Pi, the ldrex generates a PL1
> >> exception that the guest doesn
On Wed, Apr 05, 2017 at 12:38:05PM +0200, Ralf Ramsauer wrote:
> Hi,
Hi,
> I need spinlocks in inmates on ARM, so I simply included asm/spinlock.h.
> Taking locks in inmates on ARM somehow doesn't work at all, but that's
> not the main issue. As soon as I try to take locks, cells can not be
>
On Tue, May 02, 2017 at 06:08:49PM +0200, Ralf Ramsauer wrote:
> Hi,
>
> is there a way on ARM to find out on which physical CPU I'm currently
> running on?
>
> I need this information for interrupt routing. (In Jailhouse) GIC's
> ITARGETSR expects physical CPU IDs. Of course I could statically
On Mon, Jul 22, 2019 at 09:19:50AM +0200, von Wiarda, Jan wrote:
> Hi all,
>
> we implemented support for Jailhouse 32 bit inmates running on 64-bit
> Jailhouse on the i.MX 8M Mini and it works fine, GIC demo runs without
> problems. Now I have one problem, that just occurred. I'm trying to
> get
