From: Anthony Liguori <anthony@codemonkey.ws>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH qemu-kvm] device-assignment: add config fd qdev property
Date: Wed, 19 May 2010 16:50:35 -0500 [thread overview]
Message-ID: <4BF45D2B.8020000@codemonkey.ws> (raw)
In-Reply-To: <20100519211030.GL28275@x200.localdomain>
On 05/19/2010 04:10 PM, Chris Wright wrote:
> * Anthony Liguori (anthony@codemonkey.ws) wrote:
>
>> An fd as a qdev property seems like a bad idea to me.
>>
> What is your concern?
>
qdev properties are supposed to represent device tunables. A file
descriptor is not a tunable.
It's like passing the tap device fd via qdev to an e1000.
>> I'm not sure I have a better suggestion though.
>>
> Anything else requires inventing some new commandline options and monitor
> comnmands (-pcidevice anyone? ;-). I'm not sure the benefit, esp with
> hopes of moving to uio.
>
Yeah, I think device passthrough is going to require new command line
syntax to be more qemu friendly...
Regards,
Anthony Liguori
> thanks,
> -chris
>
next prev parent reply other threads:[~2010-05-19 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 19:00 [PATCH qemu-kvm] device-assignment: add config fd qdev property Chris Wright
2010-05-19 19:08 ` Alex Williamson
2010-05-19 19:18 ` Anthony Liguori
2010-05-19 21:10 ` Chris Wright
2010-05-19 21:50 ` Anthony Liguori [this message]
2010-05-19 21:59 ` Chris Wright
2010-05-19 22:27 ` Anthony Liguori
2010-05-20 10:06 ` Daniel P. Berrange
2010-05-20 12:11 ` Markus Armbruster
2010-05-24 16:53 ` Alex Williamson
2010-05-24 18:20 ` Chris Wright
2010-05-25 6:43 ` Markus Armbruster
2010-05-25 21:14 ` Alex Williamson
2010-05-31 20:22 ` Marcelo Tosatti
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=4BF45D2B.8020000@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alex.williamson@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.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.