qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"Leif Lindholm (Linaro address)" <leif.lindholm@linaro.org>,
	edk2-devel-01 <edk2-devel@lists.01.org>,
	Drew Jones <drjones@redhat.com>,
	qemu devel list <qemu-devel@nongnu.org>,
	Igor Mammedov <imammedo@redhat.com>,
	Andrea Bolognani <abologna@redhat.com>,
	libvirt devel <libvir-list@redhat.com>
Subject: Re: [Qemu-devel] dynamic DRAM base for ArmVirtQemu
Date: Fri, 13 Oct 2017 17:18:59 +0100	[thread overview]
Message-ID: <CAFEAcA8yvST1fKaLjauz3OV=gRTEKsuLfWvJ3NgCA_weFy2cOg@mail.gmail.com> (raw)
In-Reply-To: <4cce2b8b-a411-bd5d-a06f-b0b80a5fb2f1@redhat.com>

On 13 October 2017 at 13:51, Laszlo Ersek <lersek@redhat.com> wrote:
> Another idea is to move *the* system DRAM base to a different guest-phys
> address. (Likely using a different version of the "virt" machine type,
> or even a different machine type entirely.) This would not be compatible
> with current ArmVirtQemu, which hard-codes the system DRAM base in
> several, quite brittle / sensitive, locations. (More on this later --
> that's going to be the larger part of my email anyway.) In order to
> handle the new base in ArmVirtQemu, two approaches are possible: change
> the hard-coded address(es), or cope with the address dynamically.

I strongly don't want to move the DRAM base in the "virt" board.
This is one of the few fixed things we've said that guest code
can rely on without having to fish the information out of the
device tree.

thanks
-- PMM

  parent reply	other threads:[~2017-10-13 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 12:51 [Qemu-devel] dynamic DRAM base for ArmVirtQemu Laszlo Ersek
2017-10-13 13:21 ` Ard Biesheuvel
2017-10-13 19:40   ` Laszlo Ersek
2017-10-13 16:18 ` Peter Maydell [this message]
2017-10-13 16:30   ` Andrew Jones
2017-10-13 19:50   ` 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='CAFEAcA8yvST1fKaLjauz3OV=gRTEKsuLfWvJ3NgCA_weFy2cOg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=abologna@redhat.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=drjones@redhat.com \
    --cc=edk2-devel@lists.01.org \
    --cc=imammedo@redhat.com \
    --cc=leif.lindholm@linaro.org \
    --cc=lersek@redhat.com \
    --cc=libvir-list@redhat.com \
    --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).