From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] locking/qspinlock: Fix inaccessible URL of MCS lock paper
Date: Tue, 7 Jan 2020 09:14:20 -0500 [thread overview]
Message-ID: <64bac471-11c6-41b7-c647-fa2c70b1bc32@redhat.com> (raw)
In-Reply-To: <20200107130939.GV2871@hirez.programming.kicks-ass.net>
On 1/7/20 8:09 AM, Peter Zijlstra wrote:
> On Tue, Jan 07, 2020 at 01:58:24PM +0100, Peter Zijlstra wrote:
>> On Sun, Dec 22, 2019 at 09:25:32PM -0500, Waiman Long wrote:
>>> It turns out that the URL of the MCS lock paper listed in the source
>>> code is no longer accessible. I did got question about where the paper
>>> was. This patch updates the URL to one that is still accessible.
>>>
>>> Signed-off-by: Waiman Long <longman@redhat.com>
>>> ---
>>> kernel/locking/qspinlock.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
>>> index 2473f10c6956..1d008d2333c0 100644
>>> --- a/kernel/locking/qspinlock.c
>>> +++ b/kernel/locking/qspinlock.c
>>> @@ -34,7 +34,7 @@
>>> * MCS lock. The paper below provides a good description for this kind
>>> * of lock.
>>> *
>>> - * http://www.cise.ufl.edu/tr/DOC/REP-1992-71.pdf
>>> + * https://www.cs.rochester.edu/u/scott/papers/1991_TOCS_synch.pdf
>> Do we want to stick a copy of the paper in our bugzilla and link that
>> instead? ISTR we do something similar elsewhere, but I'm having trouble
>> finding it.
>>
>> Thomas, Konstantin?
> Boris provided an example from commit:
>
> 018ebca8bd70 ("x86/cpufeatures: Enable a new AVX512 CPU feature")
>
> That puts a copy of the relevant Intel document here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=204215
>
OK, that sounds good. I will put a copy of the paper in the BZ and
linked it there.
Thanks,
Longman
next prev parent reply other threads:[~2020-01-07 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 2:25 Waiman Long
2020-01-07 12:58 ` Peter Zijlstra
2020-01-07 13:09 ` Peter Zijlstra
2020-01-07 14:14 ` Waiman Long [this message]
2020-01-07 17:23 ` Will Deacon
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=64bac471-11c6-41b7-c647-fa2c70b1bc32@redhat.com \
--to=longman@redhat.com \
--cc=bp@alien8.de \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®