From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: VCPUOP_set_periodic_timer Date: Thu, 14 Nov 2013 21:39:21 +0000 Message-ID: <52854309.7000504@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3375937173085413434==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Simon Martin , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org --===============3375937173085413434== Content-Type: multipart/alternative; boundary="------------000403090804090907020000" --------------000403090804090907020000 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 14/11/2013 21:18, Simon Martin wrote: > Hi all, > > I need a periodic timer running at ideally at 125 microseconds and at > least 500 microseconds. I've just found the VCPUOP_set_periodic_timer, > however there is a comment saying "periods less than one millisecond > may not be supported". > > I will be running on an x64 machine. Is this supported? If not, is > there any alternate means of generating a fast interrupt? > > Regards. What is the usecase here? 125us is very short indeed. Xen certainly cant guarantee anything more accurate than 50us. Unless the affected vcpu is running uncontested on the hardware, there is very little chance that the vcpu will indeed be woken up again in 125us. It sounds as if you are looking for some pseudo realtime system, at which point you might want to consider a different scheduler. ~Andrew --------------000403090804090907020000 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
On 14/11/2013 21:18, Simon Martin wrote:
Hi all,
 
I need a periodic timer running at ideally at 125 microseconds and at least 500 microseconds. I've just found the VCPUOP_set_periodic_timer, however there is a comment saying "periods less than one millisecond may not be supported".
 
I will be running on an x64 machine. Is this supported? If not, is there any alternate means of generating a fast interrupt?
 
Regards.

What is the usecase here?  125us is very short indeed.  Xen certainly cant guarantee anything more accurate than 50us.  Unless the affected vcpu is running uncontested on the hardware, there is very little chance that the vcpu will indeed be woken up again in 125us.

It sounds as if you are looking for some pseudo realtime system, at which point you might want to consider a different scheduler.

~Andrew

--------------000403090804090907020000-- --===============3375937173085413434== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3375937173085413434==--