qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] Remove hardcoded xen-platform device initialization
Date: Fri, 14 Jun 2013 09:52:36 -0400	[thread overview]
Message-ID: <51BB2024.5030204@redhat.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0039278@LONPEX01CL01.citrite.net>

Il 14/06/2013 04:50, Paul Durrant ha scritto:
>> > This patch is problematic because we can't know for sure the version of
>> > upstream QEMU that is going to be used with Xen.
>> > If we apply this patch and QEMU 1.5 is going to be used with Xen 4.2,
>> > guests won't be able to use PV drivers.
>> > 
> Is there not a compatibility matrix? The hardcoded init. is just blatantly the wrong thing to be doing and it needs to go.
> 
> Could my accompanying toolstack patch not be backported to the next 4.2 release as mitigation?

I think Ian is right.  You should revert the toolstack patch and not
apply this one for now.  Then aim at using "-M pc" in 4.4 (and require
1.6 or 1.7), so that there is no need for a compatibility matrix.

Paolo

  reply	other threads:[~2013-06-14 13:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  9:50 [Qemu-devel] [PATCH] Remove hardcoded xen-platform device initialization Paul Durrant
2013-06-13 17:33 ` Stefano Stabellini
2013-06-13 17:44   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2013-06-13 18:02     ` Paolo Bonzini
2013-06-14  9:00       ` Paul Durrant
2013-06-14 10:38         ` Paul Durrant
2013-06-14 13:50           ` Paolo Bonzini
2013-06-14 14:11             ` Paul Durrant
2013-06-14 14:57               ` Paolo Bonzini
2013-06-14 15:10                 ` Paul Durrant
2013-06-18 18:56                   ` Stefano Stabellini
2013-06-18 19:12                     ` Paolo Bonzini
2013-06-18 19:35                       ` Stefano Stabellini
2013-06-18 21:38                         ` Andreas Färber
2013-06-19  8:29                           ` Ian Campbell
2013-06-19  8:37                             ` Paul Durrant
2013-06-19  8:41                             ` Paolo Bonzini
2013-06-19  8:56                               ` Ian Campbell
2013-06-19  9:11                                 ` Paul Durrant
2013-06-19 12:51                                 ` Paolo Bonzini
2013-06-19 13:47                                 ` Stefano Stabellini
2013-06-19  8:27                         ` Paul Durrant
2013-06-19 13:55                           ` Stefano Stabellini
2013-06-19 15:09                             ` Ian Campbell
2013-06-19  8:11                     ` Ian Campbell
2013-06-19 13:53                       ` Stefano Stabellini
2013-06-19 14:00                         ` Paul Durrant
2013-06-19 16:27                           ` Stefano Stabellini
2013-06-20  7:32                             ` Paul Durrant
2013-06-14  8:56     ` Paul Durrant
2013-06-14  8:50   ` [Qemu-devel] " Paul Durrant
2013-06-14 13:52     ` Paolo Bonzini [this message]
2013-06-14 13:57       ` Paul Durrant

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=51BB2024.5030204@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xen.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 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).