This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Vt-d not working with 3.4.1

To: enming.teo@xxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Vt-d not working with 3.4.1
From: "Mr. Teo En Ming (Zhang Enming)" <enming.teo@xxxxxxxxxxxxxxx>
Date: Fri, 21 Aug 2009 01:28:36 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, weidong.han@xxxxxxxxx, mad@xxxxxx, "'Bonenkamp, Ralf'" <ralf.bonenkamp@xxxxxxxx>
Delivery-date: Thu, 20 Aug 2009 10:29:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A8D8139.4060807@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <833F02C491734E2BAA6CB4265638A47A@ASOITIS16> <4A8D7C9E.30503@xxxxxxxxxxxxxxx> <4A8D8139.4060807@xxxxxxxxxxxxxxx>
Reply-to: enming.teo@xxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3
Hi All,

I saw this posting by jam834 on nvidia forums:


<QUOTE jam834>
I've fixed my problem. It was a conflict with the nvidia kernel module and the Myrinet 10G ethernet card module where they were trying to enable write-combining on two different PAT indexes (whatever that means).

>From myrinet's documentation:
If you are using another vendor's driver which also sets up PAT write
combining, and that vendor's driver uses a different PAT index than
our driver, the other vendor's driver may note a conflict and run in
reduced performance mode. Examples of other drivers which use PAT
include the Nvidia graphics driver, and various Infiniband drivers.

One way to work around this PAT conflict is to change the PAT index
used by the Myri10GE driver by rebooting, and loading the module using
the myri10ge_pat_idx modparam to specify a different PAT index. We
currently default to 6, while some other vendors use 1. Good values
to try are 1, 4, 5, and 7.

I added the line: options myri10ge myri10ge_pat_idx=1
to my /etc/modprobe.conf, made a new initrd image and rebooted.

The "NVRM: PAT configuration unsupported, falling back to MTRRs." error has gone away and everything is now working like it should. This is running the 180.06 driver with the CUDA 2.1 beta, but I'm assuming it will also work with CUDA 2.0 and its appropriate driver.

If I change the PAT index for my nvidia graphics driver, it may solve the problem. What PAT indices should I attempt? Is it possible to change the PAT index when loading the nvidia module?
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering) 
Technical Support Engineer 
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza 
Singapore 529541
Republic of Singapore
Mobile: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
Alma Maters: Singapore Polytechnic, National University of Singapore

On 08/21/2009 01:00 AM, Mr. Teo En Ming (Zhang Enming) wrote:

I saw this posting by Boris.


Perhaps the Xen dom 0 pvops kernel I am using is too new (2.6.30-rc3), and the NVIDIA driver I am using does not support it.

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>