Message: 5
Date: Tue, 30 Jan 2007 16:43:48 +0100
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Subject: RE: [Xen-devel] NVidia driver status
To: "Jacob Gorm Hansen" <jacobg@xxxxxxx>, "xen-devel"
<Xen-devel@xxxxxxxxxxxxxxxxxxx>
Message-ID:
<907625E08839C4409CE5768403633E0B018E190F@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Jacob Gorm Hansen
Sent: 30 January 2007 15:33
To: xen-devel
Subject: [Xen-devel] NVidia driver status
hi,
being dissapointed a bit by ATI's support for Xen, I just purchased a
top-of-the-line Dell box with an expensive NVidia graphics card, as
rumour said they would work better than the ATI ones.
Unfortunately, the
NVidia installer detects that I am running Xen, and then refused to
compile the kernel module, saying that Xen is not supported.
Does anyone
know of a way around this check, or have fresh experiences getting Xen
and NVidia to play together?
Now, there may be calls to say that I'm biased here, but I'm really not
working with the ATI-side of AMD anyways, so:
The reason it refuses to compile the kernel module is probably more to
do with the fact that the guys at nVidia KNOWS that it's not going to
work anyways. If that's the case, it's not really much point in
bypassing the check itself.
It's quite common for (graphics) driver code to make "nasty" stuff with
memory addresses, use DMA for all sorts of weird and wonderfull things,
and in general do things that aren't "xen-friendly". Most other drivers,
for example, won't put a memory address inside a DMA buffer, that refers
to a different area of memory that may not even be a DMA buffer in
itself.
Just as an idea for "tricking": have you run strace on the installer to
see how it figures out that you're on a Xen kernel? Is it using some
xm-tool, the kernel name (-xen) or some other method. You may be able to
bypass it once you know how it works... ;-)
--
Mats
Thanks,
Jacob
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
------------------------------
Message: 6
Date: Tue, 30 Jan 2007 15:46:47 +0000
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Clean up and fix errors in strncpy ->
strlcpy conversion
To: Christoph Egger <Christoph.Egger@xxxxxxx>,
<xen-devel@xxxxxxxxxxxxxxxxxxx>
Cc: Aron Griffis <aron@xxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Message-ID: <C1E518E7.8156%Keir.Fraser@xxxxxxxxxxxx>
Content-Type: text/plain; charset="US-ASCII"
On 30/1/07 3:26 pm, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:
You're confusing the cleanups with the bugfixes. Any use of
safe_strcpy() in my patch was just cleanup.
The bugfixes are on the signature fields (the first change quoted
above), which I changed to use memcpy since strlcpy adds an unwanted
NUL.
Aron: If the above patch is still correct (against CS 13703), please resend it
for Keir to apply.
The original patch still applies cleanly to xen-unstable so I'll apply it
without a resend.
-- Keir
------------------------------
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
End of Xen-devel Digest, Vol 23, Issue 227
******************************************
