xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Julien Grall <julien.grall@arm.com>
Cc: sstabellini@kernel.org, xen-devel@lists.xen.org
Subject: Re: [PATCH] xen/arm: alternative: Make it possible to patch outside of the hypervisor
Date: Tue, 6 Sep 2016 23:06:00 -0400	[thread overview]
Message-ID: <20160907030600.GB7512@char.us.oracle.com> (raw)
In-Reply-To: <20160906192532.GA22795@char.us.oracle.com>

> > ---
> >  xen/arch/arm/alternative.c | 58 +++++++++++++++++++++++++---------------------
> >  1 file changed, 31 insertions(+), 27 deletions(-)
> > 
> > diff --git a/xen/arch/arm/alternative.c b/xen/arch/arm/alternative.c
> > index 8ee5a11..db4bd0f 100644
> > --- a/xen/arch/arm/alternative.c
> > +++ b/xen/arch/arm/alternative.c
> > @@ -97,26 +97,11 @@ static u32 get_alt_insn(const struct alt_instr *alt,
> >  static int __apply_alternatives(const struct alt_region *region)
> >  {
> >      const struct alt_instr *alt;
> > -    const u32 *origptr, *replptr;
> > -    u32 *writeptr, *writemap;
> > -    mfn_t text_mfn = _mfn(virt_to_mfn(_stext));
> > -    unsigned int text_order = get_order_from_bytes(_end - _start);
> > +    const u32 *replptr;
> > +    u32 *origptr;
> >  
> >      printk(XENLOG_INFO "alternatives: Patching kernel code\n");

This is still there. Should it be "Patching %p->%p code" instead?


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

  reply	other threads:[~2016-09-07  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01  7:56 [PATCH] xen/arm: alternative: Make it possible to patch outside of the hypervisor Julien Grall
2016-09-06 19:25 ` Konrad Rzeszutek Wilk
2016-09-07  3:06   ` Konrad Rzeszutek Wilk [this message]
2016-09-07 11:36     ` Julien Grall
2016-09-07  6:52   ` 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=20160907030600.GB7512@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=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).