From: Laszlo Ersek <lersek@redhat.com>
To: Matt Fleming <matt.fleming@intel.com>,
"Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: mdroth@linux.vnet.ibm.com, rjones@redhat.com,
jordan.l.justen@intel.com, "Gabriel L. Somlo" <somlo@cmu.edu>,
qemu-devel@nongnu.org, gleb@cloudius-systems.com,
kraxel@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] RFC: guest-side retrieval of fw_cfg file
Date: Wed, 15 Jul 2015 13:15:08 +0200 [thread overview]
Message-ID: <55A640BC.7090301@redhat.com> (raw)
In-Reply-To: <1436958390.25906.7.camel@intel.com>
On 07/15/15 13:06, Matt Fleming wrote:
> On Tue, 2015-07-14 at 13:00 -0400, Gabriel L. Somlo wrote:
>>
>> That being said, I did reimplement systemd's escape method in cca. 30
>> lines of C, so that shouldn't be too onerous.
>
> I really don't see a reason to use systemd's naming scheme instead of
> the one already provided by the kernel.
>
>> Besides, Laszlo said he liked a real folder hierarchy, and I do too,
>> so I'm still pondering how much doing that would complicate the module
>> init function. I'm somewhat worried about what the added complexity
>> will mean in terms of upstream acceptance in the linux kernel :)
>
> Yeah, going that route will complicate the patch and you're going to get
> asked "Umm.. why?" by Greg Kroah-Hartman (definitely Cc Greg when
> sending this to the kernel mailing lists btw).
>
> But if you can provide sound technical arguments for the added
> complexity I'm sure the kernel folks will be happy. Laszlo's argument
> makes sense to me, i.e. wanting to use standard utilities to know
> whether a blob is available.
>
> Instead of rolling all this kobject-creation logic into your driver I'd
> suggest writing a patch to lib/kobject.c., since the problem sounds like
> something that should be solved with the kobject API.
Haha, this feature just got extended by six months. :)
> The question is, how simple can you make the code ;-)
The first question is how strong Gabriel's nerves are, but (from past
experience) they *are* strong. :)
Laszlo
next prev parent reply other threads:[~2015-07-15 11:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 20:09 [Qemu-devel] RFC: guest-side retrieval of fw_cfg file Gabriel L. Somlo
2015-07-13 23:03 ` Eric Blake
2015-07-14 17:00 ` Gabriel L. Somlo
2015-07-15 11:06 ` Matt Fleming
2015-07-15 11:15 ` Laszlo Ersek [this message]
2015-07-14 9:43 ` Richard W.M. Jones
2015-07-14 18:23 ` Gabriel L. Somlo
2015-07-14 18:31 ` Gabriel L. Somlo
2015-07-14 18:48 ` Richard W.M. Jones
2015-07-14 18:51 ` Richard W.M. Jones
2015-07-14 19:16 ` Peter Maydell
2015-07-14 19:24 ` Gabriel L. Somlo
2015-07-14 19:24 ` Gerd Hoffmann
2015-07-16 0:43 ` Gabriel L. Somlo
2015-07-16 19:27 ` Eric Blake
2015-07-16 20:42 ` Gabriel L. Somlo
2015-07-14 11:38 ` Laszlo Ersek
2015-07-15 12:00 ` Matt Fleming
2015-07-20 21:19 ` Gabriel L. Somlo
2015-07-20 22:07 ` Laszlo Ersek
2015-07-25 23:21 ` Gabriel L. Somlo
2015-07-26 9:37 ` Laszlo Ersek
2015-07-15 14:08 ` Michael S. Tsirkin
2015-07-15 16:01 ` Igor Mammedov
2015-07-15 16:24 ` Michael S. Tsirkin
2015-07-16 1:21 ` Gabriel L. Somlo
2015-07-16 6:57 ` Igor Mammedov
2015-07-16 7:30 ` Michael S. Tsirkin
2015-07-16 9:50 ` Igor Mammedov
2015-07-16 10:25 ` Michael S. Tsirkin
2015-07-16 11:15 ` Igor Mammedov
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=55A640BC.7090301@redhat.com \
--to=lersek@redhat.com \
--cc=gleb@cloudius-systems.com \
--cc=gsomlo@gmail.com \
--cc=jordan.l.justen@intel.com \
--cc=kraxel@redhat.com \
--cc=matt.fleming@intel.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=somlo@cmu.edu \
/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).