linux-kernel - [RFC 0/2] virtio_pci: patches never to apply.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1423635917-31282-1-git-send-email-rusty@rustcorp.com.au>
Date:	Wed, 11 Feb 2015 16:55:15 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	"lkml" <linux-kernel@...r.kernel.org>, lguest@...ts.ozlabs.org,
	virtualization@...ts.linux-foundation.org,
	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>
Subject: [RFC 0/2] virtio_pci: patches never to apply.

This should allow testing when QEMU gets VIRTIO_PCI_CAP_PCI_CFG support,
but I'm pretty sure we should never allow these patches upstream.

Tested with lguest (in virtio-next), which supports VIRTIO_PCI_CAP_PCI_CFG.

Rusty Russell (2):
  virtio_pci: abstract all MMIO accesses.
  virtio: Introducing virtio_pci.no_mmio, the worst boot option in
    history.

 drivers/virtio/virtio_pci_common.c |  70 +++++++-
 drivers/virtio/virtio_pci_common.h |  62 ++++++++
 drivers/virtio/virtio_pci_legacy.c |   1 +
 drivers/virtio/virtio_pci_modern.c | 317 ++++++++++++++++++++++++++++++-------
 4 files changed, 391 insertions(+), 59 deletions(-)

-- 
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/