From: Keir Fraser <keir@xensource.com>
To: Stefan Berger <stefanb@us.ibm.com>, Keir Fraser <keir@xensource.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] [Firmware] TCG BIOS extensions for the Bochs BIOS
Date: Fri, 08 Dec 2006 13:36:05 +0000 [thread overview]
Message-ID: <C19F1AC5.5BBC%keir@xensource.com> (raw)
In-Reply-To: <OFA5ECA0F2.3DE3C265-ON8525723E.00481862-8525723E.004A27C0@us.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]
On 8/12/06 13:30, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>> > Is there a good reason for it being implemented almost entirely in assembly
>> > language?
>
> The compiled TCG extension code adds approximately 0x2500 bytes to the BIOS
> and would add more to it if it was written in 'C'.
Presumably only those who want TPM functionality will run with the
TPM-enabled BIOS, and they are unlikely to care whether the implementation
is e.g., 10kB or 15kB. Even people not using the TPM capabilities are not
really going to care about a few kilobytes. It¹s not like you¹re constrained
to 64kB (0xF0000-0xFFFFF) ‹ you can stick the 32-bit code below 4GB.
-- Keir
[-- Attachment #1.2: Type: text/html, Size: 1299 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-12-08 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 22:04 [PATCH] [Firmware] TCG BIOS extensions for the Bochs BIOS Stefan Berger
2006-12-08 9:24 ` Keir Fraser
2006-12-08 13:30 ` Stefan Berger
2006-12-08 13:36 ` Keir Fraser [this message]
2006-12-11 15:26 ` Stefan Berger
2006-12-11 15:43 ` Keir Fraser
2006-12-12 15:25 ` Stefan Berger
2006-12-12 15:53 ` Keir Fraser
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=C19F1AC5.5BBC%keir@xensource.com \
--to=keir@xensource.com \
--cc=stefanb@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.