All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Alex Merritt <merritt.alex@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: IOMMU Domain for Dom0
Date: Mon, 27 Jun 2011 12:11:43 -0400	[thread overview]
Message-ID: <20110627161143.GN6978@dumpdata.com> (raw)
In-Reply-To: <BANLkTinFj0+srUozffOw43LXn77dUxXDTg@mail.gmail.com>

On Sun, Jun 26, 2011 at 09:35:17PM -0600, Alex Merritt wrote:
> Hello,
> 
> I'm looking to enable the NVIDIA CUDA driver/runtime stack to work in
> Dom0 on Xen. I've contacted NVIDIA through various capacities and have

I've been running the NVIDIA binary driver with 2.6.39 / 3.0 kernel.

> gotten replies essentially saying they cannot provide assistance, and
> have been following the nvnews.com forums. However, now that I have
> IOMMU-capable processors (with VT-d) and a version of Xen which can
> successfully program this hardware, I am interested to determine if it
> is possible to program the IOMMU *for* Dom0 (i.e. the target is Dom0,
> not an HVM/pvops guest).
> 
> I have successfully been able to launch an HVM guest, passing a few
> GPUs through. Installing an unmodified developer driver from NVIDIA
> works using the standard method (no SYSSRC=/-OUT= or anything) and
> CUDA applications execute as expected. Can this be done for Dom0,
> achieving the same result without requiring any involvement from
> NVIDIA or modifications to the driver?

It should be no trouble.. albeit you might need to update the Linux
kernel to 2.6.39 or 3.0 to take advantage of the 1-1 P2M mapping code.

> 
> My immediate interest is more to see if it "can be done" via a hack or
> something, not necessarily whether it would make sense for Xen to
> support this in the future. My goal with this email is to get feedback
> on two fronts: 1) is there a limitation due to the architecture,
> meaning that as Dom0 is pvops it cannot use VT-d, or is it a
> implementation addition to Xen that would be needed? 2) If the latter
> is true (programming needed), how much effort (code/time) would
> you/anyone estimate it would take to enable this to work, and could
> you provide some starting pointers for me to do so? I am untrained
> when it comes to the Xen sourcecode.
> 
> I'm using Xen 4.1.1 and pv-ops linux (not upstream) 2.6.32.40 on an
> Intel X5660 with a Tylersburg chipset. My host OS is Fedora 13, but
> that needn't be static.
> 
> I originally asked this on xen-users, but was informed this mailing
> list would be better suited:
> http://lists.xensource.com/archives/html/xen-users/2011-06/msg00451.html
> 
> Many thanks in advance!
> Alex
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2011-06-27 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  3:35 IOMMU Domain for Dom0 Alex Merritt
2011-06-27  6:01 ` Sander Eikelenboom
2011-06-27  6:44   ` Alex Merritt
2011-06-27 16:11 ` Konrad Rzeszutek Wilk [this message]
2011-06-29 23:11   ` Alex Merritt
2011-06-30 16:19     ` Konrad Rzeszutek Wilk

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=20110627161143.GN6978@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=merritt.alex@gmail.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.