qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	qemu-s390x@nongnu.org,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	"Matthew Rosato" <mjrosato@linux.ibm.com>,
	qemu-devel@nongnu.org, "David Hildenbrand" <david@redhat.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Halil Pasic" <pasic@linux.ibm.com>
Subject: Re: [PATCH v2] hw/s390x: Fix a possible crash with passed-through virtio devices
Date: Tue, 18 Nov 2025 23:56:28 +0100	[thread overview]
Message-ID: <20251118235628.5869f067.pasic@linux.ibm.com> (raw)
In-Reply-To: <8f90d4d7ea1c4ee8e088f5afb483587181278ebf.camel@linux.ibm.com>

On Tue, 18 Nov 2025 10:19:56 -0500
Eric Farman <farman@linux.ibm.com> wrote:

> > So I think it would really make sense to prevent passing through
> > virtio-ccw devices with vfio-ccw. Eric what is your take?  
> 
> It's true that the only -supported- use case is passthrough DASD, and we allow other device types to
> be passed through. The only ones we fence off are what we know aren't going to work, like FCPs.

I think we can add virto-ccw to that known to not work list ;)

> IIRC
> we'd talked a few years ago about a plan for a more detailed allow-list of passthrough devices and
> configurations, but that fell off the back of the todo list. Short of dusting all that off, I don't
> know that blocking virtio-ccw from vfio is going to buy us anything that Thomas' patch doesn't
> already provide.

See your comment form later today :)

Would prevent ending up with a most likely dysfunctional device at best.

Regards,
Halil


      reply	other threads:[~2025-11-18 22:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  9:39 [PATCH v2] hw/s390x: Fix a possible crash with passed-through virtio devices Thomas Huth
2025-11-18 11:52 ` Cornelia Huck
2025-11-18 12:09   ` Thomas Huth
2025-11-18 12:15     ` Cornelia Huck
2025-11-18 12:02 ` Halil Pasic
2025-11-18 12:28   ` Thomas Huth
2025-11-18 14:24     ` Halil Pasic
2025-11-18 14:53       ` Cornelia Huck
2025-11-18 14:25     ` Cornelia Huck
2025-11-18 14:48       ` Thomas Huth
2025-11-18 15:19   ` Eric Farman
2025-11-18 22:56     ` Halil Pasic [this message]

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=20251118235628.5869f067.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=clg@kaod.org \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).