<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/hyperv, branch release/12.3.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2021-10-12T16:01:26Z</updated>
<entry>
<title>pvclock: Add vDSO support</title>
<updated>2021-10-12T16:01:26Z</updated>
<author>
<name>Adam Fenn</name>
<email>adam@fenn.io</email>
</author>
<published>2021-08-07T20:10:04Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4b34c91973ddaf594bbb192f84e421598a1b39be'/>
<id>urn:sha1:4b34c91973ddaf594bbb192f84e421598a1b39be</id>
<content type='text'>
Add vDSO support for timekeeping devices that support the KVM/XEN
paravirtual clock API.

Also, expose, in the userspace-accessible '&lt;machine/pvclock.h&gt;',
definitions that will be needed by 'libc' to support
'VDSO_TH_ALGO_X86_PVCLK'.

Sponsored by:	Juniper Networks, Inc.
Sponsored by:	Klara, Inc.
Reviewed by:	kib
Differential Revision:	https://reviews.freebsd.org/D31418

(cherry picked from commit d4b2d3035a23d5dc468d41151487a8299bf45cdc)
</content>
</entry>
<entry>
<title>netvsc: Fix a typo in a comment</title>
<updated>2021-10-06T06:22:12Z</updated>
<author>
<name>Gordon Bergling</name>
<email>gbe@FreeBSD.org</email>
</author>
<published>2021-10-02T08:42:18Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=aa42680be7883ffb02e17abaccc225b8f6faf57f'/>
<id>urn:sha1:aa42680be7883ffb02e17abaccc225b8f6faf57f</id>
<content type='text'>
- s/prefered/preferred/

(cherry picked from commit 9ebd651b58502f0572a7832d088f53f7a2ad00a5)
</content>
</entry>
<entry>
<title>storvsc: fix auto-sense reporting</title>
<updated>2021-05-21T13:49:54Z</updated>
<author>
<name>Andriy Gapon</name>
<email>avg@FreeBSD.org</email>
</author>
<published>2021-05-07T07:17:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=9120716d91d4d98fc7fe4833bda13e100cdd3b31'/>
<id>urn:sha1:9120716d91d4d98fc7fe4833bda13e100cdd3b31</id>
<content type='text'>
I saw a situation where the driver set CAM_AUTOSNS_VALID on a failed ccb
even though SRB_STATUS_AUTOSENSE_VALID was not set in the status.
The actual sense data remained all zeros.
The problem seems to be that create_storvsc_request() always sets
hv_storvsc_request::sense_info_len, so checking for sense_info_len != 0
is not enough to determine if any auto-sense data is actually available.

Sponsored by:	CyberSecure

(cherry picked from commit 8afecefd57c5ac95200f43227cd00f265154acee)
</content>
</entry>
<entry>
<title>Hyper-V: hn: Initialize the internal field of per packet info on tx path</title>
<updated>2021-03-29T09:12:56Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2021-03-15T10:20:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=2a321939b02bbf6123ba029f1967778c10538fe6'/>
<id>urn:sha1:2a321939b02bbf6123ba029f1967778c10538fe6</id>
<content type='text'>
The RSC support feature introduced a bit field "rm_internal" in
struct rndis_pktinfo with total size unchanged.

The guest does not use this field in the tx path. However we need to
initialize it to zero in case older hosts which are not aware of this
field.

Fixes:		a491581f ("Hyper-V: hn: Enable vSwitch RSC support")
MFC after:	2 weeks
Sponsored by:	Microsoft

(cherry picked from commit 805dbff6c36a6cd84491aa53a02315fa025734cc)
</content>
</entry>
<entry>
<title>Hyper-V: hn: Enable vSwitch RSC support in hn netvsc driver</title>
<updated>2021-03-29T08:55:18Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2021-03-12T04:35:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4150446f6467f585595803db211f58152cd3587a'/>
<id>urn:sha1:4150446f6467f585595803db211f58152cd3587a</id>
<content type='text'>
Receive Segment Coalescing (RSC) in the vSwitch is a feature available in
Windows Server 2019 hosts and later. It reduces the per packet processing
overhead by coalescing multiple TCP segments when possible. This happens
mostly when TCP traffics are among different guests on same host.
This patch adds netvsc driver support for this feature.

The patch also updates NVS version to 6.1 as needed for RSC
enablement.

