qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Igor Mammedov' <imammedo@redhat.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
	pbonzini@redhat.com, 'QEMU Developers' <qemu-devel@nongnu.org>,
	'Alexander Graf' <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3] hw/arm/virt: Add high MMIO PCI region
Date: Wed, 29 Jul 2015 12:48:18 +0300	[thread overview]
Message-ID: <00f501d0c9e3$b3d19380$1b74ba80$@samsung.com> (raw)
In-Reply-To: <20150729111055.2bf307ac@nial.brq.redhat.com>

 Hello!

> this is wrong since dword is too small for values of high memory
> use aml_qword_memory() instead

 Thanks, will fix it.

> since window is at fixed position and it's not possible for guest to
> move base address of the range, make AddressMaximum the same as AddressMinimum i.e.

 But it is anyway not possible. On ARM hardware PCI range addresses are normally hardwired (at least
on simple machine which we are emulating), and the OS doesn't have control over it. And i'm not sure
whether some hotplugged memory can be overlaid on top of it. This is because on PC PCI is a core
system bus, which represents all address space, and RAM is kind of plugged into it. On ARM another
buses are used for system core, and PCI controller, from the point of view of that bus, is a single
device, which occupies some space. So AFAIK having something else on top of PCI hole on ARM would be
abnormal.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia

  reply	other threads:[~2015-07-29  9:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 11:09 [Qemu-devel] [PATCH v3] hw/arm/virt: Add high MMIO PCI region Pavel Fedin
2015-07-27 13:26 ` Igor Mammedov
2015-07-27 14:36   ` Pavel Fedin
2015-07-27 15:18     ` Michael S. Tsirkin
2015-07-27 15:51       ` Peter Maydell
2015-07-29  8:58   ` Pavel Fedin
2015-07-29  9:03     ` Peter Maydell
2015-07-29  9:45       ` Pavel Fedin
2015-07-29  9:56         ` Peter Maydell
2015-07-29 11:16           ` Pavel Fedin
2015-07-29 11:45             ` Peter Maydell
2015-07-29 14:01               ` Pavel Fedin
2015-08-03  7:03               ` Pavel Fedin
2015-08-03  7:56                 ` Peter Maydell
2015-08-03  8:09                   ` Pavel Fedin
2015-08-03  9:48                     ` Peter Maydell
2015-08-03 10:20                       ` Pavel Fedin
2015-08-03 20:17                         ` Alexander Graf
2015-07-29  9:32     ` Igor Mammedov
2015-07-29 10:03       ` Pavel Fedin
2015-07-29 10:21         ` Peter Maydell
2015-07-29 12:05         ` Igor Mammedov
2015-07-29 12:13           ` Pavel Fedin
2015-07-29 12:35           ` Peter Maydell
2015-07-29  9:10 ` Igor Mammedov
2015-07-29  9:48   ` Pavel Fedin [this message]
2015-07-29 11:59     ` Igor Mammedov
2015-07-29 12:02       ` Pavel Fedin
2015-07-29 13:24         ` Igor Mammedov

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='00f501d0c9e3$b3d19380$1b74ba80$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=agraf@suse.de \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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).