Hello,
Here is the results:
$ sudo lspci -vvvxxx -s 37:09.0
37:09.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213
Wireless Network Adapter (rev 01)
Subsystem: D-Link System Inc AirPlus DWL-G520 Wireless PCI Adapter
(rev. B)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 0: Memory at e3000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
Kernel driver in use: ath5k
00: 8c 16 13 00 06 01 90 02 01 00 00 02 10 a8 00 00
10: 00 00 00 e3 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 01 50 00 00 86 11 13 3a
30: 00 00 00 00 44 00 00 00 00 00 00 00 03 01 0a 1c
40: 00 00 00 00 01 00 c2 01 00 40 00 c6 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
And then:
$ sudo setpci -s 37:09.0 CONTROL
setpci: Unknown register "CONTROL".
Try `setpci --help' for more information.
So:
$ setpci --dumpregs | grep -i control
3e W BRIDGE_CONTROL
Your parameter "CONTROL" does not exist !!!
I guess I have to use: BRIDGE_CONTROL ???
$ sudo setpci -s 37:09.0 BRIDGE_CONTROL
1c0a
$ printf "%x\n" $((0x1c0a | 0x0400))
1c0a
Nothing to do !!!
is it normal ???
but I try:
$ sudo setpci -s 37:09.0 BRIDGE_CONTROL=0x1c0a
And:
$ sudo setpci -s 37:09.0 BRIDGE_CONTROL
1c0a
OK, seems to be good. I hope ???
Now, how can I pass the argument "prefer_msi" and/or "share_intx" to the
guest VM, in the xml file ??
I found nothing on the web, doc., ... !!!!!!!!
I did not find too, how to convert a xml guest file to a CLI !
I try to peek up the one in the log, but this does not work !
Here it is:
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M
pc-1.1 -enable-kvm -m 1024 -smp 1,sockets=1,cores=
1,threads=1 -name android_4_0 -uuid 65471d1a-613d-9046-94ce-2d57e234033e
-nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/android_4_0.monitor,server,nowait
-mon cha
rdev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-no-acpi -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/etc/libvirt/qemu/android_4_0.img,if=none,id=drive-ide0-
0-0,format=raw -device
ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device
ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1
-0,id=ide0-1-0 -chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus
-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-
codec0,bus=sound0.0,cad=0 -device
pci-assign,host=37:09.0,id=hostdev0,configfd=25,bus=pci.0,addr=0x3
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
And now ?
/Michaël C.
Le 19/09/2012 17:03, Michael Tokarev a écrit :
> On 17.09.2012 17:30, Chlon Michaël wrote:
>> Good Evening,
>>
>>
>> Well, in fact, it is *an issue with shared IRQ*.
>> I wonder if there is a mean to pass to the kernel a fixed IRQ for
>> this PCI device, at boot for example. I haven't find anything ...
>> I have also stop my server, change physically the port of the
>> WiFi card, but after reboot it's remain shared ... with an
>> another IRQ, but shared! :'(
>> Here there is:
>>
>> $ cat /proc/interrupts
>> 21: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi uhci_hcd:usb4, uhci_hcd:usb7, ath
> Ok. Please provide lspci -vvvxxx output for this
> device. Take a look at lspci, note the device number
> (left column), and do
>
> lspci -vvvxxx -s <device>
>
> like, for a random my device, "lspci -xxxvvv -s 02:00.0",
> and send the result.
>
> It might be that the device itself does not support irq
> sharing in this mode. qemu-kvm wants devices which
> either support MSI (in this case everything should just
> work, and is fast, if the device is not buggy to start
> with), or by disabling using legacy INTx by config register
> setup.
>
> You can check if the device supports the 2nd mode by writing
> bit 10 (0x0400) to CONTROL register using setpci and verifying
> (using setpci again) it is set by reading it again. For
> this:
>
> setpci -s <device> CONTROL
>
> this will return a hexadecimal number. Or it with 0x0400,
> eg, like this:
>
> printf "%x\n" $((0x<prev_value> | 0x0400))
>
> and write it back:
>
> setpci -s <device> CONTROL=<newvalue>
>
> and read it again:
>
> setpci -s <device> CONTROL
>
> If the new value is the same what you set above, it has
> some chance to work.
>
> Now, There are two parameters for -device pci-assign --
> prefer_msi and share_intx. You can experiment with the
> two - prefer_msi is now off, but if your device supports
> msi, you can turn it on. share_intx is also an on/off
> switch.
>
> Please post your findings.
>
> Thanks,
>
> /mjt
*Michaël Chlon* |/mic.a.elle.ch...@gmail.com/
My profiles: LinkedIn
<http://Type%20your%20personal%20details%20here.%20Click%20on%20Templates%20for%20a%20quick%20start%21>
Want a signature like mine?
<http://r1.wisestamp.com/r/landing?promo=22&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_22>
Click here.
<http://r1.wisestamp.com/r/landing?promo=22&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_22>
