[Xen-devel] Mini-OS as Dom0

[Oleksii Kurochko]

Hello.

I want to use Mini-OS as Dom0.

What should be done for this purpose?
Someone tried to do something like that? Maybe there are some patches.

With best regards,
 Oleksii
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [XenGT][IGVT-g] DomU pgt_device structure initialization

[Oleksii Kurochko]

Hello Greg,

Thanks for answer.

I am trying that you advice me.
Seems that there is same results.

Currently I am stopped this task, but if someone have more ideas why it can
be write please, Ill check.

Btw, I tried to look at /sys/kernel/debug/vgt/irqinfo and here seems all is
fine:

> --
>
> Interrupt control
> status:
> vGT: VLVDEISR is 10, VLVDEIIR is 0, VLVDEIMR is fffdff7f, VLVDEIER is
> 200f0
> vGT: DEISR is 0, DEIIR is 0, DEIMR is 0, DEIER is
> 8000
> vGT: SDEISR is 0, SDEIIR is 0, SDEIMR is 0, SDEIER is
> 0
> vGT: GTISR is 0, GTIIR is 0, GTIMR is 41, GTIER is
> 401001
> vGT: PMISR is 0, PMIIR is 0, PMIMR is 0, PMIER is
> 70
> vGT: RCS_IMR is , VCS_IMR is ffe00fff, BCS_IMR is
> 
> Total 207574 interrupts
> logged:
> #   WARNING: precisely this is the number of
> vGT
> #   physical interrupt handler be
> called,
> #   each calling several events can
> be
> #   been handled, so usually this
> number
> #   is less than the total events
> number.
> 4042: Render Command Streamer MI USER
> INTERRUPT
>1: Render MMIO sync flush
> status
>1: Video MMIO sync flush
> status
>  426: Blitter Command Streamer MI USER
> INTERRUPT
>1: Billter MMIO sync flush
> status
>   202447: Pipe A
> vblank
>38975: Render geyserville UP evaluation interval
> interrupt
> 1987: RP UP threshold
> interrupt
>   21: Render Frequency Downward Timeout During RC6
> interrupt
>   11740980876912: Last
> pirq
>   11740981018263: Last
> virq
>78066: Average pirq
> cycles
>15262: Average virq
> cycles
>   228105: Average delay between pirq/virq
> handling
>
>
> -->vgt-0:
>
> vreg (gtlc_mir: 8000, vlvier: 200f0, vlviir: 0, vlvimr: fffdff2f,
> vlvis)
> vreg (gtier: 401001, gtiir: 0, gtimr: 41, gtisr:
> 0)
> vreg (sdeier: 0, sdeiir: 0, sdeimr: 0, sdeisr:
> 0)
> vreg (pmier: 70, pmiir: 0, pmimr: 0, pmisr:
> 0)
> vreg (rcs_imr: , vcs_imr: 0, bcs_imr:
> 
>   11740981028847: Last
> injection
> Total 208373 virtual irq
> injection:
> 3399: Render Command Streamer MI USER
> INTERRUPT
>1: Render MMIO sync flush
> status
>1: Video MMIO sync flush
> status
>  405: Blitter Command Streamer MI USER
> INTERRUPT
>1: Billter MMIO sync flush
> status
>   202205: Pipe A
> vblank
> 2304: Primary Plane A flip
> done
>38642: Render geyserville UP evaluation interval
> interrupt
> 1737: RP UP threshold
> interrupt
>   21: Render Frequency Downward Timeout During RC6
> interrupt
>
>
> -->vgt-1:
>
> vreg (gtlc_mir: 8000, vlvier: 0, vlviir: 0, vlvimr: ,
> vlvisr: 0)
> vreg (gtier: 401001, gtiir: 0, gtimr: 41, gtisr:
> 0)
> vreg (sdeier: 0, sdeiir: 0, sdeimr: 0, sdeisr:
> 0)
> vreg (pmier: 0, pmiir: 0, pmimr: 0, pmisr:
> 0)
> vreg (rcs_imr: , vcs_imr: 0, bcs_imr:
> 
>9054347637006: Last
> injection
> Total 259251 virtual irq
> injection:
> 3359: Render Command Streamer MI USER
> INTERRUPT
>1: Render MMIO sync flush
> status
>1: Video MMIO sync flush
> status
>      174: Blitter Command Streamer MI USER
> INTERRUPT
>1: Billter MMIO sync flush
> status
>   391176: Pipe A
> vblank
> 3604: Primary Plane A flip
> done
>

With best regards,
 Oleksii



On Thu, Jan 21, 2016 at 8:56 PM, Dr. Greg Wettstein <g...@wind.enjellic.com>
wrote:

> On Jan 5, 10:04am, Oleksii Kurochko wrote:
> } Subject: Re: [Xen-devel] [XenGT][IGVT-g] DomU pgt_device structure
> initial
>
> > Hey.
>
> Hi Oleksii, I hope this note finds your day going well.
>
> > Strange for me was that I got vmid=0 and gen_type=0, so I decided go
> > to i915_gem_vgtbuffer_ioctl and write next at the start: if
> > (!xen_initial_domain()) { return -EPERM; } Also same code is in 3.17
> > kernel from XenGT-kernel repo.
> >
> > it seems that there is no more this error now( from vgt_fb_decoder ), BUT
> > there is often freeze or very laggy UI in guest.
> >
> > What it can be?
>
> It wasn't in this e-mail but I wen

Re: [Xen-devel] [XenGT][IGVT-g] DomU pgt_device structure initialization

[Oleksii Kurochko]

Hello.

Looks you didn’t set IRQ_INFO_GT for BCS event. Is it a typo?
>
Yeap, it was typo.

I will look at debug inforamtion that U told.

Thanks.

On Thu, Jan 14, 2016 at 7:44 AM, Tian, Kevin <kevin.t...@intel.com> wrote:

> if (IS_VLV(pdev)) {
>
>  SET_BIT_INFO(hstate, 2, RCS_MMIO_SYNC_FLUSH, IRQ_INFO_GT);
>
>  SET_BIT_INFO(hstate, 14, VCS_MMIO_SYNC_FLUSH, IRQ_INFO_GT);
>
>  SET_BIT_INFO(hstate, 24, BCS_MMIO_SYNC_FLUSH);
> }
>
>
>
> Looks you didn’t set IRQ_INFO_GT for BCS event. Is it a typo?
>
>
>
> Generally you can look at /sys/kernel/debug/vgt/irqinfo to see virtual
> event injection status, which may give some hint.
>
>
>
> In your log there is hangcheck triggered in Dom0:
>
> [   51.521359] vGT info:(vgt_handle_dom0_device_reset:940) DOM0 hangcheck
> timer request reset device.
>
> It means GPU is already hung.
>
>
>
> I don’t have an immediate idea now since this is only an experimental code
> and not sure how much your hardware is different from its assume
> configuration.
>
>
>
> A simpler case might be to just run some 3D workloads within Dom0 to see
> whether it works well, and then try launch another guest later.
>
>
>
> Thanks
>
> Kevin
>



-- 
Oleksii Kurochko | Embedded Dev
GlobalLogic
www.globallogic.com
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [XenGT][IGVT-g] DomU pgt_device structure initialization

[Oleksii Kurochko]

Hello.

I tried to fix next error message:
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [XenGT][IGVT-g] DomU pgt_device structure initialization

[Oleksii Kurochko]

Hello.

Thanks for answer.

About what agent are u talking about? I did not install anything
additional, just took vgt kernel and used it for Ubuntu distro.

I will look in events, thanks.

With the best regards,
Oleksii

On Mon, 11 Jan 2016, 07:07 Tian, Kevin  wrote:

> Did you install some specific agent within VM to utilize vgtbuffer ioctl
> interface? It’s not a bare metal i915 interface so suppose it shouldn’t be
> invoked for a default Linux distro environment. Yes we should add check to
> prevent it from being used within VM.
>
>
>
> However this error has nothing to do with your laggy UI issue. From my
> experience such issue is most likely being caused by losing interrupts. For
> example I saw below error message in your log (only partial line):
>
>
>
> [ 5412.902817] vGT error:(vgt_handle_events:1845) IRQ: abandon
> non-registered [)
>
> You can look into the event detail to see whether such event should be
> explicitly handled on your platform.
>
>
>
> Thanks
>
> Kevin
>
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [XenGT][IGVT-g] Device model creation failed

[Oleksii Kurochko]

Hello.

I tried to rebuild xen and qemu-xen (again *using patches from
byt_experimental branch*) and seems that now is going to show bios messages
and tried to start ubuntu, but when it starts it is very lagging.

I will create separate thread for discussing problem of ui lagging.

Thanks for help.

With best regards,
 Olesksii

On Sat, Jan 2, 2016 at 9:16 PM, Oleksii Kurochko <
oleksii.kuroc...@globallogic.com> wrote:

> Hello.
>
> I've tried byt_experimental branch and got some another result.
> With vgt=1 it failed with some time and got next log:
>
>> [ 4859.380332] vGT info:(create_vgt_instance:118) vm_id=21,
>> low_gm_sz=128MB, high_gm_sz=384MB, fence_sz=4, vgt_primary=1
>> [ 4859.389889] vGT info:(create_vgt_instance:170) Virtual GTT size:
>> 0x20
>> [ 4859.393284] VM21 Ring0 context_save_area is allocated at gm(f90d000)
>> [ 4859.416542] VM21 Ring1 context_save_area is allocated at gm(f94d000)
>> [ 4859.416916] VM21 Ring2 context_save_area is allocated at gm(f98d000)
>> [ 4859.417492] vGT info:(create_vgt_instance:206) aperture: [0xc780,
>> 0xcf7f] guest [0xc780, 0xcf7f] va(0xc9001820)
>> [ 4859.417971] vGT info:(create_vgt_instance:217) GM: [0x780,
>> 0xf7f], [0x2800, 0x3fff], guest[0x780, 0xf7f],
>> [0x2800, 0x3fff]
>> [ 4859.422914] vGT info:(create_vgt_instance:254) filling VGT_PVINFO_PAGE
>> for dom21:
>> [ 4859.422914]visable_gm_base=0x780, size=0x800
>> [ 4859.422914]hidden_gm_base=0x2800, size=0x1800
>> [ 4859.422914]fence_base=4, num=4
>> [ 4859.423521] vGT info:(vgt_hvm_io_req_handler:795) Received a IOREQ w/o
>> vcpu target
>> [ 4859.424042] vGT info:(vgt_hvm_io_req_handler:796) Possible a false
>> request from event binding
>> [ 4859.424555] vGT(1): create debugfs node: virtual_mmio_space
>> [ 4859.424713] vGT(1): create debugfs node: shadow_mmio_space
>> [ 4859.424883] vGT(1): create debugfs node: frame_buffer_format
>> [ 4859.425037] vGT(1): create debugfs node: frame_buffer_format
>> [ 4859.425974] vGT info:(vgt_emulation_thread:530) start kthread for VM21
>> [ 4859.426231] vGT info:(vgt_propagate_edid:770) EDID_PROPAGATE: Clear
>> PORT_A for vm 21
>> [ 4859.426508] vGT info:(vgt_propagate_edid:770) EDID_PROPAGATE: Clear
>> PORT_B for vm 21
>> [ 4859.426759] vGT info:(vgt_propagate_edid:770) EDID_PROPAGATE: Clear
>> PORT_C for vm 21
>> [ 4859.426992] vGT info:(vgt_propagate_edid:770) EDID_PROPAGATE: Clear
>> PORT_D for vm 21
>> [ 4859.427224] vGT info:(vgt_propagate_edid:770) EDID_PROPAGATE: Clear
>> PORT_E for vm 21
>> [ 4859.518800] vGT info:(vgt_vport_connection_store:595) Monitor
>> detection: PORT_A  is disconnected
>> [ 4859.567255] vGT info:(vgt_vport_connection_store:595) Monitor
>> detection: PORT_B  is disconnected
>> [ 4859.631077] vGT info:(vgt_vport_connection_store:595) Monitor
>> detection: PORT_C  is disconnected
>> [ 4859.682043] vGT info:(vgt_vport_connection_store:595) Monitor
>> detection: PORT_D  is disconnected
>> [ 4859.734223] vGT warning:(pch_adpa_mmio_write:1174)
>> HOTPLUG_FORCE_TRIGGER is set while VGA is enabled!
>> [ 4859.775194] vGT info:(vgt_vport_connection_store:583) Monitor
>> detection: PORT_E  is connected
>> [ 4860.111434] add_map: domid=21 gfn_s=0xc7800 mfn_s=0xc7800
>> nr_mfns=0x8000
>> [ 4933.642429] vGT warning:(vgt_hvm_vmem_init:301) VM21:
>> vmem_sz=0xf000!
>> [ 4943.772119] vGT warning:(vgt_emulate_read:355) vGT: untracked MMIO
>> read: vm_id(21), offset=0x4094,len=4, val=0x0!!! base_off=0x0
>> [ 4945.801949] vGT warning:(vgt_emulate_read:355) vGT: untracked MMIO
>> read: vm_id(21), offset=0x182110,len=4, val=0x0!!! base_off=0x2110
>> [ 4945.803030] vGT warning:(vgt_emulate_write:457) vGT: untracked MMIO
>> write: vm_id(21), offset=0x182110,len=4, val=0x0!!! base_off=0x2110
>> [ 4945.972045] vGT warning:(vgt_emulate_read:355) vGT: untracked MMIO
>> read: vm_id(21), offset=0x182110,len=4, val=0x0!!! base_off=0x2110
>> [ 4945.972649] vGT warning:(vgt_emulate_write:457) vGT: untracked MMIO
>> write: vm_id(21), offset=0x182110,len=4, val=0x1!!! base_off=0x2110
>> [ 4946.038157] vGT warning:(vgt_emulate_read:355) vGT: untracked MMIO
>> read: vm_id(21), offset=0x61204,len=4, val=0x0!!! base_off=0x0
>> [ 4946.039587] vGT warning:(vgt_emulate_write:457) vGT: untracked MMIO
>> write: vm_id(21), offset=0x61204,len=4, val=0xabcd!!! base_off=0x0
>> [ 4983.876827] vGT info:(vgt_handle_default_event_virt:947) IRQ: VM(21)
>> receive event (Blitter Command Streamer MI USER INTERRUPT)
>> [ 5023.070461] vGT error:(g2h_gm_range:

Re: [Xen-devel] [XenGT][IGVT-g] Device model creation failed

[Oleksii Kurochko]

ebug: libxl_dm.c:1257:libxl__spawn_local_dm:   -drive
> libxl: debug: libxl_dm.c:1257:libxl__spawn_local_dm:
> file=/home/vtc/Projects/system-10G.img,if=ide,index=0,media=disk,format=raw,cache=writeback
> libxl: debug: libxl_dm.c:1257:libxl__spawn_local_dm:   -drive
> libxl: debug: libxl_dm.c:1257:libxl__spawn_local_dm:
> if=ide,index=2,media=cdrom,cache=writeback,id=ide-5632
> libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
> w=0x1d96430 wpath=/local/domain/0/device-model/21/state token=3/0: register
> slotnum=3
> libxl: debug: libxl_create.c:1243:do_domain_create: ao 0x1da0060:
> inprogress: poller=0x1da0140, flags=i
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1d96430
> wpath=/local/domain/0/device-model/21/state token=3/0: event
> epath=/local/domain/0/device-model/21/state
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1d96430
> wpath=/local/domain/0/device-model/21/state token=3/0: event
> epath=/local/domain/0/device-model/21/state
> libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch
> w=0x1d96430 wpath=/local/domain/0/device-model/21/state token=3/0:
> deregister slotnum=3
> libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch
> w=0x1d96430: deregister unregistered
> libxl: debug: libxl_qmp.c:707:libxl__qmp_initialize: connected to
> /var/run/xen/qmp-libxl-21
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
> "execute": "qmp_capabilities",
> "id": 1
> }
> '
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
> "execute": "query-chardev",
> "id": 2
> }
> '
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
> "execute": "query-vnc",
> "id": 3
> }
> '
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_event.c:1737:libxl__ao_progress_report: ao 0x1da0060:
> progress report: ignored
> libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x1da0060:
> complete, rc=0
> libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x1da0060: destroy
> Daemon running with PID 5784
> xc: debug: hypercall buffer: total allocations:502 total releases:502
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
> xc: debug: hypercall buffer: cache current size:4
> xc: debug: hypercall buffer: cache hits:494 misses:4 toobig:4


