From: Avi Kivity <avi@redhat.com>
To: Xudong Hao <xudong.hao@intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mtosatti@redhat.com, takuya.yoshikawa@gmail.com,
xiantao.zhang@intel.com, Haitao Shan <haitao.shan@intel.com>
Subject: Re: [PATCH v3 4/4] Enabling Access bit when doing memory swapping
Date: Tue, 29 May 2012 17:27:19 +0300 [thread overview]
Message-ID: <4FC4DCC7.7080401@redhat.com> (raw)
In-Reply-To: <1337656995-24964-1-git-send-email-xudong.hao@intel.com>
On 05/22/2012 06:23 AM, Xudong Hao wrote:
> <Re-send>
>
> Enabling Access bit when doing memory swapping.
>
> Changes from v2:
> -Still using claer_bit() function to make sure it's atomic operation.
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-29 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 3:23 [PATCH v3 4/4] Enabling Access bit when doing memory swapping Xudong Hao
2012-05-23 13:31 ` Hao, Xudong
2012-05-28 10:21 ` Hao, Xudong
2012-05-28 10:36 ` Avi Kivity
2012-05-28 11:34 ` Hao, Xudong
2012-05-29 14:27 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-22 3:02 Xudong Hao
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=4FC4DCC7.7080401@redhat.com \
--to=avi@redhat.com \
--cc=haitao.shan@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=takuya.yoshikawa@gmail.com \
--cc=xiantao.zhang@intel.com \
--cc=xudong.hao@intel.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).