All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	marcel.a@redhat.com, qemu-devel@nongnu.org,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-1.6] pc: fix up pc initialization
Date: Tue, 13 Aug 2013 18:18:18 +0300	[thread overview]
Message-ID: <20130813151817.GA2373@redhat.com> (raw)
In-Reply-To: <520A4C8C.7090202@suse.de>

On Tue, Aug 13, 2013 at 05:11:08PM +0200, Andreas Färber wrote:
> Am 13.08.2013 16:54, schrieb Paolo Bonzini:
> > Il 13/08/2013 16:11, Anthony Liguori ha scritto:
> >>>> Fix this up, clean up a trivial code duplication
> >>>> and add a comment explaining why we special-case 1.5
> >>>> with respect to pvpanic.
> >>>>
> >>>> Reported-by: Markus Armbruster <armbru@redhat.com>
> >>>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> >> Thanks for catching this.  I'm a little disturbed by this.  I use git-am
> >> --3way specifically to avoid problems from fuzzing but I guess merge
> >> artifacts are possible.
> >>
> > 
> > I wonder if we shouldn't disable pvpanic in 1.5 too, one-off behavior is
> > ugly and likely no one will notice.
> 
> I had rejected the previous attempt to completely disable pvpanic device
> because it looked to me as if this compatibility aspect had been
> forgotten. I didn't imagine the resulting code to look as ugly though,
> with us "skipping" _1_5 to not have 1.5 overwrite has_pvpanic for 1.6+.
> 
> mst suggested to patch stable-1.5 to disable it there, too. I am not
> against but have doubts as to how well that works with migration, since
> 1.5.3 is still a bit off and I would expect 1.5.2 -> 1.6.0 migration to
> work without guest-visible changes... We could argue that having to use
> -M pc-i440fx-1.5 we can also expect users to add -device pvpanic;
> question would be how to convey that knowledge of
> if-you-use-pc-x.y-then-you-also-need-to-do-Z to users, which
> compat_props usually handle under the hood. We could misuse
> pvpanic.ioport=0 for that purpose until we have a better solution.
> 
> Regards,
> Andreas

Well, in this case then this boils down to 1.5.2 migration being buggy -
having a small race (migration during reset) which we can then close
with 1.5.3 .
I don't think anyone ever triggered this race in practice so I'm not
sure whether we should be too worried about this.


> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-08-13 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 12:53 [Qemu-devel] [PATCH for-1.6] pc: fix up pc initialization Michael S. Tsirkin
2013-08-13 13:28 ` Eric Blake
2013-08-13 14:11 ` Anthony Liguori
2013-08-13 14:54   ` Paolo Bonzini
2013-08-13 15:11     ` Andreas Färber
2013-08-13 15:18       ` Michael S. Tsirkin [this message]
2013-08-13 15:27       ` Paolo Bonzini
2013-08-13 15:57         ` Andreas Färber
2013-08-13 16:12           ` Anthony Liguori
2013-08-18 14:46           ` Paolo Bonzini

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=20130813151817.GA2373@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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.