From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stefan Berger <stefanb@us.ibm.com>,
qemu-devel@nongnu.org, Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] Add ACPI tables for TPM
Date: Wed, 30 Jul 2014 18:22:02 +0200 [thread overview]
Message-ID: <53D91BAA.5050506@redhat.com> (raw)
In-Reply-To: <20140730160706.GE27451@redhat.com>
On 07/30/14 18:07, Michael S. Tsirkin wrote:
> On Wed, Jul 30, 2014 at 06:02:21PM +0200, Laszlo Ersek wrote:
>> On 07/30/14 17:37, Michael S. Tsirkin wrote:
>>
>>> 1. execute alloc instructions, building a data structure mapping fwcfg
>>> file names to memory.
>>
>> Yes, edk2 currently lacks a good (== sub-linear) dictionary data type.
>> This week I started porting a red-black tree library that I had
>> originally written in 1999 or 2000 or so. In OVMF coding I've faced a
>> few occasions when I would have wanted a dictionary, and one of them is
>> the above.
>>
>> Laszlo
>
> number of tables is small though, seabios just uses a linked list
> and a linear search, to get N^2 complexity where N is number
> of tables.
>
> it's up to you.
Correct, I did consider that, but I probed edk2-devel for opinions about
an associative data structure first, and feedback was positive, so I
started porting. I'll even admit that for small N, the O(N^2) of lists
might beat the rbtree's O(NlogN) in practice, due to the greater
constants in the "smart" data structure, but just the API should be that
much more convenient that I'm willing to accept that.
Laszlo
next prev parent reply other threads:[~2014-07-30 16:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 10:52 [Qemu-devel] [PATCH v2] Add ACPI tables for TPM Stefan Berger
2014-07-30 11:17 ` Michael S. Tsirkin
2014-07-30 13:34 ` Stefan Berger
2014-07-30 13:20 ` Michael S. Tsirkin
2014-07-30 14:36 ` Laszlo Ersek
2014-07-30 14:46 ` Michael S. Tsirkin
2014-07-30 15:15 ` Laszlo Ersek
2014-07-30 15:37 ` Michael S. Tsirkin
2014-07-30 16:02 ` Laszlo Ersek
2014-07-30 16:07 ` Michael S. Tsirkin
2014-07-30 16:22 ` Laszlo Ersek [this message]
2014-07-30 15:03 ` Igor Mammedov
2014-07-30 15:29 ` Laszlo Ersek
2014-07-30 15:10 ` Stefan Berger
2014-07-30 15:20 ` Michael S. Tsirkin
2014-07-30 15:29 ` Stefan Berger
2014-07-30 15:41 ` Laszlo Ersek
2014-07-30 15:44 ` Stefan Berger
2014-07-30 15:58 ` Laszlo Ersek
2014-07-30 16:03 ` Stefan Berger
2014-07-30 16:10 ` Michael S. Tsirkin
2014-07-30 16:18 ` Laszlo Ersek
2014-07-30 16:35 ` Stefan Berger
2014-07-30 17:18 ` Laszlo Ersek
2014-07-30 15:50 ` Michael S. Tsirkin
2014-07-30 15:59 ` Stefan Berger
2014-07-30 16:05 ` Michael S. Tsirkin
2014-07-30 16:14 ` Laszlo Ersek
2014-07-30 16:19 ` Stefan Berger
2014-07-30 15:37 ` Laszlo Ersek
2014-07-30 15:52 ` Michael S. Tsirkin
2014-07-30 16:07 ` Laszlo Ersek
2014-07-30 16:11 ` Stefan Berger
2014-07-30 16:11 ` Michael S. Tsirkin
2014-07-30 16:24 ` Laszlo Ersek
2014-07-30 14:54 ` Stefan Berger
2014-07-30 15:07 ` Michael S. Tsirkin
2014-07-30 15:13 ` Stefan Berger
2014-07-30 15:25 ` Michael S. Tsirkin
2014-07-30 15:36 ` Stefan Berger
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=53D91BAA.5050506@redhat.com \
--to=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanb@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).