8 messages in com.xensource.lists.xen-develRe: [Xen-devel] VMX status report. Xe...
FromSent OnAttachments
Li, Haicheng28 Mar 2008 00:23 
Keir Fraser28 Mar 2008 00:26 
Li, Haicheng28 Mar 2008 06:37 
Keir Fraser28 Mar 2008 07:01 
Li, Haicheng31 Mar 2008 00:43 
Keir Fraser31 Mar 2008 00:59 
Li, Haicheng31 Mar 2008 01:56.zip
Keir Fraser31 Mar 2008 02:18 
Subject:Re: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new issue
From:Keir Fraser (keir@eu.citrix.com)
Date:03/31/2008 12:59:59 AM
List:com.xensource.lists.xen-devel

On 31/3/08 08:44, "Li, Haicheng" <haic@intel.com> wrote:

Can you provide the vmlinux file for this kernel, or otherwise find out what code is at address 0xc01af276 in that kernel. Either we are emulating something we should not emulate, or the kernel really is accessing I/O memory with SSE instructions, and we'll need to emulate them.

Should be located to _mmx_memcpy(),

How early during boot does it crash? If it's early perhaps I can repro if you send me the vmlinux file, or attach it to the bug, or otherwise make it available for download?

Does RHEL5.1 already have a directory /sys/devices/system/memory/? If so what is under there? Could you 'ls -lR' that directory and send us the output?

Yes there is alreay a directory /sys/devices/system/memory/.

Okay, it's generic Linux memory hotplug info. So I've renamed our sysfs information to /sys/devices/system/xen_memory/

-- Keir