All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH][SEABIOS] Make SMBIOS table pass MS SVVP test
Date: Mon, 23 Nov 2009 13:08:30 +0200	[thread overview]
Message-ID: <20091123110830.GE2999@redhat.com> (raw)
In-Reply-To: <20091122170750.GB13491@morn.localdomain>

On Sun, Nov 22, 2009 at 12:07:50PM -0500, Kevin O'Connor wrote:
> On Sun, Nov 22, 2009 at 04:08:53PM +0200, Gleb Natapov wrote:
> > Microsoft SVVP (Server Virtualization Validation Program) expects
> > arbitrary SMBIOS field to have certain values otherwise it fails.
> > We all want to make Microsoft happy don't we? So lets put values MS
> > expects in there.
> [...]
> > -    load_str_field_or_skip(1, manufacturer_str);
> > -    load_str_field_or_skip(1, product_name_str);
> > +    load_str_field_with_default(1, manufacturer_str, "QEMU");
> > +    load_str_field_with_default(1, product_name_str, "QEMU");
> >      load_str_field_or_skip(1, version_str);
> >      load_str_field_or_skip(1, serial_number_str);
> 
> Can the CONFIG_APPNAMExx defines in config.h be used instead of hard
> coding QEMU?  (If desired, the defaults can be changed from bochs to
> qemu.)
Qemu can do it in a local branch. But since Qemu uses SeaBIOS right now and
BOCHS doesn't lets change it.

> 
> > -    memcpy((char *)start, "CPU  " "\0" "" "\0" "", 7);
> > -	((char *)start)[4] = cpu_number + '0';
> > +    memcpy((char *)start, "CPU  \0QEMU\0\0", 12);
> > +    ((char *)start)[4] = cpu_number + '0';
> 
> BTW, snprintf can now be used here.
> 
snprintf in SeaBIOS doesn't have return value. In some situation it is
impossible to use it properly without it.


--
			Gleb.

  reply	other threads:[~2009-11-23 11:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 14:08 [Qemu-devel] [PATCH][SEABIOS] Make SMBIOS table pass MS SVVP test Gleb Natapov
2009-11-22 16:51 ` [Qemu-devel] " Sebastian Herbszt
2009-11-22 17:21   ` Gleb Natapov
2009-11-22 17:39     ` Sebastian Herbszt
2009-11-22 19:51       ` Gleb Natapov
2009-11-22 20:41         ` Sebastian Herbszt
2009-11-23  7:28           ` Gleb Natapov
2009-11-23 18:15             ` Sebastian Herbszt
2009-11-23 18:30               ` Gleb Natapov
2009-11-23 18:48                 ` Sebastian Herbszt
2009-11-23 19:39                   ` Gleb Natapov
2009-11-24  8:18                     ` Gleb Natapov
2009-11-24 15:57                 ` Kevin O'Connor
2009-11-24 16:59                   ` Gleb Natapov
2009-11-24 17:53                     ` Kevin O'Connor
2009-11-24 18:41                       ` Gleb Natapov
2009-11-24 20:30                         ` Kevin O'Connor
2009-11-25 20:09                     ` Sebastian Herbszt
2009-11-26  7:39                       ` Gleb Natapov
2009-11-26 21:38                         ` Sebastian Herbszt
2009-11-22 19:58       ` Yaniv Kaul
2009-11-22 23:57       ` Carl-Daniel Hailfinger
2009-11-23  6:28         ` Gleb Natapov
2009-11-23 18:02           ` Sebastian Herbszt
2009-11-23 11:56       ` Gleb Natapov
2009-11-22 17:07 ` Kevin O'Connor
2009-11-23 11:08   ` Gleb Natapov [this message]
2009-11-24 14:40     ` Kevin O'Connor

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=20091123110830.GE2999@redhat.com \
    --to=gleb@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=qemu-devel@nongnu.org \
    /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.