All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu, Andrew Scull <ascull@google.com>
Cc: will@kernel.org, kernel-team@android.com, catalin.marinas@arm.com
Subject: Re: [PATCH] KVM: arm64: Fix nVHE hyp panic host context restore
Date: Tue,  2 Mar 2021 18:57:09 +0000	[thread overview]
Message-ID: <161471117620.3770794.15315149295499752217.b4-ty@kernel.org> (raw)
In-Reply-To: <20210219122406.1337626-1-ascull@google.com>

On Fri, 19 Feb 2021 12:24:06 +0000, Andrew Scull wrote:
> When panicking from the nVHE hyp and restoring the host context, x29 is
> expected to hold a pointer to the host context. This wasn't being done
> so fix it to make sure there's a valid pointer the host context being
> used.
> 
> Rather than passing a boolean indicating whether or not the host context
> should be restored, instead pass the pointer to the host context. NULL
> is passed to indicate that no context should be restored.

Applied to kvmarm-master/fixes, thanks!

[1/1] KVM: arm64: Fix nVHE hyp panic host context restore
      commit: ff9b922a28554de61b9dc36578db77d6720c652a

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

  reply	other threads:[~2021-03-02 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 12:24 [PATCH] KVM: arm64: Fix nVHE hyp panic host context restore Andrew Scull
2021-03-02 18:57 ` Marc Zyngier [this message]
2021-03-15 12:21 Andrew Scull
2021-03-15 12:21 ` Andrew Scull
2021-03-15 12:38 ` Greg KH
2021-03-15 12:38   ` Greg KH
2021-03-15 12:22 Andrew Scull
2021-03-15 12:22 ` Andrew Scull

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=161471117620.3770794.15315149295499752217.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --cc=ascull@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --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.