All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Michael Abd-El-Malek <mabdelmalek@cmu.edu>
Subject: Re: Vanilla Linux 64-bit paravirt guest support
Date: Thu, 10 Apr 2008 15:40:29 +0100	[thread overview]
Message-ID: <1207838429.16779.19.camel@muff> (raw)
In-Reply-To: <47FE2358.3040307@goop.org>

On Thu, 2008-04-10 at 09:25 -0500, Jeremy Fitzhardinge wrote:
> Mark McLoughlin wrote:
> > s what we're actually shipping for F-9. It includes the x86_64 work,
> > but some other paravirt_ops patches too, most of which are queued up
> > upstream.
> 
> What else do you have?  Hm.  I was really hoping to drop /proc/xen/...

Okay, here's the list:

    xen x86_64: Initial x86_64 support for Xen paravirt_ops

Eduardo's x86_64 stuff

    xen x86_64: Add 64 bit version of privcmd_hypercall()
    xen: Add Xen's /sys/hypervisor interface
    xen: Add /proc/xen/xenbus
    xen: Add /proc/xen/privcmd
    xen: Add /proc/xen/capabilities
    xen: Add empty xenctrl module

This is /proc/xen and /sys/hypervisor stuff pulled from the dom0 tree.
In that tree we've got mostly full compatibility with the
linux-2.6.18-xen userspace interfaces AFAIR.

I probably don't need all of these for DomU, but I went for the safe bet
of including anything that userspace might be relying on.

Happy for us to drop /proc/xen in the future - this is just a "get
things going" thing.

    xen debug: Add xprintk to log directly via hypercall

Just for debugging

    xen: Add a vmlinuz target

bzImage is the way forward, but for now it was easier to just do stick
with vmlinuz - e.g. until there's support for bzImage Dom0 and we get
newer Xen HV and userspace in Fedora 

    xen blkfront: Delay wait for block devices until after the disk is added.
    xen: Add compatibility aliases for frontend drivers
    xen: Module autoprobing support for frontend drivers
    xen: Enable Xen console by default in domU
    xen pvfb: Para-virtual framebuffer, keyboard and pointer driver
    xen: Make xen-blkfront write its protocol ABI to xenstore
    xen: Do not pin/unpin PMD pages

All queued upstream

    xen x86_64: Only define load_user_cs_desc() on 32 bit
    xen execshield: fix endless GPF fault loop
    xen execshield: Add xen-specific load_user_cs_desc()
    squashfs: Fix build without CONFIG_SMP

Fedora specific (e.g. execshield)

Cheers,
Mark.

  reply	other threads:[~2008-04-10 14:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08  4:20 Vanilla Linux 64-bit paravirt guest support Michael Abd-El-Malek
2008-04-08 21:29 ` Jeremy Fitzhardinge
2008-04-10  4:14   ` Michael Abd-El-Malek
2008-04-10 14:01     ` Jeremy Fitzhardinge
2008-04-10 14:11       ` Mark McLoughlin
2008-04-10 14:25         ` Jeremy Fitzhardinge
2008-04-10 14:40           ` Mark McLoughlin [this message]
2008-04-10 15:04             ` Jeremy Fitzhardinge
2008-04-19 15:11               ` Bastian Blank
2008-04-10 14:32         ` Michael Abd-El-Malek
2008-04-10 14:49           ` Mark McLoughlin
2008-04-10 14:57           ` Jeremy Fitzhardinge
2008-04-10 15:06             ` Fix a typo in p2m.c Huang2, Wei
2008-04-10 15:14             ` Vanilla Linux 64-bit paravirt guest support Michael Abd-El-Malek
2008-04-10 15:40               ` Jeremy Fitzhardinge
2008-05-06 16:22         ` Mark McLoughlin

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=1207838429.16779.19.camel@muff \
    --to=markmc@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jeremy@goop.org \
    --cc=mabdelmalek@cmu.edu \
    --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.