Is it known issue?

With best regards,
 Oleksii

On Thu, Dec 31, 2015 at 2:56 AM, Tian, Kevin <kevin.t...@intel.com> wrote:

> What does Qemu log tell you about below error?
>
>
>
> libxl: error: libxl_dm.c:1531:device_model_spawn_outcome: domain 1 device 
> model: spawn failed (rc=-3)
>
>
>
> In the meantime, it’d be helpful if you can capture serial console output.
> If error comes from XenGT driver, there should be some useful information.
>
>
>
> btw, looks this VTC-1010 is based Baytrail. Please be noted that XenGT
> formally supports only Core based system. Atom SoC is not the target. We do
> have a BYT experimental porting (‘byt-experiment’ branch) on github, which
> is based on old code and not maintained anymore. You may want to try that
> branch instead.
>
>
>
> Thanks
>
> Kevin
>
>
>
> *From:* Oleksii Kurochko [mailto:oleksii.kuroc...@globallogic.com]
> *Sent:* Wednesday, December 30, 2015 8:56 PM
> *To:* igv...@lists.01.org; igv...@ml01.01.org; qemu-devel; Gerd Hoffmann;
> Li, Susie; Dong, Eddie; xen-devel@lists.xen.org; Tian, Kevin; Iurii
> Mykhalskyi
> *Subject:* [XenGT][IGVT-g] Device model creation failed
>
>
>
> Hello!
>
> We are going to use XenGT on Intel Atom based board(VTC-1010, with 4GB
> RAM).
>
> For this purpose we use next repos:
>
> xen - https://github.com/01org/Igvtg-xen
>
> dom0 (ubuntu linux, 1024MB or 2048MB ) -
> https://github.com/01org/Igvtg-kernel
>
> domU (android-x86, rest memory excluding xen heap, xen, about 1.7GB RAM )
> - same kernel, with some config changes
>
>
>
> Guest domain are going to be started in HVM mode.
>
> We follow iGVT-g setup guide (
> https://github.com/01org/Igvtg-kernel/blob/2015q3-3.18.0/iGVT-g_Setup_Guide.txt)
> and successfully setup dom0 with iGVT.
>
> But, when we are going to start domU (with enabled vgt=1 switch) domain
> creation failed with follow log:
>
> vtc@vtc-VTC1010:~$ sudo xl -vvv create -c ./a.cfg
>
> Parsing config from ./a.cf

[Xen-devel] [XenGT][IGVT-g] Device model creation failed

[Oleksii Kurochko]

in_create: ao 0x14c3190: inprogress: 
> poller=0x14c31f0, flags=i
> libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x14b9a20 
> wpath=/local/domain/0/device-model/1/state token=3/0: event 
> epath=/local/domain/0/device-model/1/state
> libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch 
> w=0x14b9a20 wpath=/local/domain/0/device-model/1/state token=3/0: deregister 
> slotnum=3
> libxl: error: libxl_dm.c:1531:device_model_spawn_outcome: domain 1 device 
> model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1319:domcreate_devmodel_started: device model 
> did not start: -3
> libxl: error: libxl_dm.c:1635:kill_device_model: Device Model already exited
> libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch 
> w=0x14bd010: deregister unregistered
> libxl: debug: libxl_event.c:1765:libxl__ao_complete: ao 0x14c3190: complete, 
> rc=-3
> libxl: debug: libxl_event.c:1737:libxl__ao__destroy: ao 0x14c3190: destroy
> xc: debug: hypercall buffer: total allocations:949 total releases:949
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
> xc: debug: hypercall buffer: cache current size:4
> xc: debug: hypercall buffer: cache hits:936 misses:4 toobig:9
>
>
Without this flag - are all ok, domain created and running normally.

Do you have any ideas about this issue?

Thank you.

-- 
Oleksii Kurochko | Embedded Dev
GlobalLogic
www.globallogic.com
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [iGVT-g] XenGT for PV guest

[Oleksii Kurochko]

Hello all,

Do you have any ideas about previously mentioned question?

With best regards,
 Oleksii

On Tue, Nov 24, 2015 at 6:48 PM, Oleksii Kurochko <
oleksii.kuroc...@globallogic.com> wrote:

> Hi all,
>
> I am trying to enable XenGT for Android on board vtc1010 in PV mode.
> Used:
> - Intel® Atom™ processor E3827
> - Xen 4.3.1 on branch "byt_experiment".
> - dom0: ubuntu 14-04 with linux vgt 3.11.6-vgt+ kernel version
> - domU: Android-IA 5.1 with 3.11.6-vgt+ (added Android configs)  kernel
> version
>
> vgt was successfully started in dom0.
> vgt does not start in domU. After registration of pci dev in i915_init()
> there is no call of i915_pci_driver.probe(). Inte HD Graphics is on pci
> bus, but it is not passthrough to domU. When tried to passtrough it to domU
> than dom0 crashes in drm_framebuffer_remove(). More than that it is not my
> case because of intel hd graphics need to be working in dom0 and domU.
>
> So could U give advice how to probe i915 driver in domU?
>
> With best,
>  Oleksii
>
>
> --
> Oleksii Kurochko | Embedded Dev
> GlobalLogic
> www.globallogic.com
>



-- 
Oleksii Kurochko | Embedded Dev
GlobalLogic
www.globallogic.com
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

[Xen-devel] [iGVT-g] XenGT for PV guest

[Oleksii Kurochko]

Hi all,

I am trying to enable XenGT for Android on board vtc1010 in PV mode.
Used:
- Intel® Atom™ processor E3827
- Xen 4.3.1 on branch "byt_experiment".
- dom0: ubuntu 14-04 with linux vgt 3.11.6-vgt+ kernel version
- domU: Android-IA 5.1 with 3.11.6-vgt+ (added Android configs)  kernel
version

vgt was successfully started in dom0.
vgt does not start in domU. After registration of pci dev in i915_init()
there is no call of i915_pci_driver.probe(). Inte HD Graphics is on pci
bus, but it is not passthrough to domU. When tried to passtrough it to domU
than dom0 crashes in drm_framebuffer_remove(). More than that it is not my
case because of intel hd graphics need to be working in dom0 and domU.

So could U give advice how to probe i915 driver in domU?

With best,
 Oleksii


-- 
Oleksii Kurochko | Embedded Dev
GlobalLogic
www.globallogic.com
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel