From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alexey Kardashevskiy" <aik@ozlabs.ru>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Guenter Roeck" <linux@roeck-us.net>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>, qemu-arm <qemu-arm@nongnu.org>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: Re: Question about (and problem with) pflash data access
Date: Thu, 13 Feb 2020 10:51:12 +0100 [thread overview]
Message-ID: <52f0b829-151a-3dd0-0ec7-c3155185510c@redhat.com> (raw)
In-Reply-To: <279d959f-f7e5-65e1-9c68-459f3fed56d3@ozlabs.ru>
On 13/02/20 08:40, Alexey Kardashevskiy wrote:
>>>
>>> memory-region: system
>>> 0000000000000000-ffffffffffffffff (prio 0, i/o): system
>>> 0000000000000000-0000000001ffffff (prio 0, romd): omap_sx1.flash0-1
>>> 0000000000000000-0000000001ffffff (prio 0, rom): omap_sx1.flash0-0
>> Eh two memory regions with same size and same priority... Is this legal?
>
> I'd say yes if used with memory_region_set_enabled() to make sure only
> one is enabled. Having both enabled is weird and we should print a
> warning.
Yeah, it's undefined which one becomes visible.
Paolo
next prev parent reply other threads:[~2020-02-13 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 18:46 Question about (and problem with) pflash data access Guenter Roeck
2020-02-12 21:39 ` Philippe Mathieu-Daudé
2020-02-12 23:09 ` Guenter Roeck
2020-02-12 23:50 ` Philippe Mathieu-Daudé
2020-02-13 7:40 ` Alexey Kardashevskiy
2020-02-13 9:51 ` Paolo Bonzini [this message]
2020-02-13 14:26 ` Guenter Roeck
2020-02-13 14:39 ` Peter Maydell
2020-02-13 15:24 ` Philippe Mathieu-Daudé
2020-02-13 16:21 ` Guenter Roeck
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=52f0b829-151a-3dd0-0ec7-c3155185510c@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=kwolf@redhat.com \
--cc=linux@roeck-us.net \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=plagnioj@jcrosoft.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).