From: Keir Fraser <keir.xen@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Jiageng Yu <yujiageng734@gmail.com>,
Anthony PERARD <anthony.perard@gmail.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: Re: Linux Stubdom Problem
Date: Fri, 02 Sep 2011 14:11:45 +0100 [thread overview]
Message-ID: <CA8694A1.20379%keir.xen@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1109021401000.12963@kaball-desktop>
On 02/09/2011 14:09, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
wrote:
>> Why? HVMloader is already tightly coupled to the hypervisor and the
>> toostack - special cases for stubdoms should be fine.
>
> I think think that leaking the implementation details of the device
> model into hvmloader should be avoided, but obviously if there are no
> alternatives, it can be done.
This is a fair and more general point, that we don't want fragile
dependencies on qemu now that we are using upstream. But as I say that's a
more general point on our policy regarding qemu, rather than something
specifically concerning hvmloader.
-- Keir
next prev parent reply other threads:[~2011-09-02 13:11 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 16:54 Linux Stubdom Problem Jiageng Yu
2011-07-21 17:08 ` iommu=force-hpdl385g7 boot option as workaround for missing IOMMU support in BIOS of HP DL385 g7 Mark Schneider
2011-07-21 17:18 ` Linux Stubdom Problem Stefano Stabellini
2011-07-25 16:45 ` Jiageng Yu
2011-07-26 17:50 ` Jiageng Yu
2011-07-27 11:26 ` Stefano Stabellini
2011-07-27 12:56 ` Jiageng Yu
2011-07-27 13:34 ` Stefano Stabellini
2011-07-28 15:34 ` Jiageng Yu
2011-07-28 17:01 ` Jiageng Yu
2011-07-29 14:29 ` Stefano Stabellini
2011-07-29 14:51 ` Jiageng Yu
2011-07-29 15:04 ` Stefano Stabellini
2011-07-29 15:09 ` Jiageng Yu
2011-07-29 15:18 ` Stefano Stabellini
2011-07-29 15:16 ` Jiageng Yu
2011-07-29 15:28 ` Stefano Stabellini
2011-08-12 16:22 ` Jiageng Yu
2011-08-15 12:46 ` Jiageng Yu
2011-08-18 23:39 ` Stefano Stabellini
2011-08-22 15:24 ` Jiageng Yu
2011-08-22 19:36 ` Stefano Stabellini
2011-08-22 20:16 ` Keir Fraser
2011-08-23 9:39 ` Jiageng Yu
2011-08-23 14:38 ` Stefano Stabellini
2011-08-23 10:07 ` Tim Deegan
2011-08-23 12:59 ` Stefano Stabellini
2011-08-26 16:12 ` Stefano Stabellini
2011-08-27 13:06 ` Tim Deegan
2011-08-29 12:27 ` Stefano Stabellini
2011-08-29 13:18 ` Tim Deegan
2011-08-29 16:03 ` Stefano Stabellini
2011-08-31 6:02 ` Keir Fraser
2011-09-01 17:12 ` Jiageng Yu
2011-09-01 17:27 ` Tim Deegan
2011-09-02 2:32 ` Jiageng Yu
2011-09-02 11:03 ` Tim Deegan
2011-09-02 13:09 ` Stefano Stabellini
2011-09-02 13:11 ` Keir Fraser [this message]
2011-09-14 13:38 ` Jiageng Yu
2011-09-15 11:13 ` Stefano Stabellini
2011-10-27 14:56 ` Jiageng Yu
2011-11-08 17:05 ` Stefano Stabellini
2011-11-09 8:59 ` Jiageng Yu
2011-11-09 13:47 ` Stefano Stabellini
2011-11-09 14:30 ` Jiageng Yu
2011-11-10 10:19 ` Stefano Stabellini
2011-11-17 15:18 ` Jiageng Yu
2011-11-18 11:21 ` Stefano Stabellini
2011-11-09 17:05 ` Konrad Rzeszutek Wilk
2011-11-10 10:10 ` Stefano Stabellini
2011-11-04 14:00 ` Jiageng Yu
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=CA8694A1.20379%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=anthony.perard@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.com \
--cc=yujiageng734@gmail.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.