From: Jike Song <jike.song@intel.com>
To: Eric Blake <eblake@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
kvm@vger.kernel.org, guangrong.xiao@intel.com,
qemu-devel <qemu-devel@nongnu.org>,
Xiaoguang Chen <xiaoguang.chen@intel.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Paolo Bonzini <pbonzini@redhat.com>, Neo Jia <cjia@nvidia.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] KVM: page track: add a new notifier type: track_flush_slot
Date: Mon, 24 Oct 2016 14:32:20 +0800 [thread overview]
Message-ID: <580DAAF4.5030109@intel.com> (raw)
In-Reply-To: <4fe2a0be-a632-8c74-241f-66e51b6d7fd5@redhat.com>
On 10/19/2016 09:56 PM, Eric Blake wrote:
> 17 levels of quoting is rather over-the-top. It is OKAY (and in fact
> DESIRABLE) to trim your emails to relevant portions, when posting to a
> high-volume list. Readers shouldn't have to scroll through pages of
> deeply-nested quoting...
Hi Eric,
Sorry for that, will trim the quotation next time. Thanks for
reminding!
--
Thanks,
Jike
next prev parent reply other threads:[~2016-10-24 6:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 7:41 [PATCH 0/2] page track add notifier type track_flush_slot Xiaoguang Chen
2016-10-09 7:41 ` [PATCH 1/2] KVM: page track: add a new notifier type: track_flush_slot Xiaoguang Chen
2016-10-09 8:31 ` Neo Jia
2016-10-09 8:56 ` Chen, Xiaoguang
2016-10-10 17:06 ` Paolo Bonzini
2016-10-10 18:01 ` Neo Jia
2016-10-10 18:32 ` Paolo Bonzini
2016-10-11 2:39 ` Xiao Guangrong
2016-10-11 8:54 ` Paolo Bonzini
2016-10-11 9:21 ` Xiao Guangrong
2016-10-11 9:47 ` Paolo Bonzini
2016-10-14 10:37 ` Jike Song
2016-10-14 10:43 ` Paolo Bonzini
2016-10-14 12:26 ` Jike Song
2016-10-14 14:41 ` [Qemu-devel] " Alex Williamson
2016-10-14 14:46 ` Alex Williamson
2016-10-14 16:35 ` [Qemu-devel] " Neo Jia
2016-10-14 16:51 ` Alex Williamson
2016-10-14 22:19 ` Neo Jia
2016-10-17 16:02 ` Alex Williamson
2016-10-18 12:38 ` Jike Song
2016-10-18 14:59 ` Alex Williamson
2016-10-19 2:32 ` Jike Song
2016-10-19 5:45 ` Xiao Guangrong
2016-10-19 11:56 ` Paolo Bonzini
2016-10-19 13:39 ` Xiao Guangrong
2016-10-19 14:14 ` Paolo Bonzini
2016-10-20 1:48 ` [Qemu-devel] " Xiao Guangrong
2016-10-20 17:06 ` Paolo Bonzini
2016-10-20 17:19 ` Xiao, Guangrong
2016-10-21 2:47 ` [Qemu-devel] " Jike Song
2016-10-26 13:44 ` Jike Song
2016-10-26 14:45 ` Paolo Bonzini
2016-10-29 4:07 ` Jike Song
2016-10-19 13:56 ` Eric Blake
2016-10-24 6:32 ` Jike Song [this message]
2016-10-12 20:48 ` Radim Krčmář
2016-10-09 7:41 ` [PATCH 2/2] KVM: MMU: apply page track notifier type track_flush_slot Xiaoguang Chen
2016-10-10 17:06 ` [PATCH 0/2] page track add " Paolo Bonzini
2016-10-11 2:43 ` Xiao Guangrong
2016-10-11 8:55 ` Paolo Bonzini
2016-10-12 20:52 ` Radim Krčmář
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=580DAAF4.5030109@intel.com \
--to=jike.song@intel.com \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=eblake@redhat.com \
--cc=guangrong.xiao@intel.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoguang.chen@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).