xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Matt Wilson <msw@linux.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>, Matt Wilson <msw@amazon.com>
Subject: Re: [GIT PULL] remove xend for 4.5 (Was: Re: [PATCH] MAINTAINERS: Exclude xend from toolstack maintainers entry)
Date: Mon, 31 Mar 2014 14:17:32 +0100	[thread overview]
Message-ID: <53396AEC.5010705@eu.citrix.com> (raw)
In-Reply-To: <20140331121657.GB24351@u109add4315675089e695.ant.amazon.com>

On 03/31/2014 01:16 PM, Matt Wilson wrote:
> On Mon, Mar 31, 2014 at 01:03:25PM +0100, George Dunlap wrote:
>> On 03/31/2014 12:56 PM, Matt Wilson wrote:
>>> On Mon, Mar 31, 2014 at 12:18:53PM +0100, Ian Campbell wrote:
>>>> On Fri, 2014-03-28 at 13:09 -0400, Konrad Rzeszutek Wilk wrote:
>>> [...]
>>>
>>>>> I don't really like adding more of 'xend has this' to the list,
>>>> that's ok.
>>>>
>>>>> but
>>>>> Jan discovered that 'xend' was using the group assigment hypercall for
>>>>> PCI devices while 'xl' is not doing that.
>>>>> That hypercall has certain benefits - you can use it to figure out if
>>>>> all of the PCI devices underneath a bridge are assigned to one
>>>>> guest and not shared amongts the guests.
>>>> I think this is at the wishlist rather than blocker end of the spectrum,
>>>> and probably falls under the general category of "xl pci passthrough has
>>>> sharp edges"? Does that sound right?
>>> Probably. There are other areas that are mightily sharp as well. They
>>> might not be blockers for the project to remove Xend code from the
>>> tree, but they'll be blockers for adoption of newer releases that
>>> don't include Xend.
>>>
>>> Another for the list is AER handling. That's only implemented in Xend
>>> now [1].
>> Well, given that AER was not mentioned 6 months ago when this came
>> up, it seems that keeping xend in tree is a blocker for people
>> actually asking for things to be added to xl.
> Actually, we discussed it on the phone [1]. Unfortunately I didn't
> complete my assigned action item to post on the list.

Ah, right. :-)

In any case, the relevant question isn't so much "Is this a blocker for 
xend removal", so much as "Is xl support for this a blocker for the 4.5 
release?"

  -George

  reply	other threads:[~2014-03-31 13:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 13:20 [PATCH] MAINTAINERS: Exclude xend from toolstack maintainers entry Ian Campbell
2014-03-20 13:32 ` Jan Beulich
2014-03-20 14:02   ` Ian Campbell
2014-03-27 11:00     ` [GIT PULL] remove xend for 4.5 (Was: Re: [PATCH] MAINTAINERS: Exclude xend from toolstack maintainers entry) Ian Campbell
2014-03-27 11:08       ` George Dunlap
2014-03-27 11:18         ` Ian Campbell
2014-03-27 12:03           ` George Dunlap
2014-03-27 12:12             ` Ian Campbell
2014-03-27 12:15               ` George Dunlap
2014-03-27 12:23                 ` Ian Campbell
2014-03-27 12:01         ` Olaf Hering
2014-03-27 12:13           ` George Dunlap
2014-03-27 12:14           ` Ian Campbell
2014-03-27 12:31             ` Olaf Hering
2014-03-28 17:09         ` Konrad Rzeszutek Wilk
2014-03-31 11:18           ` Ian Campbell
2014-03-31 11:56             ` Matt Wilson
2014-03-31 12:03               ` George Dunlap
2014-03-31 12:16                 ` Matt Wilson
2014-03-31 13:17                   ` George Dunlap [this message]
2014-03-31 14:05                     ` Fabio Fantoni
2014-03-31 14:08                       ` George Dunlap
2014-03-31 14:52                         ` Sander Eikelenboom
2014-03-31 15:07             ` Konrad Rzeszutek Wilk
2014-03-31 13:13           ` George Dunlap
2014-03-31 15:06             ` Konrad Rzeszutek Wilk
2014-03-20 13:32 ` [PATCH] MAINTAINERS: Exclude xend from toolstack maintainers entry Ian Jackson
2014-03-20 14:04   ` Ian Campbell

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=53396AEC.5010705@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=msw@amazon.com \
    --cc=msw@linux.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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).