virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Xen-devel <xen-devel@lists.xensource.com>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Xen paravirt_ops tree for testing
Date: Wed, 21 Feb 2007 12:55:07 -0800	[thread overview]
Message-ID: <45DCB1AB.5050103@goop.org> (raw)

Hi all,

I'm hoping to get the Xen paravirt_ops implementation into the kernel
very soon.  I've been doing regular post/refine cycles, and I think its
now very close to something that will be accepted.  The principle
concern at this point is that there haven't been very many people
actually running the code.

So this is where you come in.  I'd appreciate it if people could grab
the patch queue from http://ozlabs.org/~rusty/paravirt/ - or from the
posting I'm about to make - and tell me if it works for you.

This is a limited Xen implementation for now, so bear in mind that it's:

    * domU only
    * UP only
    * netfront and blockfront only
    * not particularly performance tuned

But it should support both PAE and non-PAE.   Oh, and the console will
be hvc0, since its using the hvc console infrastructure rather than the
traditional xen-console.

Thanks,
    J

                 reply	other threads:[~2007-02-21 20:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45DCB1AB.5050103@goop.org \
    --to=jeremy@goop.org \
    --cc=virtualization@lists.osdl.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 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).