From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
xen-devel@lists.xensource.com, konrad.wilk@oracle.com,
david.vrabel@citrix.com, boris.ostrovsky@oracle.com,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
mmarek@suse.cz, linux-kbuild@vger.kernel.org
Subject: Re: [Xen-devel] [Patch V2 4/4] xen: use generated hypercall symbols in arch/x86/xen/xen-head.S
Date: Wed, 17 Dec 2014 10:27:17 +0000 [thread overview]
Message-ID: <54915A85.10403@citrix.com> (raw)
In-Reply-To: <1418809838-14123-5-git-send-email-jgross@suse.com>
On 17/12/14 09:50, Juergen Gross wrote:
> Instead of manually list each hypercall in arch/x86/xen/xen-head.S
> use the auto generated symbol list.
>
> This also corrects the wrong address of xen_hypercall_mca which was
> located 32 bytes higher than it should.
>
> Symbol addresses have been verified to match the correct ones via
> objdump output.
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
David
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>, <xen-devel@lists.xensource.com>,
<konrad.wilk@oracle.com>, <david.vrabel@citrix.com>,
<boris.ostrovsky@oracle.com>, <tglx@linutronix.de>,
<mingo@redhat.com>, <hpa@zytor.com>, <mmarek@suse.cz>,
<linux-kbuild@vger.kernel.org>
Subject: Re: [Xen-devel] [Patch V2 4/4] xen: use generated hypercall symbols in arch/x86/xen/xen-head.S
Date: Wed, 17 Dec 2014 10:27:17 +0000 [thread overview]
Message-ID: <54915A85.10403@citrix.com> (raw)
In-Reply-To: <1418809838-14123-5-git-send-email-jgross@suse.com>
On 17/12/14 09:50, Juergen Gross wrote:
> Instead of manually list each hypercall in arch/x86/xen/xen-head.S
> use the auto generated symbol list.
>
> This also corrects the wrong address of xen_hypercall_mca which was
> located 32 bytes higher than it should.
>
> Symbol addresses have been verified to match the correct ones via
> objdump output.
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
David
next prev parent reply other threads:[~2014-12-17 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 9:50 [Patch V2 0/4] xen: auto-generate symbols for xen hypercalls Juergen Gross
2014-12-17 9:50 ` [Patch V2 1/4] xen: build infrastructure for generating hypercall depending symbols Juergen Gross
2014-12-17 10:26 ` [Xen-devel] " David Vrabel
2014-12-17 10:26 ` David Vrabel
2014-12-17 9:50 ` [Patch V2 2/4] xen: synchronize include/xen/interface/xen.h with xen Juergen Gross
2014-12-17 9:50 ` [Patch V2 3/4] xen: use generated hypervisor symbols in arch/x86/xen/trace.c Juergen Gross
2014-12-17 9:50 ` [Patch V2 4/4] xen: use generated hypercall symbols in arch/x86/xen/xen-head.S Juergen Gross
2014-12-17 10:27 ` David Vrabel [this message]
2014-12-17 10:27 ` [Xen-devel] " David Vrabel
2015-01-19 5:07 ` [Patch V2 0/4] xen: auto-generate symbols for xen hypercalls Juergen Gross
2015-01-19 15:42 ` David Vrabel
2015-01-19 15:42 ` David Vrabel
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=54915A85.10403@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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 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.