From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juan Quintela Subject: KVM minutes for 2013-06-11 Date: Tue, 11 Jun 2013 16:48:38 +0200 Message-ID: <87txl41z5l.fsf@elfo.elfo> Reply-To: quintela@redhat.com Mime-Version: 1.0 Content-Type: text/plain To: KVM devel mailing list , qemu-devel qemu-devel Return-path: Received: from mx1.redhat.com ([209.132.183.28]:31379 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753466Ab3FKOsm (ORCPT ); Tue, 11 Jun 2013 10:48:42 -0400 Sender: kvm-owner@vger.kernel.org List-ID: 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.