All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: Gleb Natapov <gleb@qumranet.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option
Date: Wed, 06 Aug 2008 17:11:05 -0500	[thread overview]
Message-ID: <489A2179.4050506@codemonkey.ws> (raw)
In-Reply-To: <02db01c8f810$f05979a0$0201a8c0@zeug>

Sebastian Herbszt wrote:
> Anthony Liguori wrote:
>>>>  I like having a configuration blob but am uncomfortable with 
>>>> stashing it in
>>>> memory somewhere.  I would think maybe stealing a few IO ports and 
>>>> using
>>>> that to read the rom may be nicer (albeit slower).  I think it's 
>>>> something
>>>> that needs to be implemented fully to work out the kinks.
>>>>     
>>>
>>> Ok, I made a new version that uses IO ports. But then you have to
>>> select a port instead of address, is that any better?
>>>   
>>
>> A lot of the BIOS code is 16-bit and accessing high memory location 
>> from 16-bit code is a royal pain.  That is simplified with using IO 
>> ports.
>
> Could put it in the 0xe000 segment, e.g. 4kb below rombios16.bin at 
> 0xf000.

Which limits the size to 4kb.  If we use the IO port patch that Blue 
Swirl proposed, we have 64kb of space with a pretty reasonable expansion 
mechanism.

Regards,

Anthony Liguori

> - Sebastian
>

  reply	other threads:[~2008-08-06 22:11 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
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                       ` Anthony Liguori [this message]
2008-07-29  8:15     ` [Qemu-devel] " 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=489A2179.4050506@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=gleb@qumranet.com \
    --cc=herbszt@gmx.de \
    --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.