Ok, now we finally know it is about qemu&kernel patches - I'll add tasks for 
Still haven't seen any xen references, setting that to incomplete.

But given how new it is I'd punt this from 19.04 to 19.10 where things
in kernel&qemu will have matured and be safer to use.

If you are not ok with this please outline important use cases that will be 
All changes are "just" adding definitions, no actual code added - but I'm 
somewhat afraid of hidden dependencies - especially since we have no associated 
testcase and it would need special (very new) hardware t be tested.

** Also affects: qemu (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: qemu (Ubuntu)
       Status: New => Triaged

** Tags added: qemu-19.10

** Changed in: qemu (Ubuntu)
   Importance: Undecided => Medium

** Changed in: xen (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

Status in linux package in Ubuntu:
Status in qemu package in Ubuntu:
Status in xen package in Ubuntu:

Bug description:
  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages

  Upstream target linux 4.20/Qemu-3.10

  Target Release: 19.04

To manage notifications about this bug go to:

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