From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH, resend] replacement for noirqdebug hack Date: Thu, 08 Jun 2006 09:00:40 +0200 Message-ID: <4487E738.76E4.0078.0@novell.com> References: <448028CD.76E4.0078.0@novell.com> <2d952ccdfba10b96dadf09495853dcdf@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2d952ccdfba10b96dadf09495853dcdf@cl.cam.ac.uk> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Keir Fraser 07.06.06 17:57 >>> > >How about the following patch, which is a cleaner modification to Linux >and does not affect shared_info layout? Note that it depends on a Xen >patch that is currently in the staging tree (extends the irq info >hypercall to inform about sharing status), and that the patch is >against xen-unstable. The status check is much slower than reading from >shared memory, but ought to be on a rare path (unless you have a >high-rate interrupt line shared across guests, which is going to be >rather suckful anyway). Yes, that looks fine to me (assuming that the other patch you mention is the one introducing PHYSDEVOP_irq_status_query, and that this is a non-intrusive addition). Jan