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

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

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 ?

Boris.


--- 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, 12:55 PM

On Fri, 28 May 2010, Boris Derzhavets wrote:
> I redefined DomU via profile :-
>
> <domain type='xen' >
>   <name>LucidHVM</name>
>   <memory>2097152</memory>
>   <currentMemory>2097152</currentMemory>
>   <vcpu>2</vcpu>
>   <os>
>     <type>hvm</type>
>     <loader>/usr/lib/xen/boot/hvmloader</loader>
>     <boot dev='hd'/>
>   </os>
>   <features>
>     <acpi/>
>     <apic/>
>     <pae/>
>   </features>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>restart</on_crash>
>   <devices>
>     <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
>     <disk type='block' device='disk'>
>       <driver name='phy'/>
>       <source dev='/dev/sda7'/>
>       <target dev='xvda' bus='xen'/>   - instead of 'ide'
>     </disk>
>     <interface type='bridge'>
>       <mac address='00:16:36:2a:cd:af'/>
>       <source bridge='br0'/>
>       <script path='/etc/xen/scripts/vif-bridge'/>
>       <target dev='vif1.0'/>
>     </interface>
>     <serial type='pty'>
>       <source path='/dev/pts/0'/>
>       <target port='0'/>
>     </serial>
>     <console type='pty' tty='/dev/pts/0'>
>       <source path='/dev/pts/0'/>
>       <target port='0'/>
>     </console>
>     <input type='mouse' bus='ps2'/>
>     <graphics type='vnc' port='5900' autoport='yes' keymap='en-us'/>
>     <sound model='es1370'/>
>   </devices>
> </domain>
>
> dmesg.log is attached.
>

I think it should be OK now

-----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