From: Avi Kivity <avi@qumranet.com>
To: Ben-Ami Yassour <benami@il.ibm.com>
Cc: amit.shah@qumranet.com, kvm@vger.kernel.org, muli@il.ibm.com,
weidong.han@intel.com, anthony@codemonkey.ws
Subject: Re: device assignemnt: updated patches
Date: Sat, 26 Jul 2008 12:05:49 +0300 [thread overview]
Message-ID: <488AE8ED.2010301@qumranet.com> (raw)
In-Reply-To: <1216728835-19721-1-git-send-email-benami@il.ibm.com>
Ben-Ami Yassour wrote:
> Following are the device assignment patches with the fixes of the
> comments that were sent for the previous version.
>
> Here is the list of changes that were made with respect to the previous
> version:
> 1. Replace the interrupt ack hook patches with the notifiers list patch
> by Avi.
> 2. Remove code from ioapic - the ack notifier is called before the
> checking the irr bit.
> 3. Remove the interrupt ack work queue and handle it directly.
> 4. Minimize the function for finding an assigned device.
> 5. Remove the pt_lock, after making the changes above it is no longer
> needed.
> 6. Move declarations from kvm_para.h
> 7. Add irq array to ioctl API. Note that this is only a change to the
> API, currently only single irq is supported.
> 8. Renaming: use "assigned device" and not "passthrough device"
> 9. Fix device release error path
> 10. Moving the assigned devices list pointer to the device struct itself
> and remove the extra structure.
>
> Pending comment: shared guest interrputs are not tested.
>
>
(and not implemented, either).
Good progress; there are still many issues, but this is inevitable with
such a large and complex patchset.
How are we standing with merging the changes to the VT-d driver, which
are a prerequisite?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-07-26 9:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 12:13 device assignemnt: updated patches Ben-Ami Yassour
2008-07-22 12:13 ` [PATCH 1/4] KVM: Add irq ack notifier list Ben-Ami Yassour
2008-07-22 12:13 ` [PATCH 2/4] KVM: pci device assignment Ben-Ami Yassour
2008-07-22 12:13 ` [PATCH 3/4] VT-d: changes to support KVM Ben-Ami Yassour
2008-07-22 12:13 ` [PATCH 4/4] KVM: Device assignemnt with VT-d Ben-Ami Yassour
2008-07-22 12:18 ` device assignment - userspace part Ben-Ami Yassour
2008-07-22 12:18 ` [PATCH 1/1] KVM/userspace: Support for assigning PCI devices to guest Ben-Ami Yassour
2008-07-26 9:02 ` [PATCH 4/4] KVM: Device assignemnt with VT-d Avi Kivity
2008-07-28 6:49 ` Han, Weidong
2008-07-28 16:34 ` Ben-Ami Yassour
2008-07-26 8:46 ` [PATCH 2/4] KVM: pci device assignment Avi Kivity
2008-07-28 7:27 ` Yang, Sheng
2008-07-28 16:41 ` Ben-Ami Yassour
2008-07-28 8:33 ` Amit Shah
2008-07-26 8:19 ` [PATCH 1/4] KVM: Add irq ack notifier list Avi Kivity
2008-07-26 9:05 ` Avi Kivity [this message]
2008-07-26 9:24 ` device assignemnt: updated patches Han, Weidong
2008-07-26 9:32 ` Avi Kivity
2008-07-26 9:48 ` Han, Weidong
-- strict thread matches above, loose matches on Subject: below --
2008-07-28 16:26 Device " Ben-Ami Yassour
2008-07-30 15: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=488AE8ED.2010301@qumranet.com \
--to=avi@qumranet.com \
--cc=amit.shah@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=benami@il.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=weidong.han@intel.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