From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org, hpa@zytor.com, mingo@redhat.com,
tglx@linutronix.de, boris.ostrovsky@oracle.com,
rusty@rustcorp.com.au, lguest@lists.ozlabs.org
Subject: Re: [PATCH 1/3] paravirt,xen: remove xen_patch()
Date: Thu, 10 Aug 2017 11:29:31 -0500 [thread overview]
Message-ID: <20170810162931.3sm5xumfu3y3su6d@treble> (raw)
In-Reply-To: <20170810125254.1347-2-jgross@suse.com>
On Thu, Aug 10, 2017 at 02:52:52PM +0200, 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 patches inline, so the special case never applies.
>
> As xen_patch() will call paravirt_patch_default() in all cases it can
> be just dropped.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Can the ENDPATCH and RELOC macros can also be removed, along with their
usages in xen-asm.S and xen-asm_64.S?
--
Josh
next prev parent reply other threads:[~2017-08-10 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 12:52 [PATCH 0/3] x86: paravirt related cleanup Juergen Gross
2017-08-10 12:52 ` [PATCH 1/3] paravirt,xen: remove xen_patch() Juergen Gross
2017-08-10 16:24 ` Peter Zijlstra
2017-08-10 16:29 ` Peter Zijlstra
2017-08-10 17:30 ` Juergen Gross
2017-08-10 16:29 ` Josh Poimboeuf [this message]
2017-08-10 12:52 ` [PATCH 2/3] x86/lguest: remove lguest support Juergen Gross
2017-08-10 12:52 ` [PATCH 3/3] x86/vsmp: remove vsmp paravirt support Juergen Gross
2017-08-10 15:28 ` Shai Fultheim (Shai@ScaleMP.com)
2017-08-10 15:30 ` Juergen Gross
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=20170810162931.3sm5xumfu3y3su6d@treble \
--to=jpoimboe@redhat.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).