public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Nakajima, Jun" <jun.nakajima-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: New VT-D spec available
Date: Sun, 20 May 2007 10:46:35 +0300	[thread overview]
Message-ID: <464FFCDB.7080408@qumranet.com> (raw)
In-Reply-To: <8FFF7E42E93CC646B632AB40643802A8031F5F10-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>

Nakajima, Jun wrote:
> An updated specification (Rev 1.0 update) of Intel(r) virtualization
> technology for Directed I/O is now available on Intel web site: 
>
> http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_Di
> rect_IO.pdf 
>
> The specification update includes DMA remapping capability, Interrupt
> remapping capability, queue management, invalidation information and
> enhancements.
>
> We are thinking how this should be enabled for KVM as well especially
> when assigning real devices to guests. Suggestions are welcome.
>   

I've had a quick look-see. There are two general approaches which I 
think make sense:

- tightly coupled kvm integration, where kvm is extended with a 
root-only 'assign pci dev x to this vm'.  As the page table format is 
the same as used by ept (I'm guessing... haven't actually read the ept 
spec), this should be quite easy to do on once npt/ept support is 
integrated.

- general interface for manipulating VT-d, with the ability to use it 
with kvm.  With this, it is possible to assign pci devices to ordinary 
userspace processes, some of which could be hosting virtual machines.  
This may fit will with the UIO patchset.

Unless I misread things, VT-d does not honor the U/S bit on the page 
table entries.  That makes the general approach fairly difficult.  I 
would recommend starting with the tightly-coupled, less generic approach 
first, and generalizing it if/when there is demand for it.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  parent reply	other threads:[~2007-05-20  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 18:47 New VT-D spec available Nakajima, Jun
     [not found] ` <8FFF7E42E93CC646B632AB40643802A8031F5F10-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-05-20  7:46   ` Avi Kivity [this message]
     [not found]     ` <464FFCDB.7080408-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-21 21:42       ` Nakajima, Jun
     [not found]         ` <8FFF7E42E93CC646B632AB40643802A80327893D-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-05-22  7:31           ` Avi Kivity
     [not found]             ` <46529C3E.8090006-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-22 17:56               ` Nakajima, Jun

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=464FFCDB.7080408@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=jun.nakajima-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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