All of lore.kernel.org
 help / color / mirror / Atom feed
From: frank.blaschka@de.ibm.com
To: qemu-devel@nongnu.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org
Cc: alex.williamson@redhat.com, pbonzini@redhat.com, agraf@suse.de
Subject: [RFC patch 0/6] vfio based pci pass-through for qemu/KVM on s390
Date: Fri, 19 Sep 2014 13:54:29 +0200	[thread overview]
Message-ID: <20140919115429.557279920@de.ibm.com> (raw)

This set of patches implements a vfio based solution for pci
pass-through on the s390 platform. The kernel stuff is pretty
much straight forward, but qemu needs more work.

Most interesting patch is:
  vfio: make vfio run on s390 platform

I hope Alex & Alex can give me some guidance how to do the changes
in an appropriate way. After creating a separate iommmu address space
for each attached PCI device I can successfully run the vfio type1
iommu. So If we could extend type1 not registering all guest memory
(see patch) I think we do not need a special vfio iommu for s390
for the moment.

The patches implement the base pass-through support. s390 specific
virtualization functions are currently not included. This would
be a second step after the base support is done.

kernel patches apply to linux-kvm-next

KVM: s390: Enable PCI instructions
iommu: add iommu for s390 platform
vfio: make vfio build on s390

qemu patches apply to qemu-master

s390: Add PCI bus support
s390: implement pci instruction
vfio: make vfio run on s390 platform

Thx for feedback and review comments

Frank

WARNING: multiple messages have this Message-ID (diff)
From: frank.blaschka@de.ibm.com
To: qemu-devel@nongnu.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org
Cc: pbonzini@redhat.com, alex.williamson@redhat.com, agraf@suse.de
Subject: [Qemu-devel] [RFC patch 0/6] vfio based pci pass-through for qemu/KVM on s390
Date: Fri, 19 Sep 2014 13:54:29 +0200	[thread overview]
Message-ID: <20140919115429.557279920@de.ibm.com> (raw)

This set of patches implements a vfio based solution for pci
pass-through on the s390 platform. The kernel stuff is pretty
much straight forward, but qemu needs more work.

Most interesting patch is:
  vfio: make vfio run on s390 platform

I hope Alex & Alex can give me some guidance how to do the changes
in an appropriate way. After creating a separate iommmu address space
for each attached PCI device I can successfully run the vfio type1
iommu. So If we could extend type1 not registering all guest memory
(see patch) I think we do not need a special vfio iommu for s390
for the moment.

The patches implement the base pass-through support. s390 specific
virtualization functions are currently not included. This would
be a second step after the base support is done.

kernel patches apply to linux-kvm-next

KVM: s390: Enable PCI instructions
iommu: add iommu for s390 platform
vfio: make vfio build on s390

qemu patches apply to qemu-master

s390: Add PCI bus support
s390: implement pci instruction
vfio: make vfio run on s390 platform

Thx for feedback and review comments

Frank

             reply	other threads:[~2014-09-19 11:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 11:54 frank.blaschka [this message]
2014-09-19 11:54 ` [Qemu-devel] [RFC patch 0/6] vfio based pci pass-through for qemu/KVM on s390 frank.blaschka
2014-09-19 11:54 ` [RFC patch 1/6] KVM: s390: Enable PCI instructions frank.blaschka
2014-09-19 11:54   ` [Qemu-devel] " frank.blaschka
2014-09-19 11:54 ` [RFC patch 2/6] iommu: add iommu for s390 platform frank.blaschka
2014-09-19 11:54   ` [Qemu-devel] " frank.blaschka
2014-09-19 11:54 ` [RFC patch 3/6] vfio: make vfio build on s390 frank.blaschka
2014-09-19 11:54   ` [Qemu-devel] " frank.blaschka
2014-09-19 11:54 ` [RFC patch 4/6] s390: Add PCI bus support frank.blaschka
2014-09-19 11:54   ` [Qemu-devel] " frank.blaschka
2014-09-19 11:54 ` [RFC patch 5/6] s390: implement pci instruction frank.blaschka
2014-09-19 11:54   ` [Qemu-devel] " frank.blaschka
2014-09-19 15:12   ` Thomas Huth
2014-09-19 15:12     ` [Qemu-devel] " Thomas Huth
2014-09-22  7:40     ` Frank Blaschka
2014-09-22  7:40       ` Frank Blaschka
2014-09-19 11:54 ` [RFC patch 6/6] vfio: make vfio run on s390 platform frank.blaschka
2014-09-19 11:54   ` [Qemu-devel] " frank.blaschka
2014-09-22 20:47 ` [RFC patch 0/6] vfio based pci pass-through for qemu/KVM on s390 Alex Williamson
2014-09-22 20:47   ` [Qemu-devel] " Alex Williamson
2014-09-22 22:08   ` Alexander Graf
2014-09-22 22:08     ` [Qemu-devel] " Alexander Graf
2014-09-22 22:28     ` Alex Williamson
2014-09-22 22:28       ` [Qemu-devel] " Alex Williamson
2014-09-23  8:33       ` Alexander Graf
2014-09-23  8:33         ` [Qemu-devel] " Alexander Graf
2014-09-24  8:47   ` Frank Blaschka
2014-09-24  8:47     ` Frank Blaschka
2014-09-24 16:05     ` Alex Williamson
2014-09-24 16:05       ` Alex Williamson
2014-09-26  6:45       ` Frank Blaschka
2014-09-26  6:45         ` Frank Blaschka
2014-09-26 19:59         ` Alex Williamson
2014-10-01  9:11           ` Frank Blaschka
2014-10-01  9:11             ` Frank Blaschka
2014-10-01 17:26             ` Alex Williamson
2014-10-01 17:26               ` Alex Williamson
2014-10-02  7:21               ` Frank Blaschka
2014-10-02  7:21                 ` Frank Blaschka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140919115429.557279920@de.ibm.com \
    --to=frank.blaschka@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.