Virtuozzo QEMU development (svt-core@virtuozzo.com)
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>, andrey.drobyshev@virtuozzo.com
Cc: svt-core@virtuozzo.com
Subject: Re: [PATCH hci-8.1 1/1] target/i386/kvm: fix latched INIT lost in kvm_put_vcpu_events() #VSTOR-153069
Date: Tue, 3 Nov 2026 22:28:25 +0100	[thread overview]
Message-ID: <762129ef-da3b-4d15-a1ee-41b3afc9319b@virtuozzo.com> (raw)
In-Reply-To: <20261103181817.834166-1-den@openvz.org>

On 11/3/26 19:18, Denis V. Lunev wrote:
> From: Denis V. Lunev <den@openvz.org>
>
> CPU_INTERRUPT_INIT is 0x0400, while kvm_vcpu_events.smi.latched_init
> is a __u8. The assignment truncates the masked value to 0, so every
> KVM_SET_VCPU_EVENTS tells KVM to clear an INIT it has latched for a
> vCPU in SMM. smi.pending survives only because CPU_INTERRUPT_SMI is
> 0x0040; normalize both with !! like the neighbouring fields.
>
> Fixes: fc12d72e1082 ("target-i386: add support for SMBASE MSR and SMIs")
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> ---
>  target/i386/kvm/kvm.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/kvm/kvm.c b/target/i386/kvm/kvm.c
> index 8dc0f134990..6efe0e6b308 100644
> --- a/target/i386/kvm/kvm.c
> +++ b/target/i386/kvm/kvm.c
> @@ -5124,8 +5124,9 @@ static int kvm_put_vcpu_events(X86CPU *cpu, int level)
>              /* As soon as these are moved to the kernel, remove them
>               * from cs->interrupt_request.
>               */
> -            events.smi.pending = cs->interrupt_request & CPU_INTERRUPT_SMI;
> -            events.smi.latched_init = cs->interrupt_request & CPU_INTERRUPT_INIT;
> +            events.smi.pending = !!(cs->interrupt_request & CPU_INTERRUPT_SMI);
> +            events.smi.latched_init =
> +                !!(cs->interrupt_request & CPU_INTERRUPT_INIT);
>              cs->interrupt_request &= ~(CPU_INTERRUPT_INIT | CPU_INTERRUPT_SMI);
>          } else {
>              /* Keep these in cs->interrupt_request.  */
queued mainstream by Paolo

  parent reply	other threads:[~2026-11-03 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 18:18 Denis V. Lunev
2026-11-03 18:20 ` no-reply
2026-11-03 21:28 ` Denis V. Lunev [this message]
2026-11-04 11:58 ` Andrey Drobyshev

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=762129ef-da3b-4d15-a1ee-41b3afc9319b@virtuozzo.com \
    --to=den@virtuozzo.com \
    --cc=andrey.drobyshev@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=svt-core@virtuozzo.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