qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Gabriel L. Somlo" <somlo@cmu.edu>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	lersek@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] fw cfg files cross-version migration races
Date: Mon, 8 Jun 2015 17:53:48 +0200	[thread overview]
Message-ID: <20150608175253-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150608133253.GC32650@HEDWIG.INI.CMU.EDU>

On Mon, Jun 08, 2015 at 09:32:53AM -0400, Gabriel L. Somlo wrote:
> On Mon, Jun 08, 2015 at 02:33:45PM +0200, Gerd Hoffmann wrote:
> >  Hi,
> > 
> > > I'm wonderingjust when exactly to start sorting items in fw_cfg ? 
> > 
> > I'd suggest to sort as entries are added, i.e. just insert the new entry
> > at the correct place instead of tacking it to the end.  So the list is
> > always sorted.
> 
> I was thinking that too, but since these are all arrays (not linked
> lists), I'm a bit put off by the idea of having to shift everything
> that's already in there by one position upon each "sorted insert".
> Not to mention updating the "select" field of each FWCfgFile entry in
> the directory (and maybe sorting/shifting the FWCfgFiles directory
> itself) :(
> 
> Combined with "only do this on machine versions 2.4 or later", maybe
> just sorting everything during the machine_ready callback would be
> less hairy ?

Unfortunately we have a bunch of code adding fw cfg entries
after machine ready.

> I'll be on vacation for one week, so meditating on this in the back
> of my mind might help come up with something... :)
> 
> Thanks,
> --Gabriel

      reply	other threads:[~2015-06-08 15:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 14:10 [Qemu-devel] fw cfg files cross-version migration races Michael S. Tsirkin
2015-06-01 14:13 ` Daniel P. Berrange
2015-06-01 15:32   ` Gabriel L. Somlo
2015-06-01 15:44     ` Michael S. Tsirkin
2015-06-01 18:00       ` Gabriel L. Somlo
2015-06-01 20:31         ` Gabriel L. Somlo
2015-06-02  7:04           ` Laszlo Ersek
2015-06-02  7:11           ` Gerd Hoffmann
2015-06-03  8:31             ` Paolo Bonzini
2015-06-03 16:03             ` Michael S. Tsirkin
2015-06-05 16:05             ` Gabriel L. Somlo
2015-06-08  7:21               ` Gerd Hoffmann
2015-06-08  9:43                 ` Michael S. Tsirkin
2015-06-08 11:19                   ` Gerd Hoffmann
2015-06-08 11:44                     ` Paolo Bonzini
2015-06-08 12:23                       ` Gabriel L. Somlo
2015-06-08 12:28                         ` Paolo Bonzini
2015-06-08 12:33                         ` Gerd Hoffmann
2015-06-08 13:32                           ` Gabriel L. Somlo
2015-06-08 15:53                             ` Michael S. Tsirkin [this message]

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=20150608175253-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=somlo@cmu.edu \
    /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).