 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] memguard_guard_stack()
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] memguard_guard_stack() |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | Fri, 28 Apr 2006 18:03:39 +0200 |
| Delivery-date: | Fri, 28 Apr 2006 09:03:07 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| 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 |
Is it really intended that the stack size, specifically bumped to 4 pages in include/asm-x86/config.h for x86-64 when debugging, gets shrunk to a single page in memguard_guard_stack()? To me it would seem much more reasonable if indeed only the first page (or at most, the first two pages) was used as a guard page here. Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] kernel Bug after upgrading to 3.0.2-2, Brian Hays |
|---|---|
| Next by Date: | RE: [Xen-devel] kernel Bug after upgrading to 3.0.2-2, Ian Pratt |
| Previous by Thread: | [Xen-devel] kernel Bug after upgrading to 3.0.2-2, Brian Hays |
| Next by Thread: | Re: [Xen-devel] memguard_guard_stack(), Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
