<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none;"></style> </head> <body dir="ltr"> <div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr"> Thanks Dave. Apologies in advance for top posting but I'm stuck on a mail client that makes a big mess when I try... >If DC was ready for the next-gen GPU it would be ready for the current >GPU, it's not the specific ASIC code that is the problem, it's the >huge midlayer sitting in the middle. We realize that (a) we are getting into the high-risk-of-breakage part of the rework and (b) no matter how much we change the code structure there's a good chance that a month after it goes upstream one of us is going to find that more structural changes are required. I was kinda thinking that if we are doing high-risk activities (risk of subtle breakage not obvious regression, and/or risk of making structural changes that turn out to be a bad idea even though we all thought they were correct last week) there's an argument for doing it in code which only supports cards that people can't buy yet. <div style="color: rgb(0, 0, 0);"> <div> <hr tabindex="-1" style="display:inline-block; width:98%"> <div id="x_divRplyFwdMsg" dir="ltr">From: Dave Airlie <airlied@gmail.com> Sent: December 11, 2016 9:57 PM To: Wentland, Harry Cc: dri-devel; amd-gfx mailing list; Bridgman, John; Deucher, Alexander; Lazare, Jordan; Cheng, Tony; Cyr, Aric; Grodzovsky, Andrey Subject: Re: [RFC] Using DC in amdgpu for upcoming GPU <div> </div> </div> </div> <div class="PlainText">On 8 December 2016 at 12:02, Harry Wentland <harry.wentland@amd.com> wrote: > We propose to use the Display Core (DC) driver for display support on > AMD's upcoming GPU (referred to by uGPU in the rest of the doc). In order to > avoid a flag day the plan is to only support uGPU initially and transition > to older ASICs gradually. [FAQ: from past few days] 1) Hey you replied to Daniel, you never addressed the points of the RFC! I've read it being said that I hadn't addressed the RFC, and you know I've realised I actually had, because the RFC is great but it presupposes the codebase as designed can get upstream eventually, and I don't think it can. The code is too littered with midlayering and other problems, that actually addressing the individual points of the RFC would be missing the main point I'm trying to make. This code needs rewriting, not cleaning, not polishing, it needs to be split into its constituent parts, and reintegrated in a form more Linux process friendly. I feel that if I reply to the individual points Harry has raised in this RFC, that it means the code would then be suitable for merging, which it still won't, and I don't want people wasting another 6 months. If DC was ready for the next-gen GPU it would be ready for the current GPU, it's not the specific ASIC code that is the problem, it's the huge midlayer sitting in the middle. 2) We really need to share all of this code between OSes, why does Linux not want it? Sharing code is a laudable goal and I appreciate the resourcing constraints that led us to the point at which we find ourselves, but the way forward involves finding resources to upstream this code, dedicated people (even one person) who can spend time on a day by day basis talking to people in the open and working upstream, improving other pieces of the drm as they go, reading atomic patches and reviewing them, and can incrementally build the DC experience on top of the Linux kernel infrastructure. Then having the corresponding changes in the DC codebase happen internally to correspond to how the kernel code ends up looking. Lots of this code overlaps with stuff the drm already does, lots of is stuff the drm should be doing, so patches to the drm should be sent instead. 3) Then how do we upstream it? Resource(s) need(s) to start concentrating at splitting this thing up and using portions of it in the upstream kernel. We don't land fully formed code in the kernel if we can avoid it. Because you can't review the ideas and structure as easy as when someone builds up code in chunks and actually develops in the Linux kernel. This has always produced better more maintainable code. Maybe the result will end up improving the AMD codebase as well. 4) Why can't we put this in staging? People have also mentioned staging, Daniel has called it a dead end, I'd have considered staging for this code base, and I still might. However staging has rules, and the main one is code in staging needs a TODO list, and agreed criteria for exiting staging, I don't think we'd be able to get an agreement on what the TODO list should contain and how we'd ever get all things on it done. If this code ended up in staging, it would most likely require someone dedicated to recreating it in the mainline driver in an incremental fashion, and I don't see that resource being available. 5) Why is a midlayer bad? I'm not going to go into specifics on the DC midlayer, but we abhor midlayers for a fair few reasons. The main reason I find causes the most issues is locking. When you have breaks in code flow between multiple layers, but having layers calling back into previous layers it becomes near impossible to track who owns the locking and what the current locking state is. Consider drma -> dca -> dcb -> drmb drmc -> dcc -> dcb -> drmb We have two codes paths that go back into drmb, now maybe drma has a lock taken, but drmc doesn't, but we've no indication when we hit drmb of what the context pre entering the DC layer is. This causes all kinds of problems. The main requirement is the driver maintains the execution flow as much as possible. The only callback behaviour should be from an irq or workqueue type situations where you've handed execution flow to the hardware to do something and it is getting back to you. The pattern we use to get our of this sort of hole is helper libraries, we structure code as much as possible as leaf nodes that don't call back into the parents if we can avoid it (we don't always succeed). So the above might becomes drma-> dca_helper -> dcb_helper -> drmb. In this case the code flow is controlled by drma, dca/dcb might be modifying data or setting hw state but when we get to drmb it's easy to see what data is needs and what locking. DAL/DC goes against this in so many ways, and when I look at the code I'm never sure where to even start pulling the thread to unravel it. Some questions I have for AMD engineers that also I'd want to see addressed before any consideration of merging would happen! How do you plan on dealing with people rewriting or removing code upstream that is redundant in the kernel, but required for internal stuff? How are you going to deal with new Linux things that overlap incompatibly with your internally developed stuff? If the code is upstream will it be tested in the kernel by some QA group, or will there be some CI infrastructure used to maintain and to watch for Linux code that breaks assumptions in the DC code? Can you show me you understand that upstream code is no longer 100% in your control and things can happen to it that you might not expect and you need to deal with it? Dave. </div> </div> </div> </body> </html>