WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Question on QEMU and P2M

To: Wei Huang <wei.huang2@xxxxxxx>
Subject: Re: [Xen-devel] Question on QEMU and P2M
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Wed, 24 Jun 2009 16:10:43 +0100
Cc: Keir, "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 24 Jun 2009 08:11:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A4165DF.9000403@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <4A4165DF.9000403@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Wei Huang writes ("[Xen-devel] Question on QEMU and P2M"):
> I am facing a qemu-dm problem when setting up 1GB page table to P2M.
...
> Any suggestion of suspicious code areas to look at?

This is unlikely to be a problem in qemu-dm; qemu-dm gets told the
guest-physical of IO requests addresses by Xen.  I would suggest that
the starting point would be xen/arch/x86/hvm/io.c and its subroutines
and callers.  That's the place where the IO requests are collected and
sent on to the device model (ie, qemu-dm).

Ian.

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

<Prev in Thread] Current Thread [Next in Thread>