From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: SATA resume slowness, e1000 MSI warning Date: Sun, 11 Mar 2007 12:27:40 -0600 Message-ID: References: <20070311112400.GB24475@mellanox.co.il> <20070311180342.GE24475@mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20070311180342.GE24475@mellanox.co.il> (Michael S. Tsirkin's message of "Sun, 11 Mar 2007 20:03:42 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: "Michael S. Tsirkin" Cc: "Kok, Auke" , Michal Piotrowski , Jeff Garzik , Ingo Molnar , linux-pm@lists.osdl.org, Linux Kernel Mailing List , Adrian Bunk , Pavel Machek , Jens Axboe , Thomas Gleixner , Linus Torvalds , Andrew Morton List-Id: linux-pm@vger.kernel.org "Michael S. Tsirkin" writes: >> Rumor has it that some pci devices can't tolerate < 32bit accesses. >> Although I have never met one. > > hopefully not bridge devices? > >> The two factors together suggest that >> for generic code it probably makes sense to operate on 32bit >> quantities, and just to ignore the read-only portion. > > The code for regular devices seems to use 16-bit accesses, so > I think it's best to stay consistent. Or do you want to change this too? If we are stomping rare probabilities we might as well change that too. The code to save pci-x state is relatively recent. So it probably just hasn't met a problem device yet (assuming they exist). Eric