From: Avi Kivity <avi@qumranet.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Dor Laor <dor.laor@qumranet.com>, Pavel Machek <pavel@ucw.cz>,
kvm-devel@lists.sourceforge.net, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [PATCH 10/13] KVM: Wire up hypercall handlers to a central arch-independent location
Date: Thu, 22 Feb 2007 12:40:48 +0200 [thread overview]
Message-ID: <45DD7330.1030001@qumranet.com> (raw)
In-Reply-To: <1172140490.3531.236.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>> I have Ingo's network PV hypercalls to commit in my piplien.
>>
>
> I have 5 or so pending as well :)
> can't wait for the infrastructure to be there so that it's relatively
> easy to add my paravirt block driver
>
I can't wait for your pv block driver :)
What do you think is missing? My list has:
- registration of hypercall handlers from modules
- execution of hypercall handlers outside vcpu_load() (so they are
preemptible and sleepable)
- passing unhandled hypercalls to userspace for qemu-based devices
Please do post the patches to kvm-devel, even if they aren't ready, so
we can get a taste of what's coming.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-02-22 10:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 10:20 [PATCH 0/13] kvm updates for 2.6.21 Avi Kivity
2007-02-19 10:21 ` [PATCH 1/13] KVM: mmu: add missing dirty page tracking cases Avi Kivity
2007-02-19 10:22 ` [PATCH 2/13] KVM: Move virtualization deactivation from CPU_DEAD state to CPU_DOWN_PREPARE Avi Kivity
2007-02-19 10:23 ` [PATCH 3/13] KVM: Cosmetics Avi Kivity
2007-02-19 10:24 ` [PATCH 4/13] KVM: vmx: hack set_cr0_no_modeswitch() to actually do modeswitch Avi Kivity
2007-02-19 10:25 ` [PATCH 5/13] KVM: Use ARRAY_SIZE macro instead of manual calculation Avi Kivity
2007-02-19 10:26 ` [PATCH 6/13] KVM: Use page_private()/set_page_private() apis Avi Kivity
2007-02-19 10:27 ` [PATCH 7/13] KVM: add MSR based hypercall API Avi Kivity
2007-02-19 10:28 ` [PATCH 8/13] KVM: Add host hypercall support for vmx Avi Kivity
2007-02-19 10:29 ` [PATCH 9/13] KVM: Add hypercall host support for svm Avi Kivity
2007-02-19 10:30 ` [PATCH 10/13] KVM: Wire up hypercall handlers to a central arch-independent location Avi Kivity
2007-02-21 10:37 ` Pavel Machek
2007-02-22 10:14 ` Avi Kivity
2007-02-22 10:17 ` [kvm-devel] " Dor Laor
2007-02-22 10:22 ` Joerg Roedel
2007-02-22 10:37 ` Avi Kivity
2007-02-22 10:34 ` Arjan van de Ven
2007-02-22 10:40 ` Avi Kivity [this message]
2007-02-22 11:01 ` Arjan van de Ven
2007-02-22 13:04 ` Avi Kivity
2007-02-22 13:12 ` Arjan van de Ven
2007-02-22 13:29 ` Avi Kivity
2007-02-22 14:09 ` Arjan van de Ven
2007-02-22 14:20 ` Avi Kivity
2007-02-23 14:55 ` Anthony Liguori
2007-02-22 13:31 ` [kvm-devel] [PATCH 10/13] KVM: Wire up hypercall handlers toa " Dor Laor
2007-02-19 10:31 ` [PATCH 11/13] KVM: svm: init cr0 with the wp bit set Avi Kivity
2007-02-19 10:32 ` [PATCH 12/13] KVM: SVM: intercept SMI to handle it at host level Avi Kivity
2007-02-19 10:33 ` [PATCH 13/13] KVM: More 0 -> NULL conversions 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=45DD7330.1030001@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dor.laor@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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