From: gengdongjiu <gengdongjiu@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: patches@linaro.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [RFC] arm: Allow system registers for KVM guests to be changed by QEMU code
Date: Fri, 7 Dec 2018 10:29:24 +0800 [thread overview]
Message-ID: <4c74e17a-840b-e1d9-6dac-71f64a190945@huawei.com> (raw)
In-Reply-To: <20181206151401.13455-1-peter.maydell@linaro.org>
On 2018/12/6 23:14, Peter Maydell wrote:
> ---
> I think this patch:
> * should be necessary for the current KVM debug code to be able
> to actually set the ESR_EL1 for the guest when it wants to
> deliver a breakpoint exception to it
> * will also be necessary for Dongjiu's patchset to inject
> external aborts on memory errors
>
> I have tagged it "RFC" because I don't have a setup to test
> that; I've just given it a quick smoke test that it runs a
> VM OK. Please test this and check whether it really does
> fix the bugs I think it does :-)
Great! thanks Peter follow up this issue and patch to fix it.
I will test it and give response.
>
> Opinions welcome on whether the "try the write-and-read-back"
> approach in write_cpustate_to_list() is too hacky and it
> would be better to actually record whether write_list_to_cpustate()
> succeeded for each register. (That would require another array.)
next prev parent reply other threads:[~2018-12-07 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 15:14 [Qemu-devel] [RFC] arm: Allow system registers for KVM guests to be changed by QEMU code Peter Maydell
2018-12-07 2:29 ` gengdongjiu [this message]
2018-12-10 10:19 ` gengdongjiu
2019-02-13 16:29 ` Alex Bennée
2019-02-13 17:02 ` Peter Maydell
2019-02-13 20:18 ` Alex Bennée
2019-02-14 1:10 ` gengdongjiu
2019-02-14 11:52 ` Alex Bennée
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=4c74e17a-840b-e1d9-6dac-71f64a190945@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=alex.bennee@linaro.org \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).