qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: qemu-devel@nongnu.org, yamahata@valinux.co.jp, anthony@codemonkey.ws
Cc: jan.kiszka@siemens.com, alex.williamson@redhat.com, mst@redhat.com
Subject: [Qemu-devel] q35 chipset support
Date: Thu, 14 Jun 2012 15:54:59 -0400	[thread overview]
Message-ID: <20120614195458.GB8244@redhat.com> (raw)

Hi,

I recently updated Isaku Yamahata's q35 patches to work on the latest qemu and
seabios trees. On the qemu side, most of the changes revolved around updating
to use QOM and updates to the memory API. I was also able to drop quite a few
patches that had already been resolved by the current qemu tree.

The trees seem pretty stable and can be found here:

git://github.com/jibaron/q35-qemu.git
git://github.com/jibaron/q35-seabios.git

A basic qemu cmd to start q35, looks like:

$ /usr/local/bin/qemu-system-x86_64  -name "f16" -M pc_q35 -m 1G -smp 4  -hda
./f16.img --enable-kvm  -bios <path>/q35-seabios/out/bios.bin
-acpitable file=<path>/q35-seabios/out/q35-acpi-dsdt.aml  -monitor stdio

The main reason to bring in q35 chipset support is for pcie support - thus
allowing drivers to make use of the extended config space, aer, pcie hotplug.
So, I wanted to start a discussion around what is missing from this patchset,
and how I should structure this patchset (perhaps, I should post the patches
to the list?). For example, does the q35 chipset support need to have feature
parity with the current i440fx before it would be considered? Or, can we bring
these features in incrementally?

As far as what I know is currently missing:

-device hotplug support needs to be added. As Michael Tsirkin pointed out
devices behind pcie bridges use up 4K i/o space, so we might quickly run out
of i/o space vs. pci bridges...
-migration vmstate needs to be updated (I didn't test or fixup migration yet)

I'm sure there is a lot more...

Thanks,

-Jason

             reply	other threads:[~2012-06-14 19:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 19:54 Jason Baron [this message]
2012-06-14 20:16 ` [Qemu-devel] q35 chipset support Anthony Liguori
2012-06-15  7:04   ` Markus Armbruster
2012-06-15 17:58     ` Anthony Liguori
2012-06-17  8:25       ` Michael S. Tsirkin
2012-06-18 14:16         ` Anthony Liguori
2012-06-18 14:35           ` Michael S. Tsirkin
2012-06-18 15:15             ` Anthony Liguori
2012-06-18 16:04             ` Jason Baron
2012-06-18 13:51       ` Markus Armbruster
2012-06-18 14:05         ` Anthony Liguori
2012-06-18 20:36           ` Jason Baron
2012-06-18 21:15             ` Anthony Liguori
2012-06-18 14:20       ` Michael S. Tsirkin
2012-06-18 14:22         ` Anthony Liguori
2012-06-18 14:37           ` Michael S. Tsirkin
2012-06-18 15:36             ` Andreas Färber
2012-06-18 15:45               ` Anthony Liguori
2012-06-15 17:57   ` Jason Baron
2012-06-15 17:59     ` Anthony Liguori
2012-06-18 13:52       ` Markus Armbruster
2012-06-18 14:38         ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120614195458.GB8244@redhat.com \
    --to=jbaron@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).