From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] fix typo in quick quiz 4.17
Date: Sun, 27 Sep 2015 09:17:15 -0700 [thread overview]
Message-ID: <20150927161715.GG30373@linux.vnet.ibm.com> (raw)
In-Reply-To: <1443355322-11907-1-git-send-email-pbonzini@redhat.com>
On Sun, Sep 27, 2015 at 02:02:02PM +0200, Paolo Bonzini wrote:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Good catch, applied.
Thanx, Paul
> ---
> toolsoftrade/toolsoftrade.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
> index 4e85a9c..ccbe0ad 100644
> --- a/toolsoftrade/toolsoftrade.tex
> +++ b/toolsoftrade/toolsoftrade.tex
> @@ -964,7 +964,7 @@ rights to assume that the value of \co{goflag} would never change.
> \QuickQuizAnswer{
> It depends.
> If the per-thread variable was accessed only from its thread,
> - and never from a single handler, then no.
> + and never from a signal handler, then no.
> Otherwise, it is quite possible that \co{ACCESS_ONCE()} is needed.
> We will see examples of both situations in
> Section~\ref{sec:count:Signal-Theft Limit Counter Implementation}.
> --
> 2.5.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-09-27 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 12:02 [PATCH] fix typo in quick quiz 4.17 Paolo Bonzini
2015-09-27 16:17 ` Paul E. McKenney [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=20150927161715.GG30373@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=perfbook@vger.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 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.