From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] x86/iommu: account for necessary allocations when calculating Dom0's initial allocation size
Date: Tue, 14 Dec 2010 09:36:37 +0000 [thread overview]
Message-ID: <4D0748B50200007800027C32@vpn.id2.novell.com> (raw)
In-Reply-To: <C92CE95B.CCD5%keir@xen.org>
>>> On 14.12.10 at 10:28, Keir Fraser <keir@xen.org> wrote:
> Thank Jan. I'm not really sure about putting your earlier patch into 4.0.2,
> so can I put only this patch in for 4.0.2, replacing max_pdx with max_page?
Yes, that would be the correct equivalent without that other patch.
But it is clear that without the other one a system may not even
boot if the holes are large enough - but that's the case in plain
4.0.0 too, i.e. not a regression.
Jan
> On 14/12/2010 09:03, "Jan Beulich" <JBeulich@novell.com> wrote:
>
>> As of c/s 21812:e382656e4dcc, IOMMU related allocations for Dom0
>> happen only after it got all of its memory allocated, and hence the
>> reserve (mainly for setting up its swiotlb) may get exhausted without
>> accounting for the necessary allocations up front.
>>
>> While not precise, the estimate has been found to be within a couple
>> of pages for the systems it got tested on.
>>
>> For the calculation to be reasonably correct, this depends on the
>> patch titled "x86/iommu: don't map RAM holes above 4G" sent out
>> yesterday.
>>
>> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>>
>> --- a/xen/arch/x86/domain_build.c
>> +++ b/xen/arch/x86/domain_build.c
>> @@ -191,6 +191,15 @@ static unsigned long __init compute_dom0
>> if ( is_pv_32on64_domain(d) )
>> avail -= opt_dom0_max_vcpus - 1;
>>
>> + /* Reserve memory for iommu_dom0_init() (rough estimate). */
>> + if ( iommu_enabled )
>> + {
>> + unsigned int s;
>> +
>> + for ( s = 9; s < BITS_PER_LONG; s += 9 )
>> + avail -= max_pdx >> s;
>> + }
>> +
>> /*
>> * If domain 0 allocation isn't specified, reserve 1/16th of available
>> * memory for things like DMA buffers. This reservation is clamped to
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-12-14 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 9:03 [PATCH] x86/iommu: account for necessary allocations when calculating Dom0's initial allocation size Jan Beulich
2010-12-14 9:28 ` Keir Fraser
2010-12-14 9:36 ` Jan Beulich [this message]
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=4D0748B50200007800027C32@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir@xen.org \
--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 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).