From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Parav Pandit <parav@mellanox.com>,
Cornelia Huck <cohuck@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>
Subject: [GIT PULL] VFIO fixes for v5.2-rc5
Date: Tue, 11 Jun 2019 11:49:55 -0600 [thread overview]
Message-ID: <20190611114955.2d0b6388@x1.home> (raw)
Hi Linus,
The following changes since commit f2c7c76c5d0a443053e94adb9f0918fa2fb85c3a:
Linux 5.2-rc3 (2019-06-02 13:55:33 -0700)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v5.2-rc5
for you to fetch changes up to 5715c4dd66a315515eedef3fc4cbe1bf4620f009:
vfio/mdev: Synchronize device create/remove with parent removal (2019-06-06 12:32:37 -0600)
----------------------------------------------------------------
VFIO fixes for v5.2-rc5
- Fix mdev device create/remove paths to provide initialized device for
parent driver create callback and correct ordering of device removal
from bus prior to initiating removal by parent. Also resolve races
between parent removal and device create/remove paths. (Parav Pandit)
----------------------------------------------------------------
Parav Pandit (3):
vfio/mdev: Improve the create/remove sequence
vfio/mdev: Avoid creating sysfs remove file on stale device removal
vfio/mdev: Synchronize device create/remove with parent removal
drivers/vfio/mdev/mdev_core.c | 136 ++++++++++++++++++---------------------
drivers/vfio/mdev/mdev_private.h | 4 +-
drivers/vfio/mdev/mdev_sysfs.c | 6 +-
3 files changed, 69 insertions(+), 77 deletions(-)
next reply other threads:[~2019-06-11 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 17:49 Alex Williamson [this message]
2019-06-12 1:55 ` [GIT PULL] VFIO fixes for v5.2-rc5 pr-tracker-bot
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=20190611114955.2d0b6388@x1.home \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.