summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-09-21Revert "[Fuel-plugin] Install kernel in post-deployment."colorado.1.0stable/coloradoYunhong Jiang5-23/+10
This reverts commit a10a10b373f17dc423800e6bb8d1a8e99450090d. According to Fuel team, this patch will be included into C-2 release instead of C-1 release, so we have to revert it to the C stable branch. To revert from C stable branch requires cherry-picking from master branch, so here it is. Change-Id: I32e1148e5c1cd24e5696270f1aa328630ef42dd0 Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com> (cherry picked from commit 8647dbbe9db84d71610f42cec6ff619783d99800)
2016-09-21Adjusted headingsSofia Wallin3-12/+9
Adjusted the headings in the installation & config guide, scenario description and user guide. Also removed the relese notes from the install and config doc since you have a separate document for this. Change-Id: I2ecbaebe2c0f337cca0a8d0ad130fa97eceabe78 Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com> (cherry picked from commit a5f72bd195d6a6cf510e415e589fddcd83f9481e)
2016-09-21Small enhancement to the release notes documentYunhong Jiang2-44/+35
Change the release notes to include the upstream version and reorgnize the structure. Change-Id: Ic28f639d9e6b877020dc226a147c7196bcad802a Signed-off-by: Reddy, Raghuveer <raghuveer.reddy@intel.com> Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com> (cherry picked from commit bd80e10bc24e3c34c31d146695f4c8429eda660d)
2016-09-20Documentation updatesSofia Wallin2-17/+5
Adjusted the heading in the user guide Adjusted the heading, licence part and release date in the release notes Change-Id: I48a561bcd0d3bab655b27f3cafd486f22fa40c77 Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com> (cherry picked from commit 42b05a5201bd85502f818744af562c5c3e1a94c8)
2016-09-19[Fuel-plugin] Install kernel in post-deployment.Michal Skalski5-10/+23
Install kernel and reboot compute nodes in post-deployment phase when there is less chance to interfere with other tasks. Implement Michael's suggestion to use reboot puppet module. Change-Id: I83867e5e2752c39d2b69c950e3e475d43de04466 Signed-off-by: Michal Skalski <mskalski@mirantis.com> (cherry picked from commit a10a10b373f17dc423800e6bb8d1a8e99450090d)
2016-09-07OPNFV KVM4NFV: Documentation Enhancementkalyanreddy2-0/+12
This patch contains some documentation enhancement for more clarity on KVM4NFV project. Change-Id: I3186d65d8d542ffd842a1a8b54289cda308056ce Signed-off-by: Gundarapu Kalyan Reddy <reddyx.gundarapu@intel.com> (cherry picked from commit f435810f53bffdf881b852a81546039c72a4c60d)
2016-08-22OPNFV KVM4NFV: Documentation Enhancementswatisharma2-9/+3
This patch contains some documentation enhancement required for KVM4NFV project. Co-Authored-By: Gundarapu Reddy <reddyx.gundarapu@intel.com> Signed-off-by: Swati Sharma <swatix.sharma@intel.com>
2016-08-20Merge "CI integration for KVMforNFV."Jiang, Yunhong5-22/+73
2016-08-19Merge "OPNFV KVM4NFV: Documentation"Jiang, Yunhong43-236/+1768
2016-08-20CI integration for KVMforNFV.swatisharma5-22/+73
This patch contains scripts for running cyclictest through yardstick as part of CI integration for KVMforNFV. The scripts will be triggered to create a docker ubuntu container for running yardstick, configuring the host, launching a guest VM and executing cyclictest through yardstick. The verification process gets completed after running the cyclictest. Co-Authored-By: Gundarapu Reddy <reddyx.gundarapu@intel.com> Signed-off-by: Swati Sharma <swatix.sharma@intel.com>
2016-08-19OPNFV KVM4NFV: Documentationswatisharma43-236/+1768
This patch contains the full documentation required for KVM4NFV project. The documents are organized into the following sections- user guide, configuration guide, installation guide. requirement document, design document, release notes and glossary. Co-Authored-By: Gundarapu Reddy <reddyx.gundarapu@intel.com> Signed-off-by: Swati Sharma <swatix.sharma@intel.com>
2016-08-19Merge "bnxt_en: Request firmware reset after successful firwmare update"Yunhong Jiang1-0/+2
2016-08-19Merge "bnxt_en: Reset embedded processor after applying firmware upgrade"Yunhong Jiang1-4/+42
2016-08-18bnxt_en: Request firmware reset after successful firwmare updateYunhong Jiang1-0/+2
Upon successful mgmt processor firmware update, request a self reset upon next PCIe reset (e.g. system reboot). upstream-status: backport Notice: Change the "signed-off-by" to "Signed -of -by" to avoid smap to original author. Signed -of -by: Rob Swindell <rob.swindell@broadcom.com> Signed -of -by: Michael Chan <michael.chan@broadcom.com> Signed -of -by: David S. Miller <davem@davemloft.net> Change-Id: I331f1c9bd091e4ed7c116d320872d3eea6a91a37 Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-08-18bnxt_en: Reset embedded processor after applying firmware upgradeYunhong Jiang1-4/+42
Use HWRM_FW_RESET command to request a self-reset of the embedded processor(s) after successfully applying a firmware update. For boot processor, the self-reset is currently deferred until the next PCIe reset. upstream-status: backport Notice: We change the Signed-off-by to "Signed -of -by" to avoid trigger the spam to the original author. Signed -of -by: Rob Swindell <swindell@broadcom.com> Signed -of -by: Michael Chan <mchan@broadcom.com> Signed -of -by: David S. Miller <davem@davemloft.net> Change-Id: Ic491d584c566b89a315d04f41b1d4fa928756403 Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-08-18Add support for Broadcom NetXtremeII 10GbMichal Skalski1-1/+3
This NIC is used on Ericsson CI POD2 JIRA: KVMFORNFV-45 JIRA: FUEL-171 upstream-status: N/A Change-Id: I3b1ab07388719380d288cb0d8c2a2af52510303d Signed-off-by: Michal Skalski <mskalski@mirantis.com> Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-08-17Install kernel in main phase of deploymentMichal Skalski1-2/+2
Kvm plugin restart compute nodes after kernel installation but after reboot mcollective agent sometimes does not start, which causes deployment failures. Preliminary tests show that rebooting nodes after pre deployment phase may reduce occurence of this problem. JIRA: KVMFORNFV-45 JIRA: FUEL-171 Change-Id: I4a599c834a3263bb487acb491f82aea7901dc201 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-08-12Build kernel in another directory and README.md update for fuel-plugindavidjchou2-5/+13
1. Since some files generated during kernel building are only root writeable, this will cause "permission denied" issue in "make clean" in fuel@opnfv iso building which uses normal user priviledge. Building kernel in another directory than the directory mapped into Docker container can resolve the issue. 2. Update and typing error correction for README.md Upstream status - NA Change-Id: Icdd1a12d38f90619dd91588cb9e0f5b9bdfe95d1 Signed-off-by: davidjchou <david.j.chou@intel.com>
2016-08-12Merge "Revert the test_kvmfornfv.sh"Yunhong Jiang1-36/+4
2016-08-12Merge "Remove OVS quirk"Jiang, Yunhong1-246/+0
2016-08-11Revert the test_kvmfornfv.shYunhong Jiang1-36/+4
It triggers several bugs and need more polish. However, we can't simply revert that changeset because that will cause failur also. A stub is created. Change-Id: I8e54d5865c16d85834a8dd011322421a6c448f8a Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-08-10CI Integration for KVMforNFVswatisharma3-0/+85
This patch contains scripts for running cyclictest through yardstick as part of CI integration for KVMforNFV. The scripts will be triggered to create a docker ubuntu container for running yardstick, configuring the host, launching a guest VM and executing cyclictest through yardstick. The verification process gets completed after running the cyclictest. Co-Authored-By: Gundarapu Reddy <reddyx.gundarapu@intel.com> Signed-off-by: Swati Sharma <swatix.sharma@intel.com>
2016-07-26scripts/package/Makefile: rpmbuild add support of RPMOPTSSrinivas Pandruvada1-2/+2
After commit 21a59991ce0c ("scripts/package/Makefile: rpmbuild is needed for rpm targets"), it is no longer possible to specify RPMOPTS. For example, we can no longer able to control _topdir using the following make command. make RPMOPTS="--define '_topdir /home/xyz/workspace/'" binrpm-pkg Fixes: 21a59991ce0c ("scripts/package/Makefile: rpmbuild is needed for rpm targets") Cc: <stable@vger.kernel.org> # 4.3+ Notice: Have to remove the original signed-off-by line because gerrit will notify the original author, which is not good. Keep the name and the email address still. Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Michal Marek <mmarek@suse.com> upstream-status: backport Change-Id: If7ce5d9d006ee9d49b2d7d200ebdc278395eb3f7 backport-by: Yunhong Jiang <yunhong.jiang@intel.com> Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-26Remove OVS quirkDonald Dugger1-246/+0
The OVS project has finally added support for the 4.4 kernel so this quirk is no longer necessary. Upstream status: NA Change-Id: I62a40b96c16b8a7754297fa108240568fa7b5646 Signed-off-by: Don Dugger <n0ano@n0ano.com>
2016-07-22Merge "Restore the non_hz_full"Yunhong Jiang1-2/+8
2016-07-22Merge "Creation of QEMU(rpm and debian builds)"Jiang, Yunhong6-0/+156
2016-07-22Merge "Add the "timers: do not raise softirq unconditionally" temporarily"Yunhong Jiang2-8/+29
2016-07-21Restore the non_hz_fullYunhong Jiang1-2/+8
Please refer to http://comments.gmane.org/gmane.linux.kernel/1891417, the last two mails on this discussion. The non_hz_full is important for RT, so take it back temporarily. Unluckily I didn't find the corresponding reverting patch on the RT tree. Upstream status: pending Change-Id: I2748a8f9b7a98ef2185a1da60089984432393eff Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-21Add the "timers: do not raise softirq unconditionally" temporarilyYunhong Jiang2-8/+29
This patch enable the nohz_full and is important for RT. Bring it back temporarily, while waiting for more work on RT community. Please refer to https://lkml.org/lkml/2015/3/17/783 for more information of the revert. A little rebase needed because it's reverted on old code base. Please notice that we change the rt_mutex_trylock() so that we can get the tvec_base lock there. This is sure to be wrong, and should be fixed cleanly. And that's the major reason the original patch are reverted on the upstream RT linux. Will discuss with upstream on how to achieve the solution. Upstream status: pending Change-Id: I2747e087faf4145b69b800a60b8d9414bc71e206 Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-21Merge "KVM: nVMX: keep preemption timer enabled during L2 execution"Jiang, Yunhong1-2/+13
2016-07-21Merge "KVM: nVMX: avoid incorrect preemption timer vmexit in nested guest"Jiang, Yunhong1-0/+2
2016-07-21Merge "KVM: VMX: reflect broken preemption timer in vmcs_config"Jiang, Yunhong1-3/+3
2016-07-21Merge "KVM: vmx: fix missed cancellation of TSC deadline timer"Jiang, Yunhong1-24/+24
2016-07-21Merge "KVM: x86: introduce cancel_hv_tscdeadline"Jiang, Yunhong1-8/+10
2016-07-21Merge "KVM: vmx: fix underflow in TSC deadline calculation"Jiang, Yunhong1-3/+3
2016-07-21Merge "kvm: vmx: hook preemption timer support"Yunhong Jiang3-2/+183
2016-07-21Merge "kvm: vmx: rename vmx_pre/post_block to pi_pre/post_block"Jiang, Yunhong1-2/+15
2016-07-21Merge "KVM: x86: support using the vmx preemption timer for tsc deadline timer"Jiang, Yunhong5-1/+100
2016-07-21Merge "kvm: lapic: separate start_sw_tscdeadline from start_apic_timer"Jiang, Yunhong1-26/+31
2016-07-21Creation of QEMU(rpm and debian builds)Swati Sharma6-0/+156
This includes the scripts that are added to create qemu-rpm and qemu-debian builds for KVM4NFV. Co-Authored-By: Gundarapu Reddy <reddyx.gundarapu@intel.com> Signed-off-by: Swati Sharma <swatix.sharma@intel.com>
2016-07-19Merge "Update fuel plugin builder installation"Jiang, Yunhong1-9/+3
2016-07-18KVM: nVMX: keep preemption timer enabled during L2 executionPaolo Bonzini1-2/+13
Because the vmcs12 preemption timer is emulated through a separate hrtimer, we can keep on using the preemption timer in the vmcs02 to emulare L1's TSC deadline timer. However, the corresponding bit in the pin-based execution control field must be kept consistent between vmcs01 and vmcs02. On vmentry we copy it into the vmcs02; on vmexit the preemption timer must be disabled in the vmcs01 if a preemption timer vmexit happened while in guest mode. The preemption timer value in the vmcs02 is set by vmx_vcpu_run, so it need not be considered in prepare_vmcs02. Cc: Yunhong Jiang <yunhong.jiang@intel.com> Cc: Haozhong Zhang <haozhong.zhang@intel.com> Tested-by: Wanpeng Li <kernellwp@gmail.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: Iffaea7689d4e653dc6224a6f05c6e5ba2fb5c8a8 upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18KVM: nVMX: avoid incorrect preemption timer vmexit in nested guestWanpeng Li1-0/+2
The preemption timer for nested VMX is emulated by hrtimer which is started on L2 entry, stopped on L2 exit and evaluated via the check_nested_events hook. However, nested_vmx_exit_handled is always returning true for preemption timer vmexit. Then, the L1 preemption timer vmexit is captured and be treated as a L2 preemption timer vmexit, causing NULL pointer dereferences or worse in the L1 guest's vmexit handler: BUG: unable to handle kernel NULL pointer dereference at (null) IP: [< (null)>] (null) PGD 0 Oops: 0010 [#1] SMP Call Trace: ? kvm_lapic_expired_hv_timer+0x47/0x90 [kvm] handle_preemption_timer+0xe/0x20 [kvm_intel] vmx_handle_exit+0x169/0x15a0 [kvm_intel] ? kvm_arch_vcpu_ioctl_run+0xd5d/0x19d0 [kvm] kvm_arch_vcpu_ioctl_run+0xdee/0x19d0 [kvm] ? kvm_arch_vcpu_ioctl_run+0xd5d/0x19d0 [kvm] ? vcpu_load+0x1c/0x60 [kvm] ? kvm_arch_vcpu_load+0x57/0x260 [kvm] kvm_vcpu_ioctl+0x2d3/0x7c0 [kvm] do_vfs_ioctl+0x96/0x6a0 ? __fget_light+0x2a/0x90 SyS_ioctl+0x79/0x90 do_syscall_64+0x68/0x180 entry_SYSCALL64_slow_path+0x25/0x25 Code: Bad RIP value. RIP [< (null)>] (null) RSP <ffff8800b5263c48> CR2: 0000000000000000 ---[ end trace 9c70c48b1a2bc66e ]--- This can be reproduced readily by preemption timer enabled on L0 and disabled on L1. Return false since preemption timer vmexits must never be reflected to L2. Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: Radim Krčmář <rkrcmar@redhat.com> Cc: Yunhong Jiang <yunhong.jiang@intel.com> Cc: Jan Kiszka <jan.kiszka@siemens.com> Cc: Haozhong Zhang <haozhong.zhang@intel.com> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: Iaffcd503666879e8157c8559876330110a66e5c4 upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18KVM: VMX: reflect broken preemption timer in vmcs_configPaolo Bonzini1-3/+3
Simplify cpu_has_vmx_preemption_timer. This is consistent with the rest of setup_vmcs_config and preparatory for the next patch. Tested-by: Wanpeng Li <kernellwp@gmail.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: I3b33a881c5e47d5d3046e28374d0b0ca363ffad7 upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18KVM: vmx: fix missed cancellation of TSC deadline timerWanpeng Li1-24/+24
INFO: rcu_sched detected stalls on CPUs/tasks: 1-...: (11800 GPs behind) idle=45d/140000000000000/0 softirq=0/0 fqs=21663 (detected by 0, t=65016 jiffies, g=11500, c=11499, q=719) Task dump for CPU 1: qemu-system-x86 R running task 0 3529 3525 0x00080808 ffff8802021791a0 ffff880212895040 0000000000000001 00007f1c2c00db40 ffff8801dd20fcd3 ffffc90002b98000 ffff8801dd20fc88 ffff8801dd20fcf8 0000000000000286 ffff8801dd2ac538 ffff8801dd20fcc0 ffffffffc06949c9 Call Trace: ? kvm_write_guest_cached+0xb9/0x160 [kvm] ? __delay+0xf/0x20 ? wait_lapic_expire+0x14a/0x200 [kvm] ? kvm_arch_vcpu_ioctl_run+0xcbe/0x1b00 [kvm] ? kvm_arch_vcpu_ioctl_run+0xe34/0x1b00 [kvm] ? kvm_vcpu_ioctl+0x2d3/0x7c0 [kvm] ? __fget+0x5/0x210 ? do_vfs_ioctl+0x96/0x6a0 ? __fget_light+0x2a/0x90 ? SyS_ioctl+0x79/0x90 ? do_syscall_64+0x7c/0x1e0 ? entry_SYSCALL64_slow_path+0x25/0x25 This can be reproduced readily by running a full dynticks guest(since hrtimer in guest is heavily used) w/ lapic_timer_advance disabled. If fail to program hardware preemption timer, we will fallback to hrtimer based method, however, a previous programmed preemption timer miss to cancel in this scenario which results in one hardware preemption timer and one hrtimer emulated tsc deadline timer run simultaneously. So sometimes the target guest deadline tsc is earlier than guest tsc, which leads to the computation in vmx_set_hv_timer can underflow and cause delta_tsc to be set a huge value, then host soft lockup as above. This patch fix it by cancelling the previous programmed preemption timer if there is once we failed to program the new preemption timer and fallback to hrtimer based method. Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: Radim Krčmář <rkrcmar@redhat.com> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: I8a2decefab743aecdfab676fb9267324bf42b848 upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18KVM: x86: introduce cancel_hv_tscdeadlineWanpeng Li1-8/+10
Introduce cancel_hv_tscdeadline() to encapsulate preemption timer cancel stuff. Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: Radim Krčmář <rkrcmar@redhat.com> Cc: Yunhong Jiang <yunhong.jiang@intel.com> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: Icc038176cbf361a9ecdf37ed3425108db57617f2 upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18KVM: vmx: fix underflow in TSC deadline calculationPaolo Bonzini1-3/+3
If the TSC deadline timer is programmed really close to the deadline or even in the past, the computation in vmx_set_hv_timer can underflow and cause delta_tsc to be set to a huge value. This generally results in vmx_set_hv_timer returning -ERANGE, but we can fix it by limiting delta_tsc to be positive or zero. Reported-by: Wanpeng Li <wanpeng.li@hotmail.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: I12eea18c3ec648dbf782d7754b7b574d7d6aa92c upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18kvm: vmx: hook preemption timer supportYunhong Jiang3-2/+183
Hook the VMX preemption timer to the "hv timer" functionality added by the previous patch. This includes: checking if the feature is supported, if the feature is broken on the CPU, the hooks to setup/clean the VMX preemption timer, arming the timer on vmentry and handling the vmexit. A module parameter states if the VMX preemption timer should be utilized. Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> [Move hv_deadline_tsc to struct vcpu_vmx, use -1 as the "unset" value. Put all VMX bits here. Enable it by default #yolo. - Paolo] Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: Icb8e0b853eedce3d52c394e510fa14d2cdd432e9 upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18kvm: vmx: rename vmx_pre/post_block to pi_pre/post_blockYunhong Jiang1-2/+15
Prepare to switch from preemption timer to hrtimer in the vmx_pre/post_block. Current functions are only for posted interrupt, rename them accordingly. upstream-status: backport Change-Id: Ie1dde9be21deeb661de095e07d6c29bcba2e7d73 Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
2016-07-18KVM: x86: support using the vmx preemption timer for tsc deadline timerYunhong Jiang5-1/+100
The VMX preemption timer can be used to virtualize the TSC deadline timer. The VMX preemption timer is armed when the vCPU is running, and a VMExit will happen if the virtual TSC deadline timer expires. When the vCPU thread is blocked because of HLT, KVM will switch to use an hrtimer, and then go back to the VMX preemption timer when the vCPU thread is unblocked. This solution avoids the complex OS's hrtimer system, and the host timer interrupt handling cost, replacing them with a little math (for guest->host TSC and host TSC->preemption timer conversion) and a cheaper VMexit. This benefits latency for isolated pCPUs. [A word about performance... Yunhong reported a 30% reduction in average latency from cyclictest. I made a similar test with tscdeadline_latency from kvm-unit-tests, and measured - ~20 clock cycles loss (out of ~3200, so less than 1% but still statistically significant) in the worst case where the test halts just after programming the TSC deadline timer - ~800 clock cycles gain (25% reduction in latency) in the best case where the test busy waits. I removed the VMX bits from Yunhong's patch, to concentrate them in the next patch - Paolo] Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Change-Id: I4aa1ecfa3463d1cbfb317511b45d2074b33d9b6f upstream-status: backport Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>