All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew D. Ball" <aball@linux.vnet.ibm.com>
To: xen-devel@lists.xensource.com
Subject: approach for heavily hw-oriented values in smbios for guests
Date: Thu, 16 Nov 2006 10:54:36 -0500	[thread overview]
Message-ID: <1163692476.24087.28.camel@localhost> (raw)

When I was implementing smbios, I occasionally put in mock values for
things like the data width of dimms, much to my chagrin.

What do y'all think the best approach to such situations would be?  If
specific migration groups were enforced, such that a guest will not be
migrated to a different type of cpu/memory/etc., putting accuracte data
there makes sense to me.  Otherwise, I'd prefer to put no values.
However, even though the SMBIOS 2.4 standard specifies lots of places
where a value of 'unknown' is syntactically valid, the comformance
guidelines require a ton of very hardware oriented things to be fully
specified.

Thanks for your help!
Andrew

             reply	other threads:[~2006-11-16 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 15:54 Andrew D. Ball [this message]
2006-11-16 15:57 ` approach for heavily hw-oriented values in smbios for guests Keir Fraser
2006-11-16 18:32 ` Alan
2006-11-16 21:17   ` Andrew D. Ball

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=1163692476.24087.28.camel@localhost \
    --to=aball@linux.vnet.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.