From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH v16 01/10] x86: add generic resource (e.g. MSR) access hypercall Date: Fri, 26 Sep 2014 09:28:21 +0100 Message-ID: <54253FC5020000780003977A@mail.emea.novell.com> References: <1411640350-26155-1-git-send-email-chao.p.peng@linux.intel.com> <1411640350-26155-2-git-send-email-chao.p.peng@linux.intel.com> <542473B2.5040504@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <542473B2.5040504@citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , Chao Peng , xen-devel@lists.xen.org Cc: keir@xen.org, Ian.Campbell@citrix.com, George.Dunlap@eu.citrix.com, stefano.stabellini@eu.citrix.com, Ian.Jackson@eu.citrix.com, dgdegra@tycho.nsa.gov List-Id: xen-devel@lists.xenproject.org >>> On 25.09.14 at 21:57, wrote: > On a different note, you need to enforce a maximum resource_op.nr of > something rather low to (16/32 perhaps?) to prevent a toolstack asking > for 0xffffffff non-preemptible operations. I'd start out as low as we can, i.e. right now just 2 (write followed by read). Any increase of the threshold will then need proper (and trackable) reasoning. Jan