RE: [Xen-devel] read_cr3()

To:	"Jan Beulich" <JBeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] read_cr3()
From:	"Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date:	Wed, 8 Feb 2006 07:25:37 -0800
Delivery-date:	Wed, 08 Feb 2006 15:36:56 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcYsrX2Omgni4PnqQ9GgsfExg4AUegAFJL3Q
Thread-topic:	[Xen-devel] read_cr3()

Jan Beulich wrote:
> Is it intentional that read_cr3() does a m2p translation on i386, but
> doesn't on x86-64? 
> 
> Thanks, Jan
> 

It was never used in x86_64 before. Looks like machine_kexec is using it
now, although the code is inactive. I think it'd be better to add m2p
for read_cr3 to avoid confusion. However, x86_64 xenlinux has two of
CR3, one for the kernel, one for user. So it would return the one for
the kernel.

Jun
---
Intel Open Source Technology Center

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

WARNING - OLD ARCHIVES

xen-devel

RE: [Xen-devel] read_cr3()