From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>, Ben Gardon <bgardon@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Sean Christopherson <sean.j.christopherson@intel.com>,
Peter Shier <pshier@google.com>, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCH 3/3] sched: Add cond_resched_rwlock
Date: Tue, 27 Oct 2020 19:50:14 +0100 [thread overview]
Message-ID: <31db67e0-bd9f-ff6d-2cee-b60ad52f71b2@redhat.com> (raw)
In-Reply-To: <20201027184440.GN2628@hirez.programming.kicks-ass.net>
On 27/10/20 19:44, Peter Zijlstra wrote:
> On Tue, Oct 27, 2020 at 09:49:50AM -0700, Ben Gardon wrote:
>
>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> index d2003a7d5ab55..ac58e7829a063 100644
>> --- a/kernel/sched/core.c
>> +++ b/kernel/sched/core.c
>> @@ -6152,6 +6152,46 @@ int __cond_resched_lock(spinlock_t *lock)
>> }
>> EXPORT_SYMBOL(__cond_resched_lock);
>>
>> +int __cond_resched_rwlock_read(rwlock_t *lock)
>> +{
>> + int resched = should_resched(PREEMPT_LOCK_OFFSET);
>> + int ret = 0;
>> +
>> + lockdep_assert_held(lock);
>
> lockdep_assert_held_read(lock);
>
>> +
>> + if (rwlock_needbreak(lock) || resched) {
>> + read_unlock(lock);
>> + if (resched)
>> + preempt_schedule_common();
>> + else
>> + cpu_relax();
>> + ret = 1;
>> + read_lock(lock);
>> + }
>> + return ret;
>> +}
>> +EXPORT_SYMBOL(__cond_resched_rwlock_read);
>> +
>> +int __cond_resched_rwlock_write(rwlock_t *lock)
>> +{
>> + int resched = should_resched(PREEMPT_LOCK_OFFSET);
>> + int ret = 0;
>> +
>> + lockdep_assert_held(lock);
>
> lockdep_assert_held_write(lock);
>
>> +
>> + if (rwlock_needbreak(lock) || resched) {
>> + write_unlock(lock);
>> + if (resched)
>> + preempt_schedule_common();
>> + else
>> + cpu_relax();
>> + ret = 1;
>> + write_lock(lock);
>> + }
>> + return ret;
>> +}
>> +EXPORT_SYMBOL(__cond_resched_rwlock_write);
>
> If this is the only feedback (the patches look fine to me), don't bother
> resending, I'll edit them when applying.
>
If that is an Acked-by, I'll merge them through the KVM tree when time
comes.
Paolo
next prev parent reply other threads:[~2020-10-27 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 16:49 [PATCH 1/3] locking/rwlocks: Add contention detection for rwlocks Ben Gardon
2020-10-27 16:49 ` [PATCH 2/3] sched: Add needbreak " Ben Gardon
2020-10-27 16:49 ` [PATCH 3/3] sched: Add cond_resched_rwlock Ben Gardon
2020-10-27 17:56 ` Sean Christopherson
2020-10-27 19:17 ` Peter Zijlstra
2020-10-27 20:17 ` Davidlohr Bueso
2020-10-27 18:44 ` Peter Zijlstra
2020-10-27 18:50 ` Paolo Bonzini [this message]
2020-10-30 17:09 ` Waiman Long
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=31db67e0-bd9f-ff6d-2cee-b60ad52f71b2@redhat.com \
--to=pbonzini@redhat.com \
--cc=bgardon@google.com \
--cc=dave@stgolabs.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pshier@google.com \
--cc=sean.j.christopherson@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