All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: XenParavirtOps wiki cleanup, comments needed
Date: Mon, 25 Jul 2011 17:04:39 -0400	[thread overview]
Message-ID: <20110725210438.GA22994@dumpdata.com> (raw)
In-Reply-To: <20110725202357.GN32373@reaktio.net>

On Mon, Jul 25, 2011 at 11:23:57PM +0300, Pasi Kärkkäinen wrote:
> Hello,
> 
> Jeremy/Konrad/others: What do you guys think of the stuff on XenParavirtOps page? 
> http://wiki.xen.org/xenwiki/XenParavirtOps
> 
> I was planning to clean it up, and remove things like this:
> 
> "Xen/paravirt_ops has not had wide use or testing, so any testing you do is extremely valuable."
> "Xen/paravirt_ops is very much a work in progress, and there are still feature gaps compared to 2.6.18-xen."

Yeah, we been quite busy testing and getting things ready.

Feature gaps .. well, there are some, I was thinking to list them on the
presentation I am doing on.

> 
> etc.. those don't sound like very up-to-date anymore :)
> 
> What about the notes like these:
> 	- "CPU hotplug" (I guess this is about vcpu hotplug?)

Done.
> 	- "Device hotplug"

There is the blkback bug that Joe Jin is going to fix.
> 	- "Device unplug/module unload"

Um, done with Bastian's Blank patches that do some MODULE_ALIAS magic.
> 
> What's the status of those so I can update the page.. ? 

I think done.

> 
> Thanks,
> 
> -- Pasi

  reply	other threads:[~2011-07-25 21:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 20:23 XenParavirtOps wiki cleanup, comments needed Pasi Kärkkäinen
2011-07-25 21:04 ` Konrad Rzeszutek Wilk [this message]
2011-07-26  8:40   ` Pasi Kärkkäinen
2011-07-25 21:12 ` Olivier B.
2011-07-27  8:54 ` Daniel Kiper
2011-07-27  9:03   ` Pasi Kärkkäinen
2011-07-28 13:10     ` Daniel Kiper
2011-07-29 17:31       ` Pasi Kärkkäinen

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=20110725210438.GA22994@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=jeremy@goop.org \
    --cc=pasik@iki.fi \
    --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.