From: Mostafa Saleh <smostafa@google.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, jean-philippe@linaro.org,
eric.auger@redhat.com, qemu-arm@nongnu.org
Subject: Re: [PATCH v3] hw/arm/smmuv3: Add GBPA register
Date: Fri, 10 Feb 2023 18:08:39 +0000 [thread overview]
Message-ID: <Y+aIJy56YYEKkpgW@google.com> (raw)
In-Reply-To: <CAFEAcA_WW1_d3y6qE3G99cZKyPPwycKAbkGDM=5_6B9t1uDQ6Q@mail.gmail.com>
On Fri, Feb 10, 2023 at 04:11:37PM +0000, Peter Maydell wrote:
>
> I think we should check the whole register against its reset value,
> not just the ABORT bit. Otherwise if the guest writes the other fields
> to non default values we won't migrate them. That doesn't change the
> device behaviour now but it will have the weird effect that the guest
> could write the register and then after a migration find it reading
> back as a different value. Plus if in future we implement actual
> functionality for any of the other fields then we'll want to know
> what their true values written by the guest are.
>
> Linux never changes any fields except ABORT so for the most interesting
> guest it won't make a difference right now.
I agree, I was trying to achieve maximum backward compatibility as we
don’t care about other fields, but this can be weird for forward
migration, if the register is not fully migrated.
And if SW touches this register it would probably want to configure the
ABORT at some point, so it won’t help much for backward migration.
I will update this in v4.
Thanks,
Mostafa
prev parent reply other threads:[~2023-02-10 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 18:19 [PATCH v3] hw/arm/smmuv3: Add GBPA register Mostafa Saleh
2023-02-10 16:11 ` Peter Maydell
2023-02-10 18:08 ` Mostafa Saleh [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=Y+aIJy56YYEKkpgW@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 \
/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).