WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [RFC][PATCH 08/10] x86: Don't ack_APIC_irq() if lapic is

To: Sheng Yang <sheng@xxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Eddie Dong <eddie.dong@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [RFC][PATCH 08/10] x86: Don't ack_APIC_irq() if lapic is disabled in GENERIC_INTERRUPT_VECTOR handler
From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
Date: Wed, 16 Sep 2009 13:37:31 +0400
Cc:
Delivery-date: Wed, 16 Sep 2009 02:41:14 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=LrNfIkDwX8N5K2SaGx0Vn5GSqP5cTbsT79QYzJh0z7A=; b=hMNfMZfeLwPxZAGXEVNOyoCemzNyV7/1CzYTPW8ICsnvgdQIkybDZqpI1/AvKieISO Q7WPMK0TibGQU5s7l9XUSTJDUbMonJTuPmyCwr2PQcdKCCvu/mDDi8nI/GRZY7oUMwAS phwTQa74OuapU6a4cNsmy5+62EOMdP/m9NSQI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=ZNUV+2SptR/3cfuqp2Gp7sJy14fZ3pqJJRPFV9mw/y4T5tmnUo2IVbbADgDj6wdifw 8/6pbaMo7u0x+eQq1QseSz1J2bxSiaAVpKOYPfSxv1QltjGnhg22vaH+Rpq+UADlnv57 qNusGLXjcXJ7ONbARW2yvP8OTmuWuUGcSc54k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090916090306.GF5094@lenovo>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1253090551-7969-1-git-send-email-sheng@xxxxxxxxxxxxxxx> <1253090551-7969-9-git-send-email-sheng@xxxxxxxxxxxxxxx> <20090916085835.GE5094@lenovo> <20090916090306.GF5094@lenovo>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
[Cyrill Gorcunov - Wed, Sep 16, 2009 at 01:03:06PM +0400]
| [Cyrill Gorcunov - Wed, Sep 16, 2009 at 12:58:35PM +0400]
| ...
| | 
| | Hi Sheng,
| | 
| | is there was some problem with it? I'm asking you
| | because if disable_apic=1 then any apic write/read
| | operations become NOPs. So I don't see how it may
| | hurt. But I could be missing something.
| |  
| |     -- Cyrill
| 
| Ah, I see -- it's due to your other patch...
| Hmm this makes all "disable apic" idea less
| general. And safety of ack_APIC_irq is now
| under suspicious.
| 
|       -- Cyrill

And how msi_compose_msg would work then?

Don't get me wrong please, I'm just trying to understand.
Perhaps Xen specifics will handle it (I didn't read Xen
internals) by substituting all this with own handler.

Since comments are requested I thought I may ask? :)

        -- Cyrill

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>