From: Anthony Liguori <anthony@codemonkey.ws>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: qemu-devel@nongnu.org, Alexandre Bique <alexandre.bique@citrix.com>
Subject: Re: [Qemu-devel] [PATCH 0/7] ATAPI CDROM passthrough v5
Date: Mon, 24 Aug 2009 08:18:14 -0500 [thread overview]
Message-ID: <4A929316.3070004@codemonkey.ws> (raw)
In-Reply-To: <19074.63829.151234.423348@mariner.uk.xensource.com>
Ian Jackson wrote:
>> I would also suggest that you only expose this as an option
>> through qdev properties instead of a new command line option as it
>> should be controllable on a per-device basis.
>>
>
> The reason to disable it is not to prevent the guest breaking the
> hardware. It is to prevent the guest escaping the containment
> entirely, which it can probably do if firmware updates are allowed.
> This seems to me to be a general property of the guest, rather than of
> the device. So I think disabling it in one place is better.
>
If you go back to the original thread, the argument against this was
that some devices abuse other atapi commands to do firmware updates so
you cannot 100% reliably contain this.
But more importantly, and the reason I originally requested this, having
a global option bakes knowledge of atapi pass through into vl.c. Making
it a qdev property means vl.c does not need explicit knowledge of this
mechanism.
I think this is an important change to make for merging.
Regards,
Anthony Liguori
> Patches follow.
>
> Thanks,
> Ian.
>
>
>
next prev parent reply other threads:[~2009-08-24 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 17:18 [Qemu-devel] [PATCH 0/7] ATAPI CDROM passthrough v5 Ian Jackson
2009-08-12 17:26 ` [Qemu-devel] " Ian Jackson
2009-08-12 22:00 ` [Qemu-devel] " Christoph Hellwig
2009-08-13 16:44 ` Ian Jackson
2009-08-24 13:18 ` Anthony Liguori [this message]
2009-08-28 20:21 ` Bique Alexandre
2009-08-29 19:35 ` Carl-Daniel Hailfinger
2009-08-29 20:49 ` Anthony Liguori
2009-08-29 21:10 ` Carl-Daniel Hailfinger
2009-08-30 0:14 ` Anthony Liguori
2010-10-18 23:29 ` Alexander Graf
2010-10-19 0:10 ` Anthony Liguori
2010-10-19 6:17 ` Alexander Graf
2010-10-19 14:27 ` Michal Suchanek
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=4A929316.3070004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Ian.Jackson@eu.citrix.com \
--cc=alexandre.bique@citrix.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).