From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@microsoft.com
Cc: linux-hyperv@vger.kernel.org
Cc: kys@microsoft.com
Cc: haiyangz@microsoft.com
Cc: sthemmin@microsoft.com
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Hyper-V commits for v5.1
Date: Fri, 01 Mar 2019 10:16:20 -0500 [thread overview]
Message-ID: <20190301151621.486D92084F@mail.kernel.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
The following changes since commit 8834f5600cf3c8db365e18a3d5cac2c2780c81e5:
Linux 5.0-rc5 (2019-02-03 13:48:04 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-next-signed
for you to fetch changes up to 396ae57ef1ef978d1d21cdb7586ba184a3f22453:
Drivers: hv: vmbus: Expose counters for interrupts and full conditions (2019-02-14 20:56:10 -0500)
- ----------------------------------------------------------------
1. Exopsing counters for state changes of channel ring buffers; this is
useful to investigate performance issues. By Kimberly Brown.
2. Switching to the new generic UUID API, by Andy Shevchenko.
- ----------------------------------------------------------------
Andy Shevchenko (1):
vmbus: Switch to use new generic UUID API
Kimberly Brown (1):
Drivers: hv: vmbus: Expose counters for interrupts and full conditions
Documentation/ABI/stable/sysfs-bus-vmbus | 33 +++++++
drivers/hv/channel.c | 4 +-
drivers/hv/channel_mgmt.c | 18 ++--
drivers/hv/hyperv_vmbus.h | 4 +-
drivers/hv/ring_buffer.c | 14 ++-
drivers/hv/vmbus_drv.c | 84 +++++++++++-------
include/linux/hyperv.h | 144 ++++++++++++++++++++-----------
7 files changed, 207 insertions(+), 94 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE4n5dijQDou9mhzu83qZv95d3LNwFAlx5TJwACgkQ3qZv95d3
LNxZfxAAjCHHRJ2HStiHhH5tOEABQsTNYwqXB8QNwL4cBC3L0DiwihynKVy/BQzg
nwQz3dZbar2h5Qj4Wkz+ygX57Sq2kRHBYNKGygcNzBYqF0IZvcmav3xUxMUrohjq
OAAt6mfzPo/rKIoT0vq4XbtZByR3g23VJpXoE/kAf9fPnLg4LXv8xu0MWpE58mvl
9pGmD0lO7K559FlYoWZNaOKbtjayOBDa9N2Mos/KM36x9kmeF2wp06RGBe2lyKuR
fzdTJhBoYkAqVeryTox9YpdvmlCvgwmudrCChrwnpx91WJb8HM5aT8tYAOfGssiR
MArxya2qFEzuzk5ToQS0HW9Id/+08MVhB7nACON3knrpH7i6RuPq9jrVqHZZeKH1
uyiItqNs3YjTrCPhrYqzRGS572kTR2hIgRvLylq7I9GXq/PPYomo34hTrGiUDK5d
t0rT6xCAzq+4DKzwEydy4l9TpEk8IXTeJ3aiIIJLr/NgZad+IGv4aP+R01xXlUld
gN5REI8mbQ7Pvov4EPGBuLuMeMTAyXPm4W5ZYlBTZxUaT1QTx2bypX41QSaX+J/7
PCTmutjP2eIYbzcJnxvfbTS6fFJTkzLyj7HrnRrf+YotH+/NwUSP7F/fzxp5ImuL
hlC4FuvWMjSjQ/OVenVL/eqMsfPbCcdqk+eKd8HfIKKToFd6seI=
=FLip
-----END PGP SIGNATURE-----
next reply other threads:[~2019-03-01 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 15:16 Sasha Levin [this message]
2019-03-01 15:46 ` [GIT PULL] Hyper-V commits for v5.1 Greg KH
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=20190301151621.486D92084F@mail.kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@microsoft.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).