From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Xen: do hv callback accounting only on x86
Date: Tue, 25 Mar 2014 17:00:21 +0100 [thread overview]
Message-ID: <12121341.4lKFpaRMcO@wuerfel> (raw)
In-Reply-To: <5057041.71iuvlcH4G@wuerfel>
On Tuesday 25 March 2014 16:52:25 Arnd Bergmann wrote:
> diff --git a/drivers/xen/events/events_base.c b/drivers/xen/events/events_base.c
> index 5dd2ddf..8b91c256 100644
> --- a/drivers/xen/events/events_base.c
> +++ b/drivers/xen/events/events_base.c
> @@ -1235,6 +1235,7 @@ void xen_evtchn_do_upcall(struct pt_regs *regs)
> #ifdef CONFIG_X86
> exit_idle();
> #endif
> + inc_irq_stat(irq_hv_callback_count);
>
> __xen_evtchn_do_upcall();
>
> diff --git a/drivers/xen/events/events_base.c b/drivers/xen/events/events_base.c
> index d5a3de8..dfa12a4 100644
> --- a/drivers/xen/events/events_base.c
> +++ b/drivers/xen/events/events_base.c
> @@ -1248,8 +1248,8 @@ void xen_evtchn_do_upcall(struct pt_regs *regs)
> irq_enter();
> #ifdef CONFIG_X86
> exit_idle();
> -#endif
> inc_irq_stat(irq_hv_callback_count);
> +#endif
>
> __xen_evtchn_do_upcall();
That was unintended: the first half of this email is actually the patch
that introduced the bug, while the second half is my workaround.
The way it's formatted, you won't be able to apply it without removing
the first half again. I'll wait if the approach is ok first and then
resend it properly if needed.
Arnd
next prev parent reply other threads:[~2014-03-25 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 15:52 [PATCH] Xen: do hv callback accounting only on x86 Arnd Bergmann
2014-03-25 16:00 ` Arnd Bergmann [this message]
2014-04-04 11:41 ` Julien Grall
2014-04-04 11:50 ` Julien Grall
2014-04-04 12:15 ` David Vrabel
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=12121341.4lKFpaRMcO@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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