linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: alex.williamson@redhat.com, kvm@vger.kernel.org
Cc: eric.auger@redhat.com, kwankhede@nvidia.com, peterx@redhat.com,
	linux-kernel@vger.kernel.org, slp@redhat.com
Subject: [PATCH v5 0/3] vfio/type1: Synchronous locked page accounting
Date: Mon, 17 Apr 2017 16:37:38 -0600	[thread overview]
Message-ID: <20170417223158.25720.59453.stgit@gimli.home> (raw)

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,
Alex

---

Alex Williamson (3):
      vfio/type1: Remove locked page accounting workqueue
      vfio/type1: Prune vfio_pin_page_external()
      vfio/type1: Reduce repetitive calls in vfio_pin_pages_remote()


 drivers/vfio/vfio_iommu_type1.c |  150 +++++++++++++++++----------------------
 1 file changed, 64 insertions(+), 86 deletions(-)

             reply	other threads:[~2017-04-17 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 22:37 Alex Williamson [this message]
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

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=20170417223158.25720.59453.stgit@gimli.home \
    --to=alex.williamson@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --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;
as well as URLs for NNTP newsgroup(s).