From: Mostafa Saleh <smostafa@google.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, jean-philippe@linaro.org,
eric.auger@redhat.com, peter.maydell@linaro.org,
qemu-arm@nongnu.org
Subject: Re: [PATCH v4] hw/arm/smmuv3: Add GBPA register
Date: Sun, 12 Feb 2023 22:20:57 +0000 [thread overview]
Message-ID: <Y+lmSTN/mTow+JGe@google.com> (raw)
In-Reply-To: <e920aa91-c153-0898-d2d3-da141233d60d@linaro.org>
On Sun, Feb 12, 2023 at 05:18:33AM -1000, Richard Henderson wrote:
> > Please correct me if I am wrong. From what I see, the initial for value
> > GBPA will be set from smmu_reset_hold which is called from context of
> > qemu_system_reset from qemu_init context.
> > And migration will start after that in migration_incoming_process from
> > qemu_main_loop context.
> >
> > I validated that also by printing the value of GBPA from vmstate_smmuv3
> > pre_load at migration without GPBA, and it is the same as
> > SMMU_GBPA_RESET_VAL.
>
> Is that from -loadvm on the command-line, or the loadvm command from the
> monitor? It's the latter that I suspect requires the pre_load.
I was testing before with migration
-From qemu monitor with migrate command
-Load it from cmdline with -incoming
I tested now with savevm/loadvm from qemu monitor
On vmload command, load_snapshot is called which in the following
order calls:
- qemu_system_reset which calls smmu_reset_hold initializing the SMMU
registers.
- qemu_loadvm_state which loads the saved state.
So From what I see, pre_load won’t be needed in this case also.
Thanks,
Mostafa
next prev parent reply other threads:[~2023-02-12 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 22:19 [PATCH v4] hw/arm/smmuv3: Add GBPA register Mostafa Saleh
2023-02-11 23:34 ` Richard Henderson
2023-02-13 16:49 ` Eric Auger
2023-02-11 23:48 ` Richard Henderson
2023-02-12 13:23 ` Mostafa Saleh
2023-02-12 15:18 ` Richard Henderson
2023-02-12 22:20 ` Mostafa Saleh [this message]
2023-02-13 10:57 ` Peter Maydell
2023-02-13 19:45 ` Richard Henderson
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=Y+lmSTN/mTow+JGe@google.com \
--to=smostafa@google.com \
--cc=eric.auger@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).