From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Maran Wilson <maran.wilson@oracle.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
George Kennedy <george.kennedy@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] pvh: add new PVH option rom
Date: Wed, 16 Jan 2019 22:17:15 +0100 [thread overview]
Message-ID: <bbec0a30-6b3e-6ba1-b439-7cc72999ea6b@redhat.com> (raw)
In-Reply-To: <00ff0393-1eab-9bc4-6370-0f959df9dca0@redhat.com>
On 16/01/19 19:31, Paolo Bonzini wrote:
> On 16/01/19 18:49, Stefano Garzarella wrote:
>> This patch series is based on "[PATCH v3 0/4] QEMU changes to do PVH boot" and
>> provides a PVH option rom that can be used with SeaBIOS to boot uncompressed
>> kernel using the x86/HVM direct boot ABI.
>>
>> Patches 1 and 2 are to prepare the PVH option rom, moving common functions in
>> the new headers. Patch 3 adds the new PVH option rom. Patch 4 uses it when we
>> are booting an uncompressed kernel using the x86/HVM direct boot ABI. Patch 5
>> adds the support of loading the initrd in the PVH option rom.
>>
>> Based-on: <1547554687-12687-1-git-send-email-liam.merwick@oracle.com>
>
> I get this:
>
> CC optionrom/pvh_main.o
> /tmp/ccoel69H.s: Assembler messages:
> /tmp/ccoel69H.s:171: Error: attempt to move .org backwards
>
> when applying this series on CentOS 7.
Oops, the issue was actaually in linux_dma - I was confused by make -j
reordering the output. The fix is trivial
--- a/pc-bios/optionrom/linuxboot_dma.c
+++ b/pc-bios/optionrom/linuxboot_dma.c
@@ -20,10 +20,6 @@
* Richard W.M. Jones <rjones@redhat.com>
*/
-#include <stdint.h>
-#include "optrom.h"
-#include "optrom_fw_cfg.h"
-
asm(
".text\n"
".global _start\n"
@@ -62,6 +58,10 @@ asm(
" jmp load_kernel\n"
);
+#include <stdint.h>
+#include "optrom.h"
+#include "optrom_fw_cfg.h"
+
static inline void set_es(void *addr)
{
uint32_t seg = (uint32_t)addr >> 4;
Also, the $? in the new rule should be $^. I wouldn't use a pattern
rule for that, writing it explicitly as "pvh.img: pvh.S pvh_main.c"
Thanks,
Paolo
next prev parent reply other threads:[~2019-01-16 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 17:49 [Qemu-devel] [PATCH v3 0/5] pvh: add new PVH option rom Stefano Garzarella
2019-01-16 17:49 ` [Qemu-devel] [PATCH v3 1/5] linuxboot_dma: remove duplicate definitions of FW_CFG Stefano Garzarella
2019-01-16 17:49 ` [Qemu-devel] [PATCH v3 2/5] linuxboot_dma: move common functions in a new header Stefano Garzarella
2019-01-16 17:49 ` [Qemu-devel] [PATCH v3 3/5] optionrom: add new PVH option rom Stefano Garzarella
2019-01-16 17:49 ` [Qemu-devel] [PATCH v3 4/5] hw/i386/pc: use " Stefano Garzarella
2019-01-16 17:49 ` [Qemu-devel] [PATCH v3 5/5] optionrom/pvh: load initrd from fw_cfg Stefano Garzarella
2019-01-16 18:31 ` [Qemu-devel] [PATCH v3 0/5] pvh: add new PVH option rom Paolo Bonzini
2019-01-16 21:17 ` Paolo Bonzini [this message]
2019-01-17 7:50 ` Stefano Garzarella
2019-01-17 10:31 ` Paolo Bonzini
2019-01-17 10:36 ` Stefano Garzarella
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=bbec0a30-6b3e-6ba1-b439-7cc72999ea6b@redhat.com \
--to=pbonzini@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ehabkost@redhat.com \
--cc=george.kennedy@oracle.com \
--cc=maran.wilson@oracle.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sgarzare@redhat.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).