gem5 - gem5

Age	Commit message (Collapse)	Author
2015-02-03	dev: Correctly clear interrupts in VirtIO PCI	Andreas Sandberg
	Correctly clear the PCI interrupt belonging to a VirtIO device when the ISR register is read.
2014-12-08	dev: Correctly transform packets into responses	Andreas Sandberg
	The VirtIO devices didn't correctly set the response flags in memory packets. This changeset adds the required Packet::makeResponse() calls.
2014-12-02	mem: Remove redundant Packet::allocate calls	Andreas Hansson
	This patch cleans up the packet memory allocation confusion. The data is always allocated at the requesting side, when a packet is created (or copied), and there is never a need for any device to allocate any space if it is merely responding to a paket. This behaviour is in line with how SystemC and TLM works as well, thus increasing interoperability, and matching established conventions. The redundant calls to Packet::allocate are removed, and the checks in the function are tightened up to make sure data is only ever allocated once. There are still some oddities in the packet copy constructor where we copy the data pointer if it is static (without ownership), and allocate new space if the data is dynamic (with ownership). The latter is being worked on further in a follow-on patch.
2014-11-24	misc: Another round of static analysis fixups	Andreas Hansson
	Mostly addressing uninitialised members.
2014-09-20	dev: Add support for 9p proxying over VirtIO	Andreas Sandberg
	This patch adds support for 9p filesystem proxying over VirtIO. It can currently operate by connecting to a 9p server over a socket (VirtIO9PSocket) or by starting the diod 9p server and connecting over pipe (VirtIO9PDiod). WARNING: Checkpoints are currently not supported for systems with 9p proxies!
2014-09-20	dev: Add a VirtIO block device model	Andreas Sandberg

2014-09-20	dev: Add a VirtIO console device model	Andreas Sandberg

2014-09-20	dev, pci: Implement basic VirtIO support	Andreas Sandberg
	This patch adds support for VirtIO over the PCI bus. It does so by providing the following new SimObjects: * VirtIODeviceBase - Abstract base class for VirtIO devices. * PciVirtIO - VirtIO PCI transport interface. A VirtIO device is hooked up to the guest system by adding a PciVirtIO device to the PCI bus and connecting it to a VirtIO device using the vio parameter. New VirtIO devices should inherit from VirtIODevice base and implementing one or more VirtQueues. The VirtQueues are usually device-specific and all derive from the VirtQueue class. Queues must be registered with the base class from the constructor since the device assumes that the number of queues stay constant.