From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
Alexey Perevalov <a.perevalov@samsung.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] migration: do not use atomic__nocheck() functions directly
Date: Fri, 19 Jan 2018 16:46:38 -0800 [thread overview]
Message-ID: <3fcd8dff-eb50-4a43-e3fc-101c17ecb849@linaro.org> (raw)
In-Reply-To: <39b15cc5-f797-8902-4b42-bf25845e7e74@amsat.org>
On 01/19/2018 10:20 AM, Philippe Mathieu-Daudé wrote:
> Maybe we should remove the __nocheck() functions and inline them in the
> 'checked' functions?
No, I use them in TCG, properly protected with CONFIG_ATOMIC*.
r~
prev parent reply other threads:[~2018-01-20 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 14:39 [Qemu-devel] [RFC PATCH] migration: do not use atomic__nocheck() functions directly Philippe Mathieu-Daudé
2018-01-19 16:14 ` Philippe Mathieu-Daudé
2018-01-19 18:01 ` Dr. David Alan Gilbert
2018-01-19 18:20 ` Philippe Mathieu-Daudé
2018-01-20 0:46 ` Richard Henderson [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=3fcd8dff-eb50-4a43-e3fc-101c17ecb849@linaro.org \
--to=richard.henderson@linaro.org \
--cc=a.perevalov@samsung.com \
--cc=dgilbert@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).