Re: [PATCH 3/3 -perfbook] debugging: Fix typo

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 21 Mar 2021 10:03:49 +0900, Akira Yokosawa wrote:
> On Sat, 20 Mar 2021 12:23:23 -0700, Paul E. McKenney wrote:
>> On Sun, Mar 21, 2021 at 12:50:43AM +0900, Akira Yokosawa wrote:
>>> On Sun, 21 Mar 2021 00:24:46 +0900, Akira Yokosawa wrote:
>>>> Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
>>>> ---
>>>>  debugging/debugging.tex | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/debugging/debugging.tex b/debugging/debugging.tex
>>>> index fd52d9e7..3f697f58 100644
>>>> --- a/debugging/debugging.tex
>>>> +++ b/debugging/debugging.tex
>>>> @@ -755,7 +755,7 @@ access to data.
>>>>  The Kernel Concurrency Sanitizer (KCSAN)~\cite{JonathanCorbet2019KCSAN}
>>>>  uses existing markings such as \co{READ_ONCE()} and \co{WRITE_ONCE()}
>>>>  to determine which concurrent accesses deserve warning messages.
>>>> -KCSAN has a significant false-positive rate, especially in from the
>>>> +KCSAN has a significant false-positive rate, especially from the
>>>>  viewpoint of developers thinking in terms of C as assembly language
>>>>  with additional syntax.
>>>>  KCSAN therefore provides a \co{data_race()} construct to forgive
>>>>
>>>
>>> Paul,
>>>
>>> I caught this one while searching the usage of "data race" in perfbook.
>>> I thought "data race" also deserves an entry in Glossaries, especially
>>> because our use of "data race" is heavily related to compiler
>>> optimizations and somewhat stricter than the common definition
>>> found on the web.
>>>
>>> The first of data race in Section 4.2.2 (just before QQ4.8) does
>>> not (explicitly) talk about optimizations.
>>>
>>> Would it be possible for you to come up with some concise definition
>>> of data race which will fit as an entry in the Glossaries?
>>
>> How about like the following?
> 
> Looks good to me!

It looked good, but I've found that there is no mention of "marked access"
in the whole text (except for Glossaries) in perfbook at the moment.

"Marked access", "unmarked load", and so on are used in
ordering.txt to be added to LKMM documentation.
They are going to appear in perfbook, I suppose.

How about adding "Plain Access" to the Glossaries as well
and amend the definition of "Data Race" using "plain access".

        Thanks, Akira

> 
> Note on the index entry:
> 
> My experiment on the way to annotate index entries can manage automatic
> capitalization of only the first letter in indexed words/terms.
> So you won't need to take care of them.
> 
> And I'll get rid of direct uses of \index{} macro.
> 
> Will start rebasing those experiment soon after the release of
> second edition.
> 
>         Thanks, Akira
> 
>>
>> 							Thanx, Paul
>>
>> ------------------------------------------------------------------------
[...]



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux