[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [PATCH] ioemu: Cleanup the code of PCI passthrough.


  • To: Simon Horman <horms@xxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Mon, 23 Feb 2009 06:23:45 -0800 (PST)
  • Cc: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 23 Feb 2009 06:24:14 -0800
  • 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:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=NG3p6RaKikxq4iPB0NeSwFgMgbB9jvcPIcwf3qGRxLVBFzoQ7hv2I7zzNnz+WYZSFVWU2AKosQc0pwlOVhxtwAbFbOoxxq/Tru5rahPUeaRfqu0cXDGD1+8bhChKjYdeuh3mZqi7y+93lX+LT1YIls+hiOCXjdTjCP0LfahQ7Ug=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

 I was under impression, that mentioned patch is supposed to support
loading HVM DomU (?).  If answer is "yes" , then my question:-
When http://xenbits.xensource.com/xen-unstable.hg will get this update?
Looks like "make tools" is using http://xenbits.xensource.com/git-http/qemu-xen-unstable.git when building xen-unstable.hg/tools/ioemu-remote.
If answer is "no", i am sorry for misunderstanding.

  Fresh Xen-Unstable Dom0 install (along with the most recent build
2.6.29-rc5) still shows during attempt to start HVM DomU:-

# xm dmesg
. . . . . .
(XEN) HVM1: HVM Loader
(XEN) HVM1: Detected Xen v3.4-unstable
(XEN) HVM1: CPU speed is 3006 MHz
(XEN) irq.c:235: Dom1 PCI link 0 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:235: Dom1 PCI link 1 changed 0 -> 10
(XEN) HVM1: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:235: Dom1 PCI link 2 changed 0 -> 11
(XEN) HVM1: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:235: Dom1 PCI link 3 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 3 routed to IRQ5
(XEN) HVM1: pci dev 01:2 INTD->IRQ5
(XEN) HVM1: pci dev 01:3 INTA->IRQ10
(XEN) HVM1: pci dev 03:0 INTA->IRQ5
(XEN) HVM1: pci dev 04:0 INTA->IRQ5
(XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f3000000
(XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM1: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM1: pci dev 04:0 bar 14 size 00000100: f3001000
(XEN) HVM1: pci dev 01:2 bar 20 size 00000020: 0000c201
(XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c221
(XEN) HVM1: Multiprocessor initialisation:
(XEN) HVM1:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1: Testing HVM environment:
(XEN) HVM1:  - REP INSB across page boundaries ... passed
(XEN) HVM1: Passed 1/1 tests
(XEN) HVM1: Writing SMBIOS tables ...
(XEN) HVM1: Loading ROMBIOS ...
(XEN) HVM1: 9788 bytes of ROMBIOS high-memory extensions:
(XEN) HVM1:   Relocating to 0xfc000000-0xfc00263c ... done
(XEN) HVM1: Creating MP tables ...
(XEN) HVM1: Loading Cirrus VGABIOS ...
(XEN) HVM1: Loading PCI Option ROM ...
(XEN) HVM1:  - Manufacturer: http://etherboot.org
(XEN) HVM1:  - Product name: gPXE
(XEN) HVM1: Loading ACPI ...


********************************
Logfile under /var/log/xen :-
********************************

domid: 1
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap1.0 eth0
Watching /local/domain/0/device-model/1/logdirty/next-active
Watching /local/domain/0/device-model/1/command
xs_read(): vncpasswd get error. /vm/1388b5b0-3888-5c75-b701-3e82249a379e/vncpasswd.
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 1388b5b0-3888-5c75-b701-3e82249a379e
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error
medium change watch on `hdc' (index: 0): /dev/loop0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
cirrus vga map change while on lfb mode


 

--- On Mon, 2/23/09, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] ioemu: Cleanup the code of PCI passthrough.
To: "Simon Horman" <horms@xxxxxxxxxxxx>
Cc: "Yuji Shimada" <shimada-yxb@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Monday, February 23, 2009, 6:36 AM

Simon Horman writes ("Re: [Xen-devel] Re: [PATCH] ioemu: Cleanup the code
of PCI passthrough."):
> On Mon, Feb 23, 2009 at 10:40:22AM +0900, Yuji Shimada wrote:
> > Signed-off-by: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>
>
> Tested-by: Simon Horman <horms@xxxxxxxxxxxx>

Thanks, I have applied this.

The problem causing it to be rejected was that hw/passthrough.[ch] and
hw/pt-msi.[ch] were full of trailing whitespace, which Yuji Shimada's
mailer evidently removes. I think the mailer was right and the code
was wrong.

So I have removed all of that trailing whitespace with a trivial perl
one-liner and then committed the cleanup patch on top. I haven't
tested the pass-through but the tree does build.

Ian.

_______________________________________________
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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.