From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen: Fix xen_flush_tlb_others
Date: Fri, 13 Feb 2009 13:54:37 +0100 [thread overview]
Message-ID: <20090213125437.GE5483@elte.hu> (raw)
In-Reply-To: <4994BE06.4040006@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> From: Ian Campbell <Ian.Campbell@citrix.com>
>
> xen: Fix xen_flush_tlb_others
> The commit
> commit 4595f9620cda8a1e973588e743cf5f8436dd20c6
> Author: Rusty Russell <rusty@rustcorp.com.au>
> Date: Sat Jan 10 21:58:09 2009 -0800
> x86: change flush_tlb_others to take a const struct cpumask
> causes xen_flush_tlb_others to allocate a multicall and then issue
applied to tip:x86/paravirt, thanks Jeremy!
Ingo
prev parent reply other threads:[~2009-02-13 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 0:25 [PATCH] xen: Fix xen_flush_tlb_others Jeremy Fitzhardinge
2009-02-13 12:54 ` Ingo Molnar [this message]
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=20090213125437.GE5483@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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