qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, alex.bennee@linaro.org, lersek@redhat.com,
	kwolf@redhat.com, qemu-ppc@nongnu.org, qemu-block@nongnu.org,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 11/11] pflash: Clean up after commit 368a354f02b part 2
Date: Tue, 5 Mar 2019 18:54:17 +0100	[thread overview]
Message-ID: <f37147d9-af24-4625-502e-1a51c3fa9a69@redhat.com> (raw)
In-Reply-To: <878sxt5l31.fsf@dusky.pond.sub.org>

On 3/5/19 5:42 PM, Markus Armbruster wrote:
> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> 
>> Hi Markus,
>>
>> On 2/26/19 8:34 PM, Markus Armbruster wrote:
>>> QOMification left parameter @size unused in pflash_cfi01_register()
>>> and pflash_cfi02_register().  Obviously, @size should match
>>> @sector_len and @nb_blocs, i.e. size == sector_len * nb_blocs.  All
>>> callers satisfy this.
>>>
>>> Remove @nb_blocs and compute it from @size and @sector_len.
>>
>> The pflash devices are simplistically modelled has having a single
>> sector size. This is not true for real hw (pflash have different sector
>> sizes). It is however true for the unofficial VirtPFlash device, which
>> doesn't have any spec.
>>
>> The only valid parameter is @size. The @sector_len and @nb_blocs don't
>> match the hardwares. QEMU @sector_len is currently "The biggest
>> sector_size the device has" and QEMU @nb_blocs is really "@size /
>> @sector_len", although it doesn't match the nb_blocs the hardware has.
>>
>> I don't disagree with the patch content, but the description is not
>> accurate. We can indeed drop the @nb_blocs argument because we model an
>> unique sector size, thus we can calculate "@nb_blocs = @size /
>> @sector_len" in the model.
>>
>> With the patch description fixed:
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> 
> Let me try to fix it.
> 
>     Our pflash devices are simplistically modelled has having
>     "num-blocks" sectors of equal size "sector-length".  Real hardware
>     commonly has sectors of different sizes.  How our "sector-length"
>     property is related to the physical device's multiple sector sizes
>     is unclear.
> 
>     Helper functions pflash_cfi01_register() and pflash_cfi02_register()
>     create a pflash device, set properties including "sector-length" and
>     "num-blocks", and realize.  They take parameters @size, @sector_len
>     and @nb_blocs.
> 
>     QOMification left parameter @size unused.  Obviously, @size should
>     match @sector_len and @nb_blocs, i.e. size == sector_len * nb_blocs.
>     All callers satisfy this.
> 
>     Remove @nb_blocs and compute it from @size and @sector_len.
> 
> D'accord?

Oui, parfait!

  reply	other threads:[~2019-03-05 17:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 19:33 [Qemu-devel] [PATCH v2 00/11] pflash: Fixes and cleanups Markus Armbruster
2019-02-26 19:33 ` [Qemu-devel] [PATCH v2 01/11] pflash: Rename pflash_t to PFlashCFI01, PFlashCFI02 Markus Armbruster
2019-03-05 12:22   ` Philippe Mathieu-Daudé
2019-02-26 19:33 ` [Qemu-devel] [PATCH v2 02/11] pflash_cfi01: Do not exit() on guest aborting "write to buffer" Markus Armbruster
2019-02-26 23:59   ` Philippe Mathieu-Daudé
2019-02-27 11:09   ` Alex Bennée
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 03/11] pflash_cfi01: Log use of flawed " Markus Armbruster
2019-02-26 23:57   ` Philippe Mathieu-Daudé
2019-02-27 11:30   ` Alex Bennée
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 04/11] pflash: Rename *CFI_PFLASH* to *PFLASH_CFI* Markus Armbruster
2019-02-27  0:00   ` Philippe Mathieu-Daudé
2019-02-27 11:09   ` Alex Bennée
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 05/11] hw: Use PFLASH_CFI0{1, 2} and TYPE_PFLASH_CFI0{1, 2} Markus Armbruster
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 06/11] sam460ex: Don't size flash memory to match backing image Markus Armbruster
2019-02-26 22:30   ` BALATON Zoltan
2019-02-27 11:04   ` Alex Bennée
2019-03-05 19:12   ` Philippe Mathieu-Daudé
2019-03-05 22:49     ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2019-03-06  6:51       ` Markus Armbruster
2019-03-06  7:47         ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 07/11] ppc405_boards: " Markus Armbruster
2019-02-27 10:35   ` Alex Bennée
2019-03-07  7:01     ` Markus Armbruster
2019-03-08  4:39       ` David Gibson
2019-03-08  9:46         ` Markus Armbruster
2019-03-05 19:23   ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 08/11] r2d: Flash memory creation is confused about size, mark FIXME Markus Armbruster
2019-03-05 17:48   ` Philippe Mathieu-Daudé
2019-03-06 15:00     ` Markus Armbruster
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 09/11] mips_malta: Clean up definition of flash memory size somewhat Markus Armbruster
2019-02-27 11:28   ` Alex Bennée
2019-03-05 16:33     ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 10/11] pflash: Clean up after commit 368a354f02b part 1 Markus Armbruster
2019-03-05 13:29   ` Philippe Mathieu-Daudé
2019-02-26 19:34 ` [Qemu-devel] [PATCH v2 11/11] pflash: Clean up after commit 368a354f02b part 2 Markus Armbruster
2019-02-27  1:11   ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2019-02-27  6:57     ` Markus Armbruster
2019-03-05 13:55   ` [Qemu-devel] " Philippe Mathieu-Daudé
2019-03-05 16:42     ` Markus Armbruster
2019-03-05 17:54       ` Philippe Mathieu-Daudé [this message]
2019-02-26 19:56 ` [Qemu-devel] [PATCH v2 00/11] pflash: Fixes and cleanups Alex Bennée
2019-02-27  6:57   ` Markus Armbruster
2019-02-27 11:30     ` Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f37147d9-af24-4625-502e-1a51c3fa9a69@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).