From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org,
Julien Grall <julien.grall@arm.com>,
Steve Capper <Steve.Capper@arm.com>
Subject: Re: [Very RFC PATCH] Livepatch - initial ARM64/32 support.
Date: Thu, 11 Aug 2016 19:08:39 -0400 [thread overview]
Message-ID: <20160811230839.GA20798@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.10.1608111201220.25028@sstabellini-ThinkPad-X260>
On Thu, Aug 11, 2016 at 12:05:33PM -0700, Stefano Stabellini wrote:
> On Thu, 11 Aug 2016, Julien Grall wrote:
> > On 09/08/2016 06:18, Konrad Rzeszutek Wilk wrote:
> > > Hey!
> >
> > Hi Konrad,
> >
> > > Over the last couple of months in my spare time I was playing
> > > with making livepatch work with ARM64 (using the FoundationModel
> > > simulator) and I finally got it working tonight.
> >
> > Congrats!
>
> Indeed, congratulations! I hope it was fun :-)
Yes!
>
>
> > > Sending out the patches just in case they don't work tomorrow :-)
> > >
> > > The ARM32 part is going slowly - as I don't have a simulator
> > > and using a real board takes time.
> >
> > Whilst I can see usage of livepatch for Xen ARM64 (e.g server), I am less
> > convinced for ARM32. I am bit worry to check-in code that will get rotten in
> > the long term. So do you see any usage on ARM32?
>
> Actually I think it is useful for embedded use cases too: think about
> security updates for any embedded devices which cannot easily be
> rebooted. Or even if they can be rebooted, it might create a
> competitive advantage to build a car that can be updated for critical
> security fixes without requesting the driver to stop.
My 'usage' is that ARM32 is the only board ARM board I've that
boots and runs without issues :-)
Either way the idea is that the test-cases will work on both
ARM32/ARM64/x86 - and I do plan to have them as part of OSSTest - so
I am not that afraid of the bitrotten part.
However for simplicity and review I will redo the patches without the
ARM32 part (the ELF part is the headache one) and keep on poking
at them until I get ARM32 working all the way (probably Xen 4.9 material).
And it was fun learning the opcodes, thought I still have much to learn.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-11 23:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 4:18 [Very RFC PATCH] Livepatch - initial ARM64/32 support Konrad Rzeszutek Wilk
2016-08-09 4:18 ` [Very RFC PATCH 1/3] mm/arm: Introduce modify_xen_mappings Konrad Rzeszutek Wilk
2016-08-09 4:18 ` [Very RFC PATCH 2/3] insn: Add arch64_insn_gen_branch_imm to generate branch Konrad Rzeszutek Wilk
2016-08-11 16:03 ` Julien Grall
2016-08-09 4:19 ` [Very RFC PATCH 3/3] livepatch: Initial ARM32/64 support Konrad Rzeszutek Wilk
2016-08-12 15:00 ` Julien Grall
2016-08-12 20:50 ` Konrad Rzeszutek Wilk
2016-08-15 13:27 ` Julien Grall
2016-08-15 15:04 ` Konrad Rzeszutek Wilk
2016-08-09 4:24 ` [Very RFC PATCH] Livepatch - initial ARM64/32 support Konrad Rzeszutek Wilk
2016-08-11 16:28 ` Julien Grall
2016-08-11 19:05 ` Stefano Stabellini
2016-08-11 23:08 ` Konrad Rzeszutek Wilk [this message]
2016-08-12 8:08 ` 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=20160811230839.GA20798@localhost.localdomain \
--to=konrad@kernel.org \
--cc=Steve.Capper@arm.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).