From: Paolo Bonzini <pbonzini@redhat.com>
To: Lara Lazier <laramglazier@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] target/i386: Added consistency checks for event injection
Date: Wed, 28 Jul 2021 11:26:16 +0200 [thread overview]
Message-ID: <eb892c47-2e9a-f5ed-37f6-c6253b5e4ed8@redhat.com> (raw)
In-Reply-To: <20210725090855.19713-1-laramglazier@gmail.com>
On 25/07/21 11:08, Lara Lazier wrote:
> VMRUN exits with SVM_EXIT_ERR if either:
> * The event injected has a reserved type.
> * When the event injected is of type 3 (exception), and the vector that
> has been specified does not correspond to an exception.
>
> This does not fix the entire exc_inj test in kvm-unit-tests.
>
> Signed-off-by: Lara Lazier <laramglazier@gmail.com>
> ---
> target/i386/tcg/sysemu/svm_helper.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/target/i386/tcg/sysemu/svm_helper.c b/target/i386/tcg/sysemu/svm_helper.c
> index a61aa23017..70d5c2e35d 100644
> --- a/target/i386/tcg/sysemu/svm_helper.c
> +++ b/target/i386/tcg/sysemu/svm_helper.c
> @@ -395,6 +395,9 @@ void helper_vmrun(CPUX86State *env, int aflag, int next_eip_addend)
> cpu_loop_exit(cs);
> break;
> case SVM_EVTINJ_TYPE_EXEPT:
> + if (vector == EXCP02_NMI || vector >= 31) {
> + cpu_vmexit(env, SVM_EXIT_ERR, 0, GETPC());
> + }
> cs->exception_index = vector;
> env->error_code = event_inj_err;
> env->exception_is_int = 0;
> @@ -410,6 +413,9 @@ void helper_vmrun(CPUX86State *env, int aflag, int next_eip_addend)
> qemu_log_mask(CPU_LOG_TB_IN_ASM, "SOFT");
> cpu_loop_exit(cs);
> break;
> + default:
> + cpu_vmexit(env, SVM_EXIT_ERR, 0, GETPC());
> + break;
> }
> qemu_log_mask(CPU_LOG_TB_IN_ASM, " %#x %#x\n", cs->exception_index,
> env->error_code);
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-07-28 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 9:08 [PATCH] target/i386: Added consistency checks for event injection Lara Lazier
2021-07-28 9:26 ` Paolo Bonzini [this message]
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=eb892c47-2e9a-f5ed-37f6-c6253b5e4ed8@redhat.com \
--to=pbonzini@redhat.com \
--cc=laramglazier@gmail.com \
--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).