From: Marc Zyngier <maz@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] KVM: arm64: selftests: Fixes for single-step test
Date: Thu, 17 Nov 2022 13:52:25 +0000 [thread overview]
Message-ID: <8635ahpu1y.wl-maz@kernel.org> (raw)
In-Reply-To: <20221117002350.2178351-1-seanjc@google.com>
On Thu, 17 Nov 2022 00:23:48 +0000,
Sean Christopherson <seanjc@google.com> wrote:
>
> Marc,
>
> I would like to route this through Paolo's tree/queue for 6.2 along with
> a big pile of other selftests updates. I am hoping to get the selftests
> pile queued sooner than later as there is a lot of active development in
> that area, and don't want to have the selftests be in a broken state.
> I'm going to send Paolo a pull request shortly, I'll Cc you (and others)
> to keep everyone in the loop and give a chance for objections.
>
>
>
> Fix a typo and an imminenent not-technically-a-bug bug in the single-step
> test where executing an atomic sequence in the guest with single-step
> enable will hang the guest due to eret clearing the local exclusive
> monitor.
>
>
> Sean Christopherson (2):
> KVM: arm64: selftests: Disable single-step with correct KVM define
> KVM: arm64: selftests: Disable single-step without relying on ucall()
I'm obviously late to the party, but hey... For the record:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
Reiji Watanabe <reijiw@google.com>
Subject: Re: [PATCH 0/2] KVM: arm64: selftests: Fixes for single-step test
Date: Thu, 17 Nov 2022 13:52:25 +0000 [thread overview]
Message-ID: <8635ahpu1y.wl-maz@kernel.org> (raw)
Message-ID: <20221117135225.oqOML1e6e2n-gqVsRWlMcng911Q9NGlWDxMbNrPEds8@z> (raw)
In-Reply-To: <20221117002350.2178351-1-seanjc@google.com>
On Thu, 17 Nov 2022 00:23:48 +0000,
Sean Christopherson <seanjc@google.com> wrote:
>
> Marc,
>
> I would like to route this through Paolo's tree/queue for 6.2 along with
> a big pile of other selftests updates. I am hoping to get the selftests
> pile queued sooner than later as there is a lot of active development in
> that area, and don't want to have the selftests be in a broken state.
> I'm going to send Paolo a pull request shortly, I'll Cc you (and others)
> to keep everyone in the loop and give a chance for objections.
>
>
>
> Fix a typo and an imminenent not-technically-a-bug bug in the single-step
> test where executing an atomic sequence in the guest with single-step
> enable will hang the guest due to eret clearing the local exclusive
> monitor.
>
>
> Sean Christopherson (2):
> KVM: arm64: selftests: Disable single-step with correct KVM define
> KVM: arm64: selftests: Disable single-step without relying on ucall()
I'm obviously late to the party, but hey... For the record:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
Reiji Watanabe <reijiw@google.com>
Subject: Re: [PATCH 0/2] KVM: arm64: selftests: Fixes for single-step test
Date: Thu, 17 Nov 2022 13:52:25 +0000 [thread overview]
Message-ID: <8635ahpu1y.wl-maz@kernel.org> (raw)
In-Reply-To: <20221117002350.2178351-1-seanjc@google.com>
On Thu, 17 Nov 2022 00:23:48 +0000,
Sean Christopherson <seanjc@google.com> wrote:
>
> Marc,
>
> I would like to route this through Paolo's tree/queue for 6.2 along with
> a big pile of other selftests updates. I am hoping to get the selftests
> pile queued sooner than later as there is a lot of active development in
> that area, and don't want to have the selftests be in a broken state.
> I'm going to send Paolo a pull request shortly, I'll Cc you (and others)
> to keep everyone in the loop and give a chance for objections.
>
>
>
> Fix a typo and an imminenent not-technically-a-bug bug in the single-step
> test where executing an atomic sequence in the guest with single-step
> enable will hang the guest due to eret clearing the local exclusive
> monitor.
>
>
> Sean Christopherson (2):
> KVM: arm64: selftests: Disable single-step with correct KVM define
> KVM: arm64: selftests: Disable single-step without relying on ucall()
I'm obviously late to the party, but hey... For the record:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-17 13:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 0:23 [PATCH 0/2] KVM: arm64: selftests: Fixes for single-step test Sean Christopherson
2022-11-17 0:23 ` Sean Christopherson
2022-11-17 0:23 ` Sean Christopherson
2022-11-17 0:23 ` [PATCH 1/2] KVM: arm64: selftests: Disable single-step with correct KVM define Sean Christopherson
2022-11-17 0:23 ` Sean Christopherson
2022-11-17 0:23 ` Sean Christopherson
2022-11-17 0:43 ` Oliver Upton
2022-11-17 0:43 ` Oliver Upton
2022-11-17 0:43 ` Oliver Upton
2022-11-17 3:07 ` Reiji Watanabe
2022-11-17 3:07 ` Reiji Watanabe
2022-11-17 3:07 ` Reiji Watanabe
2022-11-17 0:23 ` [PATCH 2/2] KVM: arm64: selftests: Disable single-step without relying on ucall() Sean Christopherson
2022-11-17 0:23 ` Sean Christopherson
2022-11-17 0:23 ` Sean Christopherson
2022-11-17 0:53 ` Oliver Upton
2022-11-17 0:53 ` Oliver Upton
2022-11-17 0:53 ` Oliver Upton
2022-11-17 1:20 ` Sean Christopherson
2022-11-17 1:20 ` Sean Christopherson
2022-11-17 1:20 ` Sean Christopherson
2022-11-17 15:19 ` Sean Christopherson
2022-11-17 15:19 ` Sean Christopherson
2022-11-17 15:19 ` Sean Christopherson
2022-11-17 22:32 ` Sean Christopherson
2022-11-17 22:32 ` Sean Christopherson
2022-11-17 22:32 ` Sean Christopherson
2022-11-17 7:07 ` Reiji Watanabe
2022-11-17 7:07 ` Reiji Watanabe
2022-11-17 7:07 ` Reiji Watanabe
2022-11-17 13:52 ` Marc Zyngier [this message]
2022-11-17 13:52 ` [PATCH 0/2] KVM: arm64: selftests: Fixes for single-step test Marc Zyngier
2022-11-17 13:52 ` Marc Zyngier
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=8635ahpu1y.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.