All of lore.kernel.org
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Viktor Mihajlovski <mihajlov@linux.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	Boris Fiuczynski <fiuczy@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Pierre Morel <pmorel@linux.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	David Hildenbrand <david@redhat.com>,
	qemu-devel@nongnu.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org, Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v2 1/1] virtio-ccw: auto-manage VIRTIO_F_IOMMU_PLATFORM if PV
Date: Wed, 10 Jun 2020 15:34:36 +0200	[thread overview]
Message-ID: <20200610153436.1b79ee11.pasic@linux.ibm.com> (raw)
In-Reply-To: <20200609180559.52298647.cohuck@redhat.com>

On Tue, 9 Jun 2020 18:05:59 +0200
Cornelia Huck <cohuck@redhat.com> wrote:

> Which devices are compatible in the end? It seems the only ones that
> are known to be working are virtio-ccw devices with IOMMU_PLATFORM on.
> virtio-pci devices and non-virtio ccw (vfio-ccw, 3270) seem to be out,
> as far as I understand it. What about non-ccw? PCI in general, vfio-ap?

I've already answered how virtio is special. Regarding PCI, it is
currently not supported in prot virt mode, and this is properly handled
by the ultravisor: facility bits fenced and operation exceptions
indicated if the guest were to try and do PCI instructions nevertheless.
That also means we don't have to worry about virtio-pci for the
moment. The status current of AP is analogous to that of PCI.

So AFAIU all we have to worry about at the moment is ccw and virtio-ccw.

Regards,
Halil


  parent reply	other threads:[~2020-06-10 13:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 22:11 [PATCH v2 1/1] virtio-ccw: auto-manage VIRTIO_F_IOMMU_PLATFORM if PV Halil Pasic
2020-05-20 12:16 ` Halil Pasic
2020-05-20 16:23 ` Michael S. Tsirkin
2020-05-22 21:04   ` Halil Pasic
2020-05-28 11:21     ` Cornelia Huck
2020-05-28 14:42       ` Janosch Frank
2020-05-28 18:49         ` Halil Pasic
2020-05-28 17:52       ` Halil Pasic
2020-06-05 23:32   ` Halil Pasic
2020-06-08 16:14     ` Cornelia Huck
2020-06-08 17:00       ` Halil Pasic
2020-06-09  6:44         ` Cornelia Huck
2020-06-09  9:41           ` Halil Pasic
2020-06-09 14:02             ` Pierre Morel
2020-06-09 15:47             ` Claudio Imbrenda
2020-06-09 16:05               ` Cornelia Huck
2020-06-09 16:41                 ` Halil Pasic
2020-06-10 13:34                 ` Halil Pasic [this message]
2020-06-09 16:28               ` Halil Pasic
2020-06-09 16:44                 ` Michael S. Tsirkin
2020-06-10  4:31                   ` David Gibson
2020-06-10  7:22                     ` David Hildenbrand
2020-06-10 10:07                       ` David Gibson
2020-06-10 10:24                         ` David Hildenbrand
2020-06-10 13:00                           ` Halil Pasic
2020-06-10 13:19                           ` Viktor Mihajlovski
2020-06-10 14:00                             ` David Hildenbrand
2020-06-19  0:36                             ` David Gibson
2020-06-19  0:33                           ` David Gibson
2020-06-10 13:15                   ` Halil Pasic
2020-06-10  4:29                 ` David Gibson
2020-06-10 13:57                   ` Halil Pasic
2020-06-19  0:59                     ` David Gibson
2020-06-09 16:41               ` Michael S. Tsirkin
2020-06-10  4:25           ` David Gibson
2020-06-10 21:37             ` Halil Pasic
2020-06-19  1:01               ` David Gibson
2020-06-08 16:53     ` Michael S. Tsirkin

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=20200610153436.1b79ee11.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=david@redhat.com \
    --cc=fiuczy@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=mihajlov@linux.ibm.com \
    --cc=mst@redhat.com \
    --cc=pmorel@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    /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.