2010-11-27 01:34:15 +01:00
|
|
|
CONFIG_PCI=y
|
Allow ISA bus to be configured out
Currently, the code to handle the legacy ISA bus is always included in
qemu. However there are lots of platforms that don't include ISA legacy
devies, and quite a few that have never used ISA legacy devices at all.
This patch allows the ISA bus code to be disabled in the configuration for
platforms where it doesn't make sense.
For now, the default configs are adjusted to include ISA on all platforms
including PCI: anything with PCI can at least in principle add an i82378
PCI->ISA bridge. Also, CONFIG_IDE_CORE which is already in pci.mak
requires ISA support.
We also explicitly enable ISA on some other non-PCI platforms which include
ISA devices: moxie, sparc and unicore32. We may want to pare this down in
future.
The platforms that will lose ISA by default are: cris, lm32, microblazeel,
microblaze, openrisc, s390x, tricore, xtensaeb, xtensa. As far as I can
tell none of these ever used ISA.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
2016-11-09 03:31:22 +01:00
|
|
|
# For now, CONFIG_IDE_CORE requires ISA, so we enable it here
|
|
|
|
|
CONFIG_ISA_BUS=y
|
2010-11-27 01:34:15 +01:00
|
|
|
CONFIG_VIRTIO_PCI=y
|
2018-05-22 21:48:22 +02:00
|
|
|
include virtio.mak
|
2010-11-27 01:34:15 +01:00
|
|
|
CONFIG_USB_UHCI=y
|
|
|
|
|
CONFIG_USB_OHCI=y
|
2010-12-03 16:17:28 +01:00
|
|
|
CONFIG_USB_EHCI=y
|
2011-02-27 21:09:09 +01:00
|
|
|
CONFIG_USB_XHCI=y
|
2017-05-17 12:33:13 +02:00
|
|
|
CONFIG_USB_XHCI_NEC=y
|
2010-11-27 01:34:15 +01:00
|
|
|
CONFIG_NE2000_PCI=y
|
|
|
|
|
CONFIG_EEPRO100_PCI=y
|
|
|
|
|
CONFIG_PCNET_PCI=y
|
2010-11-27 12:23:34 +01:00
|
|
|
CONFIG_PCNET_COMMON=y
|
2013-04-18 18:44:04 +02:00
|
|
|
CONFIG_AC97=y
|
|
|
|
|
CONFIG_HDA=y
|
|
|
|
|
CONFIG_ES1370=y
|
2018-05-22 21:44:55 +02:00
|
|
|
CONFIG_SCSI=y
|
2010-11-27 01:34:15 +01:00
|
|
|
CONFIG_LSI_SCSI_PCI=y
|
2013-04-19 09:05:46 +02:00
|
|
|
CONFIG_VMW_PVSCSI_SCSI_PCI=y
|
2012-08-01 12:56:17 +02:00
|
|
|
CONFIG_MEGASAS_SCSI_PCI=y
|
hw: Add support for LSI SAS1068 (mptsas) device
This adds the SAS1068 device, a SAS disk controller used in VMware that
is oldish but widely supported and has decent performance. Unlike
megasas, it presents itself as a SAS controller and not as a RAID
controller. The device corresponds to the mptsas kernel driver in
Linux.
A few small things in the device setup are based on Don Slutz's old
patch, but the device emulation was written from scratch based on Don's
SeaBIOS patch and on the FreeBSD and Linux drivers. It is 2400 lines
shorter than Don's patch (and roughly the same size as MegaSAS---also
because it doesn't support the similar SPI controller), implements SCSI
task management functions (with asynchronous cancellation), supports
big-endian hosts, has complete support for migration and follows the
QEMU coding standards much more closely.
To write the driver, I first split Don's patch in two parts, with
the configuration bits in one file and the rest in a separate file.
I first left mptconfig.c in place and rewrote the rest, then deleted
mptconfig.c as well. The configuration pages are still based mostly on
VirtualBox's, though not exactly the same. However, the implementation
is completely different. The contents of the pages themselves should
not be copyrightable.
Signed-off-by: Don Slutz <Don@CloudSwitch.com>
Message-Id: <1347382813-5662-1-git-send-email-Don@CloudSwitch.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2015-10-27 18:26:06 +01:00
|
|
|
CONFIG_MPTSAS_SCSI_PCI=y
|
2010-11-27 01:34:15 +01:00
|
|
|
CONFIG_RTL8139_PCI=y
|
|
|
|
|
CONFIG_E1000_PCI=y
|
net: Introduce e1000e device emulation
This patch introduces emulation for the Intel 82574 adapter, AKA e1000e.
This implementation is derived from the e1000 emulation code, and
utilizes the TX/RX packet abstractions that were initially developed for
the vmxnet3 device. Although some parts of the introduced code may be
shared with e1000, the differences are substantial enough so that the
only shared resources for the two devices are the definitions in
hw/net/e1000_regs.h.
Similarly to vmxnet3, the new device uses virtio headers for task
offloads (for backends that support virtio extensions). Usage of
virtio headers may be forcibly disabled via a boolean device property
"vnet" (which is enabled by default). In such case task offloads
will be performed in software, in the same way it is done on
backends that do not support virtio headers.
The device code is split into two parts:
1. hw/net/e1000e.c: QEMU-specific code for a network device;
2. hw/net/e1000e_core.[hc]: Device emulation according to the spec.
The new device name is e1000e.
Intel specifications for the 82574 controller are available at:
http://www.intel.com/content/dam/doc/datasheet/82574l-gbe-controller-datasheet.pdf
Throughput measurement results (iperf2):
Fedora 22 guest, TCP, RX
4 ++------------------------------------------+
| |
| X X X X X
3.5 ++ X X X X |
| X |
| |
3 ++ |
G | X |
b | |
/ 2.5 ++ |
s | |
| |
2 ++ |
| |
| |
1.5 X+ |
| |
+ + + + + + + + + + + +
1 ++--+---+---+---+---+---+---+---+---+---+---+
32 64 128 256 512 1 2 4 8 16 32 64
B B B B B KB KB KB KB KB KB KB
Buffer size
Fedora 22 guest, TCP, TX
18 ++-------------------------------------------+
| X |
16 ++ X X X X X
| X |
14 ++ |
| |
12 ++ |
G | X |
b 10 ++ |
/ | |
s 8 ++ |
| |
6 ++ X |
| |
4 ++ |
| X |
2 ++ X |
X + + + + + + + + + + +
0 ++--+---+---+---+---+----+---+---+---+---+---+
32 64 128 256 512 1 2 4 8 16 32 64
B B B B B KB KB KB KB KB KB KB
Buffer size
Fedora 22 guest, UDP, RX
3 ++------------------------------------------+
| X
| |
2.5 ++ |
| |
| |
2 ++ X |
G | |
b | |
/ 1.5 ++ |
s | X |
| |
1 ++ |
| |
| X |
0.5 ++ |
| X |
X + + + + +
0 ++-------+--------+-------+--------+--------+
32 64 128 256 512 1
B B B B B KB
Datagram size
Fedora 22 guest, UDP, TX
1 ++------------------------------------------+
| X
0.9 ++ |
| |
0.8 ++ |
0.7 ++ |
| |
G 0.6 ++ |
b | |
/ 0.5 ++ |
s | X |
0.4 ++ |
| |
0.3 ++ |
0.2 ++ X |
| |
0.1 ++ X |
X X + + + +
0 ++-------+--------+-------+--------+--------+
32 64 128 256 512 1
B B B B B KB
Datagram size
Windows 2012R2 guest, TCP, RX
3.2 ++------------------------------------------+
| X |
3 ++ |
| |
2.8 ++ |
| |
2.6 ++ X |
G | X X X X X
b 2.4 ++ X X |
/ | |
s 2.2 ++ |
| |
2 ++ |
| X X |
1.8 ++ |
| |
1.6 X+ |
+ + + + + + + + + + + +
1.4 ++--+---+---+---+---+---+---+---+---+---+---+
32 64 128 256 512 1 2 4 8 16 32 64
B B B B B KB KB KB KB KB KB KB
Buffer size
Windows 2012R2 guest, TCP, TX
14 ++-------------------------------------------+
| |
| X X
12 ++ |
| |
10 ++ |
| |
G | |
b 8 ++ |
/ | X |
s 6 ++ |
| |
| |
4 ++ X |
| |
2 ++ |
| X X X |
+ X X + + X X + + + + +
0 X+--+---+---+---+---+----+---+---+---+---+---+
32 64 128 256 512 1 2 4 8 16 32 64
B B B B B KB KB KB KB KB KB KB
Buffer size
Windows 2012R2 guest, UDP, RX
1.6 ++------------------------------------------X
| |
1.4 ++ |
| |
1.2 ++ |
| X |
| |
G 1 ++ |
b | |
/ 0.8 ++ |
s | |
0.6 ++ X |
| |
0.4 ++ |
| X |
| |
0.2 ++ X |
X + + + + +
0 ++-------+--------+-------+--------+--------+
32 64 128 256 512 1
B B B B B KB
Datagram size
Windows 2012R2 guest, UDP, TX
0.6 ++------------------------------------------+
| X
| |
0.5 ++ |
| |
| |
0.4 ++ |
G | |
b | |
/ 0.3 ++ X |
s | |
| |
0.2 ++ |
| |
| X |
0.1 ++ |
| X |
X X + + + +
0 ++-------+--------+-------+--------+--------+
32 64 128 256 512 1
B B B B B KB
Datagram size
Signed-off-by: Dmitry Fleytman <dmitry.fleytman@ravellosystems.com>
Signed-off-by: Leonid Bloch <leonid.bloch@ravellosystems.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-06-01 10:23:45 +02:00
|
|
|
CONFIG_E1000E_PCI=y
|
2010-12-14 01:34:41 +01:00
|
|
|
CONFIG_IDE_CORE=y
|
|
|
|
|
CONFIG_IDE_QDEV=y
|
|
|
|
|
CONFIG_IDE_PCI=y
|
2010-12-14 01:34:42 +01:00
|
|
|
CONFIG_AHCI=y
|
2012-08-02 15:41:47 +02:00
|
|
|
CONFIG_ESP=y
|
2012-08-04 21:10:04 +02:00
|
|
|
CONFIG_ESP_PCI=y
|
2012-10-17 09:54:20 +02:00
|
|
|
CONFIG_SERIAL=y
|
2016-02-08 01:36:54 +01:00
|
|
|
CONFIG_SERIAL_ISA=y
|
2012-10-17 09:54:20 +02:00
|
|
|
CONFIG_SERIAL_PCI=y
|
2018-01-27 17:41:07 +01:00
|
|
|
CONFIG_CAN_BUS=y
|
2018-01-27 17:43:21 +01:00
|
|
|
CONFIG_CAN_SJA1000=y
|
2018-01-27 18:06:57 +01:00
|
|
|
CONFIG_CAN_PCI=y
|
2013-01-11 18:25:29 +01:00
|
|
|
CONFIG_IPACK=y
|
2013-02-05 12:27:44 +01:00
|
|
|
CONFIG_WDT_IB6300ESB=y
|
2013-03-31 14:31:14 +02:00
|
|
|
CONFIG_PCI_TESTDEV=y
|
2013-06-04 17:17:10 +02:00
|
|
|
CONFIG_NVME_PCI=y
|
2014-12-09 00:10:33 +01:00
|
|
|
CONFIG_SD=y
|
|
|
|
|
CONFIG_SDHCI=y
|
2015-01-21 17:48:33 +01:00
|
|
|
CONFIG_EDU=y
|
2015-02-13 06:46:08 +01:00
|
|
|
CONFIG_VGA=y
|
|
|
|
|
CONFIG_VGA_PCI=y
|
2018-10-05 18:01:46 +02:00
|
|
|
CONFIG_BOCHS_DISPLAY=y
|
2017-07-14 10:33:44 +02:00
|
|
|
CONFIG_IVSHMEM_DEVICE=$(CONFIG_IVSHMEM)
|
rocker: add new rocker switch device
Rocker is a simulated ethernet switch device. The device supports up to 62
front-panel ports and supports L2 switching and L3 routing functions, as well
as L2/L3/L4 ACLs. The device presents a single PCI device for each switch,
with a memory-mapped register space for device driver access.
Rocker device is invoked with -device, for example a 4-port switch:
-device rocker,name=sw1,len-ports=4,ports[0]=dev0,ports[1]=dev1, \
ports[2]=dev2,ports[3]=dev3
Each port is a netdev and can be paired with using -netdev id=<port name>.
Signed-off-by: Scott Feldman <sfeldma@gmail.com>
Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Acked-by: Scott Feldman <sfeldma@gmail.com>
Acked-by: Jiri Pirko <jiri@resnulli.us>
Signed-off-by: David Ahern <dsahern@gmail.com>
Message-id: 1426306173-24884-7-git-send-email-sfeldma@gmail.com
rocker: fix clang compiler errors
Consolidate all forward typedef declarations to rocker.h.
Signed-off-by: David Ahern <dsahern@gmail.com>
Acked-by: Scott Feldman <sfeldma@gmail.com>
Acked-by: Jiri Pirko <jiri@resnulli.us>
rocker: add support for flow modification
We had support for flow add/del. This adds support for flow mod. I needed
this for L3 support where an existing route is modified using NLM_F_REPLACE.
For example:
ip route add 12.0.0.0/30 nexthop via 11.0.0.1 dev swp1
ip route change 12.0.0.0/30 nexthop via 11.0.0.9 dev swp2
The first cmd adds the route. The second cmd changes the existing route by
changing its nexthop info.
In the device, a mod operation results in the matching flow enty being modified
with the new settings. This is atomic to the device.
Signed-off-by: Scott Feldman <sfeldma@gmail.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2015-03-14 05:09:30 +01:00
|
|
|
CONFIG_ROCKER=y
|