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

["Li, Haicheng" <haicheng.li@xxxxxxxxx>]

Keir Fraser wrote:
> On 28/3/08 13:37, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:
> 
>> 1. Hvm guest with generic kernel 2.6.18 cannot boot up,  the serial
>> log shows "io.c:198:d1 MMIO emulation failed @ 0060:c01af276: 0f 6f
>> 06 0f 6f 4e".
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1196. 
> 
> 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(),

`Objdump -d vmlinux` shows:

c01af26b:       89 ef                   mov    %ebp,%edi
c01af26d:       eb 4e                   jmp    c01af2bd
<_mmx_memcpy+0xad>
c01af26f:       0f 0d 86 40 01 00 00    prefetch 0x140(%esi)
c01af276:       0f 6f 06                movq   (%esi),%mm0
c01af279:       0f 6f 4e 08             movq   0x8(%esi),%mm1
c01af27d:       0f 6f 56 10             movq   0x10(%esi),%mm2
c01af281:       0f 6f 5e 18             movq   0x18(%esi),%mm3
c01af285:       0f 7f 07                movq   %mm0,(%edi)



>> 2. on RHEL5.1, "insmod balloon.ko" shows error as below:
>> 
>> Xen version 3.3.
>> Hypercall area is 1 pages.
>> xen_mem: Initialising balloon driver.
>> kobject_add failed for memory with -EEXIST, don't try to register
>> things with the same name in the same directory.
> 
> 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?
> 
> I don't think anyone actually uses our balloon driver sysfs
> interface, so we could just rename it to something a bit more
> Xen-specific. 
> 

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

`ls -lR` shows : 

/sys/devices/system/memory/:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 block_size_bytes
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory0
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory1
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory2
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory3
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory4
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory5
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory6
drwxr-xr-x 2 root root    0 Mar 31 15:34 memory7
-rwx------ 1 root root 4096 Mar 31 15:34 probe

/sys/devices/system/memory/memory0:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state

/sys/devices/system/memory/memory1:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state

/sys/devices/system/memory/memory2:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state

/sys/devices/system/memory/memory3:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state

/sys/devices/system/memory/memory4:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state

/sys/devices/system/memory/memory5:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state

/sys/devices/system/memory/memory6:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state

/sys/devices/system/memory/memory7:
total 0
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_device
-r--r--r-- 1 root root 4096 Mar 31 15:34 phys_index
-rw-r--r-- 1 root root 4096 Mar 31 15:34 state


-- haicheng

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