From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Document KVM_NMI
Date: Wed, 07 Dec 2011 14:42:54 +0200 [thread overview]
Message-ID: <4EDF5F4E.4080309@redhat.com> (raw)
In-Reply-To: <1323261434.4009.9.camel@lappy>
On 12/07/2011 02:37 PM, Sasha Levin wrote:
> >
> > It's really implied by the fact that vcpu ioctls must be issued from the
> > same thread.
>
> Oh, I totally forgot about that (here, and in my 'kvm nmi' patch).
It keeps biting people. We should make the kernel warn about it.
The reason it's important is because we might some day want to move to a
syscall based API, rather than ioctl based. In this model a vcpu is
bound to the thread that calls kvm_create_vcpu(2), and all vcpu syscalls
derive the vcpu from the thread.
This model is more natural than the ioctl model, however it is a lot of
work and doesn't solve any real life problems; it only creates a larger
compatibility burden. But it's still the right thing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-07 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 10:43 [PATCH] KVM: Document KVM_NMI Avi Kivity
2011-12-07 11:02 ` Sasha Levin
2011-12-07 12:12 ` Avi Kivity
2011-12-07 12:20 ` Sasha Levin
2011-12-07 12:31 ` Avi Kivity
2011-12-07 12:37 ` Sasha Levin
2011-12-07 12:42 ` Avi Kivity [this message]
2011-12-14 18:07 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2011-12-06 20:50 Sasha Levin
2011-12-07 10:21 ` Avi Kivity
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=4EDF5F4E.4080309@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).