public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm64: add esr_el2 and far_el2 to sysreg
Date: Mon, 07 Aug 2017 17:59:05 +0100	[thread overview]
Message-ID: <59889C59.80207@arm.com> (raw)
In-Reply-To: <b834276b-b47d-51fb-7661-3eb5a2f6a68d@huawei.com>

Hi gengdongjiu,

On 07/08/17 17:23, gengdongjiu wrote:
>   As James's suggestion, I move injection SEA Error logic to the user space(Qemu), Qemu sets the related guest OS esr/elr/pstate/spsr

(because for firmware-first its the CPER records that matter, and only QEMU
knows where it reserved the memory for these, and what it told the guest it
would use as the notification method).

> through IOCTL KVM_SET_ONE_REG. For the SEA, when Qemu sets the esr_el1.IL bit, it needs to refer to esr_el2.IL, else Qemu does not know the trapped
> instruction was a 16-bit or a 32-bit instruction, also it needs to set far_el1 using far_el2, because this is synchronization abort.

The 32bit kernel doesn't support ACPI firmware first, and aarch64 doesn't
support 16-bit instructions.


James

  parent reply	other threads:[~2017-08-07 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 16:08 [PATCH] KVM: arm64: add esr_el2 and far_el2 to sysreg Dongjiu Geng
2017-08-07 15:57 ` Marc Zyngier
2017-08-07 16:23   ` gengdongjiu
2017-08-07 16:56     ` Marc Zyngier
2017-08-07 18:59       ` gengdongjiu
2017-08-07 16:59     ` James Morse [this message]
2017-08-07 17:43       ` gengdongjiu
2017-08-08 16:27         ` James Morse
2017-08-08 18:27           ` gengdongjiu

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=59889C59.80207@arm.com \
    --to=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox