From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
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 11:07:27 -0400 [thread overview]
Message-ID: <20140331150727.GH3159@phenom.dumpdata.com> (raw)
In-Reply-To: <1396264733.8667.13.camel@kazak.uk.xensource.com>
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:
> > On Thu, Mar 27, 2014 at 11:08:47AM +0000, George Dunlap wrote:
> > > On Thu, Mar 27, 2014 at 11:00 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > > > On Thu, 2014-03-20 at 14:02 +0000, Ian Campbell wrote:
> > > >> On Thu, 2014-03-20 at 13:32 +0000, Jan Beulich wrote:
> > > >> > Which reminds me - didn't you want to rip out xend
> > > >> > right away after 4.4 (which would render pointless the patch
> > > >> > here)?
> > > >>
> > > >> I still want to do it before 4.5, this is more of a short term thing
> > > >> because people were sending me patches right now.
> > > >>
> > > >> Step one of the removal is to stop osstest from testing xend, I sent a
> > > >> patch for that a week or two ago.
> > > >
> > > > That patch is now in place in the production osstest. So I propose the
> > > > following pull request (since the actual patch is nearly 3M in size,
> > > > even the diffstat here is bigger than most patches!).
> > >
> > > On my list of dependencies for removing xend, I have the following:
> > >
> > > * xend still in tree (x)
> > > - xl list -l on a dom0-only system
> > > - xl list -l doesn't contain tty console port
> > > - xl Alternate transport support for migration*
> > > - xl PVSCSI support
> > > - xl PVUSB support
> > > - xl support for vnc and vnclisten options with PV guests
> >
> > 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?
Yes, they are hazardous to ones health.
>
> Ian.
>
next prev parent reply other threads:[~2014-03-31 15:07 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
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 [this message]
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=20140331150727.GH3159@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=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=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).