Search results

Jump to: navigation, search

Page title matches

  • === Device Relationships in QOM === Everything in QOM is a device. The concept of busses are implemented as an
    9 KB (1,482 words) - 02:20, 17 September 2011
  • Convert CPUState to [[Features/QOM|QOM]]. # Short-term: Allow inspecting and modifying CPU properties via QOM.
    6 KB (753 words) - 23:14, 14 June 2012
  • == Machine as QOM object == * Getting more close to QOM's vision of single interface for device creation and so on.
    1 KB (183 words) - 12:14, 12 October 2016

Page text matches

  • ...oleted by <tt>query-cpu-model-expansion</tt> QMP commands and <tt>filtered-features</tt> property ** Actually, the new mechanism is based on the "filtered-features" X86CPU property
    15 KB (2,336 words) - 13:50, 30 October 2017
  • * [{{PagesStartingWith|Features/}} All feature pages] * [[Features/COLO|COLO]]
    678 B (76 words) - 16:36, 29 November 2017
  • = Features = ** add QEMU Object Model (QOM) support to the vhost-scsi device
    2 KB (303 words) - 15:39, 11 October 2016
  • Convert CPUState to [[Features/QOM|QOM]]. # Short-term: Allow inspecting and modifying CPU properties via QOM.
    6 KB (753 words) - 23:14, 14 June 2012
  • | [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should have initial code committed by this date. == Targeted Features ==
    1 KB (159 words) - 15:38, 11 October 2016
  • * New QOM infrastructure was introduced, exposing a boolean "realized" property. * Various minor bugfixes; no new features in this release.
    4 KB (589 words) - 12:24, 19 February 2013
  • == [[Features/QOM|QOM]] Coding Conventions == * DO use QOM cast macros (based on struct layout)
    3 KB (397 words) - 10:10, 12 October 2016
  • ...ng the mailing list nor a place to announce cool new [[Contribute#Features|features]] for users. ...nition of CPU subclasses (e.g. struct X86CPU) is now in cpu.h, so that cpu-qom.h can be included from code compiled for all targets.
    4 KB (664 words) - 13:40, 26 July 2017
  • === Making all devices QOM objects === ...cumentation/QOMConventions]] for the latest guidance on how to structure a QOM device.
    8 KB (1,232 words) - 18:25, 23 November 2017
  • ...", "-machine mem-merge" and "-machine dump-guest-core" are subsumed by the QOM objects "memory-backend-ram" and "memory-backend-file", and by the "memdev" * Support for memory hotplug using the new "pc-dimm" device and the QOM objects "memory-backend-ram" and "memory-backend-file".
    10 KB (1,454 words) - 10:42, 29 July 2014
  • ...MODEL'',enforce", of course as long as TCG or KVM support the CPU's set of features. Previously, a few CPUs included extraneous CPUID flags that cause "-cpu '' ...uring reboot. In addition, the boot order can be dynamically modified via QOM.
    7 KB (980 words) - 15:30, 14 December 2014
  • ...e. Only x3270 is supported as client. See https://wiki.qemu.org/index.php/Features/3270 for details. * CSS ids are visible in "info qtree" and as QOM properties.
    11 KB (1,614 words) - 18:24, 24 August 2017
  • * [[Features/HRandomHypercall | H_RANDOM hypercall]] device for providing good random da ...l warn when using a "-cpu" model that includes unsupported features. These features are disabled automatically, just like in previous versions of QEMU
    13 KB (2,001 words) - 11:33, 17 December 2015

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)