From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] qemu-kvm: x86: Add support for VCPU event states
Date: Sun, 15 Nov 2009 15:56:12 +0200 [thread overview]
Message-ID: <4B00087C.4060007@redhat.com> (raw)
In-Reply-To: <4AFB515D.1030202@web.de>
On 11/12/2009 02:05 AM, Jan Kiszka wrote:
> This patch extends the qemu-kvm state sync logic with support for
> KVM_GET/SET_VCPU_EVENTS, giving access to yet missing exception,
> interrupt and NMI states.
>
> diff --git a/target-i386/machine.c b/target-i386/machine.c
> index 6bd447f..1eda7c5 100644
> --- a/target-i386/machine.c
> +++ b/target-i386/machine.c
> @@ -452,6 +452,11 @@ static const VMStateDescription vmstate_cpu = {
> VMSTATE_INT32_V(interrupt_injected, CPUState, 9),
> VMSTATE_UINT32_V(mp_state, CPUState, 9),
> VMSTATE_UINT64_V(tsc, CPUState, 9),
> + VMSTATE_UINT8_V(soft_interrupt, CPUState, 11),
> + VMSTATE_UINT8_V(nmi_injected, CPUState, 11),
> + VMSTATE_UINT8_V(nmi_pending, CPUState, 11),
> + VMSTATE_UINT8_V(has_error_code, CPUState, 11),
> + VMSTATE_UINT32_V(sipi_vector, CPUState, 11),
> /* MCE */
> VMSTATE_UINT64_V(mcg_cap, CPUState, 10),
> VMSTATE_UINT64_V(mcg_status, CPUState, 10),
>
>
Is there a reason why you add 11 between 9 and 10? We'll probably see
another 11 when someone else adds the next state.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-15 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 0:04 [PATCH 1/2] qemu-kvm: x86: Refactor use of interrupt_bitmap Jan Kiszka
2009-11-12 0:05 ` [PATCH 2/2] qemu-kvm: x86: Add support for VCPU event states Jan Kiszka
2009-11-15 13:56 ` Avi Kivity [this message]
2009-11-15 14:21 ` Jan Kiszka
2009-11-15 14:27 ` Avi Kivity
2009-11-15 14:31 ` Jan Kiszka
2009-11-15 14:38 ` Avi Kivity
2009-11-15 15:02 ` Jan Kiszka
2009-11-15 15:10 ` Avi Kivity
2009-11-15 15:41 ` Jan Kiszka
2009-11-15 15:50 ` Avi Kivity
2009-11-24 14:15 ` Avi Kivity
2009-11-24 22:08 ` Marcelo Tosatti
2009-12-10 20:23 ` Marcelo Tosatti
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=4B00087C.4060007@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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