From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B70EC37C0FE; Thu, 5 Mar 2026 15:54:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772726045; cv=none; b=GTrYIntTZD4qnDAjsS0VvJPp2xQoQXwsu/muvbCJDaXXcuNpEqmLdR450r/AdoXO5stEw4/POKcu9y8BspqmbWsFLnt49YzGyWFpdYDViillSBefWBB+NSwKUo3dK3MsVeTg+xdh9l41STDU21Vrw/eXSTx+Vh7f3ru/DOznf6o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772726045; c=relaxed/simple; bh=bidVYVICOdGRtsflGC4A0uveaK1vUY8eMwnQDgINvJk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Lv1F0mvUCQQRzx8MO8D3daQhX36jjmJ0pQFsAHkWh093eTT0C0K+ooyAdA+1d5P5Oi6y5CGdmbTm7Q1aoxEZDL07r+96FkmM7XOGFPbribIio+pGwkQbWKvAAEFM/SatJkFKe8CByeGl5fzEjMKKoEs5Ltcdo8k2i5DUPAd4RNM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=eZJCCAVU; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="eZJCCAVU" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3C7B2C116C6; Thu, 5 Mar 2026 15:54:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772726045; bh=bidVYVICOdGRtsflGC4A0uveaK1vUY8eMwnQDgINvJk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=eZJCCAVUWWYORhHM/hXKwyUzjRceofEDLc5kRET0rTP7R6iy+D0Ajm0btkk8m+WFO h+fc0jfhIfLyBBpTL4+7W8xqSfn5KE1Kg2nlDIblOoWOQkrz3Pq2NJwjk4OVl/e7oO gHa1vXaMgWbQJe4aqwrwoJ/LhdDAo7wYy4FY9/Rlyj29bqqcOdrtZBgW/1C7XThz76 lIcJJ0o+bHEEAoTJgI39/deFtUjy3KRx4kZ56b16lAY+rskU9QIXDtqoEugclap2JJ IbtSMxdcIsm88dwZNkSNqjQlGc0g/U/1QflrQKmqRYFvCWTd7Qqi/ZZtTqT6jytX1D zkul7kfsLNx9A== Date: Thu, 5 Mar 2026 16:54:00 +0100 From: Niklas Cassel To: Pedro Falcato Cc: Damien Le Moal , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v2] ata: libata-core: Add BRIDGE_OK quirk for QEMU drives Message-ID: References: <20260305145312.1081112-1-pfalcato@suse.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260305145312.1081112-1-pfalcato@suse.de> On Thu, Mar 05, 2026 at 02:53:12PM +0000, Pedro Falcato wrote: > Currently, whenever you boot with a QEMU drive over an AHCI interface, > you get: > [ 1.632121] ata1.00: applying bridge limits > > This happens due to the kernel not believing the given drive is SATA, > since word 93 of IDENTIFY (ATA_ID_HW_CONFIG) is non-zero. The result is > a pretty severe limit in max_hw_sectors_kb, which limits our IO sizes. > > [...] Added Damien's R-b tag, since the patch is essentially the same as V1. Applied to libata/linux.git (libata-for-7.0-fixes), thanks! [1/1] ata: libata-core: Add BRIDGE_OK quirk for QEMU drives https://git.kernel.org/libata/linux/c/b92b0075 Kind regards, Niklas