From: "Scott Parish" Subject: Re: [patch] monitor_table is getting set to 0 for domu x86_64 Date: Sat, 18 Jun 2005 22:43:23 +0000 Message-ID: <20050618224323.GH2912@us.ibm.com> References: <20050618194911.GG2912@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20050618194911.GG2912@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Scott Parish Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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?) sRp -- Scott Parish Signed-off-by: srparish@us.ibm.com