From: Kirti Wankhede <kwankhede@nvidia.com>
To: Peter Xu <peterx@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: <kvm@vger.kernel.org>, <eric.auger@redhat.com>,
<linux-kernel@vger.kernel.org>, <slp@redhat.com>
Subject: Re: [PATCH v5 0/3] vfio/type1: Synchronous locked page accounting
Date: Wed, 19 Apr 2017 00:20:48 +0530 [thread overview]
Message-ID: <4eb2197f-e8f5-a030-64c3-8cc86c6f6318@nvidia.com> (raw)
In-Reply-To: <20170418042327.GB22226@pxdev.xzpeter.org>
On 4/18/2017 9:53 AM, Peter Xu wrote:
> On Mon, Apr 17, 2017 at 04:37:38PM -0600, Alex Williamson wrote:
>> v5:
>> - patch 1/ Use bool* to cleanup vfio_lock_acct() callers; sorry
>> we cannot re-test CAP_IPC_LOCK for all callers
>> - patch 2/ Re-add pr_warn, add Kirti's R-b
>> - patch 3/ NEW, analyzing impact of vfio_lock_acct() testing
>> CAP_IPC_LOCK for all callers revealed a long hanging
>> optimization
>>
>> Thanks for the reviews, keep 'em coming,
>
> All patches looks good to me.
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
>
> Thanks!
>
All three looks good to me too.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Thanks,
Kirti
prev parent reply other threads:[~2017-04-18 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 22:37 [PATCH v5 0/3] vfio/type1: Synchronous locked page accounting Alex Williamson
2017-04-17 22:37 ` [PATCH v5 1/3] vfio/type1: Remove locked page accounting workqueue Alex Williamson
2017-04-17 22:38 ` [PATCH v5 2/3] vfio/type1: Prune vfio_pin_page_external() Alex Williamson
2017-04-17 22:38 ` [PATCH v5 3/3] vfio/type1: Reduce repetitive calls in vfio_pin_pages_remote() Alex Williamson
2017-04-18 4:23 ` [PATCH v5 0/3] vfio/type1: Synchronous locked page accounting Peter Xu
2017-04-18 18:50 ` Kirti Wankhede [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=4eb2197f-e8f5-a030-64c3-8cc86c6f6318@nvidia.com \
--to=kwankhede@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=slp@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