From: Christoffer Dall <christoffer.dall@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
'Marc Zyngier' <marc.zyngier@arm.com>
Subject: Re: [PATCH] KVM: arm64: Decode basic HYP fault information
Date: Mon, 31 Aug 2015 11:49:27 +0200 [thread overview]
Message-ID: <20150831094927.GL24113@cbox> (raw)
In-Reply-To: <012d01d0e3b6$fa327c30$ee977490$@samsung.com>
On Mon, Aug 31, 2015 at 09:33:40AM +0300, Pavel Fedin wrote:
> Hello!
>
> > my overall concern with this patch is that it adds complexity to an
> > already really bad situation, and potentially increases the likelihood
> > of not seeing any debug info at all.
>
> Why? In this case we currently already drop into C code. I do the same, with some more useful
> printout. What is fundamentally changed?
>
Fundamentally what's changed is that you now run more custom code in C
code.
I'll think about it.
-Christoffer
next prev parent reply other threads:[~2015-08-31 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 7:34 [PATCH] KVM: arm64: Decode basic HYP fault information Pavel Fedin
2015-08-30 17:44 ` Christoffer Dall
2015-08-31 6:33 ` Pavel Fedin
2015-08-31 9:49 ` Christoffer Dall [this message]
2015-08-31 9:59 ` Pavel Fedin
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=20150831094927.GL24113@cbox \
--to=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=p.fedin@samsung.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).