[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57038D8B.9050602@citrix.com>
Date: Tue, 5 Apr 2016 11:03:55 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: Juergen Gross <jgross@...e.com>, <linux-kernel@...r.kernel.org>,
<xen-devel@...ts.xenproject.org>
CC: <jeremy@...p.org>, <jdelvare@...e.com>, <peterz@...radead.org>,
<hpa@...or.com>, <akataria@...are.com>, <x86@...nel.org>,
<rusty@...tcorp.com.au>,
<virtualization@...ts.linux-foundation.org>, <chrisw@...s-sol.org>,
<mingo@...hat.com>, <Douglas_Warzecha@...l.com>,
<pali.rohar@...il.com>, <boris.ostrovsky@...cle.com>,
<tglx@...utronix.de>, <linux@...ck-us.net>
Subject: Re: [Xen-devel] [PATCH v4 4/6] xen: add xen_pin_vcpu() to support
calling functions on a dedicated pcpu
On 05/04/16 11:01, Juergen Gross wrote:
>
> No, I don't think this is a good idea. In the EINVAL or EBUSY case a
> simple Xen admin command might be enough to make the next call succeed.
> I don't want to disable pinning in this case.
Ok.
Acked-by: David Vrabel <david.vrabel@...rix.com>
David
Powered by blists - more mailing lists