From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Akio Takebe <takebe_akio@jp.fujitsu.com>,
"Li, Xin" <xin.li@intel.com>,
"Li, Haicheng" <haicheng.li@intel.com>,
"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: Re: Critical bug: VT-d fault causes disk corruption orDom0 kernel panic.
Date: Thu, 22 Jan 2009 09:47:45 +0000 [thread overview]
Message-ID: <C59DF141.21B60%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <66C97C757FFC56takebe_akio@jp.fujitsu.com>
On 22/01/2009 09:40, "Akio Takebe" <takebe_akio@jp.fujitsu.com> wrote:
> Is compute_dom0_nr_pages() OK?
> The number of available pages seems to be increase.
> What do you think?
Now that the heaps are unified, the old Xen heap pages are visible to dom0
and available to be allocated. Is this a problem? Probably not since we
already by default prevent dom0 from allocating all memory up front. There
are similar concerns regarding the auto-ballooner by the way, which are more
likely to need addressing. If you run with dom0_mem= and no auto-ballooner
then there is no worry at all.
Btw these concerns should have nothing to do with the reported VT-d faults.
-- Keir
next prev parent reply other threads:[~2009-01-22 9:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 3:42 Critical bug: VT-d fault causes disk corruption or Dom0 kernel panic Li, Haicheng
2009-01-22 7:40 ` Keir Fraser
2009-01-22 8:58 ` Li, Xin
2009-01-22 9:23 ` Keir Fraser
2009-01-22 9:40 ` Critical bug: VT-d fault causes disk corruption orDom0 " Akio Takebe
2009-01-22 9:47 ` Keir Fraser [this message]
2009-01-23 1:01 ` Critical bug: VT-d fault causes disk corruption or Dom0 " Kay, Allen M
2009-01-23 8:33 ` Keir Fraser
2009-01-23 17:30 ` Kay, Allen M
2009-01-23 18:41 ` Keir Fraser
2009-01-23 18:44 ` Keir Fraser
2009-01-23 23:40 ` Kay, Allen M
2009-01-24 0:34 ` Cihula, Joseph
2009-01-24 9:15 ` Keir Fraser
2009-01-24 9:26 ` Keir Fraser
2009-01-24 19:07 ` Cihula, Joseph
2009-01-24 19:58 ` Keir Fraser
2009-01-24 2:19 ` Cihula, Joseph
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=C59DF141.21B60%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=haicheng.li@intel.com \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.li@intel.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.