From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [RFC]degradation on IPF due to hypercall set irq Date: Wed, 22 Nov 2006 10:27:47 +0000 Message-ID: References: <51CFAB8CB6883745AE7B93B3E084EBE207DD55@pdsmsx412.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE207DD55@pdsmsx412.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Xu, Anthony" , Keir Fraser Cc: xen-devel@lists.xensource.com, xen-ia64-devel List-Id: xen-devel@lists.xenproject.org On 22/11/06 10:23, "Xu, Anthony" wrote: >> because it will require the shadow wire bitmap to be updated with >> atomic accesses and the multicall state to be per-thread or to be >> protected with a mutex. Each thread should flush multicall state >> before it blocks. > > I prefer atomic access, we used it in shared PIC. > If each thread flush multicall seperately, > There are some extra hypercalls. Since the threads run independently there seems little choice but for each to be able to flush. If the IDE DMA support had been properly integrated into the qemu select() event loop this would not be an issue. -- Keir