From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: qemu-devel@nongnu.org,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
kraxel@redhat.com, "Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"jacek burghardt" <jaceksburghardt@gmail.com>
Subject: Re: [Qemu-devel] [Xen-devel] target-i386: Introduce ICC bus/device/bridge
Date: Tue, 28 May 2013 16:12:21 +0200 [thread overview]
Message-ID: <51A4BB45.7040708@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1305281358150.4799@kaball.uk.xensource.com>
Il 28/05/2013 15:44, Stefano Stabellini ha scritto:
>
> I actually tested it and seems to work fine but I wouldn't want to paint
> me into a corner by setting up a new use case that nobody else is
> testing.
> On the other hand I dislike having to create a "useless" x86 cpu, that
> at the moment doesn't even work because cpu_x86_init seems to be broken
> by the lack of the ICC bridge.
>
> Overall if the QEMU machine model supports it (and it looks like it
> does), I would rather choose the "no cpu" option.
I also prefer this. I wonder if this change would make xen_machine_pv.c
work for any architecture rather than just i386, at least for xen_mode
== XEN_ATTACH.
Paolo
next prev parent reply other threads:[~2013-05-28 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHyyzzROOonCohQnHcFKnOyutirb4BY5-+8y5dvg_9hUo1HFrA@mail.gmail.com>
2013-05-27 14:12 ` [Qemu-devel] [Xen-devel] target-i386: Introduce ICC bus/device/bridge Igor Mammedov
2013-05-28 1:19 ` jacek burghardt
2013-05-28 11:49 ` Stefano Stabellini
2013-05-28 11:57 ` Andreas Färber
2013-05-28 13:12 ` jacek burghardt
2013-05-28 15:15 ` Stefano Stabellini
2013-05-28 13:44 ` Stefano Stabellini
2013-05-28 14:12 ` Paolo Bonzini [this message]
2013-05-28 15:14 ` Stefano Stabellini
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=51A4BB45.7040708@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=jaceksburghardt@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--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).