From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Xu, Jiajun" <jiajun.xu@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Biweekly VMX status report. Xen: #21438 & Xen0: #a3e7c7...
Date: Wed, 2 Jun 2010 13:17:10 +0100 [thread overview]
Message-ID: <C82C0A56.16765%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731E7ECF6D@shsmsx501.ccr.corp.intel.com>
That version of alloc_xenheap_pages is not built for x86_64.
K.
On 02/06/2010 11:23, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
> But in alloc_xenheap_pages(), we do unguard the page again, is that useful?
>
> --jyh
>
>> -----Original Message-----
>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>> Sent: Wednesday, June 02, 2010 5:41 PM
>> To: Jiang, Yunhong; Xu, Jiajun; xen-devel@lists.xensource.com
>> Subject: Re: [Xen-devel] Biweekly VMX status report. Xen: #21438 & Xen0:
>> #a3e7c7...
>>
>> On 02/06/2010 10:24, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
>>
>>> (XEN) Pagetable walk from ffff83022fe1d000:
>>> (XEN) L4[0x106] = 00000000cfc8d027 5555555555555555
>>> (XEN) L3[0x008] = 00000000cfef9063 5555555555555555
>>> (XEN) L2[0x17f] = 000000022ff2a063 5555555555555555
>>> (XEN) L1[0x01d] = 000000022fe1d262 5555555555555555
>>>
>>> I really can't imagine how this can happen considering the vmx_alloc_vmcs()
>>> is
>>> so straight-forward. My test machine is really magic.
>>
>> Not at all. The free-memory pool was getting spiked with guarded (mapped
>> not-present) pages. The later unlucky allocator is the one that then
>> crashes.
>>
>> I've just fixed this as xen-unstable:21504. The bug was a silly typo.
>>
>> Thanks,
>> Keir
>>
>
next prev parent reply other threads:[~2010-06-02 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:51 Biweekly VMX status report. Xen: #21438 & Xen0: #a3e7c7 Xu, Jiajun
2010-05-24 16:53 ` Keir Fraser
2010-05-25 8:17 ` Xu, Jiajun
2010-05-25 8:27 ` Dulloor
2010-05-25 8:29 ` Xu, Jiajun
2010-05-26 13:48 ` Xu, Jiajun
2010-05-25 9:13 ` Keir Fraser
2010-05-25 9:15 ` Keir Fraser
2010-06-01 7:43 ` Jiang, Yunhong
2010-06-01 9:30 ` Keir Fraser
2010-06-02 7:28 ` Jiang, Yunhong
2010-06-02 8:01 ` Keir Fraser
2010-06-02 8:49 ` Jiang, Yunhong
2010-06-02 9:24 ` Jiang, Yunhong
2010-06-02 9:41 ` Keir Fraser
2010-06-02 10:23 ` Jiang, Yunhong
2010-06-02 12:17 ` Keir Fraser [this message]
2010-06-02 13:33 ` Jiang, Yunhong
2010-06-02 12:14 ` Keir Fraser
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=C82C0A56.16765%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jiajun.xu@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@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 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).