mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, JGross@suse.com,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	roger.pau@citrix.com
Subject: Re: [Xen-devel] [PATCH v3 4/9] xen/pvh: Bootstrap PVH guest
Date: Mon, 6 Feb 2017 15:37:28 -0500	[thread overview]
Message-ID: <64ef3143-4710-5714-e070-6a768c16b390@oracle.com> (raw)
In-Reply-To: <201702070358.H5rpxssJ%fengguang.wu@intel.com>

On 02/06/2017 02:29 PM, kbuild test robot wrote:
> Hi Boris,
>
> [auto build test WARNING on xen-tip/linux-next]
> [also build test WARNING on v4.10-rc7]
> [cannot apply to next-20170206]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url:    https://github.com/0day-ci/linux/commits/Boris-Ostrovsky/x86-boot-32-Convert-the-32-bit-pgtable-setup-code-from-assembly-to-C/20170207-014642
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git linux-next
> config: x86_64-randconfig-it0-02062149 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
>
> All warnings (new ones prefixed by >>):
>
>>> arch/x86/xen/xen-pvh.o: warning: objtool: pvh_start_xen()+0x57: call without frame pointer save/setup

pvh_start_xen() is never called so this needs

diff --git a/arch/x86/xen/xen-pvh.S b/arch/x86/xen/xen-pvh.S
index 512fda0..5e24671 100644
--- a/arch/x86/xen/xen-pvh.S
+++ b/arch/x86/xen/xen-pvh.S
@@ -133,7 +133,7 @@ ENTRY(pvh_start_xen)
 
        ljmp $__BOOT_CS, $_pa(startup_32)
 #endif
-ENDPROC(pvh_start_xen)
+END(pvh_start_xen)
 
        .section ".init.data","aw"
        .balign 8

(I don't think it's worth re-sending the series with just this change).

-boris

  reply	other threads:[~2017-02-06 20:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 17:00 [PATCH v3 0/9] PVH v2 support (domU) Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 1/9] x86/boot/32: Convert the 32-bit pgtable setup code from assembly to C Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 2/9] xen/x86: Remove PVH support Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 3/9] xen/pvh: Import PVH-related Xen public interfaces Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 4/9] xen/pvh: Bootstrap PVH guest Boris Ostrovsky
2017-02-06 19:29   ` [Xen-devel] " kbuild test robot
2017-02-06 20:37     ` Boris Ostrovsky [this message]
2017-02-07 10:05       ` Juergen Gross
2017-02-06 17:00 ` [PATCH v3 5/9] xen/pvh: Make sure we don't use ACPI_IRQ_MODEL_PIC for SCI Boris Ostrovsky
2017-02-07 10:19   ` Juergen Gross
2017-02-06 17:00 ` [PATCH v3 6/9] xen/pvh: Initialize grant table for PVH guests Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 7/9] xen/pvh: PVH guests always have PV devices Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 8/9] xen/pvh: Enable CPU hotplug Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 9/9] xen/pvh: Use Xen's emergency_restart op for PVH guests Boris Ostrovsky
2017-02-07 17:48 ` [PATCH v3 0/9] PVH v2 support (domU) Boris Ostrovsky

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=64ef3143-4710-5714-e070-6a768c16b390@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JGross@suse.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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

all inboxes | Powered by JetHome®