From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] memory: simple memory tree printer
Date: Wed, 14 Sep 2011 22:24:26 +0300 [thread overview]
Message-ID: <4E70FF6A.8050401@redhat.com> (raw)
In-Reply-To: <4E70EDFF.4000008@siemens.com>
On 09/14/2011 09:10 PM, Jan Kiszka wrote:
> OK, let's try again: Do we have to model hierarchy in PIO address space
> at all? I don't think so.
We do. A device listens to addresses 0x100-0x110. Another BAR (at
0x106) clips this to 0x100-0x106. The pci/pci bridge clips this to
0x105-0x106. The host pci bridge remaps this as
0x1000000105-0x1000000106 in the memory address space space. But
someone configured a cpu-local region at this address, so the cpu can't
reach it at all.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-09-14 19:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 20:31 [Qemu-devel] [PATCH] memory: simple memory tree printer Blue Swirl
2011-09-12 6:43 ` Richard Henderson
2011-09-12 9:01 ` Jan Kiszka
2011-09-12 9:11 ` Avi Kivity
2011-09-12 9:19 ` Jan Kiszka
2011-09-14 15:10 ` Richard Henderson
2011-09-14 15:23 ` Avi Kivity
2011-09-14 15:27 ` Richard Henderson
2011-09-14 15:29 ` Avi Kivity
2011-09-14 15:36 ` Richard Henderson
2011-09-14 15:46 ` Avi Kivity
2011-09-14 17:58 ` Jan Kiszka
2011-09-14 18:10 ` Jan Kiszka
2011-09-14 19:24 ` Avi Kivity [this message]
2011-09-15 9:30 ` Jan Kiszka
2011-09-15 9:53 ` Avi Kivity
2011-09-15 10:18 ` Jan Kiszka
2011-09-15 11:21 ` Avi Kivity
2011-09-14 18:26 ` Richard Henderson
2011-09-12 7:00 ` Peter Maydell
2011-09-12 8:46 ` Avi Kivity
2011-09-12 8:53 ` Jan Kiszka
2011-09-12 9:12 ` Avi Kivity
2011-09-12 10:37 ` Gerd Hoffmann
2011-09-12 10:53 ` Avi Kivity
2011-09-12 20:07 ` Blue Swirl
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=4E70FF6A.8050401@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.