public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm64/kvm: use alternative auto-nop
Date: Thu, 8 Sep 2016 12:33:39 +0100	[thread overview]
Message-ID: <20160908113339.GB26570@leverpostej> (raw)
In-Reply-To: <20160908111648.GZ23592@cbox>

On Thu, Sep 08, 2016 at 01:16:48PM +0200, Christoffer Dall wrote:
> On Wed, Sep 07, 2016 at 11:07:10AM +0100, Mark Rutland wrote:
> > Make use of the new alternative_if and alternative_else_nop_endif and
> > get rid of our homebew NOP sleds, making the code simpler to read.
> 
> homebew?

Whoops. Should have been 'homebrew', though I'll change that to
'open-coded' to make this clearer.

> > Note that for __kvm_call_hyp the branch to __vhe_hyp_call has been moved
> > out of the alternative sequence, and in the default case there will be
> > four additional NOPs executed.
> > 
> > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > Cc: Marc Zyngier <marc.zyngier@arm.com>
> > Cc: Christoffer Dall <christoffer.dall@linaro.org>
> > Cc: kvmarm at lists.cs.columbia.edu
> 
> Acked-by: Christoffer Dall <christoffer.dall@linaro.org>

Cheers!

Mark.

      reply	other threads:[~2016-09-08 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 10:07 [PATCH 0/3] arm64: alternative: add auto-nop support Mark Rutland
2016-09-07 10:07 ` [PATCH 1/3] arm64: alternative: add auto-nop infrastructure Mark Rutland
2016-09-13  8:36   ` Ard Biesheuvel
2016-09-13  8:57     ` Mark Rutland
2016-09-13  8:59       ` Ard Biesheuvel
2016-09-07 10:07 ` [PATCH 2/3] arm64: use alternative auto-nop Mark Rutland
2016-09-07 10:07 ` [PATCH 3/3] arm64/kvm: " Mark Rutland
2016-09-08 11:16   ` Christoffer Dall
2016-09-08 11:33     ` Mark Rutland [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=20160908113339.GB26570@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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