From: "Michael S. Tsirkin" <mst@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Gabriel L . Somlo" <somlo@cmu.edu>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] fw_cfg: RFQDN rules, documentation
Date: Wed, 13 Apr 2016 20:53:58 +0300 [thread overview]
Message-ID: <20160413205343-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <87h9f5iiue.fsf@dusky.pond.sub.org>
On Wed, Apr 13, 2016 at 06:17:29PM +0200, Markus Armbruster wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > On Wed, Apr 13, 2016 at 10:59:35AM +0200, Markus Armbruster wrote:
> >> I have a hard time coming up with realistic unclean breakage.
> >
> > The issue is that Linux is now exposing fw cfg to userspace.
> > So it's use is about to expand significantly.
> >
> > This is what I am trying to prevent:
> > - in 2016, users build a guest using a path XXX outside opt.
> > there's a warning on host, but it is not noticed.
>
> Amend:
>
> The guest treats path XXX as optional.
>
> > - in 2020, qemu starts using path XXX for internal purposes.
> > - using guest from 2016 now breaks uncleanly on this new qemu
>
> Amend:
>
> when we're not specifying the optional path XXX with -fw_cfg.
>
> > since guest thinks it's talking to the external tool.
>
> Okay, that's a much more plausible scenario. The question remains
> whether preventing it justifies the compat break and the additional
> interface complexity.
there is no break as long as people follow the rules.
next prev parent reply other threads:[~2016-04-13 17:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 7:54 [Qemu-devel] [PATCH v3] fw_cfg: RFQDN rules, documentation Michael S. Tsirkin
2016-04-08 16:31 ` Markus Armbruster
2016-04-09 17:05 ` Michael S. Tsirkin
2016-04-11 11:04 ` Markus Armbruster
2016-04-11 11:31 ` Michael S. Tsirkin
2016-04-13 8:59 ` Markus Armbruster
2016-04-13 11:00 ` Michael S. Tsirkin
2016-04-13 16:17 ` Markus Armbruster
2016-04-13 17:53 ` Michael S. Tsirkin [this message]
2016-04-14 7:36 ` Markus Armbruster
2016-04-14 8:10 ` Michael S. Tsirkin
2016-04-14 11:28 ` Markus Armbruster
2016-04-13 14:44 ` Michael S. Tsirkin
2016-04-13 16:19 ` Markus Armbruster
2016-04-13 17:53 ` Michael S. Tsirkin
2016-04-14 7:39 ` Markus Armbruster
2016-04-14 8:11 ` Michael S. Tsirkin
2016-04-14 11:29 ` Markus Armbruster
2016-04-14 12:13 ` Michael S. Tsirkin
2016-04-15 15:39 ` Markus Armbruster
2016-04-17 6:55 ` Michael S. Tsirkin
2016-04-18 16:42 ` Markus Armbruster
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=20160413205343-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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.