From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O74mD-0006Wk-6S for qemu-devel@nongnu.org; Wed, 28 Apr 2010 06:45:57 -0400 Received: from [140.186.70.92] (port=36703 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O74mB-0006W4-05 for qemu-devel@nongnu.org; Wed, 28 Apr 2010 06:45:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O74m7-0005lP-Us for qemu-devel@nongnu.org; Wed, 28 Apr 2010 06:45:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46972) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O74m7-0005lF-Nb for qemu-devel@nongnu.org; Wed, 28 Apr 2010 06:45:51 -0400 Date: Wed, 28 Apr 2010 13:45:48 +0300 From: Gleb Natapov Message-ID: <20100428104548.GS10044@redhat.com> References: <1271705694.2505.36.camel@localhost.localdomain> <20100422011200.GA10677@morn.localdomain> <4BD80054.9090409@redhat.com> <20100428103020.GQ10044@redhat.com> <4BD810EF.5070601@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BD810EF.5070601@redhat.com> Subject: [Qemu-devel] Re: [SeaBIOS] About cpu_set, CPU hotplug and related subjects List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jes Sorensen Cc: Lucas Meneghel Rodrigues , Kevin O'Connor , seabios@seabios.org, qemu mailing list , KVM mailing list On Wed, Apr 28, 2010 at 12:41:51PM +0200, Jes Sorensen wrote: > On 04/28/10 12:30, Gleb Natapov wrote: > > On Wed, Apr 28, 2010 at 11:31:00AM +0200, Jes Sorensen wrote: > >> On 04/22/10 03:12, Kevin O'Connor wrote: > >> Generating the more complex tables dynamically would be preferred, but > >> it requires like half an AML compiler in Seabios, so it kinda stalled > >> there.... > >> > > We can try to be smart and generate most of the code statically and only > > minimum that absolutely required dynamically. Haven't looked at how > > simple dynamic part can be made. > > I looked at it briefly and ran away screaming :) I am sure it can be This is normal reaction to ACPI of a healthy human being. > done, bit it would require pretty good understanding of the AML encodings. > > The CPU declarations are particularly tricky as they get pretty big and > complex and need to live in the DSDT, whereas a lot of other things we > can shift off to separate SSDT tables and only put the minimum that > needs to be generated dynamically in it's own table. > We can generate complex code statically and call it from dynamically generated CPU declarations. -- Gleb.