From: Markus Armbruster <armbru@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu baseline requirements/portability?
Date: Thu, 06 Jun 2019 07:30:08 +0200 [thread overview]
Message-ID: <87ef47jn6n.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <aaf15ebe-7442-2e25-d533-c40c2e2df8cb@zytor.com> (H. Peter Anvin's message of "Wed, 5 Jun 2019 13:46:48 -0700")
"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.
next prev parent reply other threads:[~2019-06-06 5:30 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 [this message]
2019-06-06 9:48 ` Daniel P. Berrangé
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=87ef47jn6n.fsf@dusky.pond.sub.org \
--to=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 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.