From: David Vrabel <david.vrabel@citrix.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
<david.vrabel@citrix.com>, <konrad.wilk@oracle.com>,
<boris.ostrovsky@oracle.com>, <xen-devel@lists.xenproject.org>
Cc: <kvm@vger.kernel.org>, "Luis R. Rodriguez" <mcgrof@suse.com>,
<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<rostedt@goodmis.org>, <paulmck@linux.vnet.ibm.com>
Subject: Re: [Xen-devel] [RFC v4 0/2] x86/xen: add xen hypercall preemption
Date: Fri, 23 Jan 2015 11:51:09 +0000 [thread overview]
Message-ID: <54C235AD.5010202@citrix.com> (raw)
In-Reply-To: <1421972951-3940-1-git-send-email-mcgrof@do-not-panic.com>
On 23/01/15 00:29, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>
> This v4 addresses some of the cleanups recommended and adds
> tracing option for when we do actually preempt a hypercall.
> I kept the NOKPROBE_SYMBOL() for now but did remove the 'notrace'
> stuff.
>
> This goes out as RFC still as I have not been able to test 32-bit.
> Can anyone test that or at least confirm that the 32-bit point
> we do the upcall is definitely not on the IRQ stack?
You can omit fixing this for 32-bit guests (provided you note as such in
the commit message).
David
next prev parent reply other threads:[~2015-01-23 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 0:29 [RFC v4 0/2] x86/xen: add xen hypercall preemption Luis R. Rodriguez
2015-01-23 0:29 ` [RFC v4 1/2] x86/xen: add xen_is_preemptible_hypercall() Luis R. Rodriguez
2015-01-23 1:40 ` Andy Lutomirski
2015-01-27 1:45 ` Luis R. Rodriguez
2015-01-23 11:30 ` [Xen-devel] " David Vrabel
2015-01-23 18:57 ` Luis R. Rodriguez
2015-01-23 0:29 ` [RFC v4 2/2] x86/xen: allow privcmd hypercalls to be preempted Luis R. Rodriguez
2015-01-23 1:40 ` Andy Lutomirski
2015-01-23 1:57 ` Steven Rostedt
2015-01-23 11:45 ` [Xen-devel] " David Vrabel
2015-01-23 18:58 ` Luis R. Rodriguez
2015-01-26 10:46 ` Jan Beulich
2015-01-26 10:47 ` David Vrabel
2015-01-23 19:16 ` Luis R. Rodriguez
2015-01-23 11:51 ` David Vrabel [this message]
2015-01-23 18:58 ` [Xen-devel] [RFC v4 0/2] x86/xen: add xen hypercall preemption Luis R. Rodriguez
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=54C235AD.5010202@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--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