All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH 0/2] clang: fixes for the indirect thunk
Date: Wed, 24 Jan 2018 15:48:47 +0000	[thread overview]
Message-ID: <20180124154849.84889-1-roger.pau@citrix.com> (raw)

Hello,

The following two patches fix building Xen with clang and the indirect
thunk.

Patch 2 is not strictly needed, because when building with clang we
still compile assembly only files with -no-integrated-as, but it's a
nice to have so that we don't regress more in assembly only code.

Thanks, Roger.

Roger Pau Monne (2):
  x86/clang: fix build with indirect thunks
  x86: fix indirect thunk usage of CONFIG_INDIRECT_THUNK

 xen/Rules.mk                           |  6 ++++--
 xen/arch/x86/extable.c                 |  3 ++-
 xen/arch/x86/x86_emulate/x86_emulate.c |  3 ++-
 xen/common/wait.c                      |  1 +
 xen/include/asm-x86/asm_defns.h        | 10 +++++++---
 5 files changed, 16 insertions(+), 7 deletions(-)

-- 
2.15.1


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

             reply	other threads:[~2018-01-24 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 15:48 Roger Pau Monne [this message]
2018-01-24 15:48 ` [PATCH 1/2] x86/clang: fix build with indirect thunks Roger Pau Monne
2018-01-24 16:40   ` Jan Beulich
2018-01-24 17:06     ` Roger Pau Monné
2018-01-25  9:39       ` Jan Beulich
2018-01-25  9:50         ` Roger Pau Monné
2018-01-24 15:48 ` [PATCH 2/2] x86: fix indirect thunk usage of CONFIG_INDIRECT_THUNK Roger Pau Monne
2018-01-24 16:23   ` Jan Beulich
2018-01-24 16:52     ` Roger Pau Monné
2018-01-25 10:13       ` Jan Beulich
2018-01-25 10:15       ` Roger Pau Monné

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=20180124154849.84889-1-roger.pau@citrix.com \
    --to=roger.pau@citrix.com \
    --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 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.