From: Avi Kivity <avi@argo.co.il>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Keith Owens <kaos@ocs.com.au>, Hugh Dickins <hugh@veritas.com>,
Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] WTF is VLI?
Date: Fri, 19 Nov 2004 01:38:25 +0200 [thread overview]
Message-ID: <419D3271.7050804@argo.co.il> (raw)
In-Reply-To: <200411181808.iAII8ECH009759@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
>>ksymoops can disasemble the entire code line, but starting at different
>>offsets (up to the maximum instruction length) from the start. the first
>>disassembly to include the program counter in the output would be deemed
>>correct.
>>
>>
>
>There might be several... I see no reason to consider the first one
>correct.
>
>
Of course, there is no way to guarantee correctness. the point is with
the current system the chances of being correct are around 1:(average
instruction length) (a bit better because there is a chance to resync),
while with my proposal to be _incorrect_ you need to start wrong _and_
hit a bad resync.
I don't get to see many oopsen, but it seems to me most would have
garbage before eip, no?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2004-11-18 23:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 21:05 [PATCH] WTF is VLI? Hugh Dickins
2004-11-11 21:10 ` Dave Jones
2004-11-12 23:26 ` Horst von Brand
2004-11-15 21:18 ` Hugh Dickins
2004-11-16 6:00 ` Keith Owens
2004-11-16 9:56 ` Hugh Dickins
2004-11-17 5:55 ` Keith Owens
2004-11-18 15:47 ` Avi Kivity
2004-11-18 18:08 ` Horst von Brand
2004-11-18 23:38 ` Avi Kivity [this message]
2004-11-21 3:58 ` Keith Owens
2004-11-11 21:14 ` Andrew Morton
[not found] <fa.inbtt12.195ed02@ifi.uio.no>
[not found] ` <fa.cg6f09j.ji89hv@ifi.uio.no>
2004-11-18 18:28 ` Bodo Eggert
2004-11-18 23:44 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=419D3271.7050804@argo.co.il \
--to=avi@argo.co.il \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=hugh@veritas.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.