From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Juan Quintela <quintela@redhat.com>,
Patch Tracking <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Blue Swirl <blauwirbel@gmail.com>,
Amit Shah <amit.shah@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/8] target-sparc: Update to use VMStateDescription
Date: Fri, 15 Jan 2016 17:53:05 +0000 [thread overview]
Message-ID: <56993201.60603@ilande.co.uk> (raw)
In-Reply-To: <CAFEAcA8ocqrVe4fuUBLtbCV9kMqXvLGPdCa5Bp-GwKoLwfbDbA@mail.gmail.com>
On 15/01/16 17:07, Peter Maydell wrote:
> On 15 January 2016 at 17:03, Mark Cave-Ayland
> <mark.cave-ayland@ilande.co.uk> wrote:
>> I've just run through some SPARC32 tests with this patchset applied -
>> testing a savevm/loadvm pair pre-patch and post-patch, and then a few
>> random tests with various OSs at random points during boot and no
>> regressions here, so:
>>
>> Tested-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>
> Thanks.
>
>> The only minor nit I could see during review was that both patches 7 and
>> 8 bump the VMState revision for SPARC64, and given that before the last
>> patch in the set nothing works then is it just worth bumping once to
>> version 8 in patch 7 and let that be it?
>
> My general feeling is that there isn't a significant shortage
> of positive integers that would lead us to want to conserve them :-)
> If you prefer only bumping once you can do that when you apply the
> patches to your target-sparc queue if you like.
Ha well if no-one minds too much then I'm not too worried either :)
>From the cover letter it sounds like you've got some further QOM
clean-ups waiting on this, so I'll get it merged and queued shortly.
ATB,
Mark.
prev parent reply other threads:[~2016-01-15 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 12:40 [Qemu-devel] [PATCH v2 0/8] target-sparc: Update to use VMStateDescription Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 1/8] vmstate: introduce CPU_DoubleU arrays Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 2/8] vmstate: Introduce VMSTATE_VARRAY_MULTPLY Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 3/8] vmstate: define vmstate_info_uinttl Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 4/8] target-sparc: Split cpu_put_psr into side-effect and no-side-effect parts Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 5/8] target-sparc: Don't flush TLB in cpu_load function Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 6/8] target-sparc: Convert to VMStateDescription Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 7/8] target-sparc: Use VMState arrays for SPARC64 TLB/MMU state Peter Maydell
2016-01-11 12:40 ` [Qemu-devel] [PATCH v2 8/8] target-sparc: Migrate CWP and PIL for SPARC64 Peter Maydell
2016-01-15 17:03 ` [Qemu-devel] [PATCH v2 0/8] target-sparc: Update to use VMStateDescription Mark Cave-Ayland
2016-01-15 17:07 ` Peter Maydell
2016-01-15 17:53 ` Mark Cave-Ayland [this message]
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=56993201.60603@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=amit.shah@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).