I tend to agree with the spirit of Andi's comment -- disabling this will (I think) make the rare time when it happens into something impossible to debug without a new kernel and reproducing the problem. Not being familiar with EMBEDDED, I am curious whether the savings is critical. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 7/15] misc: Make x86 doublefault handling optional
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 7/15] misc: Make x86 doublefault handling optional
- From: Adrian Bunk <[email protected]>
- Re: [PATCH 7/15] misc: Make x86 doublefault handling optional
- References:
- [PATCH 7/15] misc: Make x86 doublefault handling optional
- From: Matt Mackall <[email protected]>
- Re: [PATCH 7/15] misc: Make x86 doublefault handling optional
- From: Rob Landley <[email protected]>
- Re: [PATCH 7/15] misc: Make x86 doublefault handling optional
- From: Matt Mackall <[email protected]>
- [PATCH 7/15] misc: Make x86 doublefault handling optional
- Prev by Date: Re: [PATCH] [IPV4] Fix secondary IP addresses after promotion
- Next by Date: Re: [PATCH] libata error handling fixes (ATAPI)
- Previous by thread: Re: [PATCH 7/15] misc: Make x86 doublefault handling optional
- Next by thread: Re: [PATCH 7/15] misc: Make x86 doublefault handling optional
- Index(es):
 |