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

RE: [Xen-devel] [patch] monitor_table is getting set to 0 for domux86_64

  • To: "Scott Parish" <srparish@xxxxxxxxxx>
  • From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
  • Date: Sat, 18 Jun 2005 16:48:23 -0700
  • Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 18 Jun 2005 23:47:30 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcV0Xg9kGGmD69sUTkidOoNnhrq/GAAASGFw
  • Thread-topic: [Xen-devel] [patch] monitor_table is getting set to 0 for domux86_64

Scott Parish wrote:
> On Sat, Jun 18, 2005 at 07:49:11PM +0000, Scott Parish wrote:
>> While the attached patch takes care of the problem, and i don't
>> understand everything i know about TF_kernel_mode and
>> guest_table_user, so likely a better solution is in order. If
>> somebody wouldn't mind saying a few words about either of these, i'd
>> appreciate it. 
> I retract said patch--after understanding more of what i knew about
> TF_kernel_mode, and looking into the syscall problem, it seems clear
> that the problem is that TF_kernel_mode isn't set.
> So now the question is, why is TF_kernel_mode is getting cleared by
> arch_set_info_guest()? (or why isn't VGCF_IN_KERNEL set?)

I think you need to set VGCF_IN_KERNEL for x86_64 domains in
xc_linux_build.c for initialization.

For example, we are setting VGCF_VMX_GUEST in the builder
(libxc/xc_vmx_build.c) like
    ctxt->flags = VGCF_VMX_GUEST; 
> sRp

Intel Open Source Technology Center

Xen-devel mailing list



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