From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 0/7] Consolidate vcpu ioctl locking
Date: Thu, 13 May 2010 12:29:51 +0000 [thread overview]
Message-ID: <4BEBF0BF.2020404@redhat.com> (raw)
In-Reply-To: <1273749459-622-1-git-send-email-avi@redhat.com>
On 05/13/2010 03:18 PM, Alexander Graf wrote:
>
>> [PATCH 0/7] Consolidate vcpu ioctl locking
>>
>> In general, all vcpu ioctls need to take the vcpu mutex, but each one does it
>> (or not) individually. This is cumbersome and error prone.
>>
>> This patchset moves all locking to a central place. This is complicated
>> by the fact that ppc's KVM_INTERRUPT and s390's KVM_S390_INTERRUPT break
>> the convention and need to run unlocked.
>>
> Why is the x86 non-kernel-pic path different?
>
Userspace issues the ioctl from a vcpu thread.
It has to, btw, since whether an interrupt can be injected or not
depends on vcpu-synchronous registers: eflags.if and tpr/cr8.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-05-13 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 11:17 [PATCH 0/7] Consolidate vcpu ioctl locking Avi Kivity
2010-05-13 11:57 ` Alexander Graf
2010-05-13 12:01 ` Avi Kivity
2010-05-13 12:03 ` Avi Kivity
2010-05-13 12:03 ` Avi Kivity
2010-05-13 12:18 ` Alexander Graf
2010-05-13 12:29 ` Avi Kivity [this message]
2010-05-13 19:49 ` Alexander Graf
2010-05-15 17:30 ` Avi Kivity
2010-05-16 1:00 ` Alexander Graf
2010-05-16 8:23 ` Avi Kivity
2010-05-16 9:01 ` Alexander Graf
2010-05-16 9:09 ` Avi Kivity
2010-05-16 9:35 ` Alexander Graf
2010-05-16 9:47 ` Avi Kivity
2010-05-16 10:19 ` Alexander Graf
2010-05-21 7:35 ` Carsten Otte
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=4BEBF0BF.2020404@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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