From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49986) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cX7vH-0003gH-Kl for qemu-devel@nongnu.org; Fri, 27 Jan 2017 09:54:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cX7vF-0001DZ-R6 for qemu-devel@nongnu.org; Fri, 27 Jan 2017 09:54:43 -0500 Received: from mail-ua0-x22c.google.com ([2607:f8b0:400c:c08::22c]:36052) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cX7vF-0001DD-Li for qemu-devel@nongnu.org; Fri, 27 Jan 2017 09:54:41 -0500 Received: by mail-ua0-x22c.google.com with SMTP id 96so206410880uaq.3 for ; Fri, 27 Jan 2017 06:54:41 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <98b1ad64-fe10-4ede-3493-f6d4b49ee1d9@sysgo.com> <20170112113619.zuc5tuhmhzvawnmz@hawk.localdomain> From: Peter Maydell Date: Fri, 27 Jan 2017 14:54:20 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH] pflash_cfi01: fix per device sector length in CFI table List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrew Jones Cc: David Engraf , Kevin Wolf , QEMU Developers , Qemu-block , Max Reitz , "Dr. David Alan Gilbert" On 27 January 2017 at 14:31, Peter Maydell wrote: > On 12 January 2017 at 11:36, Andrew Jones wrote: >> On Thu, Jan 12, 2017 at 10:42:41AM +0000, Peter Maydell wrote: >>> Thanks for the patch. I haven't checked against the pflash spec yet, >>> but this looks like it's probably the right thing. >>> >>> The only two machines which use a setup with multiple devices (ie >>> which specify device_width to the pflash_cfi01) are vexpress and virt. >>> For all other machines this patch leaves the behaviour unchanged. >>> >>> Q: do we need to have some kind of nasty hack so that pre-2.9 virt >>> still gets the old broken values in the CFI table, for version and >>> migration compatibility? Ccing Drew for an opinion... >>> >> >> I'm pretty sure we need the nasty hack, but I'm also Ccing David for >> his opinion. > > So given our decision about not needing the back-compat property > for the UEFI table entry, do we still agree that we need one here? Looking more closely at the patch, changing writeblock underneath a guest's feet is probably not very polite, so let's take the safe path of making it version-dependent. I've applied David's patch to target-arm.next (with some tweaks to the commit message). thanks -- PMM