[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new issue


  • To: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Mon, 31 Mar 2008 09:00:22 +0100
  • Delivery-date: Mon, 31 Mar 2008 01:01:25 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciQpKWD0nUpLcYoQJO5vdBPtedtsQAAGYrCAARoKiAACWpq/QCJQougAAD5Lxs=
  • Thread-topic: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new issue

On 31/3/08 08:44, "Li, Haicheng" <haicheng.li@xxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.