From: "Richard W.M. Jones" <rjones@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Marc Marí" <marc.mari.barcelo@gmail.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v6] Add optionrom compatible with fw_cfg DMA version
Date: Mon, 9 May 2016 17:12:45 +0100 [thread overview]
Message-ID: <20160509161245.GR1683@redhat.com> (raw)
In-Reply-To: <CAJSP0QU6reLA6VR6yFk25dWpg4ConQ-YhkYOeGH+VhPpbySaoA@mail.gmail.com>
On Mon, May 09, 2016 at 04:31:26PM +0100, Stefan Hajnoczi wrote:
> On Mon, May 9, 2016 at 2:24 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > On Mon, Apr 25, 2016 at 05:04:40PM +0100, Richard W.M. Jones wrote:
> >> v5 -> v6:
> >>
> >> - Changed the xen_load_linux assertion as suggested by Stefan.
> >>
> >> - I renamed the variables in get_e801_addr function, since the
> >> registers were really (16 bit 8086-style) AX, not EAX etc. Also I
> >> changed the GCC asm to make it a little bit more efficient. I
> >> verified by disassembling the function that GCC is still generating
> >> the right code after this change.
> >>
> >> - Re-tested with small (342K) libguestfs initramfs and with large
> >> (20M) Fedora initramfs, and works fine in both cases.
> >
> > No one has picked this up, so I have (for QEMU 2.7).
> >
> > Thanks, applied to my block tree:
> > https://github.com/stefanha/qemu/commits/block
>
> The bad news is this patch breaks the build under clang:
[...]
> The .code16gcc issue can probably be resolved with -m16 (which gcc
> 4.9+ also supports!). I haven't looked into the other issues though.
It looks as if the easiest way to get around this will be to use
gas instead of clang's integrated assembler, ie:
CFLAGS += -m16 -fno-integrated-as
However I have no idea if there are platforms we support which use
clang and require the integrated assembler instead of binutils.
Opinions on this?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
next prev parent reply other threads:[~2016-05-09 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 16:04 [Qemu-devel] [PATCH v6] Add optionrom compatible with fw_cfg DMA version Richard W.M. Jones
2016-04-25 16:04 ` Richard W.M. Jones
2016-05-08 18:57 ` Marc Marí
2016-04-26 9:59 ` Stefan Hajnoczi
2016-05-09 13:24 ` Stefan Hajnoczi
2016-05-09 15:31 ` Stefan Hajnoczi
2016-05-09 16:12 ` Richard W.M. Jones [this message]
2016-05-09 16:48 ` Richard W.M. Jones
2016-05-09 21:16 ` Laszlo Ersek
2016-05-09 21:37 ` Richard W.M. Jones
2016-05-10 17:19 ` Paolo Bonzini
2016-05-10 17:24 ` Paolo Bonzini
2016-05-10 17:36 ` Richard W.M. Jones
2016-05-10 19:00 ` Laszlo Ersek
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=20160509161245.GR1683@redhat.com \
--to=rjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marc.mari.barcelo@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
/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).