From: 'Joerg Roedel' <joro@8bytes.org>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: "Woodhouse, David" <david.woodhouse@intel.com>,
'Jesse Barnes' <jbarnes@virtuousgeek.org>,
'Avi Kivity' <avi@redhat.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
'Mark McLoughlin' <markmc@redhat.com>,
"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>,
"'iommu@lists.linux-foundation.org'"
<iommu@lists.linux-foundation.org>
Subject: Re: [PATCH 0/17] [v4] Support VT-d multiple device assignment for KVM
Date: Mon, 8 Dec 2008 21:18:04 +0100 [thread overview]
Message-ID: <20081208201803.GC18346@8bytes.org> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C018BF4DC9F@pdsmsx503.ccr.corp.intel.com>
Great. I rebased the IOMMU API and AMD IOMMU support patches and pushed
them out to kernel.org. I will also do a post of them.
On Tue, Dec 09, 2008 at 12:01:52AM +0800, Han, Weidong wrote:
> This patchset supports VT-d multiple device assignment for KVM.
>
> Main changes from V3 to V4:
> - rebase intel iommu patches to dave's iommu-2.6 tree, KVM patches are still based on avi/master tree
> - fix a potential infinite loop in vm_domain_remove_one_dev_info
> - add a spin lock to protect iommu setting in domain
> - fix most of comments from Mark, but some comments are not adopted. I still use iommu bitmap, because it's simple, and iommu list is not more complex to implement. Additionally, I still separate some functions for virtual machine domain, because i think mixing many flag judgments in common functions makes things complex, and hard to maintain.
> - On KVM side, assign device in kvm_free_assigned_device, because In kvm_iommu_unmap_memslots(), assigned_dev_head is already empty.
>
>
> Regards,
> Weidong
prev parent reply other threads:[~2008-12-08 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 16:01 [PATCH 0/17] [v4] Support VT-d multiple device assignment for KVM Han, Weidong
2008-12-08 20:18 ` 'Joerg Roedel' [this message]
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=20081208201803.GC18346@8bytes.org \
--to=joro@8bytes.org \
--cc=allen.m.kay@intel.com \
--cc=avi@redhat.com \
--cc=david.woodhouse@intel.com \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.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;
as well as URLs for NNTP newsgroup(s).