public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: "Yang, Sheng" <sheng.yang@intel.com>,
	Ben-Ami Yassour1 <BENAMI@il.ibm.com>,
	kvm@vger.kernel.org, amit.shah@qumranet.com,
	weidong.han@intel.com, anthony@codemonkey.ws, "Kay,
	Allen M" <allen.m.kay@intel.com>
Subject: Re: [PATCH] KVM: PCIPT: VT-d support
Date: Thu, 10 Jul 2008 19:00:47 +0300	[thread overview]
Message-ID: <20080710160047.GE7273@il.ibm.com> (raw)
In-Reply-To: <48762374.3000002@qumranet.com>

On Thu, Jul 10, 2008 at 05:57:56PM +0300, Avi Kivity wrote:

> It makes sense to initialize VT-d before.  Since memslots can be
> created and destroyed dynamically, with the current implementation
> we can see
>
>  create slot
>  create slot
>  init VT-d
>  create slot
>
> which means we need to support both slot-creation-after-VT-d and
> init-VT-d-after-slot-creation.  If we initialize VT-d up front, we
> only need to support (and test) one scenario.

Fair enough---we'll take a look at whether initializing VT-d first
introduces any complications other than hot-plug (see below).

> On the other hand, this means that you will not be able to assign
> devices unless you specified this when creating the VM; but I think
> this is fair.

It will be nice to support hot-plugged pass-through devices some time
in the future.

Cheers,
Muli

  reply	other threads:[~2008-07-10 16:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10  9:14 VT-d pci passthrough patches Ben-Ami Yassour
2008-07-10  9:14 ` [PATCH] VT-d : changes to support KVM Ben-Ami Yassour
2008-07-10  9:14   ` [PATCH] KVM: PCIPT: VT-d support Ben-Ami Yassour
2008-07-10  9:30     ` Yang, Sheng
2008-07-10  9:51       ` Ben-Ami Yassour
2008-07-10 10:07         ` Yang, Sheng
2008-07-10 14:41           ` Muli Ben-Yehuda
2008-07-10 14:57             ` Avi Kivity
2008-07-10 16:00               ` Muli Ben-Yehuda [this message]
2008-07-13  7:34                 ` Avi Kivity
2008-07-14  7:49                   ` Ben-Ami Yassour
2008-07-14  8:48                     ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2008-07-06 10:52 VT-d pci passthrough patches Ben-Ami Yassour
2008-07-06 10:52 ` [PATCH] VT-d : changes to support KVM Ben-Ami Yassour
2008-07-06 10:52   ` [PATCH] KVM: PCIPT: VT-d support Ben-Ami Yassour
2008-07-09 15:49     ` Anthony Liguori
2008-07-10  9:19       ` Ben-Ami Yassour
2008-07-02 15:33 VT-d pci passthrough patches Ben-Ami Yassour
2008-07-02 15:33 ` [PATCH] VT-d : changes to support KVM Ben-Ami Yassour
2008-07-02 15:33   ` [PATCH] KVM: PCIPT: VT-d support Ben-Ami Yassour
2008-07-03  4:55     ` Han, Weidong
2008-07-06 11:15       ` Ben-Ami Yassour
     [not found]     ` <08DF4D958216244799FC84F3514D70F00181AB10@pdsmsx415.ccr.corp.intel.com>
2008-07-03  6:16       ` Han, Weidong
2008-07-03 11:33         ` Ben-Ami Yassour

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=20080710160047.GE7273@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=BENAMI@il.ibm.com \
    --cc=allen.m.kay@intel.com \
    --cc=amit.shah@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --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