qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio: Mark virtio-device as non-user-creatable
Date: Fri, 4 Aug 2017 00:11:32 +0200	[thread overview]
Message-ID: <74f5e1dd-73f0-9a43-0de0-93082f8a7273@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170803144508.GI3108@localhost.localdomain>



On 08/03/2017 04:45 PM, Eduardo Habkost wrote:
> On Wed, Aug 02, 2017 at 02:33:00PM +0200, Halil Pasic wrote:
>>
>>
>> On 08/02/2017 01:01 AM, Eduardo Habkost wrote:
>>> TYPE_VIRTIO_DEVICE devices are already not usable with -device
>>> and device_add, but they are reported as user-creatable on
>>> "-device help" and through monitor interfaces.
>>
>> I've tried -device virtio-rng on s390x and from what I see, it
>> seems we 'auto-magically' create the 'controlling' virtio-rng-ccw
>> device. So I have to ask what do you mean by 'already not usable'?
> 
> virtio-rng is just an alias for virtio-rng-<transport>, and it's
> not a TYPE_VIRTIO_DEVICE device.
> 
> virtio-rng-device is the TYPE_VIRTIO_DEVICE subclass, and you
> shouldn't be able to use "-device virtio-rng-device".  Except
> that it works with "qemu-system-arm -machine virt", as I noted on
> another message, and this patch breaks it.
> 

Sorry, I was in a hurry leaving for holiday (I'm in a holiday
for approx 2 weeks) and acted on assumptions -- obviously wrong
ones.

AFAIU you withdrew the patch because of this arm exception in
the other message.

Sorry for the noise.

Halil

  reply	other threads:[~2017-08-03 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 23:01 [Qemu-devel] [PATCH] virtio: Mark virtio-device as non-user-creatable Eduardo Habkost
2017-08-02 12:33 ` Halil Pasic
2017-08-03 14:45   ` Eduardo Habkost
2017-08-03 22:11     ` Halil Pasic [this message]
2017-08-02 13:10 ` Eduardo Habkost

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=74f5e1dd-73f0-9a43-0de0-93082f8a7273@linux.vnet.ibm.com \
    --to=pasic@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mst@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 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).