All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <Keir.Fraser@xensource.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] Re: [Xen-staging] [xen-unstable] pv-qemu 1/10: Add a QEMU machine type for fullvirt guests
Date: Thu, 25 Oct 2007 09:48:53 -0600	[thread overview]
Message-ID: <1193327333.6665.2.camel@bling> (raw)
In-Reply-To: <200710251354.l9PDsMgP008283@latara.uk.xensource.com>


On Thu, 2007-10-25 at 14:54 +0100, Xen staging patchbot-unstable wrote:
> # HG changeset patch
> # User Keir Fraser
> # Date 1193319181 -3600
> # Node ID 65b961265093ccde3df8b1df17cafbcc3e78091e
> # Parent  168beb9a27a5c1d1c7f16dee9c25dd5aabdaf50a
> pv-qemu 1/10: Add a QEMU machine type for fullvirt guests
> 
> This patch does a (no functional change) re-arrangement of the code
> for starting up a fully virtualized guest. In particular it creates a
> new QEMU machine type for Xen fullyvirt guests which can be specified
> with '-M xenfv'. For compatibility this is in fact made to be the
> default. The code for setting up memory maps is moved out of vl.c, and
> into hw/xen_machine_fv.c. This is basically to ensure that it can be
> easily skipped when we add a paravirt machine type in the next patch.

   Trivial ia64 build fix.  Thanks,

	Alex

Signed-off-by: Alex Williamson <alex.williamson@hp.com>
---

diff -r 3d97c1c1f7c8 tools/ioemu/hw/xen_machine_fv.c
--- a/tools/ioemu/hw/xen_machine_fv.c	Thu Oct 25 15:54:19 2007 +0100
+++ b/tools/ioemu/hw/xen_machine_fv.c	Thu Oct 25 09:43:16 2007 -0600
@@ -201,6 +201,7 @@ static void xen_init_fv(uint64_t ram_siz
     unsigned long nr_pages;
     xen_pfn_t *page_array;
     extern void *buffered_pio_page;
+    int i;
 #endif
 
 #if defined(__i386__) || defined(__x86_64__)

           reply	other threads:[~2007-10-25 15:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200710251354.l9PDsMgP008283@latara.uk.xensource.com>]

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=1193327333.6665.2.camel@bling \
    --to=alex.williamson@hp.com \
    --cc=Keir.Fraser@xensource.com \
    --cc=berrange@redhat.com \
    --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.