From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <jbeulich@suse.com>, ross.lagerwall@citrix.com
Cc: lars.kurth@citrix.com, sstabellini@kernel.org, liuw@liuw.name,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH for-4.9 v2] livepatch: Declare live patching as a supported feature
Date: Thu, 29 Jun 2017 15:30:49 +0100 [thread overview]
Message-ID: <d1d8e1cb-011d-8ebf-9be7-1f09ade5fdc6@arm.com> (raw)
In-Reply-To: <5954A29E02000078001016C9@prv-mh.provo.novell.com>
Hi,
On 06/29/2017 07:47 AM, Jan Beulich wrote:
>>>> Ross Lagerwall <ross.lagerwall@citrix.com> 06/28/17 6:14 PM >>>
>> --- a/xen/common/Kconfig
>> +++ b/xen/common/Kconfig
>> @@ -226,7 +226,7 @@ config CRYPTO
> >bool
> >
> >config LIVEPATCH
>> - bool "Live patching support (TECH PREVIEW)"
>> + bool "Live patching support"
> >default n
>
> I think the patch shouldn't be tagged for 4.9 anymore now that is has gone out,
> and the default be changed as discussed. The backport to 4.9 then should discard
> that default adjustment.
Based on this patch, livepatch will be declared supported on x86. So it
sounds a bit odd to provide a default configuration for ARM that will
contain non-supported feature.
Any opinions?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-29 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 16:13 [PATCH for-4.9 v2] livepatch: Declare live patching as a supported feature Ross Lagerwall
2017-06-28 17:32 ` Konrad Rzeszutek Wilk
2017-06-29 6:47 ` Jan Beulich
2017-06-29 14:30 ` Julien Grall [this message]
2017-06-29 16:07 ` Jan Beulich
2017-06-30 10:30 ` Julien Grall
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=d1d8e1cb-011d-8ebf-9be7-1f09ade5fdc6@arm.com \
--to=julien.grall@arm.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=lars.kurth@citrix.com \
--cc=liuw@liuw.name \
--cc=ross.lagerwall@citrix.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).