- 13 Jul, 2016 26 commits
-
-
Andrey Smetanin authored
BugLink: http://bugs.launchpad.net/bugs/1583357 This rearrangement places functions declarations together according to their functionality, so future additions will be simplier. Signed-off-by:
Andrey Smetanin <asmetanin@virtuozzo.com> Reviewed-by:
Roman Kagan <rkagan@virtuozzo.com> CC: Gleb Natapov <gleb@kernel.org> CC: Paolo Bonzini <pbonzini@redhat.com> CC: "K. Y. Srinivasan" <kys@microsoft.com> CC: Haiyang Zhang <haiyangz@microsoft.com> CC: Vitaly Kuznetsov <vkuznets@redhat.com> CC: Roman Kagan <rkagan@virtuozzo.com> CC: Denis V. Lunev <den@openvz.org> CC: qemu-devel@nongnu.org Signed-off-by:
Paolo Bonzini <pbonzini@redhat.com> (cherry picked from commit e18eaeed) Signed-off-by:
Tim Gardner <tim.gardner@canonical.com> Acked-by:
Brad Figg <brad.figg@canonical.com> Signed-off-by:
Kamal Mostafa <kamal@canonical.com>
-
Andrey Smetanin authored
BugLink: http://bugs.launchpad.net/bugs/1583357 A new vcpu exit is introduced to notify the userspace of the changes in Hyper-V SynIC configuration triggered by guest writing to the corresponding MSRs. Changes v4: * exit into userspace only if guest writes into SynIC MSR's Changes v3: * added KVM_EXIT_HYPERV types and structs notes into docs Signed-off-by:
Denis V. Lunev <den@openvz.org> CC: Gleb Natapov <gleb@kernel.org> CC: Paolo Bonzini <pbonzini@redhat.com> CC: Roman Kagan <rkagan@virtuozzo.com> CC: Denis V. Lunev <den@openvz.org> CC: qemu-devel@nongnu.org Signed-off-by:
-
Andrey Smetanin authored
BugLink: http://bugs.launchpad.net/bugs/1583357 SynIC (synthetic interrupt controller) is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI semantics - a message page in the guest memory with 16 256-byte per-SINT message slots - an event flag page in the guest memory with 16 2048-bit per-SINT event flag areas The host triggers a SINT whenever it delivers a new message to the corresponding slot or flips an event flag bit in the corresponding area. The guest informs the host that it can try delivering a message by explicitly asserting EOI in lapic or writing to End-Of-Message (EOM) MSR. The userspace (qemu) triggers interrupts and receives EOM notifications via irqfd with resampler; for that, a GSI is allocated for each configured SINT, and irq_routing api is extended to support GSI-SINT mapping. Changes v4: * added activation of SynIC by vcpu KVM_ENABLE_CAP * added per SynIC active flag * added deactivation of APICv upon SynIC activation Changes v3: * added KVM_CAP_HYPERV_SYNIC and KVM_IRQ_ROUTING_HV_SINT notes into docs Changes v2: * do not use posted interrupts for Hyper-V SynIC AutoEOI vectors * add Hyper-V SynIC vectors into EOI exit bitmap * Hyper-V SyniIC SINT msr write logic simplified Signed-off-by:
-
Andrey Smetanin authored
BugLink: http://bugs.launchpad.net/bugs/1583357 The decision on whether to use hardware APIC virtualization used to be taken globally, based on the availability of the feature in the CPU and the value of a module parameter. However, under certain circumstances we want to control it on per-vcpu basis. In particular, when the userspace activates HyperV synthetic interrupt controller (SynIC), APICv has to be disabled as it's incompatible with SynIC auto-EOI behavior. To achieve that, introduce 'apicv_active' flag on struct kvm_vcpu_arch, and kvm_vcpu_deactivate_apicv() function to turn APICv off. The flag is initialized based on the module parameter and CPU capability, and consulted whenever an APICv-specific action is performed. Signed-off-by:
-
Andrey Smetanin authored
BugLink: http://bugs.launchpad.net/bugs/1583357 The function to determine if the vector is handled by ioapic used to rely on the fact that only ioapic-handled vectors were set up to cause vmexits when virtual apic was in use. We're going to break this assumption when introducing Hyper-V synthetic interrupts: they may need to cause vmexits too. To achieve that, introduce a new bitmap dedicated specifically for ioapic-handled vectors, and populate EOI exit bitmap from it for now. Signed-off-by:
-
Haiyang Zhang authored
BugLink: http://bugs.launchpad.net/bugs/1583357 In commit 2a04ae8a ("hv_netvsc: remove locking in netvsc_send()"), the locking for MSD (Multi-Send Data) field was removed. This could cause a race condition between RNDIS control messages and data packets processing, because these two types of traffic are not synchronized. This patch fixes this issue by sending control messages out directly without reading MSD field. Signed-off-by:
Haiyang Zhang <haiyangz@microsoft.com> Reviewed-by:
K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:
David S. Miller <davem@davemloft.net> (cherry picked from commit cf8190e4) Signed-off-by:
-
Long Li authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Introduce a logging level for storvsc to log certain error/warning messages. Those messages are helpful in some environments, e.g. Microsoft Azure, for customer support and troubleshooting purposes. Signed-off-by:
Long Li <longli@microsoft.com> Acked-by:
Martin K. Petersen <martin.petersen@oracle.com> (cherry picked from commit f8aea701) Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate vlan_tci from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate status from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate xmit_more from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate completion_func from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate is_data_pkt from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate send_completion_tid from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate page_buf from struct hv_netvsc_packet. Signed-off-by:
-
Vitaly Kuznetsov authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Packet scheduler guarantees there won't be multiple senders for the same queue and as we use q_idx for multi_send_data the spinlock is redundant. Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com> Signed-off-by:
-
Vitaly Kuznetsov authored
BugLink: http://bugs.launchpad.net/bugs/1583357Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 The rndis header is 116 bytes big and can be placed in the default head room that will be available in the skb. Since the netvsc packet is less than 48 bytes, we can use the skb control buffer for the netvsc packet. With these changes we don't need to ask for additional head room. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate send_completion_ctx from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate send_completion from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminatte the data field from struct hv_netvsc_packet. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate rndis_msg pointer from hv_netvsc_packet structure. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Eliminate the channel field in hv_netvsc_packet structure. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 Rearrange the elements of struct hv_negtvsc_packet for optimal layout - eliminate unnecessary padding. Signed-off-by:
-
KY Srinivasan authored
BugLink: http://bugs.launchpad.net/bugs/1583357 As part of reducing the size of the hv_netvsc_packet, resize some of the variables based on their usage. Signed-off-by:
-
Vitaly Kuznetsov authored
BugLink: http://bugs.launchpad.net/bugs/1583357 There are several issues in hv_netvsc driver with regards to link status change handling: - RNDIS_STATUS_NETWORK_CHANGE results in calling userspace helper doing '/etc/init.d/network restart' and this is inappropriate and broken for many reasons. - link_watch infrastructure only sends one notification per second and in case of e.g. paired disconnect/connect events we get only one notification with last status. This makes it impossible to handle such situations in userspace. Redo link status changes handling in the following way: - Create a list of reconfig events in network device context. - On a reconfig event add it to the list of events and schedule netvsc_link_change(). - In netvsc_link_change() ensure 2-second delay between link status changes. - Handle RNDIS_STATUS_NETWORK_CHANGE as a paired disconnect/connect event. Signed-off-by:
-
Kamal Mostafa authored
Ignore: yes Signed-off-by:
-
- 12 Jul, 2016 2 commits
-
-
Kamal Mostafa authored
Signed-off-by: -
Ben Skeggs authored
BugLink: http://bugs.launchpad.net/bugs/1602340Signed-off-by:
Ben Skeggs <bskeggs@redhat.com> (back-ported from https://github.com/skeggsb/nouveau.git 11fcd1624b0a1c73fe3b2fa15c3cc45816da0470) Signed-off-by:
Benjamin M Romer <benjamin.romer@canonical.com>
-
- 05 Jul, 2016 1 commit
-
-
Kamal Mostafa authored
Ignore: yes Signed-off-by:
-
- 30 Jun, 2016 11 commits
-
-
Kamal Mostafa authored
Signed-off-by: -
Hannes Reinecke authored
Not every device will return a useable VPD identification, but still might support ALUA. Rather than disable ALUA support we should be allowing the device identification to be empty and attach individual ALUA device handler to each devices. [mkp: Fixed typo reported by Bart] Reported-by:
Paul Mackerras <paulus@ozlabs.org> Signed-off-by:
Hannes Reinecke <hare@suse.com> Tested-by:
Bart Van Assche <bart.vanassche@sandisk.com> Signed-off-by:
Stefan Bader <stefan.bader@canonical.com> Acked-by:
-
Hannes Reinecke authored
Sending a 'REPORT TARGET PORT GROUP' command is a costly operation, as the array has to gather information about all ports. So instead of using RTPG to poll for a status update when a port is in transitioning we should be sending a TEST UNIT READY, and wait for the sense code to report success. Reviewed-by:
Ewan Milne <emilne@redhat.com> Reviewed-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
Hannes Reinecke <hare@suse.de> Signed-off-by:
-
Hannes Reinecke authored
When we read in the target port group state we should be updating all affected port groups, otherwise we risk running out of sync. Reviewed-by:
-
Hannes Reinecke authored
When we receive a unit attention code of 'ALUA state changed' we should recheck the state, as it might be due to an implicit ALUA state transition. This allows us to return NEEDS_RETRY instead of ADD_TO_MLQUEUE, allowing to terminate the retries after a certain time. At the same time a workqueue item might already be queued, which should be started immediately to avoid any delays. Reviewed-by:
-
Hannes Reinecke authored
Add a new blacklist flag BLIST_SYNC_ALUA to instruct the alua device handler to use synchronous command submission for ALUA commands. Reviewed-by:
-
Hannes Reinecke authored
Some arrays may only capable of handling one STPG at a time, so this patch adds a singlethreaded workqueue for STPGs to be submitted synchronously. Reviewed-by:
-
Hannes Reinecke authored
The current ALUA device_handler has two drawbacks: - We're sending a 'SET TARGET PORT GROUP' command to every LUN, disregarding the fact that several LUNs might be in a port group and will be automatically switched whenever _any_ LUN within that port group receives the command. - Whenever a LUN is in 'transitioning' mode we cannot block I/O to that LUN, instead the controller has to abort the command. This leads to increased traffic across the wire and heavy load on the controller during switchover. With this patch the RTPG handling is moved to a per-portgroup workqueue. This reduces the number of 'REPORT TARGET PORT GROUP' and 'SET TARGET PORT GROUPS' sent to the controller as we're sending them now per port group, and not per device as previously. It also allows us to block I/O to any LUN / port group found to be in 'transitioning' ALUA mode, as the workqueue item will be requeued until the controller moves out of transitioning. Reviewed-by:
-
Hannes Reinecke authored
The 'relative port' field is not used, and might get stale when the port group changes. So remove the field altogether. Reviewed-by:
-
Hannes Reinecke authored
When the optimize_stpg module option is set we should just set it once during port_group allocation. Doing so allows us to override it later with device specific settings. Reviewed-by:
-
Hannes Reinecke authored
revert commit a8e5a2d5 ("[SCSI] scsi_dh_alua: ALUA handler attach should succeed while TPG is transitioning") This reverts commit a8e5a2d5 Obsoleted by the next patch. Reviewed-by:
-
