All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: gregkh@suse.de, jeremy@goop.org, davem@davemloft.net,
	jaswinder@kernel.org
Subject: Re: Xen is a feature
Date: Fri, 29 May 2009 13:48:59 +0200	[thread overview]
Message-ID: <4A1FCBAB.2030100@wpkg.org> (raw)

Greg KH wrote:

> On Thu, May 28, 2009 at 05:45:34PM -0700, Jeremy Fitzhardinge wrote:
>> Mozilla and Debian are hosted on Xen systems.
> 
> A tiny data point about these domains.  They are hosted by osuosl.org,
> which uses xen systems running with the current dom0 patch set.  Because
> those patches are out-of-tree, they have a hard time updating kernel
> versions, and generally lag kernel.org releases by a lot, which is not
> always a good thing.
> 
> So getting the dom0 patches into mainline will make their lives much
> easier, and more secure.

I know at least a couple of mid-sized hosting companies migrating all or 
part of their infrastructure off Linux/Xen to a proprietary solution, 
because of this very reason (problems with keeping dom0 kernel up to 
date, problems with deploying it on new machines etc.).

-- 
Tomasz Chmielewski
http://wpkg.org


             reply	other threads:[~2009-05-29 11:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 11:48 Tomasz Chmielewski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-02 22:44 Xen is a feature Sander Eikelenboom
2009-05-31 21:11 devzero
2009-05-29 13:08 Sander Eikelenboom
2009-05-26 18:26 [Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops) Avi Kivity
2009-05-26 19:18 ` Dan Magenheimer
2009-05-28  0:13   ` Ingo Molnar
2009-05-29  0:45     ` Xen is a feature Jeremy Fitzhardinge
2009-05-29  1:27       ` Greg KH
2009-05-29  4:05       ` David Miller
2009-05-29  6:37         ` Jaswinder Singh Rajput
2009-05-29  6:51           ` David Miller
2009-05-29 12:01         ` George Dunlap
2009-05-29 14:14           ` Pasi Kärkkäinen
2009-05-29 21:29             ` David Miller
2009-06-02 15:23           ` Thomas Gleixner
2009-06-02 16:41             ` George Dunlap
2009-06-02 17:28               ` Chris Friesen
2009-06-02 17:46               ` Linus Torvalds
2009-06-02 18:02                 ` Linus Torvalds
2009-06-02 18:59                   ` Avi Kivity
2009-06-07  9:13                     ` Ingo Molnar
2009-06-07 10:01                       ` Avi Kivity
2009-06-07 10:35                         ` Ingo Molnar
2009-06-07 12:46                           ` Avi Kivity
2009-06-07 13:02                             ` Jaswinder Singh Rajput
2009-06-02 18:59               ` Thomas Gleixner
2009-06-03 19:49             ` Bill Davidsen
2009-06-03 20:20               ` Thomas Gleixner
2009-06-03 22:37                 ` Bill Davidsen
2009-06-03 23:29                   ` Frans Pop
2009-06-04 13:21                     ` George Dunlap
2009-06-04 15:10                       ` Theodore Tso
2009-06-04 15:31                       ` Chris Friesen
2009-06-05  4:14                     ` Bill Davidsen
2009-06-05  4:55                       ` Chris Friesen
2009-06-02 22:40           ` Steven Rostedt
2009-06-02 23:41             ` Thomas Gleixner

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=4A1FCBAB.2030100@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=jaswinder@kernel.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.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.