All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew D. Ball" <aball@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [RFC] [PATCH] HVM SMBIOS support 1/6
Date: Tue, 11 Jul 2006 15:27:51 -0400	[thread overview]
Message-ID: <1152646072.5663.21.camel@localhost.localdomain> (raw)
In-Reply-To: <425338b80088758ffe25b230cf126129@cl.cam.ac.uk>

On Tue, 2006-07-11 at 19:34 +0100, Keir Fraser wrote:
> On 11 Jul 2006, at 19:12, Andrew D. Ball wrote:
> 
> > Do you see any other things to work on for the SMBIOS patches?  Making
> > SMBIOS not optional cuts down on a bit of the code, so I'm working on
> > that and getting the code to run on the latest changeset today.
> 
> I think they're basically okay. I find it a bit weird that hvmloader 
> puts SMBIOS tables in a fixed place and then rombios copies them -- not 
> sure why that's needed but I suppose you're only copying what is done 
> for ACPI tables. Couldn't hvmloader write all BIOS tables to a safe 
> location and be done with them, or is the problem that 0xf0000 upwards 
> is not available at the time hvmloader runs? 

More or less.  0xf0000-0xfffff is reserved for the ROMBIOS, but I need a
31-bit entry point somewhere on a 16-byte boundary there.  It's only the
31-bit entry point that gets copied.

> Also, is the e820 
> reservation entry actually valid: 0x9f000-0xA0000 is reserved, but 
> rombios copies the tables out of that area, right? Does rombios also 
> update the e820 table?

I'm a little confused about this myself.  Whenever I change the e820 map
in libxenguest, it seems to work, but I see two other places that might
change it

(1) copy_e820_table in rombios.c -- looks like this doesn't do anything
if 0x91e8 is 0, which is probably the case.
(2) some code in vmxassist's setup.c -- looks like this has a copy of
the same e820map defined in xc_hvm_build.c and only changes it if TEST
is defined.

Thanks for your help!
Andrew

> 
>   -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

      parent reply	other threads:[~2006-07-11 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 19:36 [RFC] [PATCH] HVM SMBIOS support 1/6 Andrew D. Ball
2006-07-10 14:49 ` Keir Fraser
2006-07-10 15:11   ` Andrew D. Ball
2006-07-11 18:12   ` Andrew D. Ball
2006-07-11 18:34     ` Keir Fraser
2006-07-11 19:01       ` Keir Fraser
2006-07-11 19:27       ` Andrew D. Ball [this message]

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=1152646072.5663.21.camel@localhost.localdomain \
    --to=aball@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.