All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander Eikelenboom <linux@eikelenboom.it>
To: Keir Fraser <keir@xen.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	xen-devel@lists.xensource.com
Subject: Re: Linux kernel summit 2010 topic: "Xen, in or out" (Greg KH)
Date: Tue, 19 Oct 2010 12:23:30 +0200	[thread overview]
Message-ID: <104334708.20101019122330@eikelenboom.it> (raw)
In-Reply-To: <C8E32CF9.26467%keir@xen.org>

Tuesday, October 19, 2010, 12:09:45 PM, you wrote:

> On 19/10/2010 10:19, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:

>>> Iirc Konrad wrote he's going there..
>>> Sounds like some Xen people definitely should be there :)
>> 
>>> -- Pasi
>> 
>> 
>> Perhaps someone more into the hypervisor side of things (Keir?) could be wise
>> too ?

> Attendance at the kernel summit is by invitation only.

Ahh i see that complicates it a bit :-)
Although an email to Greg KH if there could be any need from responses from within Xen on the points discussed could lead to something ?
On the other hand perhaps the kernel folks should first agree on what they think ...

I don't know if Jeremy goes ? He seems to be on the "potential invitation list".


>  -- Keir

>> I could imagine a discussion could go to how much Xen hypervisor wise has
>> to/could change to make the kernel changes more clean and less intrusive, as
>> that seems to be the old discussion that keeps popping up from time to time.
>> It also seems people are hesitant to get the patches in mainline because there
>> doesn't seems to be much of an outline of what will come after the first
>> perhaps less intrusive patches and fear there could be some crap later that is
>> less easy to refuse since a part is allready in.
>> Any willingness and vision on that part could reduce the hesitation to include
>> Xen patches in mainline i think.
>> 
>> --
>> 
>> Sander
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel





-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it

  reply	other threads:[~2010-10-19 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19  2:43 Linux kernel summit 2010 topic: "Xen, in or out" (Greg KH) Dan Magenheimer
2010-10-19  8:13 ` Pasi Kärkkäinen
2010-10-19  9:19   ` Sander Eikelenboom
2010-10-19 10:09     ` Keir Fraser
2010-10-19 10:23       ` Sander Eikelenboom [this message]
2010-10-19 15:26   ` Konrad Rzeszutek Wilk
2010-10-20 16:59 ` Jeremy Fitzhardinge

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=104334708.20101019122330@eikelenboom.it \
    --to=linux@eikelenboom.it \
    --cc=dan.magenheimer@oracle.com \
    --cc=keir@xen.org \
    --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.