From: Eric Blake <eblake@redhat.com>
To: "Bryan D. Payne" <bdpayne@acm.org>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qmp: extend QMP to provide read/write access to physical memory
Date: Thu, 04 Dec 2014 15:43:48 -0700 [thread overview]
Message-ID: <5480E3A4.5000704@redhat.com> (raw)
In-Reply-To: <CAFpPvXBXaip5=sgj=g+_DsZz7jkeAdQLoUnM8NGbtmjXiKNtog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On 12/04/2014 11:40 AM, Bryan D. Payne wrote:
>>
>> Off the top of my head, I know the -tpm command line options (related to
>> the 'query-tpm' QMP command) do this; look at hw/tpm/tpm_passthrough.c
>> for that implementation.
>
>
> So now I do see what you are talking about. But I don't think it applies
> to this patch. I'm not using qemu_open in this patch.
But my argument is that you SHOULD be using qemu_open, so that someone
can have the option of passing in a pre-opened fd rather than having
qemu open it. It matters for cases like libvirt where qemu is running
under restricted privileges, and it is easier to have libvirt pass in a
pre-opened fd than to figure out how to give qemu the privileges it
needs to open the file itself. Even if you don't think your feature
will be exposed by libvirt any time soon, it's still worth designing
things to be flexible from the beginning.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-12-04 22:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 8:41 [Qemu-devel] [PATCH 0/1] qmp: extend QMP to provide read/write access to physical memory Bryan D. Payne
2014-11-26 8:41 ` [Qemu-devel] [PATCH 1/1] " Bryan D. Payne
2014-11-26 15:16 ` Eric Blake
2014-11-26 20:27 ` [Qemu-devel] [PATCH v2] " Bryan D. Payne
2014-11-26 20:27 ` [Qemu-devel] [PATCH] " Bryan D. Payne
2014-11-27 2:04 ` Fam Zheng
2014-12-04 3:37 ` Bryan D. Payne
2014-12-04 4:57 ` Fam Zheng
2014-12-04 6:28 ` Bryan D. Payne
2014-12-04 7:38 ` Fam Zheng
2014-12-04 16:43 ` Bryan D. Payne
2014-12-05 1:20 ` Fam Zheng
2014-12-04 9:08 ` Markus Armbruster
2014-12-04 16:49 ` Bryan D. Payne
2014-12-05 8:44 ` Markus Armbruster
2014-12-05 21:25 ` Bryan D. Payne
2014-12-08 15:06 ` Markus Armbruster
2014-12-09 15:12 ` Bryan D. Payne
2014-12-11 3:33 ` Bryan D. Payne
2014-12-11 5:45 ` Fam Zheng
2014-12-11 6:07 ` Bryan D. Payne
2014-12-12 2:28 ` Bryan D. Payne
2014-12-12 3:29 ` Fam Zheng
2014-12-01 22:10 ` Eric Blake
2014-12-03 23:07 ` Bryan D. Payne
2014-12-04 15:08 ` Eric Blake
2014-12-04 16:50 ` Bryan D. Payne
2014-12-04 18:40 ` Bryan D. Payne
2014-12-04 22:43 ` Eric Blake [this message]
2014-12-01 22:12 ` [Qemu-devel] [PATCH v2] " Eric Blake
2014-12-02 4:36 ` Bryan D. Payne
2014-12-02 5:26 ` Fam Zheng
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=5480E3A4.5000704@redhat.com \
--to=eblake@redhat.com \
--cc=bdpayne@acm.org \
--cc=lcapitulino@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).