qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: qemu-devel@nongnu.org, xen-devel@lists.xen.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [Qemu-devel] [PATCH] Remove hardcoded xen-platform device initialization
Date: Thu, 13 Jun 2013 10:50:54 +0100	[thread overview]
Message-ID: <1371117054-5694-1-git-send-email-paul.durrant@citrix.com> (raw)

The xen-platform device should be initialized by the Xen toolstack by
passing the appropriate -device argument on the command line.

Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
---
 hw/i386/pc_piix.c |    3 ---
 1 file changed, 3 deletions(-)

diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
index d618570..e25012d 100644
--- a/hw/i386/pc_piix.c
+++ b/hw/i386/pc_piix.c
@@ -174,9 +174,6 @@ static void pc_init1(MemoryRegion *system_memory,
     pc_register_ferr_irq(gsi[13]);
 
     pc_vga_init(isa_bus, pci_enabled ? pci_bus : NULL);
-    if (xen_enabled()) {
-        pci_create_simple(pci_bus, -1, "xen-platform");
-    }
 
     /* init basic PC hardware */
     pc_basic_device_init(isa_bus, gsi, &rtc_state, &floppy, xen_enabled());
-- 
1.7.10.4

             reply	other threads:[~2013-06-13  9:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  9:50 Paul Durrant [this message]
2013-06-13 17:33 ` [Qemu-devel] [PATCH] Remove hardcoded xen-platform device initialization Stefano Stabellini
2013-06-13 17:44   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2013-06-13 18:02     ` Paolo Bonzini
2013-06-14  9:00       ` Paul Durrant
2013-06-14 10:38         ` Paul Durrant
2013-06-14 13:50           ` Paolo Bonzini
2013-06-14 14:11             ` Paul Durrant
2013-06-14 14:57               ` Paolo Bonzini
2013-06-14 15:10                 ` Paul Durrant
2013-06-18 18:56                   ` Stefano Stabellini
2013-06-18 19:12                     ` Paolo Bonzini
2013-06-18 19:35                       ` Stefano Stabellini
2013-06-18 21:38                         ` Andreas Färber
2013-06-19  8:29                           ` Ian Campbell
2013-06-19  8:37                             ` Paul Durrant
2013-06-19  8:41                             ` Paolo Bonzini
2013-06-19  8:56                               ` Ian Campbell
2013-06-19  9:11                                 ` Paul Durrant
2013-06-19 12:51                                 ` Paolo Bonzini
2013-06-19 13:47                                 ` Stefano Stabellini
2013-06-19  8:27                         ` Paul Durrant
2013-06-19 13:55                           ` Stefano Stabellini
2013-06-19 15:09                             ` Ian Campbell
2013-06-19  8:11                     ` Ian Campbell
2013-06-19 13:53                       ` Stefano Stabellini
2013-06-19 14:00                         ` Paul Durrant
2013-06-19 16:27                           ` Stefano Stabellini
2013-06-20  7:32                             ` Paul Durrant
2013-06-14  8:56     ` Paul Durrant
2013-06-14  8:50   ` [Qemu-devel] " Paul Durrant
2013-06-14 13:52     ` Paolo Bonzini
2013-06-14 13:57       ` Paul Durrant

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=1371117054-5694-1-git-send-email-paul.durrant@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xen.org \
    /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).