From: Keir Fraser <keir@xen.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: stefano.stabellini@eu.citrix.com, xen-devel@lists.xensource.com,
bruce.edge@gmail.com, gianni.tedesco@citrix.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [RFC Patch] Support for making an E820 PCI hole in toolstack (xl + xm)
Date: Mon, 15 Nov 2010 19:57:47 +0000 [thread overview]
Message-ID: <C907413B.A0AD%keir@xen.org> (raw)
In-Reply-To: <4CE18AD6.5070102@goop.org>
On 15/11/2010 19:32, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
>> Or, is there much disadvantage, to having a static really big PCI hole? Say
>> starting at 1GB? The advantage of this would be the ability to hotplug PCI
>> devices to a domU even across save/restore/migrate -- this may not work so
>> well if you commit yourself to the hole size of the original host, and the
>> restore/migrate target host has a bigger hole!
>
> Well, the other question is whether the devices have to have the same
> pfn as mfn within the hole. We're emulating the PCI config space anyway
> - couldn't we stick the passthrough PCI space at 3G regardless of where
> it is on the real hardware?
Well, I don't know. It sounds pretty sensible to me. :-)
Certain virtualisation feature sdisappearing after a save/restore/migrate --
or worsse, becoming unreliable -- would be a bit sad.
-- Keir
next prev parent reply other threads:[~2010-11-15 19:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 23:08 [RFC Patch] Support for making an E820 PCI hole in toolstack (xl + xm) Konrad Rzeszutek Wilk
2010-11-12 23:16 ` Konrad Rzeszutek Wilk
2010-11-13 7:40 ` Keir Fraser
2010-11-15 17:03 ` Konrad Rzeszutek Wilk
2010-11-15 17:20 ` Ian Campbell
2010-11-15 17:28 ` Konrad Rzeszutek Wilk
2010-11-15 17:48 ` Keir Fraser
2010-11-15 18:15 ` Konrad Rzeszutek Wilk
2010-11-15 18:41 ` Keir Fraser
2010-11-15 19:32 ` Jeremy Fitzhardinge
2010-11-15 19:57 ` Keir Fraser [this message]
2010-11-15 23:11 ` Konrad Rzeszutek Wilk
2010-11-16 1:06 ` Jeremy Fitzhardinge
2010-11-16 9:26 ` Ian Campbell
2010-11-16 9:52 ` Keir Fraser
2010-11-16 10:02 ` Ian Campbell
2010-11-16 10:11 ` Keir Fraser
2010-11-16 18:01 ` Jeremy Fitzhardinge
2010-11-16 15:50 ` Konrad Rzeszutek Wilk
2010-11-17 14:23 ` Ian Campbell
2010-11-16 7:40 ` Keir Fraser
2010-11-15 19:30 ` Jeremy Fitzhardinge
2010-11-17 11:14 ` Gianni Tedesco
2010-11-17 11:43 ` Ian Campbell
2010-11-17 13:37 ` Gianni Tedesco
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=C907413B.A0AD%keir@xen.org \
--to=keir@xen.org \
--cc=bruce.edge@gmail.com \
--cc=gianni.tedesco@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.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.