From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Wei Huang <wei@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V1 1/1] tests: Add migration test for aarch64
Date: Mon, 29 Jan 2018 09:53:31 +0000 [thread overview]
Message-ID: <20180129095330.GA2408@work-vm> (raw)
In-Reply-To: <CAFEAcA_QgROXb-7ZbWhL6zM5RmqLK5hyU7Whh+-7REMsXghQmA@mail.gmail.com>
* Peter Maydell (peter.maydell@linaro.org) wrote:
> On 26 January 2018 at 19:46, Dr. David Alan Gilbert <dgilbert@redhat.com> wrote:
> > * Peter Maydell (peter.maydell@linaro.org) wrote:
> >> I think the correct fix here is that your test code should turn
> >> its MMU on. Trying to treat guest RAM as uncacheable doesn't work
> >> for Arm KVM guests (for the same reason that VGA device video memory
> >> doesn't work). If it's RAM your guest has to arrange to map it as
> >> Normal Cacheable, and then everything should work fine.
> >
> > Does this cause problems with migrating at just the wrong point during
> > a VM boot?
>
> It wouldn't surprise me if it did, but I don't think I've ever
> tried to provoke that problem...
If you think it'll get the RAM contents wrong, it might be best to fail
the migration if you can detect the cache is disabled in the guest.
Dave
> thanks
> -- PMM
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-01-29 9:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 21:22 [Qemu-devel] [PATCH V1 1/1] tests: Add migration test for aarch64 Wei Huang
2018-01-25 20:05 ` Dr. David Alan Gilbert
2018-01-26 15:47 ` Wei Huang
2018-01-26 16:39 ` Peter Maydell
2018-01-26 17:08 ` Wei Huang
2018-01-26 19:46 ` Dr. David Alan Gilbert
2018-01-28 15:08 ` Peter Maydell
2018-01-29 9:53 ` Dr. David Alan Gilbert [this message]
2018-01-29 10:04 ` Peter Maydell
2018-01-29 10:19 ` Dr. David Alan Gilbert
2018-01-29 10:32 ` Marc Zyngier
2018-01-31 9:53 ` Christoffer Dall
2018-01-31 15:18 ` Ard Biesheuvel
2018-01-31 15:23 ` Dr. David Alan Gilbert
2018-01-31 16:53 ` Christoffer Dall
2018-01-31 16:59 ` Ard Biesheuvel
2018-01-31 17:39 ` Christoffer Dall
2018-01-31 18:00 ` Ard Biesheuvel
2018-01-31 19:12 ` Christoffer Dall
2018-01-31 20:15 ` Ard Biesheuvel
2018-02-01 9:17 ` Christoffer Dall
2018-02-01 9:33 ` Ard Biesheuvel
2018-02-01 9:59 ` Christoffer Dall
2018-02-01 10:09 ` Ard Biesheuvel
2018-02-01 10:42 ` Andrew Jones
2018-02-01 10:48 ` Christoffer Dall
2018-02-01 12:25 ` Andrew Jones
2018-02-01 14:04 ` Christoffer Dall
2018-02-01 20:01 ` Dr. David Alan Gilbert
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=20180129095330.GA2408@work-vm \
--to=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wei@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.