From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org, lguest@lists.ozlabs.org
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com,
rusty@rustcorp.com.au
Subject: Re: [PATCH v2 1/2] paravirt,xen: remove xen_patch()
Date: Fri, 18 Aug 2017 09:22:31 -0400 [thread overview]
Message-ID: <0ad4eb2a-7935-e574-9485-638f98613452@oracle.com> (raw)
In-Reply-To: <20170816173157.8633-2-jgross@suse.com>
On 08/16/2017 01:31 PM, Juergen Gross wrote:
> Xen's paravirt patch function xen_patch() does some special casing for
> irq_ops functions to apply relocations when those functions can be
> patched inline instead of calls.
>
> Unfortunately none of the special case function replacements is small
> enough to be patched inline, so the special case never applies.
>
> As xen_patch() will call paravirt_patch_default() in all cases it can
> be just dropped. xen-asm.h doesn't seem necessary without xen_patch()
> as the only thing left in it would be the definition of XEN_EFLAGS_NMI
> used only once. So move that definition and remove xen-asm.h.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Applied to for-linus-4.14
-boris
next prev parent reply other threads:[~2017-08-18 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 17:31 [PATCH v2 0/2] x86: paravirt related cleanup Juergen Gross
2017-08-16 17:31 ` [PATCH v2 1/2] paravirt,xen: remove xen_patch() Juergen Gross
2017-08-16 19:16 ` Josh Poimboeuf
2017-08-18 13:22 ` Boris Ostrovsky [this message]
2017-08-24 8:25 ` [tip:x86/asm] x86/paravirt/xen: Remove xen_patch() tip-bot for Juergen Gross
2017-08-16 17:31 ` [PATCH v2 2/2] x86/lguest: remove lguest support Juergen Gross
2017-08-24 8:25 ` [tip:x86/asm] x86/lguest: Remove " tip-bot for Juergen Gross
2017-08-17 0:58 ` [PATCH v2 0/2] x86: paravirt related cleanup Rusty Russell
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=0ad4eb2a-7935-e574-9485-638f98613452@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=lguest@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®