Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755674Ab1FXLlE (ORCPT ); Fri, 24 Jun 2011 07:41:04 -0400 Received: from h1446028.stratoserver.net ([85.214.92.142]:40062 "EHLO mail.ahsoftware.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753491Ab1FXLlA (ORCPT ); Fri, 24 Jun 2011 07:41:00 -0400 Message-ID: <4E0477AB.3080400@ahsoftware.de> Date: Fri, 24 Jun 2011 13:40:27 +0200 From: Alexander Holler User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.10 MIME-Version: 1.0 To: Alan Stern CC: Arnd Bergmann , gregkh@suse.de, Nicolas Pitre , linux-usb@vger.kernel.org, lkml , Rabin Vincent , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] USB: ehci: use packed, aligned(4) instead of removing the packed attribute References: In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2865 Lines: 58 Am 23.06.2011 16:25, schrieb Alan Stern: > On Thu, 23 Jun 2011, Alexander Holler wrote: > >> Sorry, I never wanted to talk about the issue itself (I've already said >> that), I just wanted to bring in some additional clarity for people >> looking at the code. >> >> I think if there is a packed,aligned(4) most people reading that are >> able to imaging how the struct looks like, whereas nothing (without >> packed) might leave doubts which than requires to read compiler docs or >> the generated code, if one searches a problem in that area. > > I disagree. If there are no annotations at all (no packed), there > should be no doubts. The compiler will add padding wherever it is > needed for internal alignment and perhaps also at the end of the > structure. Nowhere else. I agree to disagree but I assume thats ok. ;) Let me finally add some maybe interesting or informational points for those who are working or examing the issue and/or who might be involved in other discussions on the reason for removing the packed: - I didn't have any problems booting from ehci with kernels compiled with gcc 4.6 on armv5 (or x86*). - 2.6.38.4 (and below) compiled with gcc 4.6 booted from ehci (on a classic beagleboard c4, armv7), whereas everything from 2.6.38.5 upwards didn't (same compiler, same config). I've discovered that before having seen that this might be the issue with the packed, therefor I haven't tested if 2.6.38.5 might work without a packed and have just used gcc 4.5.x for 2.6.38.x. I have tested that a 2,6,39.x compiled with gcc 4.6 and with a removed packed boots from ehci on the beagleboard, so the patch which removes the packed might be a candidate for the stable tree. The reason why booting from ehci stopped with 2.6.38.5+ (gcc 4.6) might be interesting for someone. Looking at the git log I haven't seen something special and I don't know why anything below 2.6.38.5 worked with gcc 4.6 and the packed. - I don't like the idea that every member of every packed struct (without an aligned) might be handled byte by byte. It might be necessary but I still don't like it and would prefer the old behaviour of gcc. I've added this point just to express my personal humble opinion and I don't want to get involved in a discussion on that topic. ;) I've just got involved on that topic by accident and never have had a real reason to do something there (I've done that just for fun). Therefore I now prefer to disappear, which means there is absolutely no reason to respond (to me) or to explain anything to me. Regards and sorry if I wasted someones time, Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/