From: Joel Schopp <joel.schopp@amd.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] arm64: 64K pages and > 1024MB guest
Date: Fri, 1 Aug 2014 09:02:16 -0500 [thread overview]
Message-ID: <53DB9DE8.3020805@amd.com> (raw)
In-Reply-To: <53DB7CF4.1020702@redhat.com>
> I agree.
>
> I think the patch is right but, besides these considerations, does this
> bug still manifest itself after Andrew fixed the start address of the
> device at 0x90010000 (IIRC it was the pl031)?
The device I see with that address is:
hw/arm/virt.c: [VIRT_RTC] = { 0x90010000, 0x1000 },
The bug still manifests itself with that in the tree (without my patch
applied).
next prev parent reply other threads:[~2014-08-01 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 20:09 [Qemu-devel] [PATCH] arm64: 64K pages and > 1024MB guest Joel Schopp
2014-08-01 11:28 ` Peter Maydell
2014-08-01 11:41 ` Paolo Bonzini
2014-08-01 14:02 ` Joel Schopp [this message]
2014-08-01 14:19 ` Paolo Bonzini
2014-08-01 18:36 ` Joel Schopp
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=53DB9DE8.3020805@amd.com \
--to=joel.schopp@amd.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).