All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Kevin O'Connor <kevin@koconnor.net>, beth kon <eak@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] PC machine types switched to SeaBIOS/gPXE
Date: Tue, 03 Nov 2009 07:01:52 +0200	[thread overview]
Message-ID: <4AEFB940.1020201@redhat.com> (raw)
In-Reply-To: <6C88F564-1E98-4F82-90F8-99F390927042@suse.de>

On 11/03/2009 06:57 AM, Alexander Graf wrote:
>> Yes, I'd prefer to see this.  In earlier emails, Gleb made a reference
>> to a qemu-cfg "stream" interface that is used for acpi tables - maybe
>> the kernel could be put in one of the streams and the rom could copy
>> it into ram on boot.
>
>
> I don't think streaming is the right approach here. Streaming would 
> mean the rom had to copy, which again either a lot of PIO accesses 
> (slow!) or a complicated DMA interface.

A rep/ins instruction will take one exit/page so it won't be 
particularly slow.

> I'd rather go for a RAM poking approach. As soon as the option rom is 
> loaded, it calls qemu via PIO telling it to "load the kernel in RAM 
> now" and as of the next instruction everything's in place at the 
> determined addresses. It's not like we could do anything about the 
> physical layout in the option rom anyways, usually the kernel tells us 
> what that looks like.

That works too, but if firmware config can use rep/ins, that's one less 
interface we have to add.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2009-11-03  5:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 14:54 [Qemu-devel] PC machine types switched to SeaBIOS/gPXE Anthony Liguori
2009-10-30 19:37 ` [Qemu-devel] " Jan Kiszka
2009-10-30 19:45   ` Anthony Liguori
2009-10-31 12:42     ` Stefan Weil
2009-10-31 13:10       ` Jan Kiszka
2009-11-02 23:09         ` Beth Kon
2009-11-02 23:22           ` Anthony Liguori
2009-11-03  4:16             ` Kevin O'Connor
2009-11-03 14:11               ` Beth Kon
2009-11-04  1:38                 ` Kevin O'Connor
2009-11-04  1:55                   ` Anthony Liguori
2009-10-31 11:07 ` [Qemu-devel] " Stefan Weil
2009-10-31 12:02   ` [Qemu-devel] " Jan Kiszka
2009-11-02 12:51 ` [Qemu-devel] " Alexander Graf
2009-11-02 13:08   ` Avi Kivity
2009-11-02 13:15     ` Alexander Graf
2009-11-02 13:32       ` Avi Kivity
2009-11-02 13:51         ` Kevin O'Connor
2009-11-02 13:56           ` Avi Kivity
2009-11-02 14:06             ` Alexander Graf
2009-11-02 14:39               ` Avi Kivity
2009-11-09 18:41               ` Glauber Costa
2009-11-10 13:02                 ` Avi Kivity
2009-11-10 13:03                   ` Alexander Graf
2009-11-10 13:07                     ` Avi Kivity
2009-11-10 13:09                       ` Alexander Graf
2009-11-03  4:50             ` Kevin O'Connor
2009-11-03  4:57               ` Alexander Graf
2009-11-03  5:01                 ` Avi Kivity [this message]
2009-11-03  6:02                   ` Kevin O'Connor
2009-11-03  6:08                     ` Avi Kivity
2009-11-03 13:42                       ` Kevin O'Connor
2009-11-03  4:58               ` Avi Kivity
2009-11-02 14:51   ` Gleb Natapov
2009-11-02 14:54     ` Gleb Natapov

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=4AEFB940.1020201@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=eak@us.ibm.com \
    --cc=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.