[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC 0 PATCH 3/3] PVH dom0: construct_dom0 changes

>>> On 08.10.13 at 02:58, Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> wrote:
> On Fri, 04 Oct 2013 07:53:20 +0100
> "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>> Nothing specific, but I know that SR-IOV virtual functions easily
>> cause kernels to run out of MMIO space below 4G (namely when
>> the hole is only around 1Gb or even less), and Intel must have
>> knowledge of graphics cards having so huge a frame buffer that
>> it can only be mapped above 4G.
> In that case, I don't see why this is a MUST for the patch. Combined
> with the fact that at present pv-ops doesn't even allow for mapping
> above the last e820 entry, I think this can be left FIXME/bug-fix for 
> near future that can be done relatively quickly by an expert in that
> area if learning that takes me a long time.

Okay, so it seems you're back in Linux-only mode. I'm asking
for there not being fundamental holes. Dealing with the majority
of the "fixme"s you have already sprinkled around the code has
at least a clear path associated with it. Here, however, we're not
even certain how to properly deal with the problem.

And just to be clear - _any_ of the "fixme"s we intend to allow to
go in with this series is a compromise already, with - afaict - no
precedent. The more you ask for, the more likely it'll become for
at least me to start re-thinking about this. Over the past years I
think we made good progress in morphing Xen from an
experimental project to a stable, enterprise ready one. I'm not
eager to see us get pushed back significantly on that road.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.