[Bug 6357] savage problem: glxgears produce black window - locking problems with DRIClipNotify
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6357 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 19:33 --- pushed to savage git master. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8348] [MESA 6.5.1] PPracer causes r300 driver to assert failure
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8348 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 19:05 --- More information: [drm] Initialized radeon 1.25.0 20060524 on minor 0: [102234.244000] mtrr: 0xe000,0x800 overlaps existing 0xe000,0x400 [102234.244000] mtrr: 0xe000,0x800 overlaps existing 0xe000,0x400 [102234.244000] mtrr: 0xe000,0x800 overlaps existing 0xe000,0x400 [102234.244000] agpgart: Found an AGP 2.0 compliant device at :00:00.0. [102234.244000] agpgart: Putting AGP V2 device at :00:00.0 into 4x mode [102234.248000] agpgart: Putting AGP V2 device at :01:00.0 into 4x mode [102234.544000] [drm] Setting GART location based on new memory map [102234.544000] [drm] Loading R300 Microcode [102234.544000] [drm] writeback test succeeded in 2 usecs * libdrm 2.0.2 * Sept 16th snapshot of drm kernel drivers. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8348] New: [MESA 6.5.1] PPracer causes r300 driver to assert failure
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8348 Summary: [MESA 6.5.1] PPracer causes r300 driver to assert failure Product: Mesa Version: unspecified Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: Drivers/DRI/r300 AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] Running ppracer for a little while, while playing it aborts with this in a console. ppracer: r300_ioctl.c:683: r300AllocDmaRegion: Assertion `rmesa->dma.current.ptr <= rmesa->dma.current.end' failed. This is reproducible. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5376] xmoto help menu causes mouse cursor related locks to appear
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5376 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 18:32 --- (In reply to comment #5) > Followup from Bug 8299: > > There blender locks the display and either -nosilk when starting X, setting > SWCursor in xorg.conf or running with MergedFramebuffer disabled prevents it. Both SilkenMouse and SWCursor work for me with blender. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4799] radeon driver should support 3d texture maps without raster fallback
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4799 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 17:51 --- I'll send a brief explanation to your email address, Simon. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4799] radeon driver should support 3d texture maps without raster fallback
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4799 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 16:57 --- I hope nobody minds fielding newbie questions - can one of you explain what 3D texture maps are, and what they get used for? I understand 2D texture maps already, I think, but I'm not sure what is meant by 3D, the gl man page for glTexCoordxx is really terse, and searching online hasn't totally clarified it for me. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM memory manager on cards with hardware contexts
On Mon, 2006-09-18 at 16:46 +0200, Thomas Hellström wrote: > Unfortunately this leads to rather costly cache and TLB flushes. > Particularly on SMP. > > I think Keith was referring to the drawbacks with buffers pinned in > AGP or VRAM space. What about a futex-like approach: A shared are mapped by both kernel and user has locks for the buffers. When submitting a command involving a buffer, userland tries to lock it. This is a simple atomic operation in user space. If that fails (the lock for that buffer is held, possibly by the kernel, or the buffer is swapped out), them it does an ioctl to the DRM to get access (which involves sleeping until the buffer can be retreived). One the operation is complete, the apps can release the locks to buffers it holds. In fact, if there is a mapping to buffers <-> objects for cards like nVidia with objects and notifiers, the kernel could auto-unlock objects when the completion interrupt for them occurs. Ben. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4799] radeon driver should support 3d texture maps without raster fallback
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4799 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #3577 is|0 |1 obsolete|| --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 14:41 --- Created an attachment (id=7064) --> (https://bugs.freedesktop.org/attachment.cgi?id=7064&action=view) new patch for enabling 3d textures New try for 3d textures, it now disables the perspective bit, as it just makes things worse. However, this still doesn't work. I'm now pretty sure that you indeed have to route the r coord manually as s coord to unit 2, and setup won't do that for you. (With this patch, you can see that r tex coord is not set up, just start multiarb demo (with unit 2 enabled) and you can see that the output of stex3d will change according to redraws of multiarb, and permanently change after multiarb has been closed.). If TXFORMAT_2 is initialized to use RADEON_TXFORMAT_ST_ROUTE_STQ0 (instead of STQ2) then you no longer have that problem, but it looks to me like the interpolator of unit 2 for the r coord will simply use the s coord (as a result s and r coord are always identical), which is obviously wrong. So, unless I'm missing some setup bits to change that, this makes 3d textures practically unimplementable. You could hack up tex gen / tex matrix stuff on unit 2 more or less easily in tcl mode, but I don't think the swtcl code could handle that easily. And noone really seemed to have missed that feature too hard, so you can see where this is heading... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM memory manager on cards with hardware contexts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: > > Extending the memory manager would involve adding an ability to lock and > unlock surfaces to VRAM/AGP addresses - this would require kernel > interaction I guess. The driver would have to lock the surfaces then be > free to submit commands to the ring, then explicitly unlock the > surfaces. This is actually a pretty nasty approach - it makes it very > hard to deal with low-memory situations - it's impossible to kick out > another processes allocations. This was similar to how I had designed the memory manager that I never finished. In order to make this work, you have to set a fence when you unlock the surface. You can still kick out surfaces that we locked by another process, but you have to wait until the fence has past. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFDxHFX1gOwKyEAw8RAgK8AKCLZb0FXQMF7cFP4fWxdTjIb+aLwQCcClRk yk/LjKRuECunVbP8/EFRxfk= =YUsT -END PGP SIGNATURE- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM memory manager on cards with hardware contexts
> Actually, the TTM memory manager already does this, > but also changes the caching policy of the linear kernel map. The later is not portable unfortunately, and can have other serious performance impacts. Typically, the kernel linear map is mapped using larger page sizes, or in some cases, even large TLB entries, or separate translation registers (like BATs). Thus you cannot affect the caching policy of a single 4k page. Also, on some processors, you can't just break down a single large page into small pages neither. For example, on desktop PowerPC, entire segments of 256M can have only one page size. Even x86 might have some interesting issues here... > Unfortunately this leads to rather costly cache and TLB flushes. > Particularly on SMP. Yup. > I think Keith was referring to the drawbacks with buffers pinned in > AGP or VRAM space. > > /Thomas. > > > > > > - > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > -- > > ___ > > Dri-devel mailing list > > Dri-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8246] Recent DRM r200 driver stop working with 'failure adding irq handler'
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8246 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 14:24 --- wow our domain support sucks ass I think I've fixed this in git.. please close bug if I have. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Doom3 benchmarks.
Aapo Tahkola wrote: > On Sun, 13 Aug 2006 02:17:40 +0200 > Rune Petersen <[EMAIL PROTECTED]> wrote: > >> Roland Scheidegger wrote: >>> Rune Petersen wrote: Roland Scheidegger wrote: fragment.position input is not implemented yet. fglrx driver parses it from VP to FP via a texcoord route. I've been hitting my head on this for some time. Only got as far as only getting a soft lockup which isn't very useful. >>> That kinda makes sense. On r200 you could already pass vertex data >>> to the fragment registers (but you couldn't use position as input), >>> so the data was interpolated by the texcoord interpolator but >>> texture lookup was disabled (see the ATI_fs spec / r200 dri >>> implementation). At first sight looks like a similar mechanism >>> might be used by r300 I guess, interpolating position or texcoords >>> isn't too different is it? >>> >> I've had been looking into this, and the vertex shader is supplying >> the position to the fragment shader as a texcoord, the only apparent >> difference in shader setup between a position and a real texcoord, is >> a real texcoord is supplied as input for the vertex shader. >> >> >> I would really like to capture the vertex program of >> program/fp/tri-depth and the fglrx driver. >> >> But I'm betting the vertex shader is capable of writing to a texcoord. >> All I need is a safe way for the vertex shader code to know if the >> fragment shader needs the position. >> >> Any help with this would be great. > > Bug #8056 patch can do this. Take a look at r300_select_vertex_shader(). > Thank you. Getting wpos to the fragment shader is not too reliable atm, but something strange: Only x & y are valid for hpos in the vertex shader.. z = 0 & w = 1 as you would expect if they weren't set... Am I missing something obvious? Rune Petersen - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5376] xmoto help menu causes mouse cursor related locks to appear
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5376 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 11:23 --- Followup from Bug 8299: There blender locks the display and either -nosilk when starting X, setting SWCursor in xorg.conf or running with MergedFramebuffer disabled prevents it. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 6357] savage problem: glxgears produce black window - locking problems with DRIClipNotify
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6357 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 09:28 --- (In reply to comment #25) Great work! I have applied your patch to the current "Fedora rawhide" package "xorg-x11-drv-savage-2.1.1-5.fc6", and it works nicely. Finally, "glxgears" is back, and moreover, the patch also fixes https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196011 and https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195851 which means it kills 3 birds with one stone :) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 6357] savage problem: glxgears produce black window - locking problems with DRIClipNotify
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6357 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 08:44 --- (In reply to comment #27) > The patch proposed by Alex Deucher works fine. I tested it. I think, it is > better to call the original block handler, instead of trying to copy its behaviour. > > I think, that this patch should be commited on the official driver. > > Hmmm... there may be other problems with the savage 3D driver in xorg 7.1 then... I'm still getting lockups. Perhaps it's an issue with my setup. I'll apply the patch soon. Thanks again for tracking this down! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 6357] savage problem: glxgears produce black window - locking problems with DRIClipNotify
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6357 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 08:18 --- The patch proposed by Alex Deucher works fine. I tested it. I think, it is better to call the original block handler, instead of trying to copy its behaviour. I think, that this patch should be commited on the official driver. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm: Branch 'drm-ttm-0-2-branch'
Keith Whitwell wrote: >Thomas Hellström wrote: > > >>Keith Whitwell wrote: >> >> >>>Thomas Hellstrom wrote: >>> >>> >>> linux-core/drmP.h | 13 +++- linux-core/drm_bo.c | 31 ++- linux-core/drm_fence.c | 128 +++- linux-core/drm_lock.c |4 - >>>Thomas, >>> >>>Can you be more specific about the changes in drm_lock.c -- what is the >>>background there - the change doesn't seem related to the commit comment? >>> >>>Keith >>> >>> >>> >>> >>Ah, OK, this one more or less slipped through. >>I might need to revert that. >> >>In a situation where there are many processes waiting on the hardware >>lock, and one process grabs it, the lock will lose the CONTENDED flag, >>until one of the sleeping processes is woken up by a clock tick and >>sends the CONTENDED flag again. The process taking the lock will not >>call the kernel to wake up sleeping processes, and can retake the lock >>again without calling the kernel. >> >>This is not an ideal situation, and the change makes sure that the >>process taking the lock calls the kernel again to wake up any sleeping >>processes even if there are none available. This seems improve >>scheduling at the cost of some extra CPU when there are more than one >>DRI client. >> >> > >Ah, interesting. This sounds like the cause of some pretty >long-standing bad behaviour of dri locking where some contexts end up >being 'locked out' despite the dri lock being repeatedly grabbed and >released by a given process. > >Keith > > Yes. Hmm, Actually the sleeping processes will not wake up by clock ticks since schedule() is called instead of schedule_timeout(), so the starvation can potentially go on forever. That's probably why some window movement sometimes seemed to wake a locked-out context. Anyway, while the current code seems to fix the problem, the best fix is probably to add a sleeping process counter to the lock. That would avoid unnecessary kernel calls when the lock is released and there are no processes waiting. Thomas >- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >-- >___ >Dri-devel mailing list >Dri-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/dri-devel > > - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM memory manager on cards with hardware contexts
Benjamin Herrenschmidt wrote: Yes, this is really a different hardware model than we're used to dealing with for DRI drivers, however it's not a problem for the most part - if you don't need to take the lock, don't. But then you need some other way of dealing with the other hacky stuff we get away with by lock abuses eg. VT switching. We could abuse a RW lock model here where normal command submission takes a read lock (can be shared) and big hammer like VT switch takes a write lock. For the memory manager, I guess there are two choices: 1) make the driver use a command-buffer approach even though the hardware supports per-context ring buffers, or 2) extend the memory manager. Extending the memory manager would involve adding an ability to lock and unlock surfaces to VRAM/AGP addresses - this would require kernel interaction I guess. The driver would have to lock the surfaces then be free to submit commands to the ring, then explicitly unlock the surfaces. This is actually a pretty nasty approach - it makes it very hard to deal with low-memory situations - it's impossible to kick out another processes allocations. I wonder how NV deals with this... I've heard some of the proprietary drivers play MMU tricks. We could do something similar... when kicking a pixmap out, we "remap" the virtual mapping for that pixmap to backup memory. But that means fundamentally changing our model where we have a big mapping for the fb which we then cut into objects and instead mmap objects separately. As for kicking out mappings behind somebody's back, it works fine :) We do that for SPEs local stores on the Cell processor. A no_page() function will refill as needed from either the HW or the backing store and use unmap_mapping_range() can kick that out behind any process back. The main problem I see with that approach is that you have to either map the backup memory non-cacheable which can be trouble on some platforms (*) or cacheable which means that the same bit of memory will either be cacheable or non-cacheable depending on wether you get the HW, which might be trouble to some apps unless you are careful. (*) The kernel always keeps a cacheable linear mapping of all memory and the nasty prefetchers or speculative execution units might thus bring something from your page otherwise mapped non-cacheable into userspace in the cache that way. Some CPUs will shoke badly if you access via a non-cacheable mapping something that is present in the cache. Ben. Actually, the TTM memory manager already does this, but also changes the caching policy of the linear kernel map. Unfortunately this leads to rather costly cache and TLB flushes. Particularly on SMP. I think Keith was referring to the drawbacks with buffers pinned in AGP or VRAM space. /Thomas. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm: Branch 'drm-ttm-0-2-branch'
Thomas Hellström wrote: > Keith Whitwell wrote: >> Thomas Hellstrom wrote: >> >>> linux-core/drmP.h | 13 +++- >>> linux-core/drm_bo.c | 31 ++- >>> linux-core/drm_fence.c | 128 >>> +++- >>> linux-core/drm_lock.c |4 - >>> >> >> Thomas, >> >> Can you be more specific about the changes in drm_lock.c -- what is the >> background there - the change doesn't seem related to the commit comment? >> >> Keith >> >> > Ah, OK, this one more or less slipped through. > I might need to revert that. > > In a situation where there are many processes waiting on the hardware > lock, and one process grabs it, the lock will lose the CONTENDED flag, > until one of the sleeping processes is woken up by a clock tick and > sends the CONTENDED flag again. The process taking the lock will not > call the kernel to wake up sleeping processes, and can retake the lock > again without calling the kernel. > > This is not an ideal situation, and the change makes sure that the > process taking the lock calls the kernel again to wake up any sleeping > processes even if there are none available. This seems improve > scheduling at the cost of some extra CPU when there are more than one > DRI client. Ah, interesting. This sounds like the cause of some pretty long-standing bad behaviour of dri locking where some contexts end up being 'locked out' despite the dri lock being repeatedly grabbed and released by a given process. Keith - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm: Branch 'drm-ttm-0-2-branch'
Keith Whitwell wrote: Thomas Hellstrom wrote: linux-core/drmP.h | 13 +++- linux-core/drm_bo.c | 31 ++- linux-core/drm_fence.c | 128 +++- linux-core/drm_lock.c |4 - Thomas, Can you be more specific about the changes in drm_lock.c -- what is the background there - the change doesn't seem related to the commit comment? Keith Ah, OK, this one more or less slipped through. I might need to revert that. In a situation where there are many processes waiting on the hardware lock, and one process grabs it, the lock will lose the CONTENDED flag, until one of the sleeping processes is woken up by a clock tick and sends the CONTENDED flag again. The process taking the lock will not call the kernel to wake up sleeping processes, and can retake the lock again without calling the kernel. This is not an ideal situation, and the change makes sure that the process taking the lock calls the kernel again to wake up any sleeping processes even if there are none available. This seems improve scheduling at the cost of some extra CPU when there are more than one DRI client. /Thomas - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5376] xmoto help menu causes mouse cursor related locks to appear
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5376 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 07:22 --- (In reply to comment #3) > > Is this with MergedFB enabled or disabled? > > Enabled. Even with cloned displays. If it doesn't happen with MergedFB disabled, then I'd guess it's related to RADEONChooseCursorCRTC(). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5376] xmoto help menu causes mouse cursor related locks to appear
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5376 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 06:52 --- (In reply to comment #2) > Is this with MergedFB enabled or disabled? Enabled. Even with cloned displays. > Does disabling SilkenMouse also work around it? With xmoto-0.1.14 it would seem to. Haven't been able to reproduce this with xmoto-0.2.1 . Probably due to the stats bar on the right... And yes, I believe this is the same bug that Vladimir experienced. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5376] xmoto help menu causes mouse cursor related locks to appear
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5376 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 06:06 --- Is this with MergedFB enabled or disabled? Does disabling SilkenMouse also work around it? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8273] smooth shading and alpha shading mixed up in r300
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8273 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 05:48 --- (In reply to comment #10) > Though a more descriptive list might be in order. If there's anything wrong with the built-in descriptions, I think it would be much better to fix it than to create a duplicated list. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8299] R300 + MergedFB + blender + some movement => lock-up
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8299 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 05:30 --- Ok, as I am no experienced programmer in C and graphics programming and there won't be any free time to learn it, I won't work on it. So my plan would be now to open a bug report specific to this problem - maybe someone with more experience in this field finds time to implement that. BTW: Thx for the help - being able to use blender in dualhead setup at least on the internal display is really great! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915 on FreeBSD issues.
I know the line that causing this.This code :if (m->m_flags & MUTEX_FLAGS_PRIVATE) PANIC("Recurse on a private mutex.");at file "/usr/src/lib/libpthread/thread/thr_mutex.c" line 1002 prevent the recursive to run.
I think I whould report it to freebsd instead here.Or may be the code at libX11 should be change. I found also that libX11 doesn't compile when opetion "--disable-thread" is active.Regards,
On 9/15/06, Angka H. K. <[EMAIL PROTECTED]> wrote:
Thanks for the replay, and I am sorry for hijacking thread, I was thinking it a little bit related to i915.Here the error I found :Fatal error 'Recurse on a private mutex.' at line 1003 in file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 35)
It appears whe I run glxgears and glxinfo. A core dump also produced by itRegards,On 9/14/06,
Eric Anholt <
[EMAIL PROTECTED]> wrote:On Thu, 2006-09-14 at 09:28 +0700, Angka H. K. wrote:
> Does anyone here using freebsd ?>> I have 2 problem with my i915 dri>> 1. glxgears not running with error 35 from> "/usr/src/lib/lipthread/thr_mutex.c" line 1003> 2. X always crash when exit and the screen stay at graphic, gdb output
> shows problem with dri close function,> dlclose(extension_pointer_number). I think Eric knows well about it.>> My second problem gones when dri is disable.> Any suggestion ?Please don't hijack unrelated threads.
1) you didn't supply the full error message, but this could be the usualissue when you load two major versions of libpthread.so. ldd will tellyou if you are.2) This is a known issue with AIGLX on Intel on FreeBSD, with no known
solution other than disabling AIGLX.--Eric Anholt [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: What can the FSF do to help?
>From: "Alex Deucher" <[EMAIL PROTECTED]> > >If you have any way of working with hardware vendors to get them to >provide specs, or even better, open source driver code, it would be >much appreciated. The more you ask, the less likely you get them. The driver code includes software algorithms which does API specific operations. We really don't need them. We neither need detailed hardware information when it means the chip design details. We basically just need to know how to enable/disable things in the graphics pipeline, how to set variables, how to send graphics data, etc. We actually don't need to understand the meaning of the registers and the like: we just need to know the sequences of numbers which needs to be sent in order to achieve something. But as written here, somebody with NDA wrote open source driver enchangements and is unable to publish. If he does not explane anything in the code, it is the same what I suggested in the above paragraph. ATI also has "Closer-to-the-metal API CTM" mentioned in http://pharr.org/matt/talks/graphicshardware.pdf The talk briefly plays with the idea of "Has the time come to kill the graphics API and expose the hardware instead?". Juhana -- http://music.columbia.edu/mailman/listinfo/linux-graphics-dev for developers of open source graphics software - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM memory manager on cards with hardware contexts
> Yes, this is really a different hardware model than we're used to > dealing with for DRI drivers, however it's not a problem for the most > part - if you don't need to take the lock, don't. But then you need > some other way of dealing with the other hacky stuff we get away with by >lock abuses eg. VT switching. We could abuse a RW lock model here where normal command submission takes a read lock (can be shared) and big hammer like VT switch takes a write lock. > For the memory manager, I guess there are two choices: 1) make the > driver use a command-buffer approach even though the hardware supports > per-context ring buffers, or 2) extend the memory manager. > > Extending the memory manager would involve adding an ability to lock and > unlock surfaces to VRAM/AGP addresses - this would require kernel > interaction I guess. The driver would have to lock the surfaces then be > free to submit commands to the ring, then explicitly unlock the > surfaces. This is actually a pretty nasty approach - it makes it very > hard to deal with low-memory situations - it's impossible to kick out > another processes allocations. > > I wonder how NV deals with this... I've heard some of the proprietary drivers play MMU tricks. We could do something similar... when kicking a pixmap out, we "remap" the virtual mapping for that pixmap to backup memory. But that means fundamentally changing our model where we have a big mapping for the fb which we then cut into objects and instead mmap objects separately. As for kicking out mappings behind somebody's back, it works fine :) We do that for SPEs local stores on the Cell processor. A no_page() function will refill as needed from either the HW or the backing store and use unmap_mapping_range() can kick that out behind any process back. The main problem I see with that approach is that you have to either map the backup memory non-cacheable which can be trouble on some platforms (*) or cacheable which means that the same bit of memory will either be cacheable or non-cacheable depending on wether you get the HW, which might be trouble to some apps unless you are careful. (*) The kernel always keeps a cacheable linear mapping of all memory and the nasty prefetchers or speculative execution units might thus bring something from your page otherwise mapped non-cacheable into userspace in the cache that way. Some CPUs will shoke badly if you access via a non-cacheable mapping something that is present in the cache. Ben. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 6357] savage problem: glxgears produce black window - locking problems with DRIClipNotify
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6357 --- Additional Comments From [EMAIL PROTECTED] 2006-09-18 01:50 --- (In reply to comment #22) > I found how to correct the bug. > The SAREA drawable lock must be released in the BlockHandler overloaded by the > savage DRI driver, as it is done in the original BlockHandler function. > I post two patches to resolve the problem. > They first apply on the xserver tree, and the second on the savage-driver > tree. howto can i apply these patches? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM memory manager on cards with hardware contexts
Dave Airlie wrote: >> Obviously, we are interested in making use of the new DRM memory manager >> on that hardware. Now if I understand how it works correctly, this new >> memory manager allocates opaque handles which are not to be used as >> offset in memory, because they are not. Therefore, a translation from >> the handle into a proper memory adress has to be done before the >> commands are sent to the hardware. This is easy to add when the DRM >> validates all the commands. > > Also the multiple contexts means taking the drm lock is not something we > would want to be doing in on a regular basis... I've got some ideas > already discussed with Stephane but I'd like to see what other methods ppl > might have.. Yes, this is really a different hardware model than we're used to dealing with for DRI drivers, however it's not a problem for the most part - if you don't need to take the lock, don't. But then you need some other way of dealing with the other hacky stuff we get away with by lock abuses eg. VT switching. For the memory manager, I guess there are two choices: 1) make the driver use a command-buffer approach even though the hardware supports per-context ring buffers, or 2) extend the memory manager. Extending the memory manager would involve adding an ability to lock and unlock surfaces to VRAM/AGP addresses - this would require kernel interaction I guess. The driver would have to lock the surfaces then be free to submit commands to the ring, then explicitly unlock the surfaces. This is actually a pretty nasty approach - it makes it very hard to deal with low-memory situations - it's impossible to kick out another processes allocations. I wonder how NV deals with this... Keith - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
