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

Re: [Xen-devel] [PATCH] xen: implement vector callback for evtchn delive

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen: implement vector callback for evtchn delivery
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Fri, 28 May 2010 10:19:18 -0700 (PDT)
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Fri, 28 May 2010 10:20:40 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1275067159; bh=erXAo985QqpbH+J4mtBKX3qCE9n6kmgs4jnURCDu2v8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=fVxqPZOPQp+tpUVmKXTBlssaC0dIPs6JT4+xI9miH5eL465rIiRmL1almaEtf2tV5ScKyHVrdNs6THjNxNdg4mtHWd1nW0OTCBlq+JwLH8hGkThoefHpY2PujAA6x/zKiIYr4RSbrWgCF8laU9hRUWXf/RmzhQNIBDPWXFMO7wo=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=BzMzj0U18suONW9aTDrKy+8pQgikSa6AHqHFp4G74l8WSAm8ynsQE3QhtA4eFcrFgRoXhHWqEnyk+69rh3vtFBj3EusRBnA7tq1kOiApctiFn2U6Gg/hy6wmGVF2eSfGep3Tvs8MdnUojqOCxYMlOOeN6FRPxXNXH9S1VkNb1v4=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1005281821090.25605@kaball-desktop>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Got it.
Thank you.

--- On Fri, 5/28/10, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:

From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen: implement vector callback for evtchn delivery
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxxx>, "Stefano Stabellini" <Stefano.Stabellini@xxxxxxxxxxxxx>
Date: Friday, May 28, 2010, 1:21 PM

On Fri, 28 May 2010, Boris Derzhavets wrote:
> It stays the same as well as dmesg log been sent.
>
> root@LucidSRV:~# cat /proc/interrupts
>            CPU0       CPU1      
>   0:         30          0   IO-APIC-edge      timer
>   1:         29        102   IO-APIC-edge      i8042
>   4:          1          0   IO-APIC-edge   
>   6:          2          0   IO-APIC-edge      floppy
>   8:          0          0   IO-APIC-edge      rtc0
>   9:          0          0   IO-APIC-fasteoi   acpi
>  12:        325          7   IO-APIC-edge      i8042
>  14:          0          0   IO-APIC-edge      ata_piix
>  15:          0          0   IO-APIC-edge      ata_piix
>  16:        196          0   xen-dyn-event     xenbus
>  17:       5057          0   xen-dyn-event     blkif
>  18:        109          0   xen-dyn-event     eth0
>  23:          0          0   IO-APIC-fasteoi   uhci_hcd:usb1
>  36:          0          0   IO-APIC-fasteoi   Ensoniq AudioPCI
> NMI:          0          0   Non-maskable interrupts
> LOC:       2712       2532   Local timer interrupts
> SPU:          0          0   Spurious interrupts
> PMI:          0          0   Performance monitoring interrupts
> PND:          0          0   Performance pending work
> PLT:       5139          0   Platform interrupts
> RES:       1451       1562   Rescheduling interrupts
> CAL:        117        103   Function call interrupts
> TLB:        222        185   TLB shootdowns
> TRM:          0          0   Thermal event interrupts
> THR:          0          0   Threshold APIC interrupts
> MCE:          0          0   Machine check exceptions
> MCP:          1          1   Machine check polls
> ERR:          0
> MIS:          0
>
>
> Is it OK ?

Yep, no more interrupts for your ata_piix devices

-----Inline Attachment Follows-----

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

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