qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Alexander Graf' <agraf@suse.de>,
	'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] Virt machine memory map
Date: Wed, 22 Jul 2015 09:52:09 +0300	[thread overview]
Message-ID: <03d501d0c44a$eefe6da0$ccfb48e0$@samsung.com> (raw)
In-Reply-To: <55ACDA41.2080201@suse.de>

 Hello!

> > I think the theory we discussed at the time of putting in the PCIe
> > device was that if we wanted this we'd add support for the other
> > PCIe memory window (which would then live at somewhere above 4GB).
> > Alex, can you remember what the idea was?
> 
> Yes, pretty much. It would give us an upper bound to the amount of RAM
> that we're able to support, but at least we would be able to support big
> MMIO regions like for ivshmem.

 But i currently think that specification of "Generic PCI host" assumes only a single MMIO region + single PIO region + single ECAM. And we cannot have two MMIO regions without changing its specification, which can be problematic. Am i wrong about this ?

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

  parent reply	other threads:[~2015-07-22  6:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20  8:55 [Qemu-devel] [RFC] Virt machine memory map Pavel Fedin
2015-07-20  9:41 ` Peter Maydell
2015-07-20 11:23   ` Alexander Graf
2015-07-20 13:30     ` Igor Mammedov
2015-07-20 13:44       ` Alexander Graf
2015-07-22  6:52     ` Pavel Fedin [this message]
2015-07-22  7:33       ` Alexander Graf
2015-07-22  8:42         ` Pavel Fedin

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='03d501d0c44a$eefe6da0$ccfb48e0$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=agraf@suse.de \
    --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).