From: Christoffer Dall <christoffer.dall@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: Wei Huang <wei@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Juan Quintela <quintela@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V1 1/1] tests: Add migration test for aarch64
Date: Thu, 1 Feb 2018 15:04:11 +0100 [thread overview]
Message-ID: <20180201140411.GD21802@cbox> (raw)
In-Reply-To: <20180201122520.b2o75bmjaqwukuqs@kamzik.brq.redhat.com>
On Thu, Feb 01, 2018 at 01:25:20PM +0100, Andrew Jones wrote:
> On Thu, Feb 01, 2018 at 11:48:31AM +0100, Christoffer Dall wrote:
> > On Thu, Feb 01, 2018 at 11:42:22AM +0100, Andrew Jones wrote:
> > > On Thu, Feb 01, 2018 at 10:59:54AM +0100, Christoffer Dall wrote:
> > > > On Thu, Feb 1, 2018 at 10:33 AM, Ard Biesheuvel
> > > > > If you could use dirty page tracking to only perform the cache
> > > > > invalidation when the framebuffer memory has been updated, you can at
> > > > > least limit the impact to cases where the framebuffer is actually
> > > > > used, rather than sitting idle with a nice wallpaper image.
> > >
> > > Yes, this is the exact approach I took back when I experimented with
> > > this. I must have screwed up my PoC in some way (like using the gcc
> > > builtin), because it wasn't working for me...
> > >
> > Does that mean you have some code you feel like reviving and use to send
> > out an RFC based on? ;)
> >
>
> I don't usually delete things, but I do do some sort of copy on use
> from old homedirs to new ones from time to time, letting stuff that
> gets really old completely drop at some point. I might be able to
> find the old work, or just hack a quick and ugly version from my
> memory to share - hopefully whatever I did to cause it to fail last
> time has been forgotten :-)
>
If you have bandwidth to look at this that's great. Otherwise let us
know, and I'll see if I can devote some time to it.
Thanks,
-Christoffer
next prev parent reply other threads:[~2018-02-01 14:04 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
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 [this message]
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=20180201140411.GD21802@cbox \
--to=christoffer.dall@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=marc.zyngier@arm.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 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).