All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	linux-kernel@vger.kernel.org,
	Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 00 of 11] xen: smattering of dom0 patches
Date: Thu, 18 Dec 2008 16:53:05 -0800	[thread overview]
Message-ID: <patchbomb.1229647985@abulafia.goop.org> (raw)

Hi Ingo,

Here are some more Xen dom0 patches.  Functionally the patches are all
over the place, and mostly touch pure Xen-only code.  The exception is
the mtrr change, and pv-op for page_is_ram().

Thanks,
    J

             reply	other threads:[~2008-12-19  0:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  0:53 Jeremy Fitzhardinge [this message]
2008-12-19  0:53 ` [PATCH 01 of 11] xen: short-circuit tests for dom0 Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 02 of 11] xen dom0: Make hvc_xen console work " Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 03 of 11] xen dom0: Initialize xenbus " Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 04 of 11] xen dom0: Set up basic IO permissions " Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 05 of 11] xen-dom0: only selectively disable cpu features Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 06 of 11] xen dom0: Add support for the platform_ops hypercall Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 07 of 11] xen mtrr: Add mtrr_ops support for Xen mtrr Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 08 of 11] xen: forcibly disable PAT support Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 09 of 11] xen/dom0: use _PAGE_IOMAP in ioremap to do machine mappings Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 10 of 11] paravirt/xen: add pvop for page_is_ram Jeremy Fitzhardinge
2008-12-19  0:53 ` [PATCH 11 of 11] xen: use machine memory map in domain 0 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=patchbomb.1229647985@abulafia.goop.org \
    --to=jeremy@goop.org \
    --cc=ian.campbell@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.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.