From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Roland Dreier <roland@kernel.org>,
qemu-devel@nongnu.org,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Yishai Hadas <yishaih@mellanox.com>,
LKML <linux-kernel@vger.kernel.org>,
"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Sean Hefty <sean.hefty@intel.com>,
Christoph Lameter <cl@linux.com>
Subject: Re: [Qemu-devel] [PATCH] rdma: don't make pages writeable if not requiested
Date: Thu, 21 Mar 2013 11:21:50 -0600 [thread overview]
Message-ID: <20130321172150.GA3118@obsidianresearch.com> (raw)
In-Reply-To: <20130321171525.GE2994@redhat.com>
On Thu, Mar 21, 2013 at 07:15:25PM +0200, Michael S. Tsirkin wrote:
> No because application does this:
> init page
>
> ...
>
> after a lot of time
>
> ..
>
> register
> send
> unregister
>
> so it can not be read only.
mprotect(READONLY)
register
send
unregister
mprotect(WRITABLE)
?
With something like GIFT the app already has to give up writing to the
pages while they are moving, so changing the protection seems in line
with that?
Jason
next prev parent reply other threads:[~2013-03-21 17:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 6:18 [Qemu-devel] [PATCH] rdma: don't make pages writeable if not requiested Michael S. Tsirkin
2013-03-21 6:55 ` Roland Dreier
2013-03-21 7:03 ` Michael S. Tsirkin
2013-03-21 7:15 ` Roland Dreier
2013-03-21 8:51 ` Michael S. Tsirkin
2013-03-21 9:13 ` Roland Dreier
2013-03-21 9:39 ` Michael S. Tsirkin
2013-03-21 17:11 ` Jason Gunthorpe
2013-03-21 17:15 ` Michael S. Tsirkin
2013-03-21 17:21 ` Jason Gunthorpe [this message]
2013-03-21 17:42 ` Michael S. Tsirkin
2013-03-21 17:57 ` Jason Gunthorpe
2013-03-21 18:03 ` Michael S. Tsirkin
2013-03-21 18:16 ` Michael S. Tsirkin
2013-03-21 18:41 ` Jason Gunthorpe
2013-03-21 19:15 ` Michael S. Tsirkin
2013-03-21 20:09 ` Jason Gunthorpe
2013-03-21 9:32 ` Michael S. Tsirkin
2013-03-21 11:30 ` Michael S. Tsirkin
2013-03-21 12:23 ` Michael R. Hines
2013-03-21 12:32 ` Michael S. Tsirkin
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=20130321172150.GA3118@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=cl@linux.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mrhines@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=yishaih@mellanox.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).