From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"Luis R. Rodriguez" <mcgrof@suse.com>
Cc: <x86@kernel.org>, <kvm@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
<linux-kernel@vger.kernel.org>, Davidlohr Bueso <dbueso@suse.de>,
Joerg Roedel <jroedel@suse.de>, Jan Beulich <JBeulich@suse.com>,
<xen-devel@lists.xenproject.org>, <boris.ostrovsky@oracle.com>,
Borislav Petkov <bp@suse.de>, Olaf Hering <ohering@suse.de>
Subject: Re: [Xen-devel] [PATCH] xen: privcmd: schedule() after private hypercall when non CONFIG_PREEMPT
Date: Mon, 1 Dec 2014 11:01:18 +0000 [thread overview]
Message-ID: <547C4A7E.6020207@citrix.com> (raw)
In-Reply-To: <5477FECF.2060404@suse.com>
On 28/11/14 04:49, Juergen Gross wrote:
> On 11/27/2014 07:50 PM, Andrew Cooper wrote:
>>
>> XenServer uses
>>
>> https://github.com/xenserver/linux-3.x.pg/blob/master/master/0001-x86-xen-allow-privcmd-hypercalls-to-be-preempted.patch
>>
>>
>> to deal with these issues. That patch is based on 3.10.
>
> Clever. :-)
>
>>
>> I can remember whether this has been submitted upstream before (and
>> there were outstanding issues), or whether it fell at an inconvenient
>> time with our development cycles.
>
> I found
>
> http://lists.xen.org/archives/html/xen-devel/2014-02/msg02540.html
>
> and nothing else.
I dropped it because it copy-and-paste a bunch of otherwise generic x86
assembler and looked unlikely to get an x86 maintainer ack. If you
think otherwise, feel free to pick it up and run with it.
David
next prev parent reply other threads:[~2014-12-01 11:01 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 22:26 [PATCH] xen: privcmd: schedule() after private hypercall when non CONFIG_PREEMPT Luis R. Rodriguez
2014-11-27 6:36 ` Juergen Gross
2014-11-27 6:36 ` Juergen Gross
2014-11-27 18:36 ` Luis R. Rodriguez
2014-11-27 18:46 ` Luis R. Rodriguez
2014-11-27 18:46 ` Luis R. Rodriguez
2014-11-27 18:50 ` [Xen-devel] " Andrew Cooper
2014-11-28 4:49 ` Juergen Gross
2014-11-28 4:49 ` [Xen-devel] " Juergen Gross
2014-12-01 11:01 ` David Vrabel
2014-12-01 11:01 ` David Vrabel [this message]
2014-12-01 13:32 ` Luis R. Rodriguez
2014-12-01 13:32 ` [Xen-devel] " Luis R. Rodriguez
2014-12-01 14:42 ` Juergen Gross
2014-12-01 15:50 ` Luis R. Rodriguez
2014-12-01 15:50 ` [Xen-devel] " Luis R. Rodriguez
2014-12-01 14:42 ` Juergen Gross
2014-11-28 21:51 ` Luis R. Rodriguez
2014-11-28 21:51 ` [Xen-devel] " Luis R. Rodriguez
2014-11-27 18:50 ` Andrew Cooper
2014-12-01 11:11 ` David Vrabel
2014-12-01 11:11 ` David Vrabel
2014-12-01 15:05 ` Luis R. Rodriguez
2014-12-01 15:05 ` Luis R. Rodriguez
2014-12-01 15:18 ` David Vrabel
2014-12-01 15:44 ` Luis R. Rodriguez
2014-12-01 15:54 ` David Vrabel
2014-12-01 16:19 ` Luis R. Rodriguez
2014-12-01 17:07 ` Juergen Gross
2014-12-01 17:07 ` Juergen Gross
2014-12-01 17:52 ` Luis R. Rodriguez
2014-12-01 17:52 ` Luis R. Rodriguez
2014-12-01 18:16 ` [Xen-devel] " David Vrabel
2014-12-01 22:36 ` Luis R. Rodriguez
2014-12-01 22:36 ` [Xen-devel] " Luis R. Rodriguez
2014-12-02 11:11 ` David Vrabel
2014-12-02 11:11 ` [Xen-devel] " David Vrabel
2014-12-03 2:28 ` Luis R. Rodriguez
2014-12-03 4:37 ` Juergen Gross
2014-12-03 19:39 ` Luis R. Rodriguez
2014-12-05 16:20 ` Luis R. Rodriguez
2014-12-05 16:20 ` [Xen-devel] " Luis R. Rodriguez
2014-12-03 19:39 ` Luis R. Rodriguez
2014-12-03 4:37 ` Juergen Gross
2014-12-03 2:28 ` Luis R. Rodriguez
2014-12-01 18:16 ` David Vrabel
2014-12-01 16:19 ` Luis R. Rodriguez
2014-12-01 15:54 ` David Vrabel
2014-12-01 15:44 ` Luis R. Rodriguez
2014-12-01 15:18 ` David Vrabel
2014-11-27 18:36 ` 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=547C4A7E.6020207@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=dbueso@suse.de \
--cc=jgross@suse.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=ohering@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.