From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Jiang Liu <liuj97@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Gleb Natapov <gleb@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Wang YanQing <udknight@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arch@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
Yang Zhang <yang.z.zhang@Intel.com>,
xen-devel@lists.xenproject.org, Ingo Molnar <mingo@elte.hu>,
Shaohua Li <shli@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>,
xen-devel@lists.xensource.com, Al Viro <viro@zeniv.linux.org.uk>,
Jiri Kosina <trivial@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
virtualization@lists.linux-foundation.org,
Seiji Aguchi <seiji.aguchi@hds.com>,
linux-kernel@vger.kernel.org, David
Subject: Re: [RFC PATCH v3 19/19] smp, x86: kill SMP single function call interrupt
Date: Wed, 11 Dec 2013 23:10:11 +0100 [thread overview]
Message-ID: <20131211221011.GA26423@breakpoint.cc> (raw)
In-Reply-To: <1386173591-28514-20-git-send-email-liuj97@gmail.com>
On 05.12.13, Jiang Liu wrote:
I like this in general however
> diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
> index 7cf1689..f241792 100644
> --- a/arch/x86/xen/smp.c
> +++ b/arch/x86/xen/smp.c
> @@ -560,7 +560,6 @@ static inline int xen_map_vector(int vector)
> xen_vector = XEN_RESCHEDULE_VECTOR;
> break;
> case CALL_FUNCTION_VECTOR:
> - case CALL_FUNCTION_SINGLE_VECTOR:
> xen_vector = XEN_CALL_FUNCTION_VECTOR;
> break;
> case IRQ_WORK_VECTOR:
This chunk does not apply again tip's master branch, the code looks
different. You need to also kill XEN_CALL_FUNCTION_SINGLE_VECTOR which
is either part of a different patch or against a different tree. I
haven't seen a note in 0/19 or this patch description so I'm confused
here :)
Sebastian
next prev parent reply other threads:[~2013-12-11 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1386173591-28514-1-git-send-email-liuj97@gmail.com>
2013-12-04 16:13 ` [RFC PATCH v3 18/19] smp, tile: kill SMP single function call interrupt Jiang Liu
2013-12-04 16:13 ` [RFC PATCH v3 19/19] smp, x86: " Jiang Liu
2013-12-11 22:10 ` Sebastian Andrzej Siewior [this message]
2013-12-15 15:49 ` Jiang Liu
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=20131211221011.GA26423@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=seiji.aguchi@hds.com \
--cc=shli@kernel.org \
--cc=tglx@linutronix.de \
--cc=trivial@kernel.org \
--cc=udknight@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@Intel.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 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).