MFC after:	2 weeks
Sponsored by:	Microsoft
Differential Revision:	https://reviews.freebsd.org/D29075

(cherry picked from commit a491581f3f8df07cdff0236bd556895205929af4)
</content>
</entry>
<entry>
<title>Hyper-V: hn: Store host hash value in flowid</title>
<updated>2021-03-29T08:32:39Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2021-02-24T05:07:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1aadba9cc8af4c1925eb27215eaf6d68e6fbf4d8'/>
<id>urn:sha1:1aadba9cc8af4c1925eb27215eaf6d68e6fbf4d8</id>
<content type='text'>
When rx packet contains hash value sent from host, store it in
the mbuf's flowid field so when the same mbuf is on the tx path,
the hash value can be used by the host to determine the outgoing
network queue.

MFC after:	2 weeks
Sponsored by:	Microsoft

(cherry picked from commit 80f39bd95f22322152709ea5fae3a3c546044c9c)
</content>
</entry>
<entry>
<title>Hyper-V: hn: Relinquish cpu in HN_LOCK to avoid deadlock</title>
<updated>2021-03-15T05:15:21Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2020-10-15T11:44:28Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=70f7b24753336efeb3cf6e73040780b2e4d28d8a'/>
<id>urn:sha1:70f7b24753336efeb3cf6e73040780b2e4d28d8a</id>
<content type='text'>
The try lock loop in HN_LOCK put the thread spinning on cpu if the lock
is not available. It is possible to cause deadlock if the thread holding
the lock is sleeping. Relinquish the cpu to work around this problem even
it doesn't completely solve the issue. The priority inversion could cause
the livelock no matter how less likely it could happen. A more complete
solution may be needed in the future.

Reported by:	Microsoft, Netapp
MFC after:	2 weeks
Sponsored by:	Microsoft

(cherry picked from commit b3460f44524b145c6c8a760ebe65052560a810bf)
</content>
</entry>
<entry>
<title>Hyper-V: pcib: Check revoke status during device attach</title>
<updated>2021-03-15T05:11:50Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2020-10-15T05:57:20Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=279041093326704636531051ad188e81b8beb32c'/>
<id>urn:sha1:279041093326704636531051ad188e81b8beb32c</id>
<content type='text'>
It is possible that the vmbus pcib channel is revoked during attach path.
The attach path could be waiting for response from host and this response will never
arrive since the channel has already been revoked from host point of view. Check
this situation during wait complete and return failed if this happens.

Reported by:	Netapp
MFC after:	2 weeks
Sponsored by:	Microsoft
Differential Revision:	https://reviews.freebsd.org/D26486

(cherry picked from commit 75c2786c25fef9a6f8239c9fc1631cd17756579b)
</content>
</entry>
<entry>
<title>Hyper-V: storvsc: Enhance srb_status code handling.</title>
<updated>2021-03-15T05:08:43Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2020-08-31T09:05:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=919a160fc6224a4bf281134b3b9584ffb7ebba3d'/>
<id>urn:sha1:919a160fc6224a4bf281134b3b9584ffb7ebba3d</id>
<content type='text'>
In hv_storvsc_io_request() when coring, prevent changing of the send channel
from the base channel to another one. storvsc_poll always probes on the base
channel.

Based upon conversations with Microsoft, changed the handling of srb_status
codes. Most we should never get, others yes. All are treated as retry-able
except for two. We should not get these statuses, but if we ever do, the I/O
state is not known.

Submitted by:	Alexander Sideropoulos &lt;Alexander.Sideropoulos@netapp.com&gt;
Reviewed by:	trasz, allanjude, whu
MFC after:	1 week
Sponsored by:	Netapp Inc
Differential Revision:	https://reviews.freebsd.org/D25756

(cherry picked from commit 2a0ce39d086ffe13782c9dc1e24bb240abbe790a)
</content>
</entry>
<entry>
<title>hyperv/vmbus: Fix the wrong size in ndis_offload structure</title>
<updated>2021-03-15T05:03:58Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2019-07-09T08:21:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b05c1dd0d1622fba5810513f3cefee4e34041c36'/>
<id>urn:sha1:b05c1dd0d1622fba5810513f3cefee4e34041c36</id>
<content type='text'>
Submitted by:	whu
MFC after:	2 weeks
Sponsored by:	Microsoft

(cherry picked from commit 23a499203c5b3fd74f781d1383269a6e168588cf)
</content>
</entry>
</feed>
