qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Dongjiu Geng <gengdongjiu@huawei.com>
Cc: Andrew Jones <drjones@redhat.com>,
	Shannon Zhao <shannon.zhaosl@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	Zheng Xiang <zhengxiang9@huawei.com>
Subject: Re: [Qemu-devel] [PATCH RFC v11 2/2] target/arm: Add support for VCPU event states
Date: Tue, 16 Oct 2018 15:05:45 +0100	[thread overview]
Message-ID: <CAFEAcA83hcHqsZRzn8+PiVCTyQT=H_uXubxZPU=0H+tycoia-g@mail.gmail.com> (raw)
In-Reply-To: <1538067351-23931-3-git-send-email-gengdongjiu@huawei.com>

On 27 September 2018 at 17:55, Dongjiu Geng <gengdongjiu@huawei.com> wrote:
> This patch extends the qemu-kvm state sync logic with support for
> KVM_GET/SET_VCPU_EVENTS, giving access to yet missing SError exception.
> And also it can support the exception state migration.
>
> The SError exception states include SError pending state and ESR value,
> the kvm_put/get_vcpu_events() will be called when set or get system
> registers. When do migration, if source machine has SError pending,
> QEMU will do this migration regardless whether the target machine supports
> to specify guest ESR value, because if target machine does not support that,
> it can also inject the SError with zero ESR value.
>
> Signed-off-by: Dongjiu Geng <gengdongjiu@huawei.com>

Reviewed-by: Peter Maydell <peter.maydell@linaro.org>

thanks
-- PMM

  parent reply	other threads:[~2018-10-16 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1538067351-23931-1-git-send-email-gengdongjiu@huawei.com>
2018-10-16 12:57 ` [Qemu-devel] [PATCH RFC v11 0/2] add support for VCPU event states Peter Maydell
2018-10-18  9:38   ` gengdongjiu
     [not found]   ` <5bc854f3.1c69fb81.c9089.8940SMTPIN_ADDED_BROKEN@mx.google.com>
2018-10-18 16:31     ` Peter Maydell
     [not found] ` <1538067351-23931-3-git-send-email-gengdongjiu@huawei.com>
2018-10-04 13:40   ` [Qemu-devel] [PATCH RFC v11 2/2] target/arm: Add " Andrew Jones
2018-10-16 14:05   ` Peter Maydell [this message]
     [not found] ` <1538067351-23931-2-git-send-email-gengdongjiu@huawei.com>
2018-10-16 14:06   ` [Qemu-devel] [PATCH RFC v11 1/2] linux-headers: Update to linux kernel 4.19-rc5 Peter Maydell

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='CAFEAcA83hcHqsZRzn8+PiVCTyQT=H_uXubxZPU=0H+tycoia-g@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=drjones@redhat.com \
    --cc=gengdongjiu@huawei.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhaosl@gmail.com \
    --cc=zhengxiang9@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).