xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: andrew.cooper3@citrix.com,
	Marcos Matsunaga <Marcos.Matsunaga@oracle.com>,
	xen-devel@lists.xensource.com, mpohlack@amazon.com
Subject: Re: Livepatch for Xen 4.9
Date: Mon, 24 Oct 2016 12:25:47 +0100	[thread overview]
Message-ID: <1f6c5ff1-827e-0e31-d54c-0ea9e473554e@citrix.com> (raw)
In-Reply-To: <20161003141641.GG20896@char.us.oracle.com>

On 10/03/2016 03:16 PM, Konrad Rzeszutek Wilk wrote:
> Hey!
>
> [CC-ing xen-devel]
>
> Xen 4.8-rc1 is out and means taking a break from some of the Livepatch hypervisor
> parts for me.

Thanks for all the work you put in!

>
> My plan for 4.8 is to concentrate on any livepatch fallout and doing OSSTest along
> with Marcos (CC-ed) and see if we can wrestle it to expand on what
> we want to have done.
>
> However going forward (Xen 4.9) I believe the top issues we need
> to get addressed are:
>
>  a) "A better mechanism to "mask" NMIs during patching. The existing mechanism looses
>    NMI if they have been sent and we don't have a mechanism to replay them. Note that
>    this is also fixes alternative section patching. Could (like Linux) annotate handlers don't get patched."
>    (https://wiki.xenproject.org/wiki/LivePatch).
>  b) Restart the shrinking of code using__LINE__
>  c) When figuring out the new_addr, take into account name being <symbol>+<offset>.
>  d) Make asm code be in its own section. That eases the livepatch tools work in figuring out a change.
>     See https://lkml.org/lkml/2009/2/24/364
>  e) ?
>
>  g) Make XENPF_get_symbol also include Live Patch symbols.
>
>
> I was wondering if folks could put in their preference and what they are thinking
> to work on during 4.9?
>
>

I'm going to try implement signature verification of livepatch modules. 
The bits for signing modules are already in livepatch-build-tools, so it 
just requires the hypervisor to verify the signature. How hard can that 
be? :-)

>
>
> Also I was thinking we can drop the IRC meeting we have setup. It has been quite useful during the
> starting stage to re-sync patches but at this point I think emails are more suited?
>

Sure.

-- 
Ross Lagerwall

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

      parent reply	other threads:[~2016-10-24 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 14:16 Livepatch for Xen 4.9 Konrad Rzeszutek Wilk
2016-10-03 14:37 ` Jan Beulich
2016-10-03 15:33 ` Andrew Cooper
2016-10-24 11:25 ` Ross Lagerwall [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=1f6c5ff1-827e-0e31-d54c-0ea9e473554e@citrix.com \
    --to=ross.lagerwall@citrix.com \
    --cc=Marcos.Matsunaga@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=mpohlack@amazon.com \
    --cc=xen-devel@lists.xensource.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).