On Wed, 2013-01-30 at 22:13 -0500, Kevin OConnor wrote:
This bothers me a little as well. Would it be possible to separate out the UMBStart/End stuff into a separate patch. (The main patch would assume OVMF doesn't lock 0xc0000-0xfffff at all, and the UMBStart/End patch would assume that OVMF has your proposed extensions.)
I've done that and pushed it to the git tree. Although the latest version actually works fine anyway, as long as OVMF has the simple one-line to avoid locking the range.
The extra fields in the table don't bother it at all since the table has a TableLength field and the checksum is calculated over that. So they're just ignored.