> On July 17, 2014, 9:35 a.m., Andreas Sandberg wrote:
> > I'm sorry I didn't spot this earlier, but it seems like you forgot to 
> > include the ethernet device's interrupt in the MP table. See the interrupt 
> > declaration for pci_dev4_inta for an example. Without that entry, Linux 
> > won't be able to setup interrupt routing properly.
> 
> Jiuyue Ma wrote:
>     We don't need anything in MP table, kernel can configure PCI device's 
> interrupt itself :)
>     Maybe only ISA device need a MP table entry?
>     
>     After apply 2314/2315/2310 and 2300(needed by 2.6.28.4; 2.6.22.9 did not 
> care this),
>     I can boot system and discover&configure ethernet device successfully.
>     
>     ----------------------- boot log ----------------------------
>     Intel(R) PRO/1000 Network Driver - version 7.3.20-k2Copyright (c) 
> 1999-2006 Intel Corporation.
>     PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
>     e1000: 0000:00:02.0: e1000_probe: (PCI:33MHz:32-bit) 00:90:00:00:00:01
>     e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
>     
>     ----------------------- config ----------------------------
>     loading script...
>     Script from M5 readfile is empty, starting bash shell...
>     (none) / # ifconfig eth0 192.168.0.1
>     ADDRCONF(NETDEV_UP): eth0: link is not ready
>     (none) / # e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full 
> Duplex, Flow Control: None
>     ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>     ifconfig lo 127.0.0.1
>     (none) / # ping 192.168.0.1
>     PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
>     64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.008 ms
>     
>     --- 192.168.0.1 ping statistics ---
>     1 packets transmitted, 1 received, 0% packet loss, time 0ms
>     rtt min/avg/max/mdev = 0.008/0.008/0.008/0.000 ms
> 
> Andreas Sandberg wrote:
>     It probably depends on the kernel version. I tested with 3.4.94 and got a 
> warning that the MP table was broken because it didn't find the interrupt 
> routing information for the ethernet device. I think the warning even stated 
> that the kernel was unable to figure out the interrupt.

fixed :)


- Jiuyue


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2301/#review5200
-----------------------------------------------------------


On July 18, 2014, 12:29 a.m., Jiuyue Ma wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/2301/
> -----------------------------------------------------------
> 
> (Updated July 18, 2014, 12:29 a.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> -------
> 
> config, x86: add ethernet support for x86 fullsystem
> 
> This patch add a IGbE_e1000 ethernet device to x86 fs system, it does
> the followings:
> 1) add IGbE_e1000 to x86_sys.pc.ethernet,
> 2) connect x86_sys.pc.ethernet.pio/config/dma to x86_sys.iobus,
> 3) add interrupt assignment for x86_sys.pc.ethernet in MP table.
> 
> 
> Diffs
> -----
> 
>   configs/common/FSConfig.py 878f2f30b12d38f619b80b5d80d52498946f6ad1 
> 
> Diff: http://reviews.gem5.org/r/2301/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Jiuyue Ma
> 
>

_______________________________________________
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to