All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Xen-devel <xen-devel@lists.xensource.com>, xen-users@lists.xensource.com
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Xen/paravirt_ops page on Xen wiki
Date: Fri, 30 May 2008 12:10:51 +0100	[thread overview]
Message-ID: <483FE0BB.4080300@goop.org> (raw)

I've added a Xen/paravirt_ops page to the Xen wiki.  This is intended to 
let people know the current status, give them a guide on how to use the 
Xen support in current Linux kernels, and (ideally) start contributing 
to its ongoing development, with testing, debugging and patches.

http://wiki.xensource.com/xenwiki/XenParavirtOps

Thanks,
    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Xen-devel <xen-devel@lists.xensource.com>, xen-users@lists.xensource.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Xen/paravirt_ops page on Xen wiki
Date: Fri, 30 May 2008 12:10:51 +0100	[thread overview]
Message-ID: <483FE0BB.4080300@goop.org> (raw)

I've added a Xen/paravirt_ops page to the Xen wiki.  This is intended to 
let people know the current status, give them a guide on how to use the 
Xen support in current Linux kernels, and (ideally) start contributing 
to its ongoing development, with testing, debugging and patches.

http://wiki.xensource.com/xenwiki/XenParavirtOps

Thanks,
    J

             reply	other threads:[~2008-05-30 11:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 11:10 Jeremy Fitzhardinge [this message]
2008-05-30 11:10 ` Xen/paravirt_ops page on Xen wiki 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=483FE0BB.4080300@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.