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] Re: logs attached. Re: [Xen-users] Can not findthe cdrom

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not findthe cdrom device in /dev/ afterbooted into xen(3.0.3)
From: Alan <alan@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 1 Dec 2006 19:58:36 +0000
Cc: Liang Yang <multisyncfe991@xxxxxxxxxxx>, "Petersson, Mats" <Mats.Petersson@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, tim.post@xxxxxxxxxxxxxxx, Keir Fraser <keir@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Dec 2006 11:52:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C19631F1.53B5%keir@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BAY125-DAV1296AC45C73817F49D092093DA0@xxxxxxx> <C19631F1.53B5%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 01 Dec 2006 19:24:33 +0000
Keir Fraser <keir@xxxxxxxxxxxxx> wrote:

> Looks like the I/O ports are allocated correctly to the device in both cases
> (both Xen and native). So I have no idea why the IDE PCI probing code isn't
> picking up on this. At this point I'd be adding tracing to the two kernels
> to find out where their probing paths diverge.

Looking over the current kernel code it is known to work in the non-Xen
case. The native mode on the ESB2 has other problems recently reported
but they would cause hangs later with stuck interrupts. Since I've got
bugs filed on this I know the detection works outside of Xen.

The old IDE probe code predates PCI so conveniently the PCI side of the
scan logic is all in setup-pci.c. Modules registering with ide during
init are added to a list and all run post init, modules added later get
their setup methods run immediately. Thus you can trace loading the piix
module pretty directly through idepci_register_driver and
ide_setup_pci_device, beyond that you are pretty much out of PCI territory

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

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