From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v2 0/3] xen/arm: Survive unknown traps from guests
Date: Mon, 8 May 2017 11:28:28 +0100 [thread overview]
Message-ID: <3b426ee5-fbf3-a388-717d-c5a11ed96f67@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1705051209150.2892@sstabellini-ThinkPad-X260>
Hi Stefano,
On 05/05/17 20:09, Stefano Stabellini wrote:
> On Fri, 5 May 2017, Julien Grall wrote:
>> Hi all,
>>
>> This small patch series ensure that Xen will not die when receiving unknown
>> trap from the guests. I am not aware of any issue with platform we currently
>> support, so I am not sure whether it would be Xen 4.9 material.
>
> Given that it is a bug fix and of small risk, I think it should be in
> 4.9.
I agree here, this would allow Xen to be used safely on new hardware if
no other patch is required.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-05-08 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 14:30 [PATCH v2 0/3] xen/arm: Survive unknown traps from guests Julien Grall
2017-05-05 14:30 ` [PATCH v2 1/3] xen/arm: arm32: Rename the trap to the correct name Julien Grall
2017-05-05 14:30 ` [PATCH v2 2/3] xen/arm: do_trap_hypervisor: Separate hypervisor and guest traps Julien Grall
2017-05-05 19:09 ` Stefano Stabellini
2017-05-05 14:30 ` [PATCH v2 3/3] xen/arm: Survive unknown traps from guests Julien Grall
2017-05-05 19:09 ` [PATCH v2 0/3] " Stefano Stabellini
2017-05-08 10:28 ` Julien Grall [this message]
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=3b426ee5-fbf3-a388-717d-c5a11ed96f67@arm.com \
--to=julien.grall@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).