linux-kernel - [PATCH 0/3] Drivers: hv: Fix CPU assignment for FC devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1450225615-4672-1-git-send-email-kys@microsoft.com>
Date:	Tue, 15 Dec 2015 16:26:55 -0800
From:	"K. Y. Srinivasan" <kys@...rosoft.com>
To:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	vkuznets@...hat.com, jasowang@...hat.com
Cc:	"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: [PATCH 0/3] Drivers: hv: Fix CPU assignment for FC devices

Currently all channels of a Fibre channel device are being bound to CPU 0.
Correct this by including Fibre Channel devices in the list of
performance critical devices. Also included is a patch to correct the
returned error code for util drivers as well as cleanup of the
vmbus signaling function.

K. Y. Srinivasan (2):
  Drivers: hv: vmbus: Treat Fibre Channel devices as performance
    critical
  Drivers: hv: vmbus: Cleanup vmbus_set_event()

Vitaly Kuznetsov (1):
  Drivers: hv: utils: fix hvt_op_poll() return value on transport
    destroy

 drivers/hv/channel_mgmt.c       |    3 +++
 drivers/hv/connection.c         |    4 ++--
 drivers/hv/hv.c                 |   16 ----------------
 drivers/hv/hv_utils_transport.c |    2 +-
 drivers/hv/hyperv_vmbus.h       |    4 +---
 5 files changed, 7 insertions(+), 22 deletions(-)

-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/