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] [PATCH 2/5] xen/x86-64: clean up warnings aboutIST-usin

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2/5] xen/x86-64: clean up warnings aboutIST-usingtraps
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Fri, 08 May 2009 16:30:39 +0100
Cc: Ingo Molnar <mingo@xxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>
Delivery-date: Fri, 08 May 2009 08:30:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A044E55.20803@xxxxxxxx>
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>
References: <4A032EE0.9030607@xxxxxxxx> <4A03F947.76EA.0078.0@xxxxxxxxxx> <4A044E55.20803@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Jeremy Fitzhardinge <jeremy@xxxxxxxx> 08.05.09 17:23 >>>
>Jan Beulich wrote:
>>> else if (addr == (unsigned long)int3)
>>>             addr = (unsigned long)xen_int3;
>>> -   else
>>> -           WARN_ON(val->ist != 0);
>>> +   else if (addr == (unsigned long)double_fault ||
>>> +            addr == (unsigned long)stack_segment) {
>>>     
>>
>> I don't think you want to exclude handling stack faults: Ordinary memory
>> references using rsp or rbp as the base register will cause these instead
>> of general protection faults when the resulting effective address is non-
>> canonical.
>>   
>
>So even usermode memory accesses?  Ew.

Yes, just try it out - you'll observe them generate SIGBUS instead of SIGSEGV.

Jan


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