All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Martin Cerveny <M.Cerveny@computer.org>
Cc: Gordan Bobic <gordan@bobich.net>, xen-devel@lists.xen.org
Subject: Re: Some trouble to use NVIDIA CUDA with Xen
Date: Tue, 13 Aug 2013 16:20:59 -0400	[thread overview]
Message-ID: <20130813202059.GA10103@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1308132112500.8031@dmz.c-home.cz>

On Tue, Aug 13, 2013 at 09:59:48PM +0200, Martin Cerveny wrote:
> Hello.
> 
> On Mon, 12 Aug 2013, Konrad Rzeszutek Wilk wrote:
> >On Mon, Aug 12, 2013 at 01:33:13PM +0100, Gordan Bobic wrote:
> >>Your Nvidia device ID seems to imply a GTX770.
> >>I could be wrong, but wasn't this only supported on Quadro/Grid GPUs?
> >>Or is that limitation only applicable to Windows?
> 
> I did not try to use it in "multios" (domU) environment (only simple Dom0).
> 
> >>>>NVRM: PAT configuration unsupported.
> >Right, so there are couple of patches that can enable that back.
> >
> >You need to revert these two:
> >8eaffa67b43e99ae581622c5133e20b0f48bcef1
> >c79c49826270b8b0061b2fca840fc3f013c8a78a
> >
> >And apply this patch:
> >
> >https://lkml.org/lkml/2012/2/10/229
> >
> >That should re-enable PAT.  Try that and please report back.
> 
> I applied the patch to 3.9.11-200.PAT.fc18.x86_64 (3.10 is not
> working due to incompatibilities with nvidia driver source code).

Did you revert the other two git commits?
> 
> Error persists:
> "NVRM: PAT configuration unsupported."
> 
> There is one progress at least.
> The tested programs are working in "normal speed" (as without Xen)
> - speedup 20x to compare with non-patched kernel on Dom0.
> 
> The CUDA error still persists:
> 
> ---
> # /usr/bin/time ./bandwidthTest
> [CUDA Bandwidth Test] - Starting...
> Running on...
> 
>  Device 0: GeForce GTX 770
>  Quick Mode
> 
> CUDA error at bandwidthTest.cu:719
> code=46(cudaErrorDevicesUnavailable) "cudaEventCreate(&start)"
> 
> 0.00user 0.20system 0:00.26elapsed 79%CPU (0avgtext+0avgdata 5236maxresident)k
> 0inputs+0outputs (0major+1182minor)pagefaults 0swaps
> ---
> 
> I reported the problem to NVIDIA too and waiting for solution.
> 
> Any other hint ?
> 
> Thanks, Martin Cerveny

  reply	other threads:[~2013-08-13 20:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-10 16:21 Some trouble to use NVIDIA CUDA with Xen Martin Cerveny
2013-08-12 12:33 ` Gordan Bobic
2013-08-12 13:00   ` Konrad Rzeszutek Wilk
2013-08-13 19:59     ` Martin Cerveny
2013-08-13 20:20       ` Konrad Rzeszutek Wilk [this message]
2013-08-13 20:32         ` Martin Cerveny
2013-08-14 22:21         ` Martin Cerveny
2013-08-15 13:19           ` Konrad Rzeszutek Wilk
2013-08-15 13:28             ` Martin Cerveny
2013-08-15 14:15               ` Konrad Rzeszutek Wilk
2013-08-27 13:17                 ` Martin Cerveny
  -- strict thread matches above, loose matches on Subject: below --
2013-04-30 11:39 Sébastien Frémal
2013-04-30 11:57 ` George Dunlap
2013-04-30 12:05   ` Samuel Thibault
2013-04-30 14:13     ` Sébastien Frémal
2013-04-30 14:19       ` Samuel Thibault
2013-04-30 14:32         ` Sébastien Frémal
2013-04-30 14:41           ` Samuel Thibault
2013-05-03 13:54         ` Samuel Thibault

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=20130813202059.GA10103@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=M.Cerveny@computer.org \
    --cc=gordan@bobich.net \
    --cc=xen-devel@lists.xen.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 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.