From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: KVM minutes for 2013-06-11
Date: Tue, 11 Jun 2013 16:48:38 +0200 [thread overview]
Message-ID: <87txl41z5l.fsf@elfo.elfo> (raw)
2013-06-11
----------
- move ACPI table generation to QEMU
- code sharing with SEABIOS
- easier to generate there
Anthony: it is the same put in QEMU or SEABIOS
Michael: there are some information not easily available in
seabios (hot plug)
Anthony: transfer QOM tree to SEABIOS, current interface shows its age.
- information hardcoded that change over time
this is easier in qemu
Example bus device number:
maintain device number stable over migration
It is easier to maintian the mostly static tables in QEMU.
QEMU knows the whole device tree, so it is easy to generate.
Where are we know? Do we have enough ACPI support into QEMU?
Anthony wants a mergable tree before starting. Still think it is the wrong approach.
Create a new serial port and enable it through ACPI?
Using iasl at roon time and source table is problematic. iasl don't
work on big endian hosts.
- VFIO?
How to do it (Alex), will be discussed on the list
Later, Juan.
reply other threads:[~2013-06-11 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87txl41z5l.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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