Linux virtualization list
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Juan Quintela <quintela@redhat.com>,
	Stephen Tweedie <sct@redhat.com>,
	Chris Wright <chrisw@sous-sol.org>,
	"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>
Subject: Updated dom0 for pvops: now boots on 32-bit!
Date: Fri, 01 Feb 2008 21:02:42 +0000	[thread overview]
Message-ID: <1201899762.11365.10.camel@sisko.scot.redhat.com> (raw)

Hi folks,

I've finished off Xen dma support for pv_ops, and dom0 now boots!  

I've had an uptime of 40 minutes so far with it.  Under intensive disk
load it locks up with a soft lockup, but still, this is good progress.  

I've pushed the current bits to the "WIP" (work-in-progress) branch at
the usual git repo,

	git://et.redhat.com/linux-2.6-dom0-pvops.git

with gitweb at 

	http://git.et.redhat.com/?p=linux-2.6-dom0-pvops.git 

New since the last drop are some MTRR cleanups from Mark McLoughlin, a
number of dma-mapping cleanups, and full dma_alloc/free_coherent
support, including xen contiguous mapping support.  I've also updated it
to Linus' final v2.6.24.

The APIC code is still non-pvops-friendly, but other than that, all the
new code is completely pvops-friendly and will work happily on baremetal
as well as Xen.  So next job is to clean up the xen contiguous-region
support (split it up, update the calls to use cleaner, pvops
virt/mfn/pfn macros, and use Jeremy's per-cpu pvops multicall batching),
and to redo much of the APIC code to work properly with pvops.

But in its current state it's useful enough for testing that I've pushed
it as it stands.

NOTE: this current code has not actually been tagged and rebased, it's
not exactly a "release" as much as a snapshot of the development work
--- I'll do a rebase and patchqueue release of it once I've done the
contig region cleanups.  I've also got paravirt framebuffer patches from
Markus Armbruster to integrate for that.

--Stephen

             reply	other threads:[~2008-02-01 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 21:02 Stephen C. Tweedie [this message]
2008-02-02  0:02 ` Updated dom0 for pvops: now boots on 32-bit! Jeremy Fitzhardinge
2008-02-05 16:17   ` Stephen C. Tweedie

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=1201899762.11365.10.camel@sisko.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@goop.org \
    --cc=markmc@redhat.com \
    --cc=quintela@redhat.com \
    --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