From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] KVM: x86: Add VCPU substate for event states
Date: Wed, 04 Nov 2009 14:51:33 +0200 [thread overview]
Message-ID: <4AF178D5.2040008@redhat.com> (raw)
In-Reply-To: <4AF166C4.9080802@siemens.com>
On 11/04/2009 01:34 PM, Jan Kiszka wrote:
>
>> we're missing has_error_code here.
>>
>>
> Isn't it statically defined by the arch? exception_has_error_code()
> regenerates it (just like user land does).
>
In real mode exceptions lose their error code, so we have to look at
cr0, and now we depend on the order of loading of state...
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-04 12:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 16:20 [PATCH v3 0/4] Extensible VCPU state IOCTL Jan Kiszka
2009-11-02 16:20 ` [PATCH v3 1/4] KVM: Reorder IOCTLs in main kvm.h Jan Kiszka
2009-11-10 10:17 ` Avi Kivity
2009-11-02 16:20 ` [PATCH v3 3/4] KVM: x86: Add support for KVM_GET/SET_VCPU_STATE Jan Kiszka
2009-11-02 16:20 ` [PATCH v3 2/4] KVM: Add unified KVM_GET/SET_VCPU_STATE IOCTL Jan Kiszka
2009-11-04 11:18 ` Avi Kivity
2009-11-04 11:35 ` Jan Kiszka
2009-11-04 12:52 ` Avi Kivity
2009-11-10 10:14 ` Avi Kivity
2009-11-10 12:03 ` Jan Kiszka
2009-11-10 12:57 ` Avi Kivity
2009-11-10 13:22 ` Jan Kiszka
2009-11-10 13:31 ` Avi Kivity
2009-11-10 13:41 ` Jan Kiszka
2009-11-02 16:20 ` [PATCH v3 4/4] KVM: x86: Add VCPU substate for event states Jan Kiszka
2009-11-04 11:23 ` Avi Kivity
2009-11-04 11:34 ` Jan Kiszka
2009-11-04 12:51 ` Avi Kivity [this message]
2009-11-04 14:44 ` Jan Kiszka
2009-11-05 8:25 ` [PATCH v4 " Jan Kiszka
2009-11-05 11:00 ` Gleb Natapov
2009-11-05 11:51 ` [PATCH v5 " Jan Kiszka
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=4AF178D5.2040008@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.