All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v4] KVM: VMX: Improve handle_external_interrupt_irqoff inline assembly
Date: Mon, 4 May 2020 08:33:43 -0700	[thread overview]
Message-ID: <20200504153343.GD16949@linux.intel.com> (raw)
In-Reply-To: <CAFULd4bWmcrsdfeyc++P9pGhn-MS703yWisKKmr601nAvP86gw@mail.gmail.com>

On Mon, May 04, 2020 at 05:32:19PM +0200, Uros Bizjak wrote:
> On Mon, May 4, 2020 at 5:25 PM Sean Christopherson
> <sean.j.christopherson@intel.com> wrote:
> >
> > On Mon, May 04, 2020 at 01:05:45AM +0200, Uros Bizjak wrote:
> > > Improve handle_external_interrupt_irqoff inline assembly in several ways:
> > > - use "re" operand constraint instead of "i" and remove
> > >   unneeded %c operand modifiers and "$" prefixes
> > > - use %rsp instead of _ASM_SP, since we are in CONFIG_X86_64 part
> > > - use $-16 immediate to align %rsp
> > > - remove unneeded use of __ASM_SIZE macro
> > > - define "ss" named operand only for X86_64
> > >
> > > The patch introduces no functional changes.
> >
> > Hmm, for handcoded assembly I would argue that the switch from "i" to "re"
> > is a functional change of sorts.  The switch also needs explicit
> > justification to explain why it's correct/desirable.  Maybe make it a
> > separate patch?
> 
> I think this would be a good idea. So, in this patch the first point should read
> 
> "- remove unneeded %c operand modifiers and "$" prefixes"
> 
> The add-on patch will then explain that PUSH can only handle signed
> 32bit immediates and change "i" to "re".
> 
> Is this what you had in mind?

Yep, exactly.

      reply	other threads:[~2020-05-04 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03 23:05 [PATCH v4] KVM: VMX: Improve handle_external_interrupt_irqoff inline assembly Uros Bizjak
2020-05-04 15:25 ` Sean Christopherson
2020-05-04 15:32   ` Uros Bizjak
2020-05-04 15:33     ` Sean Christopherson [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=20200504153343.GD16949@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=ubizjak@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.