From: Keir Fraser <keir@xensource.com>
To: "Li, Xin B" <xin.b.li@intel.com>,
"Xin, Xiaohui" <xiaohui.xin@intel.com>,
xen-devel@lists.xensource.com
Cc: "Mallick, Asit K" <asit.k.mallick@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Li, Susie" <susie.li@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"He, Qing" <qing.he@intel.com>
Subject: Re: Two dead-lock situation occurs on 32bit HVM SMP Windows
Date: Tue, 14 Nov 2006 17:37:11 +0000 [thread overview]
Message-ID: <C17FAF47.48AB%keir@xensource.com> (raw)
In-Reply-To: <B30DA1341B0CFA4893EF8A36B40B5C5D679212@pdsmsx411.ccr.corp.intel.com>
On 14/11/06 17:33, "Li, Xin B" <xin.b.li@intel.com> wrote:
> On x86_64 xen, we saw get_mfn_from_gpfn gets into the fault-and-fixup
> path frequently when running 64bit windows guests with 1G RAM, and quite
> a few of them are caused by gpfn > 0x100000, i.e. above 4G, so how about
> aslo adding a gpfn range check into get_mfn_from_gpfn? And we can use
> hvm_set_param to set the max gpfn # in xc_hvm_build.c.
Any idea what it's trying to access? Presumably nothing is mapped up there
so it just gets all-ones back from reads? I'm surprised it would be doing
lots of accesses to totally unused memory space. That tends to be fairly
slow even on native hardware.
-- Keir
next prev parent reply other threads:[~2006-11-14 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 17:33 Two dead-lock situation occurs on 32bit HVM SMP Windows Li, Xin B
2006-11-14 17:37 ` Keir Fraser [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 18:02 Li, Xin B
2006-11-14 17:42 Li, Xin B
2006-11-14 17:56 ` Keir Fraser
2006-11-06 1:54 Tian, Kevin
2006-11-04 13:48 Xin, Xiaohui
2006-11-04 18:57 ` Keir Fraser
2006-11-05 12:06 ` Pasi Kärkkäinen
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=C17FAF47.48AB%keir@xensource.com \
--to=keir@xensource.com \
--cc=asit.k.mallick@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=qing.he@intel.com \
--cc=susie.li@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiaohui.xin@intel.com \
--cc=xin.b.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.