xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: andrew.cooper3@citrix.com, nd@arm.com, andre.przywara@linaro.org,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v3 0/4] xen/arm: Inject an exception to the guest rather than crashing it
Date: Fri, 2 Feb 2018 23:10:42 +0000	[thread overview]
Message-ID: <5e307f15-be71-195c-271b-db09d64fa3c7@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1802021448070.10160@sstabellini-ThinkPad-X260>



On 02/02/2018 22:48, Stefano Stabellini wrote:
> Committed, thanks

I know you acked/reviewed all the patches, but it would have been nice 
to wait/give more feedback regarding Andre's valid point on patch #4.

Cheers,

> On Fri, 2 Feb 2018, Julien Grall wrote:
>> Hi all,
>>
>> This small series replaces all call to domain_crash_synchronous by injecting
>> an exception to the guest.
>>
>> This will result to a nicer trace from the guest (no need to manually walk
>> the stack) and give a chance to the guest to give a bit more information on
>> what it was doing.
>>
>> Cheers,
>>
>> Julien Grall (4):
>>    xen/arm: traps: Merge try_handle_mmio() and handle_mmio()
>>    xen/arm: io: Distinguish unhandled IO from aborted one
>>    xen/arm: Don't crash domain on bad MMIO emulation
>>    xen/arm: Don't crash the domain on invalid HVC immediate
>>
>>   xen/arch/arm/io.c          | 65 ++++++++++++++++++++++++++++++++---------
>>   xen/arch/arm/traps.c       | 72 +++++++++++++++-------------------------------
>>   xen/arch/arm/vgic-v2.c     |  2 --
>>   xen/arch/arm/vgic-v3-its.c |  3 --
>>   xen/arch/arm/vgic-v3.c     |  8 ------
>>   xen/arch/arm/vpl011.c      |  2 --
>>   xen/include/asm-arm/mmio.h | 11 ++++++-
>>   7 files changed, 84 insertions(+), 79 deletions(-)
>>
>> -- 
>> 2.11.0
>>

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-02-02 23:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 10:14 [PATCH v3 0/4] xen/arm: Inject an exception to the guest rather than crashing it Julien Grall
2018-02-02 10:14 ` [PATCH v3 1/4] xen/arm: traps: Merge try_handle_mmio() and handle_mmio() Julien Grall
2018-02-02 14:34   ` Andre Przywara
2018-02-02 14:47     ` Julien Grall
2018-02-02 15:15       ` Andre Przywara
2018-02-02 10:14 ` [PATCH v3 2/4] xen/arm: io: Distinguish unhandled IO from aborted one Julien Grall
2018-02-02 14:34   ` Andre Przywara
2018-02-02 14:48     ` Julien Grall
2018-02-02 10:14 ` [PATCH v3 3/4] xen/arm: Don't crash domain on bad MMIO emulation Julien Grall
2018-02-02 14:35   ` Andre Przywara
2018-02-02 10:14 ` [PATCH v3 4/4] xen/arm: Don't crash the domain on invalid HVC immediate Julien Grall
2018-02-02 14:37   ` Andre Przywara
2018-02-02 14:59     ` Julien Grall
2018-02-02 22:48 ` [PATCH v3 0/4] xen/arm: Inject an exception to the guest rather than crashing it Stefano Stabellini
2018-02-02 23:10   ` Julien Grall [this message]
2018-02-05  9:54     ` Andre Przywara

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=5e307f15-be71-195c-271b-db09d64fa3c7@arm.com \
    --to=julien.grall@arm.com \
    --cc=andre.przywara@linaro.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=nd@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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).