From: Igor Mammedov <imammedo@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'QEMU Developers' <qemu-devel@nongnu.org>,
'Peter Maydell' <peter.maydell@linaro.org>,
pbonzini@redhat.com, 'Alexander Graf' <agraf@suse.de>,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] hw/arm/virt: Add high MMIO PCI region
Date: Wed, 29 Jul 2015 14:05:19 +0200 [thread overview]
Message-ID: <20150729140519.175de902@nial.brq.redhat.com> (raw)
In-Reply-To: <011301d0c9e5$e2c21b90$a84652b0$@samsung.com>
On Wed, 29 Jul 2015 13:03:57 +0300
Pavel Fedin <p.fedin@samsung.com> wrote:
> Hello!
>
> > > I'm not sure that ARM architecture has this machine_done callback.
> > Maybe this would help you,
> > git grep machine_done
>
> Heh, i was not patient enough. I have already discovered this by myself, and yes, "virt" uses the
> same mechanism. But, still, i perhaps can have problems with testing it.
>
> > > So, can we leave fixed layout for now?
> > I suppose we could, it just means that we will have to add version-ed machines like
> > it's done on x86 to keep memory layout on old machine type the same so that
> > hardware won't change under guest's feet unexpectedly.
>
> Why?
> First, "virt" is completely virtual hardware. It does not exist in real world.
> Second, ARM architecture is flexible by definition. Guest is never expected to use hardcoded
> addresses, it is expected to read device tree. And, if base address of RAM changes, or base address
> of PCI region changes, nothing bad should happen.
Now imagine that guest was started on host with 'old' layout and then has been
migrated to a host with 'new' layout. Stability of layout matters, that's why
we support versioned machine types and compat nightmare even if basic machine
is the same, the same applies to ARM's virt machine.
>
> > Also in light of guests with huge memory size, 512Gb gap for RAM seems too small,
> > what are limitations of ARM64 regarding max supported physical address bits?
>
> 40 bits IIRC.
>
> > Could we put this 64 bit PCI hole at the end of address space, leaving the rest of
> > address space for RAM or whatever?
>
> I've done exactly this. Start = 512GB and size = 512GB. 0x8000000000...0xFFFFFFFFFF. I've done this
> after Paolo's comment that 2G is still small. And i agree because single ivshmem could be used by
> lots of VMs.
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>
next prev parent reply other threads:[~2015-07-29 12:05 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 [this message]
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
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=20150729140519.175de902@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=agraf@suse.de \
--cc=mst@redhat.com \
--cc=p.fedin@samsung.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).