[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] [Firmware] TCG BIOS extensions for the Bochs BIOS

  • To: Stefan Berger <stefanb@xxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Tue, 12 Dec 2006 15:53:16 +0000
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 12 Dec 2006 07:53:35 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcceBaLl4TAfmYn4EduMlQANk04WTA==
  • Thread-topic: [Xen-devel] [PATCH] [Firmware] TCG BIOS extensions for the Bochs BIOS

On 12/12/06 3:25 pm, "Stefan Berger" <stefanb@xxxxxxxxxx> 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 single function into 32 bit space and then continuously put more up there, but get the linking right. Probably funneling everything through a single function and demultiplexing in 32 bit space is not what we would want.

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 produced as part of the building and linking of the 32-bit extensions (it’ll probably be a C array of pointers, in its own data section which the linker will know 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
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.