From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Qemu-devel] Qemu baseline requirements/portability?
Date: Thu, 6 Jun 2019 10:48:19 +0100 [thread overview]
Message-ID: <20190606094819.GF14300@redhat.com> (raw)
In-Reply-To: <87ef47jn6n.fsf@dusky.pond.sub.org>
On Thu, Jun 06, 2019 at 07:30:08AM +0200, Markus Armbruster wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>
> > On 6/5/19 12:55 PM, H. Peter Anvin wrote:
> >> Hi,
> >>
> >> I am writing some code I'm hoping will be able to make it into Qemu, but I
> >> can't seem to find what the baseline portability requirements are. I'm
> >> specifically wondering about newer POSIX features like openat(), which seems
> >> to be used in the 9p filesystem and nowhere else, and what version of glib one
> >> can rely on?
> >>
> >
> > Specifically, I'm trying to satisfy a 10-year-old request by me and others to
> > support composite initrd during Linux boot.
>
> Please peruse qemu-doc.texi @appendix Supported build platforms. If it
> doesn't fully answer your question, ask for clarification here.
And specificially on the glib version question, we currently mandate 2.40.
If you try to use a glib API from a version newer than 2.40 we have things
setup so that you should get a fatal compile error due to our use of
#define GLIB_VERSION_MAX_ALLOWED GLIB_VERSION_2_40
If you do think it is useful to have an API from glib > 2.40 you can put
some back compat logic in include/glib-compat.h so that you can use the
newer API and gracefully degrade on older glib.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2019-06-06 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 19:55 [Qemu-devel] Qemu baseline requirements/portability? H. Peter Anvin
2019-06-05 20:46 ` H. Peter Anvin
2019-06-06 5:30 ` Markus Armbruster
2019-06-06 9:48 ` Daniel P. Berrangé [this message]
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=20190606094819.GF14300@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=hpa@zytor.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).