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

Re: [Xen-devel] [Patch v3 0/4] Xen stack trace printing improvements

>>> On 19.11.13 at 17:07, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
> On 19/11/2013 03:01, "George Dunlap" <george.dunlap@xxxxxxxxxxxxx> wrote:
>> On 11/19/2013 10:50 AM, Andrew Cooper wrote:
>>> On 19/11/2013 10:10, George Dunlap wrote:
>>> Benefits:
>>> * Use frame pointers in the stack overflow case
>>> * Correct boundaries for frame pointer traces
>>> * Wild function pointer semantics in the common case now
>>> Risks:
>>> * Issues with printing stack traces (although if you notice, I haven't
>>> actually changed either of the printing algorithms)
>>> This series seemed accepted-in-principle at v1 ages ago, pending me
>>> confirming the boundaries. (which have admittedly be tweaked in this
>>> latest series).
>> That makes more sense, thanks.  If Jan and/or Keir see it that way, then
>> the series is fine with me f/ a release perspective.
> Yes, this series should go in.

Which I'll then read as an ack (but I still want to go through the
patches before committing them).


Xen-devel mailing list



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