All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Corey Minyard <minyard@acm.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Sort the fw_cfg file list
Date: Wed, 16 Mar 2016 10:21:07 -0500	[thread overview]
Message-ID: <56E979E3.8080806@mvista.com> (raw)
In-Reply-To: <20160315185844-mutt-send-email-mst@redhat.com>

On 03/15/2016 12:01 PM, Michael S. Tsirkin wrote:
> On Tue, Mar 15, 2016 at 11:36:39AM -0500, Corey Minyard wrote:
>
>> I've hit a bit of a snag here.  For 0.11 and before, PCI option ROMs
>> were loaded via fw_cfg, not in the PCI ROM BAR.  This causes two
>> issues:
>>
>> * The order depends on the device initialization order,
>> which I'm not sure is quantifiable.  I believe it depends on
>> how they are listed on the command line.
>>
>> * Users can load their own romfile with their own name, which
>> means it can't be in the list.
>>
>> Also, for the ISA VGA ROMs, their order will also depend on the
>> device list order.
>>
>> Outside of that, I have an order of file names.
>>
>> I think if I treat the device ROMs separately and handle them
>> in init order, and then stick that device list in the proper location,
>> that will work.  Does that sound reasonable?
>>
>> Thanks,
>>
>> -corey
> I think so. By the time this becomes an issue we might decide to
> disable migration from 0.11
>

One more thing here.  I've realized that this is used for
non-x86, too, and I'm wondering how much those matter.
It's going to be really hard to figure out an order for these,
as different boards/arches use the same names and install
them in different orders.

For legacy mode, can I just put them in order for non-x86?
Is there an easy way to detect that you are running x86?

-corey

  reply	other threads:[~2016-03-16 15:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 16:55 [Qemu-devel] [PATCH v2] Sort the fw_cfg file list minyard
2016-03-15  6:57 ` Michael S. Tsirkin
2016-03-15  7:04   ` Gerd Hoffmann
2016-03-15  7:17     ` Michael S. Tsirkin
2016-03-15  7:34       ` Gerd Hoffmann
2016-03-15  7:45         ` Michael S. Tsirkin
2016-03-15  8:45           ` Gerd Hoffmann
2016-03-15  9:37             ` Michael S. Tsirkin
2016-03-15 12:38               ` Corey Minyard
2016-03-15 12:45                 ` Michael S. Tsirkin
2016-03-15 12:56                   ` Corey Minyard
2016-03-15 13:47                     ` Michael S. Tsirkin
2016-03-15 14:43                     ` Michael S. Tsirkin
2016-03-15 16:36                   ` Corey Minyard
2016-03-15 17:01                     ` Michael S. Tsirkin
2016-03-16 15:21                       ` Corey Minyard [this message]
2016-03-16 15:34                         ` Paolo Bonzini
2016-03-16 15:37                         ` Michael S. Tsirkin
2016-03-15 13:03               ` Gerd Hoffmann
2016-03-15 13:19                 ` Michael S. Tsirkin

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=56E979E3.8080806@mvista.com \
    --to=cminyard@mvista.com \
    --cc=kraxel@redhat.com \
    --cc=minyard@acm.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@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 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.