From: Avi Kivity <avi@redhat.com>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
kvm@vger.kernel.org, Amit Shah <amit.shah@redhat.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"Yang, Sheng" <sheng.yang@intel.com>,
benami@il.ibm.com, muli@il.ibm.com, "Woodhouse,
David" <david.woodhouse@intel.com>,
"Barnes, Jesse" <jesse.barnes@intel.com>
Subject: Re: [PATCH] [RESEND] VT-d: Support multiple device assignment to one guest
Date: Fri, 10 Oct 2008 08:40:12 +0200 [thread overview]
Message-ID: <48EEF8CC.5000309@redhat.com> (raw)
In-Reply-To: <0122C7C995D32147B66BF4F440D3016301D55E1A@pdsmsx415.ccr.corp.intel.com>
Han, Weidong wrote:
> It's hard to move kvm_vtd_domain inside current iommu API. It's kvm
> specific. It's not elegant to include kvm_vtd_domain stuffs in native
> VT-d code.
It's cleaner than adding knowledge of how the iommu works to kvm.
> I think leave it in kvm side is more clean at this point.
> Moveover it's very simple. I read Joerg's iommu API foils just now, I
> think it's good. Native AMD iommu code will be in 2.6.28, it's a
> suitable to implement a generic iommu API based both on Intel and AMD
> iommu for kvm after 2.6.28. What's your opinion?
>
2.6.27 is out, so anything we do will be for 2.6.29.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-10-10 6:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 6:38 [PATCH] [RESEND] VT-d: Support multiple device assignment to one guest Han, Weidong
2008-10-07 10:04 ` Zhang, Xiantao
2008-10-07 13:59 ` Avi Kivity
2008-10-08 1:58 ` Zhang, Xiantao
2008-10-07 13:29 ` Avi Kivity
2008-10-08 5:40 ` Han, Weidong
2008-10-08 10:32 ` Avi Kivity
2008-10-08 15:06 ` Han, Weidong
2008-10-08 19:49 ` Avi Kivity
2008-10-09 6:11 ` Han, Weidong
2008-10-09 8:31 ` Avi Kivity
2008-10-09 9:25 ` Han, Weidong
2008-10-09 12:50 ` Avi Kivity
2008-10-09 14:31 ` Han, Weidong
[not found] ` <0122C7C995D32147B66BF4F440D3016301CB08EF@pdsmsx415.ccr.corp.intel.com>
2008-10-10 5:50 ` Han, Weidong
2008-10-10 6:40 ` Avi Kivity [this message]
2008-10-10 7:22 ` Han, Weidong
2008-10-10 7:32 ` Avi Kivity
2008-10-10 7:50 ` Han, Weidong
2008-10-29 10:25 ` Joerg Roedel
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=48EEF8CC.5000309@redhat.com \
--to=avi@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@redhat.com \
--cc=benami@il.ibm.com \
--cc=david.woodhouse@intel.com \
--cc=jesse.barnes@intel.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=sheng.yang@intel.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).