All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com,
	Stefano.Stabellini@eu.citrix.com, wei.lui2@citrix.com,
	qemu-devel@nongnu.org, Fabio Fantoni <fabio.fantoni@m2r.biz>,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu
Date: Thu, 18 Jul 2013 12:13:59 +0100	[thread overview]
Message-ID: <51E7CDF7.60000@eu.citrix.com> (raw)
In-Reply-To: <20967.52442.308010.563288@mariner.uk.xensource.com>

On 18/07/13 12:09, Ian Jackson wrote:
> Fabio Fantoni writes ("Re: [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu"):
>> Il 12/07/2013 17:33, George Dunlap ha scritto:
>>> On 12/07/13 13:36, Fabio Fantoni wrote:
> [someone wrote:]
>>>>> I'm just curious, why is this so complicated?  Is this likely to be
>>>>> fragile and break in the future?
> ...
>>>> I tried already but there are problems with retrocompatibility:
>>>> http://lists.xen.org/archives/html/xen-devel/2013-07/msg00491.html
>>>> I was also asking if it is possible to remove some hardcoded options
>>>> without breaking something but I had no reply.
>>> So this seems to be a response to the first paragraph ("why is this so
>>> complicated, is it fragile").
> I'm afraid that I don't think it's really a sufficient response to
> "why is this so complicated, is it fragile?".  "I don't know" is not
> very convincing :-).
>
> My worry would be that these options would change their meaning in the
> future, or indeed that the whole edifice which requires callers to
> specify things at this excruciating level of detail might (sensibly!)
> be abolished.

So far qemu has been pretty good about supporting deprecated 
command-line arguments; e.g., libxl still passes outdated usb parameters 
to qemu-xen.

  -George

WARNING: multiple messages have this Message-ID (diff)
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com,
	Stefano.Stabellini@eu.citrix.com, wei.lui2@citrix.com,
	qemu-devel@nongnu.org, Fabio Fantoni <fabio.fantoni@m2r.biz>,
	pbonzini@redhat.com
Subject: Re: [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu
Date: Thu, 18 Jul 2013 12:13:59 +0100	[thread overview]
Message-ID: <51E7CDF7.60000@eu.citrix.com> (raw)
In-Reply-To: <20967.52442.308010.563288@mariner.uk.xensource.com>

On 18/07/13 12:09, Ian Jackson wrote:
> Fabio Fantoni writes ("Re: [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu"):
>> Il 12/07/2013 17:33, George Dunlap ha scritto:
>>> On 12/07/13 13:36, Fabio Fantoni wrote:
> [someone wrote:]
>>>>> I'm just curious, why is this so complicated?  Is this likely to be
>>>>> fragile and break in the future?
> ...
>>>> I tried already but there are problems with retrocompatibility:
>>>> http://lists.xen.org/archives/html/xen-devel/2013-07/msg00491.html
>>>> I was also asking if it is possible to remove some hardcoded options
>>>> without breaking something but I had no reply.
>>> So this seems to be a response to the first paragraph ("why is this so
>>> complicated, is it fragile").
> I'm afraid that I don't think it's really a sufficient response to
> "why is this so complicated, is it fragile?".  "I don't know" is not
> very convincing :-).
>
> My worry would be that these options would change their meaning in the
> future, or indeed that the whole edifice which requires callers to
> specify things at this excruciating level of detail might (sensibly!)
> be abolished.

So far qemu has been pretty good about supporting deprecated 
command-line arguments; e.g., libxl still passes outdated usb parameters 
to qemu-xen.

  -George

  reply	other threads:[~2013-07-18 11:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 10:22 [Qemu-devel] [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu Fabio Fantoni
2013-07-12 10:22 ` Fabio Fantoni
2013-07-12 11:06 ` [Qemu-devel] " George Dunlap
2013-07-12 11:06   ` George Dunlap
2013-07-12 11:15   ` [Qemu-devel] " Ian Campbell
2013-07-12 11:15     ` Ian Campbell
2013-07-12 12:36   ` [Qemu-devel] " Fabio Fantoni
2013-07-12 12:36     ` Fabio Fantoni
2013-07-12 15:33     ` [Qemu-devel] " George Dunlap
2013-07-12 15:33       ` George Dunlap
2013-07-15  9:10       ` [Qemu-devel] " Fabio Fantoni
2013-07-15  9:10         ` Fabio Fantoni
2013-07-18 11:09         ` [Qemu-devel] " Ian Jackson
2013-07-18 11:09           ` Ian Jackson
2013-07-18 11:13           ` George Dunlap [this message]
2013-07-18 11:13             ` George Dunlap
2013-07-18 11:31           ` [Qemu-devel] " Anthony Liguori
2013-07-18 11:31             ` Anthony Liguori
2013-07-18 12:15             ` [Qemu-devel] " Ian Jackson
2013-07-18 12:15               ` Ian Jackson
2013-07-18 12:31   ` [Qemu-devel] " Andreas Färber
2013-07-18 12:31     ` Andreas Färber
2013-07-18 12:35     ` [Qemu-devel] " Paolo Bonzini
2013-07-18 12:35       ` Paolo Bonzini
2013-08-14 10:30       ` [Qemu-devel] " Fabio Fantoni
2013-08-14 10:30         ` Fabio Fantoni
2013-09-11 10:14         ` [Qemu-devel] " Fabio Fantoni
2013-09-11 10:14           ` Fabio Fantoni
2013-09-11 10:19           ` [Qemu-devel] " Ian Campbell
2013-09-11 10:19             ` Ian Campbell
2013-09-11 11:38             ` [Qemu-devel] " Fabio Fantoni
2013-09-11 11:38               ` Fabio Fantoni
2013-09-11 13:19               ` [Qemu-devel] " Fabio Fantoni
2013-09-11 13:19                 ` Fabio Fantoni

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=51E7CDF7.60000@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=fabio.fantoni@m2r.biz \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wei.lui2@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.