WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Filtered!] Re: [Xen-devel] xen and agpgart

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Filtered!] Re: [Xen-devel] xen and agpgart
From: Gerald Britton <gbritton@xxxxxxxxxxx>
Date: Sun, 5 Sep 2004 14:01:47 -0400
Cc: Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 06 Sep 2004 02:29:08 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1C3pXl-0005Z2-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>
References: <20040904203654.GA27317@xxxxxxxxxxxxxx> <E1C3pXl-0005Z2-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
Warning: This message has had one or more attachments removed
Warning: (xorg.log.xen.agp).
Warning: Please read the "FilterNotice.txt" attachment(s) for more information.

On Sun, Sep 05, 2004 at 06:26:25AM +0100, Keir Fraser wrote:
> I'm really interested to know (a) if with the patch X works; (b) if
> not, why not [e.g., crash dump]; (c) if the patch works with Xen, does
> it also work with native Linux (i.e., have I broken the normal case!).

I needed to fix the asm-i386/agp.h wbinvd, as well as one in
arch/i386/mm/pageattr.c  After that, The module loaded, and I tried starting
X.  This resulted in my laptop rebooting (just as my test did).  I setup
netconsole to see if linux logged anything else before dieing:

netconsole: network logging started
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 855PM Chipset.
agpgart: Maximum main memory to use for agp memory: 440M
agpgart: AGP aperture is 256M @ 0xd0000000
[drm] Initialized radeon 1.11.0 20020828 on minor 0:
 << X starts here >>
ioperm not fully supported - set iopl to 3
ioperm not fully supported - ignore resource release
ioperm not fully supported - ignore resource release
 << logging to disk loses here >>
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode

So I didn't really learn much.

Ok.  I've mounted / sync in hopes of gaining more logs from X and I
think i've made a little progress (attached are the complete xorg logs from
a native run (with exec-shield disabled, i'm running fedora), and from
within xen.  The last few lines are probably the most interesting:

diff -u xorg.log.native.no-exec-shield xorg.log.xen.agp
 . . .
 (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:0:0"
-(II) RADEON(0): [drm] added 8192 byte SAREA at 0x42879000
-(II) RADEON(0): [drm] mapped SAREA 0x42879000 to 0x59307000
+(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe10d4000
+(II) RADEON(0): [drm] mapped SAREA 0xe10d4000 to 0x44306000
 (II) RADEON(0): [drm] framebuffer handle = 0xe0000000
 (II) RADEON(0): [drm] added 1 reserved context for kernel
 (II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x8086/0x3340; Card 0x1002/0x4c66]
 (II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
 (II) RADEON(0): [agp] ring handle = 0xd0000000
-(II) RADEON(0): [agp] Ring mapped at 0x59309000
-(II) RADEON(0): [agp] ring read ptr handle = 0xd0101000
-(II) RADEON(0): [agp] Ring read ptr mapped at 0x5940a000
-(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xd0102000
-(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x5940b000
-(II) RADEON(0): [agp] GART texture map handle = 0xd0302000
-(II) RADEON(0): [agp] GART Texture map mapped at 0x5960b000

The +'s are Xen, the -'s are Native.  The line:

 (II) RADEON(0): [agp] ring handle = 0xd0000000

Is the last line printed in Xen's log.  Which may suggest where it died.
I also noticed the differences in the SAREA addresses.  I have just built
the same Xen kernel for native x86 and tested that.  This seemed to work
fine, X started and I had working 3d acceleration.  The SAREA address here
was a bit closer to what was there before:

2.6.8.1 native -> 2.6.8.1 xen
-(II) RADEON(0): [drm] added 8192 byte SAREA at 0xf8834000
-(II) RADEON(0): [drm] mapped SAREA 0xf8834000 to 0x44306000
+(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe10d4000
+(II) RADEON(0): [drm] mapped SAREA 0xe10d4000 to 0x44306000

> Gerald: my patch has a better chance of working than yours as I also
> fixed the page-allocation call to definitely return a
> physically-contiguous extent of memory. If it doesn't then I gues
> we'll have to see whether anyone with a serial line can help.

I'll hopefully be able to do some testing on my workstation at work (which
has a serial port), but I might not be able to do that for a week or so as
we're moving offices this week.

                                -- Gerald

Attachment: xorg.log.native.no-exec-shield
Description: Text document

Attachment: xorg.log.native.2681
Description: Text document

Attachment: FilterNotice.txt
Description: Text document

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