From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] [Firmware] TCG BIOS extensions for the Bochs BIOS Date: Tue, 12 Dec 2006 15:53:16 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0061386084==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan Berger Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============0061386084== Content-type: multipart/alternative; boundary="B_3248783596_54132946" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3248783596_54132946 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable On 12/12/06 3:25 pm, "Stefan Berger" wrote: > Since I am running out of space in the BIOS segment now while converting = the > functions to 'C'... > Do you know of some good 'constructs' that can be left in the rombios as > markers for linking the two pieces? I'd like to start with lifting up a s= ingle > function into 32 bit space and then continuously put more up there, but g= et > the linking right. Probably funneling everything through a single functio= n and > demultiplexing in 32 bit space is not what we would want. >=20 > I suppose HVMloader will have to carry a relocateable file (-fPIC) and be= able > to re-locate it to whatever memory could be reserved. How about just have a table below 1MB, indexed by function id (where function ids also are statically allocated too). This table will be produce= d as part of the building and linking of the 32-bit extensions (it=B9ll probabl= y be a C array of pointers, in its own data section which the linker will kno= w to place at the very start of the extension ROM): it can then be patched into the rombios at compile time, or copied to a pre-decided address below 1MB by hvmloader at boot time. -- Keir --B_3248783596_54132946 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [Xen-devel] [PATCH] [Firmware] TCG BIOS extensions for the Bochs= BIOS On 12= /12/06 3:25 pm, "Stefan Berger" <stefanb@us.ibm.com> wrote:<= BR>
Since I am running out of space in the BIOS segment now while= converting the functions to 'C'...
Do you know of some good 'construct= s' that can be left in the rombios as markers for linking the two pieces? I'= d like to start with lifting up a single function into 32 bit space and then= continuously put more up there, but get the linking right. Probably funneli= ng everything through a single function and demultiplexing in 32 bit space i= s not what we would want.

I suppose HVMloader will have to ca= rry a relocateable file (-fPIC) and be able to re-locate it to whatever memo= ry could be reserved.

How about just have a table below 1MB, indexed by function id (where functi= on ids also are statically allocated too). This table will be produced as pa= rt of the building and linking of the 32-bit extensions (it’ll probabl= y be a C array of pointers, in its own data section which the linker will kn= ow to place at the very start of the extension ROM): it can then be patched = into the rombios at compile time, or copied to a pre-decided address below 1= MB by hvmloader at boot time.

 -- Keir
 --B_3248783596_54132946-- --===============0061386084== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0061386084==--