From: Thomas Gleixner <tglx@linutronix.de>
To: "Zhang, Qiang1" <qiang1.zhang@intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"will@kernel.org" <will@kernel.org>,
"longman@redhat.com" <longman@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zhang, Qiang1" <qiang1.zhang@intel.com>
Subject: RE: [PATCH v2] locking/rtmutex: Fix incorrect spinning condition
Date: Sat, 18 Dec 2021 10:34:56 +0100 [thread overview]
Message-ID: <87zgoy9ry7.ffs@tglx> (raw)
In-Reply-To: <PH0PR11MB5880A552E7A3856D8F9165FBDA799@PH0PR11MB5880.namprd11.prod.outlook.com>
On Sat, Dec 18 2021 at 07:24, Qiang1 Zhang wrote:
> -----Original Message-----
> From: Thomas Gleixner <tglx@linutronix.de>
> Sent: 2021年12月18日 4:53
> To: Zhang, Qiang1 <qiang1.zhang@intel.com>; peterz@infradead.org; mingo@redhat.com; will@kernel.org; longman@redhat.com
> Cc: linux-kernel@vger.kernel.org; Zhang, Qiang1 <qiang1.zhang@intel.com>
> Subject: Re: [PATCH v2] locking/rtmutex: Fix incorrect spinning
> condition
Can you please fix your mail client to do proper replies without copying
the mail headers into the message?
>>Though this does not apply because the condition is incomplete. You
>>somehow dropped this from the condition:
>>
>> vcpu_is_preempted(task_cpu(owner)))
>>
>>Please make always sure that your patches apply against Linus tree
>>before sending them out.
>
> This commit c0bed69daf4b ("locking: Make owner_on_cpu() into <linux/sched.h>")
> make the following modifications in latest linux-next.
>
> +static inline bool owner_on_cpu(struct task_struct *owner)
> +{
> + /*
> + * As lock holder preemption issue, we both skip spinning if
> + * task is not on cpu or its cpu is preempted
> + */
> + return owner->on_cpu && !vcpu_is_preempted(task_cpu(owner));
> +}
> +
Fine, but then please tell against which tree/branch the patch is.
Thanks,
tglx
next prev parent reply other threads:[~2021-12-18 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 7:42 [PATCH v2] locking/rtmutex: Fix incorrect spinning condition Zqiang
2021-12-17 20:53 ` Thomas Gleixner
2021-12-18 7:24 ` Zhang, Qiang1
2021-12-18 9:34 ` Thomas Gleixner [this message]
2021-12-20 1:45 ` Zhang, Qiang1
2021-12-18 10:01 ` [tip: locking/core] locking/rtmutex: Fix incorrect condition in rtmutex_spin_on_owner() tip-bot2 for Zqiang
2021-12-19 21:09 ` [PATCH v2] locking/rtmutex: Fix incorrect spinning condition Waiman Long
2021-12-20 1:54 ` Zhang, Qiang1
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=87zgoy9ry7.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qiang1.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox