From: Marc Zyngier <maz@kernel.org>
To: Ricardo Koller <ricarkol@google.com>
Cc: kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] KVM: arm64: Don't serialize if the access flag isn't set
Date: Wed, 30 Nov 2022 08:21:17 +0000 [thread overview]
Message-ID: <87pmd4ua2q.wl-maz@kernel.org> (raw)
In-Reply-To: <Y4awiKLuKORZmU2z@google.com>
On Wed, 30 Nov 2022 01:23:20 +0000,
Ricardo Koller <ricarkol@google.com> wrote:
>
> On Tue, Nov 29, 2022 at 09:15:21PM +0000, Oliver Upton wrote:
> > Hi Ricardo,
> >
> > Thanks for having a look.
> >
> > On Tue, Nov 29, 2022 at 12:52:12PM -0800, Ricardo Koller wrote:
> > > On Tue, Nov 29, 2022 at 07:19:44PM +0000, Oliver Upton wrote:
> >
> > [...]
> >
> > > > + ret = stage2_update_leaf_attrs(pgt, addr, 1, KVM_PTE_LEAF_ATTR_LO_S2_AF, 0,
> > > > + &pte, NULL, 0);
> > > > + if (!ret)
> > > > + dsb(ishst);
> > >
> > > At the moment, the only reason for stage2_update_leaf_attrs() to not
> > > update the PTE is if it's not valid:
> > >
> > > if (!kvm_pte_valid(pte))
> > > return 0;
> > >
> > > I guess you could check that as well:
> > >
> > > + if (!ret || kvm_pte_valid(pte))
> > > + dsb(ishst);
> >
> > Thanks for catching this.
> >
> > Instead of pivoting on the returned PTE value, how about we return
> > -EAGAIN from the early return in stage2_attr_walker()? It would better
> > match the pattern used elsewhere in the pgtable code.
>
> That works, although I would use another return code (e.g., EINVAL)? as
> that's not exactly a "try again" type of error.
EINVAL usually is an indication of something that went horribly wrong.
But is that really a failure mode? Here, failing to update the PTE
should not be considered a failure, but just a benign race: access
fault being taken on a CPU and the page being evicted on another (not
unlikely, as the page was marked old before).
And if I'm correct above, this is definitely a "try again" situation:
you probably won't take the same type of fault the second time though.
Thanks,
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: Ricardo Koller <ricarkol@google.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] KVM: arm64: Don't serialize if the access flag isn't set
Date: Wed, 30 Nov 2022 08:21:17 +0000 [thread overview]
Message-ID: <87pmd4ua2q.wl-maz@kernel.org> (raw)
Message-ID: <20221130082117.5r0oxppEhEDeBkIcqzqbVKDWOel0qUQwwZniUPgg0p8@z> (raw)
In-Reply-To: <Y4awiKLuKORZmU2z@google.com>
On Wed, 30 Nov 2022 01:23:20 +0000,
Ricardo Koller <ricarkol@google.com> wrote:
>
> On Tue, Nov 29, 2022 at 09:15:21PM +0000, Oliver Upton wrote:
> > Hi Ricardo,
> >
> > Thanks for having a look.
> >
> > On Tue, Nov 29, 2022 at 12:52:12PM -0800, Ricardo Koller wrote:
> > > On Tue, Nov 29, 2022 at 07:19:44PM +0000, Oliver Upton wrote:
> >
> > [...]
> >
> > > > + ret = stage2_update_leaf_attrs(pgt, addr, 1, KVM_PTE_LEAF_ATTR_LO_S2_AF, 0,
> > > > + &pte, NULL, 0);
> > > > + if (!ret)
> > > > + dsb(ishst);
> > >
> > > At the moment, the only reason for stage2_update_leaf_attrs() to not
> > > update the PTE is if it's not valid:
> > >
> > > if (!kvm_pte_valid(pte))
> > > return 0;
> > >
> > > I guess you could check that as well:
> > >
> > > + if (!ret || kvm_pte_valid(pte))
> > > + dsb(ishst);
> >
> > Thanks for catching this.
> >
> > Instead of pivoting on the returned PTE value, how about we return
> > -EAGAIN from the early return in stage2_attr_walker()? It would better
> > match the pattern used elsewhere in the pgtable code.
>
> That works, although I would use another return code (e.g., EINVAL)? as
> that's not exactly a "try again" type of error.
EINVAL usually is an indication of something that went horribly wrong.
But is that really a failure mode? Here, failing to update the PTE
should not be considered a failure, but just a benign race: access
fault being taken on a CPU and the page being evicted on another (not
unlikely, as the page was marked old before).
And if I'm correct above, this is definitely a "try again" situation:
you probably won't take the same type of fault the second time though.
Thanks,
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: Ricardo Koller <ricarkol@google.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] KVM: arm64: Don't serialize if the access flag isn't set
Date: Wed, 30 Nov 2022 08:21:17 +0000 [thread overview]
Message-ID: <87pmd4ua2q.wl-maz@kernel.org> (raw)
In-Reply-To: <Y4awiKLuKORZmU2z@google.com>
On Wed, 30 Nov 2022 01:23:20 +0000,
Ricardo Koller <ricarkol@google.com> wrote:
>
> On Tue, Nov 29, 2022 at 09:15:21PM +0000, Oliver Upton wrote:
> > Hi Ricardo,
> >
> > Thanks for having a look.
> >
> > On Tue, Nov 29, 2022 at 12:52:12PM -0800, Ricardo Koller wrote:
> > > On Tue, Nov 29, 2022 at 07:19:44PM +0000, Oliver Upton wrote:
> >
> > [...]
> >
> > > > + ret = stage2_update_leaf_attrs(pgt, addr, 1, KVM_PTE_LEAF_ATTR_LO_S2_AF, 0,
> > > > + &pte, NULL, 0);
> > > > + if (!ret)
> > > > + dsb(ishst);
> > >
> > > At the moment, the only reason for stage2_update_leaf_attrs() to not
> > > update the PTE is if it's not valid:
> > >
> > > if (!kvm_pte_valid(pte))
> > > return 0;
> > >
> > > I guess you could check that as well:
> > >
> > > + if (!ret || kvm_pte_valid(pte))
> > > + dsb(ishst);
> >
> > Thanks for catching this.
> >
> > Instead of pivoting on the returned PTE value, how about we return
> > -EAGAIN from the early return in stage2_attr_walker()? It would better
> > match the pattern used elsewhere in the pgtable code.
>
> That works, although I would use another return code (e.g., EINVAL)? as
> that's not exactly a "try again" type of error.
EINVAL usually is an indication of something that went horribly wrong.
But is that really a failure mode? Here, failing to update the PTE
should not be considered a failure, but just a benign race: access
fault being taken on a CPU and the page being evicted on another (not
unlikely, as the page was marked old before).
And if I'm correct above, this is definitely a "try again" situation:
you probably won't take the same type of fault the second time though.
Thanks,
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-30 8:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 19:19 [PATCH 0/4] KVM: arm64: Parallel access faults Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 19:19 ` [PATCH 1/4] KVM: arm64: Use KVM's pte type/helpers in handle_access_fault() Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 19:19 ` [PATCH 2/4] KVM: arm64: Don't serialize if the access flag isn't set Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 20:52 ` Ricardo Koller
2022-11-29 20:52 ` Ricardo Koller
2022-11-29 20:52 ` Ricardo Koller
2022-11-29 21:15 ` Oliver Upton
2022-11-29 21:15 ` Oliver Upton
2022-11-29 21:15 ` Oliver Upton
2022-11-30 1:23 ` Ricardo Koller
2022-11-30 1:23 ` Ricardo Koller
2022-11-30 1:23 ` Ricardo Koller
2022-11-30 8:21 ` Marc Zyngier [this message]
2022-11-30 8:21 ` Marc Zyngier
2022-11-30 8:21 ` Marc Zyngier
2022-11-30 23:21 ` Ricardo Koller
2022-11-30 23:21 ` Ricardo Koller
2022-11-30 23:21 ` Ricardo Koller
2022-12-01 18:11 ` Oliver Upton
2022-12-01 18:11 ` Oliver Upton
2022-12-01 18:11 ` Oliver Upton
2022-11-29 19:19 ` [PATCH 3/4] KVM: arm64: Handle access faults behind the read lock Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 21:00 ` Ricardo Koller
2022-11-29 21:00 ` Ricardo Koller
2022-11-29 21:00 ` Ricardo Koller
2022-11-29 19:19 ` [PATCH 4/4] KVM: arm64: Condition HW AF updates on config option Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-29 19:19 ` Oliver Upton
2022-11-30 16:54 ` [PATCH 0/4] KVM: arm64: Parallel access faults Marc Zyngier
2022-11-30 16:54 ` Marc Zyngier
2022-11-30 16:54 ` 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=87pmd4ua2q.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvm@vger.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=ricarkol@google.com \
--cc=will@kernel.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 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.