qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Lalancette <clalance@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option
Date: Tue, 29 Jul 2008 22:50:48 +0300	[thread overview]
Message-ID: <20080729195048.GC11061@minantech.com> (raw)
In-Reply-To: <488F6E0E.2070504@codemonkey.ws>

On Tue, Jul 29, 2008 at 02:22:54PM -0500, Anthony Liguori wrote:
> Gleb Natapov wrote:
>> On Mon, Jul 28, 2008 at 09:37:01AM -0500, Anthony Liguori wrote:
>>   
>>> The backdoor interface is deprecated (from a VMware perspective) and 
>>> is  pretty terrible.  I'll go through and do a more thorough review 
>>> of the  patches Chris posted but one thing I already know I'd like to 
>>> see the      
>> Review my last submission I linked above then too.
>>   
>
> Applying the -uuid support without making use of that uuid anywhere  
> isn't very useful.
>
You can read it from monitor, so management software can benefit from
it. And this will reduce my patch backlog :)

>>> UUID plumbed through the SMBIOS tables for x86.  That's a requirement 
>>> in  my mind for adding a -uuid option.  I see no harm in also 
>>> supporting the  backdoor interface but the primary way to expose a 
>>> UUID should be SMBIOS.
>>>     
>> I am not sure I understand what you mean. Currently SMBIOS tables are
>> built by bochs bios and UUID backdoor is needed to fill in missing info.
>>   
>
> But that patch that got pushed into the Bochs BIOS was wrong.
>
> So here's what I'd like to see in order to apply these patches:
>
> 1) A new patch to the Bochs BIOS that used CMOS to pass a UUID (or  
> possibly an OF data structure as Blue Swirl suggested--although CMOS is  
> safer).
We will run out of space in CMOS quickly if we will use it as qemu->bios
communication channel. Is passing pointer to memory location (Blue Swirl
suggestion) acceptable solution by everyone?

--
			Gleb.

  reply	other threads:[~2008-07-29 19:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 13:25 [Qemu-devel] [PATCH 0/3]: Add UUID command-line option Chris Lalancette
2008-07-28 14:15 ` [Qemu-devel] " Gleb Natapov
2008-07-28 14:37   ` Anthony Liguori
2008-07-28 14:41     ` Chris Lalancette
2008-07-28 15:02       ` Anthony Liguori
2008-07-28 15:09         ` Chris Lalancette
2008-07-28 15:12           ` Anthony Liguori
2008-07-28 15:42             ` Chris Lalancette
2008-07-28 16:02               ` Gleb Natapov
2008-07-28 16:17                 ` Anthony Liguori
2008-07-28 16:27                   ` Gleb Natapov
2008-07-28 17:41                     ` Blue Swirl
2008-07-28 16:28                   ` Jamie Lokier
2008-07-28 19:02                     ` Anthony Liguori
2008-07-28 20:00                       ` Jamie Lokier
2008-07-28 20:25                         ` Anthony Liguori
2008-07-28 20:40                           ` Paul Brook
2008-07-28 20:55                             ` Anthony Liguori
2008-07-29  6:31                           ` Gleb Natapov
2008-07-28 15:48             ` Jamie Lokier
2008-07-31 19:45               ` [Qemu-devel] " Sebastian Herbszt
2008-07-28 15:49             ` [Qemu-devel] " Jamie Lokier
2008-07-28 16:06               ` Anthony Liguori
2008-07-28 15:35     ` Gleb Natapov
2008-07-29 19:22       ` Anthony Liguori
2008-07-29 19:50         ` Gleb Natapov [this message]
2008-07-30 17:32           ` Blue Swirl
2008-08-05 14:33             ` Gleb Natapov
2008-08-06  2:35               ` Anthony Liguori
2008-08-06 16:26                 ` Blue Swirl
2008-08-06 16:33                   ` Anthony Liguori
2008-08-06 22:07                     ` [Qemu-devel] " Sebastian Herbszt
2008-08-06 22:11                       ` [Qemu-devel] " Anthony Liguori
2008-07-29  8:15     ` Daniel P. Berrange
2008-07-29  8:42       ` Chris Lalancette
2008-07-28 15:51   ` Jamie Lokier

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=20080729195048.GC11061@minantech.com \
    --to=gleb@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --cc=clalance@redhat.com \
    --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 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).