From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Breno Leitao <leitao@debian.org>, linuxppc-dev@lists.ozlabs.org
Cc: Breno Leitao <leitao@debian.org>, gromero@linux.vnet.ibm.com
Subject: Re: [v2] selftests/powerpc: Do not fail with reschedule
Date: Thu, 20 Sep 2018 14:21:02 +1000 (AEST) [thread overview]
Message-ID: <42G3Sc2C0jz9sCD@ozlabs.org> (raw)
In-Reply-To: <1536784265-19806-1-git-send-email-leitao@debian.org>
On Wed, 2018-09-12 at 20:31:05 UTC, Breno Leitao wrote:
> There are cases where the test is not expecting to have the transaction
> aborted, but, the test process might have been rescheduled, either in the
> OS level or by KVM (if it is running on a KVM guest machine). The process
> reschedule will cause a treclaim/recheckpoint which will cause the
> transaction to doom, aborting the transaction as soon as the process is
> rescheduled back to the CPU. This might cause the test to fail, but this is
> not a failure in essence.
>
> If that is the case, TEXASR[FC] is indicated with either
> TM_CAUSE_RESCHEDULE or TM_CAUSE_KVM_RESCHEDULE for KVM interruptions.
>
> In this scenario, ignore these two failures and avoid the whole test to
> return failure.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> Reviewed-by: Gustavo Romero <gromero@linux.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/44d947eff19d64384efc06069509db
cheers
prev parent reply other threads:[~2018-09-20 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 18:56 [PATCH] selftests/powerpc: Do not fail on TM_CAUSE_RESCHED Breno Leitao
2018-08-28 23:08 ` Gustavo Romero
2018-09-12 20:31 ` [PATCH v2] selftests/powerpc: Do not fail with reschedule Breno Leitao
2018-09-20 4:21 ` Michael Ellerman [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=42G3Sc2C0jz9sCD@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=gromero@linux.vnet.ibm.com \
--cc=leitao@debian.org \
--cc=linuxppc-dev@lists.ozlabs.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.