From: Cornelia Huck <cohuck@redhat.com>
To: Eric Auger <eauger@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Gavin Shan" <gshan@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v5 2/3] arm/kvm: add support for MTE
Date: Mon, 27 Feb 2023 16:11:01 +0100 [thread overview]
Message-ID: <874jr75eka.fsf@redhat.com> (raw)
In-Reply-To: <f24a826e-2f90-d23a-c3f3-5985e90814f2@redhat.com>
On Wed, Feb 15 2023, Eric Auger <eauger@redhat.com> wrote:
> Hi Richard,
> On 2/6/23 19:27, Richard Henderson wrote:
>> On 2/6/23 03:32, Eric Auger wrote:
>>>> +void kvm_arm_enable_mte(Error **errp)
>>>> +{
>>>> + static bool tried_to_enable = false;
>>>> + Error *mte_migration_blocker = NULL;
>>> can't you make the mte_migration_blocker static instead?
>>>
>>>> + int ret;
>>>> +
>>>> + if (tried_to_enable) {
>>>> + /*
>>>> + * MTE on KVM is enabled on a per-VM basis (and retrying
>>>> doesn't make
>>>> + * sense), and we only want a single migration blocker as well.
>>>> + */
>>>> + return;
>>>> + }
>>>> + tried_to_enable = true;
>>>> +
>>>> + if ((ret = kvm_vm_enable_cap(kvm_state, KVM_CAP_ARM_MTE, 0))) {
>>>> + error_setg_errno(errp, -ret, "Failed to enable
>>>> KVM_CAP_ARM_MTE");
>>>> + return;
>>>> + }
>>>> +
>>>> + /* TODO: add proper migration support with MTE enabled */
>>>> + error_setg(&mte_migration_blocker,
>>>> + "Live migration disabled due to MTE enabled");
>>
>> Making the blocker static wouldn't stop multiple errors from
>> kvm_vm_enable_cap.
> Sorry I don't get what you mean. instead of checking tried_to_enable why
> can't we check !mte_migration_blocker?
[missed this one]
Do you mean
if (mte_migration_blocker) {
return;
}
error_setg(&mte_migration_blocker, ...);
if ((ret = kvm_vm_enable_cap(...))) {
return;
}
if (migrate_add_blocker(...)) {
error_free(mte_migration_blocker);
// is mte_migration_blocker guaranteed != NULL here?
}
next prev parent reply other threads:[~2023-02-27 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 13:44 [PATCH v5 0/3] arm: enable MTE for QEMU + kvm Cornelia Huck
2023-02-03 13:44 ` [PATCH v5 1/3] arm/virt: don't try to spell out the accelerator Cornelia Huck
2023-02-03 19:32 ` Richard Henderson
2023-02-06 12:46 ` Eric Auger
2023-02-03 13:44 ` [PATCH v5 2/3] arm/kvm: add support for MTE Cornelia Huck
2023-02-03 20:40 ` Richard Henderson
2023-02-06 13:10 ` Eric Auger
2023-02-06 16:15 ` Cornelia Huck
2023-02-27 15:12 ` Cornelia Huck
2023-02-06 16:41 ` Cornelia Huck
2023-02-06 13:32 ` Eric Auger
2023-02-06 18:27 ` Richard Henderson
2023-02-15 10:36 ` Eric Auger
2023-02-27 15:11 ` Cornelia Huck [this message]
2023-02-03 13:44 ` [PATCH v5 3/3] qtests/arm: add some mte tests Cornelia Huck
2023-02-06 18:23 ` Eric Auger
2023-02-10 15:35 ` Cornelia Huck
2023-02-27 15:16 ` Cornelia Huck
2023-02-15 10:59 ` Cornelia Huck
2023-02-16 17:30 ` Eric Auger
2023-02-16 11:40 ` [PATCH v5 0/3] arm: enable MTE for QEMU + kvm Peter Maydell
2023-02-16 11:46 ` Cornelia Huck
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=874jr75eka.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eauger@redhat.com \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=thuth@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).