From: Marcel Apfelbaum <marcel.a@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
"edk2-devel@lists.sourceforge.net"
<edk2-devel@lists.sourceforge.net>,
qemu-devel <qemu-devel@nongnu.org>,
Jordan Justen <jljusten@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Laszlo Ersek <lersek@redhat.com>, afaerber <afaerber@suse.de>,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] exec: fix regression by making system-memory region UINT64_MAX size
Date: Thu, 07 Nov 2013 23:38:34 +0200 [thread overview]
Message-ID: <1383860314.2527.72.camel@localhost.localdomain> (raw)
In-Reply-To: <527C06B5.2020401@redhat.com>
On Thu, 2013-11-07 at 22:31 +0100, Paolo Bonzini wrote:
> Il 07/11/2013 22:24, Marcel Apfelbaum ha scritto:
> > Thank you Laszlo for the detailed info!
> > I think the problem is right above. Why pci-hole and system.flash collide?
> > IMHO we should not play with priorities here, better solve the collision.
>
> We need to audit all the other boards that support PCI... I'll take a
> look tomorrow since you guys are off.
Thanks Paolo,
Let me just point out what I know (or I think I know):
1. Not all architectures have the behavior: "Address space that is not RAM(and friends) is for sure PCI".
Only x86 behaves like this (I think). That means that you cannot have a 64bit wide pci-hole
with lower priority that catches all accesses that are not for RAM(and firends).
2. If the above is right, and making pci-hole 64 bit wide is not an option,
playing with pci-holes/other-region priorities it would be just wrong,
it would be only to "fight" with the locality of the memory region's priority.
That being said, I am looking forward for your findings.
Thanks!
Marcel
>
> Paolo
next prev parent reply other threads:[~2013-11-07 21:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 20:48 [Qemu-devel] [PATCH] exec: fix regression by making system-memory region UINT64_MAX size Marcel Apfelbaum
2013-11-03 21:26 ` Peter Maydell
2013-11-04 6:18 ` Michael S. Tsirkin
2013-11-04 9:33 ` Marcel Apfelbaum
2013-11-04 9:59 ` Michael S. Tsirkin
2013-11-07 20:27 ` Jordan Justen
2013-11-07 20:44 ` Marcel Apfelbaum
2013-11-07 21:12 ` Laszlo Ersek
2013-11-07 21:21 ` [Qemu-devel] [edk2] " Paolo Bonzini
2013-11-07 21:32 ` Laszlo Ersek
2013-11-07 21:24 ` [Qemu-devel] " Marcel Apfelbaum
2013-11-07 21:31 ` Paolo Bonzini
2013-11-07 21:38 ` Marcel Apfelbaum [this message]
2013-11-07 21:51 ` Peter Maydell
2013-11-07 22:06 ` Marcel Apfelbaum
2013-11-08 8:05 ` Paolo Bonzini
2013-11-08 10:44 ` Peter Maydell
2013-11-08 11:00 ` Paolo Bonzini
2013-11-08 15:16 ` Marcel Apfelbaum
2013-11-08 15:08 ` Marcel Apfelbaum
2013-11-08 16:12 ` Paolo Bonzini
2013-11-08 16:19 ` Marcel Apfelbaum
2013-11-07 21:48 ` Laszlo Ersek
2013-11-07 22:09 ` Marcel Apfelbaum
2013-11-07 22:23 ` [Qemu-devel] [PATCH 0/2] " Laszlo Ersek
2013-11-07 22:23 ` [Qemu-devel] [PATCH 1/2] i386/pc: propagate flash size from pc_system_flash_init() to pc_init1() Laszlo Ersek
2013-11-08 6:09 ` Jordan Justen
2013-11-08 15:07 ` Laszlo Ersek
2013-11-08 15:16 ` Peter Maydell
2013-11-08 15:27 ` Laszlo Ersek
2013-11-08 15:28 ` Peter Maydell
2013-11-07 22:23 ` [Qemu-devel] [PATCH 2/2] i386/pc_piix: the pci-hole should end where the system flash starts Laszlo Ersek
2013-11-08 10:14 ` [Qemu-devel] reverting commit a53ae8e934cd54686875b5bcfc2f434244ee55d6 Re: [edk2] [PATCH 0/2] Re: exec: fix regression by making system-memory region UINT64_MAX size Paolo Bonzini
2013-11-08 16:37 ` [Qemu-devel] " Igor Mammedov
2013-11-08 15:42 ` [Qemu-devel] [PATCH] " Andreas Färber
2013-11-08 16:19 ` Laszlo Ersek
2013-11-08 16:26 ` Paolo Bonzini
2013-11-08 17:09 ` Andreas Färber
2013-11-08 17:15 ` Paolo Bonzini
2013-11-08 17:30 ` Laszlo Ersek
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=1383860314.2527.72.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=edk2-devel@lists.sourceforge.net \
--cc=jan.kiszka@siemens.com \
--cc=jljusten@gmail.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).