** Changed in: linux (Ubuntu)
       Status: Incomplete => Triaged

** Description changed:

  Use !hypervisor_is_type(X86_HYPER_NATIVE) checks
  
  ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration
-  -> do this by default on paravirt machines, or potentially kvm only machines
+  -> probably redundant on kvmclock systems
  
  3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age
-  -> do this by default on paravirt machines, or potentially kvm only machines
+  -> livecd-rootfs should do this in the ext4 superblock
  
  4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1
-  -> do this by default on paravirt machines, or potentially kvm only machines
- 
+  -> already default on kvm systems
  
  bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable
-  -> kvm init should do what vmware init is doing and setting TSC_RELIABLE 
capability
-                 wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1);
-                 setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE);
+  -> kvm init should do what vmware init is doing and setting TSC_RELIABLE 
capability
+                 wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1);
+                 setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE);
  
  And then we should change config to move virtio & ext4 filesystems as
  built in.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2006488

Title:
  Kill linux-kvm flavour

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Use !hypervisor_is_type(X86_HYPER_NATIVE) checks

  ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration
   -> probably redundant on kvmclock systems

  3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age
   -> livecd-rootfs should do this in the ext4 superblock

  4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1
   -> already default on kvm systems

  bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable
   -> kvm init should do what vmware init is doing and setting TSC_RELIABLE 
capability
                  wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1);
                  setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE);

  And then we should change config to move virtio & ext4 filesystems as
  built in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006488/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to