Bugs item #1750844, was opened at 2007-07-09 17:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1750844&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface (example)
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: aji003 (aji003)
Assigned to: Nobody/Anonymous (nobody)
Summary: Not able to memory map serial device to the address 0xd000
Initial Comment:
*cpu model
Intel(R) Xeon(R) CPU 5140 @ 2.33GHz Dual Core
*kvm version you are using
v2.6.22-rc7-263-g556c094
*the host kernel version
Linux 2.6.22-rc7-1-kvm (ubuntu X window system version 7.2.0)
* what host kernel arch you are using
x86_64 GNU/Linux
* what guest you are using,
qnx 4 : 32 bit
* the qemu command line you are using to start the guest
qemu-system-x86_64 -boot c -hda dev.qcow -fda floppy.img -m 128
* whether the problem also appears with the -no-kvm switch.
NO.
Bug detailed description:
Not able to memory map serial device to the address 0xd000.
I am trying to build a serial memory map driver which is mapped to address
0xd0000. So I am calling serial_mm_init function, instead of the default
serial_init funtion from pc_init1 function in pc.c.
No errors are reported while running the kvm. But the memory map driver is not
working (not able to read or write to the specified location). However If I
change the address to 0xB0000 (in pc.c) , driver is working. ie the call to
serial_mm_readb and serial_mm_writeb is correctly made. Also with qemu (
-no-kvm switch) mapping to both 0xd0000 and 0xb0000 is working as correctly.
I am calling cpu_register_physical_memory function, with start_addr = 0xd0000
and size =0x1000 from serial_mm_init().
It is important for me to write to and read from 0xd0000 memory locations,
becuase of the legacy requirements.
I have attached the backtrace obtained, by running qemu-system-x86_64 through
the gdb.
Under bt_kvm ::
contains different backtrace obtained when it hit the breakpoint I set at
function cpu_register_physical_memory (in exec.c) with the start_addr =0xd0000
(851968 decimal), while running KVM.
under bt_qemu ::
contains different backtrace obtained when it hit the breakpoint I set at
function cpu_register_physical_memory (in exec.c) with the start_addr =0xd0000
(851968 decimal), while running Qemu.
Please let me know, if you require any more information regarding it. I will be
thankful if somebody could point to any link which explains, how the devices
are memory mapped in KVM.
Thanking you
Ajith
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1750844&group_id=180599
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
