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] results

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] results
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 13 Jul 2004 08:15:38 +0100
Cc: ron minnich <rminnich@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Jul 2004 08:16:54 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 13 Jul 2004 08:04:07 BST." <E1BkHKi-0000z7-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> If Mark's right about there being a 2D driver in the Xserver that
> works without the nvidia binary-only kernel driver, then that's
> definitely the way to go.
> I seriously think it's worth a doing a disassembly of the binary
> module and seeing the scale of the problem. If we're lucky and
> it's just the rd/wrmsr that are the problem, they'll be easy to
> deal with by nop'ing them. If there are cli/sti then that's more
> of a pain, but it would actually be pretty easy to do in a Linux
> (as opposed to Xen) GPF handler that spots them and does the
> appropriate Xen call. They're both 1 byte instructions (0xfa/b)
> with no operands, so easy to spot.

Retaining the possibility of doing this kind of thing is another good
reason for keeping PAGE_OFFSET the same as native in our Linux 2.6
port as well as the 2.4 port. If __va() and __pa() change then that's
likely to be a much bigger rewriting problem.

 -- Keir

This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>