public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Amit Shah <amit.shah@qumranet.com>,
	kvm@vger.kernel.org, muli@il.ibm.com, anthony@codemonkey.ws,
	jbarnes@virtuousgeek.org, "Woodhouse,
	David" <david.woodhouse@intel.com>,
	"Gross, Mark" <mark.gross@intel.com>,
	benami@il.ibm.com, "Han, Weidong" <weidong.han@intel.com>,
	"Kay, Allen M" <allen.m.kay@intel.com>
Subject: Re: [PATCH 2/2] KVM: Device Assignment with VT-d
Date: Tue, 26 Aug 2008 17:41:02 +0300	[thread overview]
Message-ID: <48B415FE.4030006@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC0188EA70@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
> Amit Shah wrote:
>   
>> * On Tuesday 26 Aug 2008 15:58:42 Zhang, Xiantao wrote:
>>     
>>> Maybe vtd.c should be put @ virt/kvm so that ia64 can share it to
>>> avoid future code move.
>>>       
>> As of now, device assignment resides inside the x86 directory and is
>> only tested in x86 environment. Once we support ia64, we'll have a
>> lot of files moving anyway.
>>     
>
> Just a suggestion.  Even if put it @ virt/kvm, we still can make it only
>   

I'm fine with keeping it in x86 and moving it later, since the code is 
late already.  However if someone is willing to do the work to move it 
to virt/kvm/, I'm happy with that as well.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-08-26 14:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26  8:55 VT-d support for device assignment Amit Shah
2008-08-26  8:55 ` [PATCH 1/2] VT-d: changes to support KVM Amit Shah
2008-08-26  8:55   ` [PATCH 2/2] KVM: Device Assignment with VT-d Amit Shah
2008-08-26 10:28     ` Zhang, Xiantao
2008-08-26 10:35       ` Amit Shah
2008-08-26 10:42         ` Zhang, Xiantao
2008-08-26 10:57           ` Amit Shah
2008-08-26 11:04             ` Zhang, Xiantao
2008-08-26 14:41           ` Avi Kivity [this message]
2008-08-26 15:09             ` Han, Weidong
2008-09-03 16:52     ` Amit Shah
2008-09-09  7:18       ` Han, Weidong
2008-08-26  9:10 ` VT-d support for device assignment Avi Kivity
2008-08-26 14:11   ` Amit Shah
2008-08-26 14:38     ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2008-09-09 13:51 [PATCH 2/2] KVM: Device Assignment with VT-d Han, Weidong
2008-09-09 14:39 ` Amit Shah
2008-09-09 15:05   ` Han, Weidong
2008-09-09 14:44 VT-d support for device assignment Amit Shah
2008-09-09 14:44 ` [PATCH 1/2] VT-d: Changes to support KVM Amit Shah
2008-09-09 14:44   ` [PATCH 2/2] KVM: Device Assignment with VT-d Amit Shah
2008-09-09 15:37 VT-d support for device assignment Amit Shah
2008-09-09 15:37 ` [PATCH 1/2] VT-d: Changes to support KVM Amit Shah
2008-09-09 15:37   ` [PATCH 2/2] KVM: Device Assignment with VT-d Amit Shah
2008-09-11  7:21     ` Han, Weidong
2008-09-14  0:49       ` 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=48B415FE.4030006@qumranet.com \
    --to=avi@qumranet.com \
    --cc=allen.m.kay@intel.com \
    --cc=amit.shah@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --cc=benami@il.ibm.com \
    --cc=david.woodhouse@intel.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kvm@vger.kernel.org \
    --cc=mark.gross@intel.com \
    --cc=muli@il.ibm.com \
    --cc=weidong.han@intel.com \
    --cc=xiantao.zhang@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